error 1950679035

[ramji]

Dear All ,

Anybody comeacross   of the attachment error .

whenever iam monitoring the value iam getting this error . any solution for this problem ... please !!!!!!!!

check it out the attachment .

Regards,

Ramji

[MattP]

Hello Ramji,

The error described in the screenshot you sent is fairly common, so I'm curious to know more details about when you encounter it.  Does it only happen when using the monitor variables window, or does it also occur when you run the actual VI?  If you attach an indicator on the shared variable in question, does it show any errors when you try to read from it?  You should also verify that you can read any shared variable at all through the Variable Monitor - hitting this error regardless of variable could point to a firewall problem.

If you have a firewall enabled, I recommend following the steps outlined in this KnowledgeBase Article to allow exceptions for the necessary components of the shared variable engine, as this error often is associated with the shared variable engine being blocked by the Windows Firewall.

[DG3005]

Hello Matt,

I have just checked my server , and found that there is no windows firewall in the server.

only when iam writing to a variable in the monitor , iam receiving this error .

any other ways... please....

Regards,

Ramji .

[MattP]

Hi Ramji,

Based on your screenshot, I assume the variable that is causing the issue is 01_ichg_sheetwidth, and then only when you are using the variable monitor to write data to the variable.  Does the same behavior happen with any other variable, or just this one?  Is this variable being updated if you do not explicitly write to it?  If you haven't already, verify that you can write to this variable in a VI and read back the value in the same VI, and also wire an indicator to the error terminal of the shared variable for each operation. 

If this is the only variable affected, is there anything unique about this variable (i.e., defined in a different library, communicating to a different OPC source, etc)?  If no other variable is affected, you may also consider deleting and recreating the variable in the library, as it is possible that it became corrupted in the library itself.

[ramji]

HEllo mat ,

this error is happend only to the read varible .

this error is coming for all variable.

now i have another doubt ....

in LV 7.1 .scf file exists .... which ever .vi ur running  and if the vi is having tagname which exists in the tunning .scf file ... then the vi will get a link automatically to this .scf file .

but same thing is not happening in LV 8.0 when ever iam changing the .lvlib file ( just renaming the .lvlib file ) then i have to manually link each variable to this existing .lvlib ...

wHY ... OR ISIT ANY WAY TO SHOW THIS LINK TO NEW SHARED VARABLE..

itis confussing for you .. please let me know .

Regards,

VBR

[MattP]

Hello Ramji,

LabVIEW DSC 7.1 was based off of scf files, and the closest equivalent to these in LV DSC 8 is the lvlib file.  The key thing to remember when working with DSC 8 is that it is a project-based environment - it's designed so that each project will have one or more .lvlib's containing all of the variables (tags) with which you want to communicate, rather than a single loaded .scf file that affects all VI's on your machine.  So, unless you explicitly load in the same saved library file into your projects, the variable listings in each project will be completely independent of each other.  If you have a saved library, you can add the library to any new project that you like, and it will then be able to communicate with the same data items as your other projects, and give you similar behavior to what you might expect from DSC 7.1.

[ramji]

Hello Matt ,

yes , i agree with your answer ....

but my problem is different .

iam having two vi ..... each vi is connected to some 50 shared variables .

when iam starting the project ... everything worked fine and program is linked with correct shared variable ....

now the problem started ....

when i changed the name of sharedvariable .lvlib  file to some xxxx.lvlib file .

and when iam running the vi ...... tthis shared variable is not getting linked with xxxx.lvlib file .

so , i can overcome this only by again double clicking each shared variable for all the variable in the program ...... which is not correct method 🙂

itis anyway that vi can recognise this xxxx.lvlib and get linked to it.

Sorry to bother you ... i know u can solve my problem.

Regards,

Ramji .

[REM1]

---

@ramji wrote:

Hello Matt ,

yes , i agree with your answer ....

but my problem is different .

iam having two vi ..... each vi is connected to some 50 shared variables .

when iam starting the project ... everything worked fine and program is linked with correct shared variable ....

now the problem started ....

when i changed the name of sharedvariable .lvlib  file to some xxxx.lvlib file .

and when iam running the vi ...... tthis shared variable is not getting linked with xxxx.lvlib file .

so , i can overcome this only by again double clicking each shared variable for all the variable in the program ...... which is not correct method 🙂

itis anyway that vi can recognise this xxxx.lvlib and get linked to it.

Sorry to bother you ... i know u can solve my problem.

Regards,

Ramji .

---

Greetings Ramji,

I am not clear about a couple things.  Are you renaming the .lvlib inside the project window or on the file system?  Is the VI inside the same project as the .lvlib?

[ramji]

Hello Robert

actually i have changed the path of .lvlib ....

but in the project tree i undeployed the old .lvlib and added new .lvlib .....and deployed it it deployed successfully ... but inside the program the shared variable is not getting ref from new .lvlib file .... its still refering the old one .....

Regardxs,

Ramji.

[MattP]

Hi Ramji,

You mentioned that you undeployed the old library, but have you removed it from the project?  The shared variables in your project created from that library will not relink to the new library if the original library still exists in the project.