DSC Saving Shared Variables to Library

[Kyle Smith]

I'm guessing this is a bug (LV/DSC 2009 SP1), but I wanted to see if anyone else had experienced this or had a workaround.

I'd like to make changes to the logging state of some shared variables programmatically and be able to save the changes. When I use the SharedVariablestoLib.vi function on a simple test library it works. However when I use it on my actual library I get the following (testing vi I'm using is Untitled 2):

Error Code 1

Invoke Node in PRC_SVsToLib.vi->PRC_DumpSharedVariables.vi->NI_DSC.lvlib:SharedVariablesToLib.vi->Untitled 2

Possible reason(s):

LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488:  Command requires GPIB Controller to be Controller-In-Charge.

I think the culprit is that my library has variables organized into virtual folders. Any thoughts?

Thanks,

Kyle

[Bertha]

I had a similar problem and I the following post helped

http://forums.ni.com/ni/board/message?board.id=170&message.id=455083&query.id=1130174#M455083

[Kyle Smith]

I fail to see how that's related beyond the fact that it involves the shared variable engine...

[Ben_S]

Kyle Smith,

I tested your theory of the virtual folders causing the problem but wasn't able to get the error message you are seeing. Can you cause it with virtual folders?

Also, the error message says, "if the input is a path, the path might contain a character not allowed by the OS such as ? or @". Are you using any characters that might make the OS unhappy? Also, how big is the file path? I've seen similar errors happen when a file path was very very long. Try moving your project to a really short filepath location such as C:\PROJECT\.

[Kyle Smith]

I can pretty well cause the problem with virtual folders. I have attached the vi I'm using to change the logging state and save the changes as well as the two libraries I used for testing purposes.

What I did to test:

-Disabled logging on both variables in both libraries.

-Saved, undeployed, and redeployed both libraries.

-Ran my log enabling vi on each library. It ran on Test 2 (no folders) fine. On Test 3 (includes a folder) it threw the same error as above.

-At this point I tested and both libraries were logging both variables.

-Looking at the variable properties in the project, both Test 2 variables showed Enable Logging checked. Neither Test 3 variable did.

-Exited the project. Test 3 had unsaved changes so I saved it.

-Re-opened the project and examined the variables, both Test 2 variables showed Enable Logging as before. In Test3 the root variable showed Enable Logging but the variable in the folder did not.

-Undeployed and redeployed both libraries.

-Confirmed that both Test 2 variables and only the root Test 3 variable were logging.