Can't connect to alarm database

[Ben]

A BridgeVIEW app that was ported to LV 6 DSC then to LV 8.2 ran well for years without issues.

After updating the machines to new hardware and installing a government approved Windows image with all of the associated lock-downs and restrictions would fail to query a tag history.

Investigation using MAX to try to view the history was giving me a "failed to map shared memory" error. If I wen through a song and dance to shutdown the tag engine etc etc, I could see the tag history.

Giving the operator Admin on that machine cleared up that problem.

The other problem that the customer gave up on trying to narrow down was that when connected to the government network the application would lock-up trying to write new tag values. machines that were physically disconnected from the network did NOT lock-up. As far as I was able to X-shoot there were entries in the sucurity log indicating that privledges were being adjusted.

Due to the $$$ involved, the customer changed their operating procedure to include pulling the network cable before a test started and plugging it back in when they were done.

Ben

[Charlie Silver]

Thanks for the detail, Ben.  I am an administrator on this computer, so I don't think that's the problem in my case.  It definitely seems to be related to the 2 SQL logins, "NT AUTHORITY\SYSTEM" and "nicitadeluser".

I wish I could find somebody at NI with some more SQL experience than I've got...

[Ben]

If you have admin then this tool may help you.

NI Support pointed me at this tool to help with my situation. I believe it was developed by some compant that MS swallowed up and they offer it as tool for getting at the system internals. Once you set set-up filters to reduce the singal to noise ratio of the screen updates, it will show most of the interactions happneing inside the OS including file I/O as well as networks etc.

Not sure if it will help you, but it what little I have to offer,

Your partner in wire,

Ben