Shared Variable Engine Error Handling

[Maryam]

I have a HMI system that connects through shared variables to an OPC Server. I have encountered problems with Variable Engine, and a problem with tagger which I don't know anything about. I checked OPC Server to see  ifit's installed properly and the items status is good, and the server's connected. I tried to restart the shared variable engine service but it doesn't reply. When I monitor variables there's no connection. I used Alarm&Event query.vi in my application and then encountering tagger error, server connection failed. How could I handle these errors? 

I appreciate any help.

[Stuart_R]

Can you confirm that the Shared Variables that you are using are Bound to the OPC items that you are trying to use via the variables property page (screenshots may help)?

You mention 'tagger' errors - can you be more specific and mention at what point this occured and the error message/code that you received? Has the Shared Variable's library been deployed? Please provide as much information as possible.

Thanks,

Stuart

[Maryam]

I've created Bindings to OPC items I want to read/write through an OPC Client instance, bound front panel objects to these shared variables, deployed the entire library and run the VI.

All the connections were true (green PSP-LED. through the Monitor Variables all the variables and OPC items of client instance had good quality and right value.

All the variables were configured to log data and alarms.

Configuring the library for a data base through it's DSCsettings:database, I used Historical VIs (Read trace,… ) to retrieve data from citadel and they worked properly. I used Alarm & Event Query.vi to retrieve alarms from citadel, the VI encountered this Error:

        "Some part of tagger encountered a problem and should be closed"

After that the entire connections failed (PSP-LEDs goes red) and the I/O Engine couldn't be restarted and shows this Error:

             "Could not stop the National Instruments Variable Engine Service on local computer.

              Error 1053: the service did not respond to the start or control request in a timely fashion."

And the variable monitor dosen't show any library and variables.

[Maryam]

My Shared Variable Engine doesn't respond anymore, and when the windows starts the error dialog box which says: " part of tagger encountered a problem and need to close" always is showing.   

[jdr_ni]

From you description, it sounds like running the Alarm & Event Query VI is causing a crash in the Network Variable Engine. I don't particularly understand why this would occur, as the two components should be unrelated.

Can you send us some more information? In particular, when the "part of tagger has encountered a problem" dialog appears, click the "click here" link to display additional information on the crash. Please post all the information in the error signature section. A screenshot would be ideal.

Also take a look at the system event log: Start>>Settings>>Control Panel>>Administrative Tools>>Event Viewer. Look in the Application section. If there are any Error entries for the NI Variable Engine, please post their contents.

You can also enable release assertions in the variable engine to get more debugging information. In the registry, create a DWORD value in the key HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\DSC Shared named "ShowReleaseAsserts" with a value of 1.

Try running the Alarm and Event Query VI without starting the Network Variable Engine. Does the query succeed?

Deleting or detaching your Citadel databases using MAX may allow you to restart the variable engine and continue working.

[Maryam]

It appears my problem was related to my Zone Alarm Security, and part of tagger was encountered a blocking situation from zone alarm. I just raised the trust level and access mode for "Part of Tagger" in program control of Zone Alarm Security, and it sounds my problem is solved.  

Message Edited by Maryam on 05-21-2006 01:57 AM