Can't connect to alarm database

[Charlie Silver]

My DSC alarm query returns error 1967386594: HIST_RunAlarmQueryCORE.vi, Citadel:  (Hex 0x8ABC101E) Could not connect to alarm and events database.

When I try to view the alarm in the MAX Citadel viewer it says "Reading Alarms/Events failed", with no further information.

The properties of the database show that there is data in there.

Is this a security problem?   I've played around extensively with the "DSC Settings: Data Access" settings and the Domain Account Manager settings, but nothing seems to work.  I'm having a really difficult time migrating from DSC7.1 to DSC8.6, and any assistance would here be appreciated.  Thanks,

Charlie

[Ben_S]

Charlie Silver,

Hello! I have found a few reported cases of this error and in all them the final resolution was to repair or reinstall the software. I know this isn't the most desired resolution, but give a software repair a shot and see what happens. Also, you could try installing all the software on a new/second computer and see if your code gives you the same error there.

[Ben]

There was a utility available to convert LV 7 to LV * DSC. Did you run it to convert your DB?

Ben

[Ben_S]

There is a document on our website that talks about Migrating from LabVIEW DSC 7.1 to 8.0

[Charlie Silver]

I've created a new db in 8.6, so I don't think that's the problem.

I uninstalled DSC8.6 and all SQL server components and reinstalled everything.  Same problem!

[Ben_S]

Sorry to hear that! Have you been able to try it on a new/different computer?

[Ben]

---

Charlie Silver wrote:

I've created a new db in 8.6, so I don't think that's the problem.

I uninstalled DSC8.6 and all SQL server components and reinstalled everything.  Same problem!

---

Check the properties of the llb for your tags and verify the seting for alram logging and the file spec etc.

Ben

[Charlie Silver]

I've checked and re-checked the properties - I'm positive they're all set correctly to enable alarm logging.  I can tell the citadel database is filling up because the size increases, and it's generating new files.  It doesn't seem to be a logging problem - it seems to be related to accessing the database.

The Windows event viewer records errors relating to SQL login for accounts "nicitadeluser" and "NT AUTHORITY/SYSTEM".  I can understand in some general way that there's a SQL account security problem going on here, but I'm not familiar enough with SQL to troubleshoot this.

Thanks.

[Ben]

After just been through a very painful DSC logging experience myself...

Get an IT person to login with full privledges and try it again.

Ben

[Charlie Silver]

I'm one step away from that, but that takes some time and $. 

Can you share any specific advice from the experience?  What resolved your connectivity problems?  Was your problem on the SQL end or the LV end?  Did you have to change any SQL sever settings, or did it turn out to be a Windows problem?  Thanks.