DSC ERROR: "Citadel Access Denied, data will be logged to Default_database error" when programmatically creating database/shared variable.

[Jed394]

I'm am programmatically creating a database and group of shared variable, however, i get an "Citadel Access Denied, Data will be logged in Default_database" error. The database is being created i can see it in NI Measurement and Automation Explorer and the variable are being deployed, i can see them in the distributed system manager, however, citadel seems unable to write to this new database.  Do i have to configure some sort of access to it?  Currently the work flow is to:

1)create new database,

2)create a new process, 

3)Configure Process Log state

4)Enable Alarm and Data Logging on Process

5) Generate Shared Variables and associated alarms

6) Deploy shared variables.

There is an additional strange behavior, in that if i deploy a separate library after configuring the setup within the library-> DSC Settings: Data Access to point at the same database, then both my programmatically created shared variables and this other library's variables are logged in the database and the problem seems to disappear.  I'm wondering if there i some step i am omitting that happens when you deploy my library of Shared Variables.  I have not used the DSC module much and i based my variable/database setup on an example.

I have attached my code for creating the database and shared variables.  Thanks

[Jeff-P]

Hi Jed394,

Are you attempting to deploy these shared variables on a computer that you have administrator access on? 

Also what version of LabVIEW are you using and in MAX, what version of Citadel?

I am looking more into this error to see what could be causing it.

Regards,

[Jed394]

Jeff, 

Thanks for taking the time to respond.  I am using LV 2011, and Citadel V5.  I am able to programatically deploy the shared variable, i do have administrator access on this computer.  I am able to write to them programatically to them as well from other VI's and the database is being created. I can log to it using a non programmatic method. 

A little more background.  I had done some research to try to address this problem, even going so far as to add Full Access Writes for the "Network Service", within windows folder properties of my database storage folder, as i had read that the citadel services uses this and it would need access.  This did not solve the problem.  

I really was unable to identify this error until i went to the Distributed System Manager: View -> Alarm & Events and begin tracking my newly created shared variable process.  It was there that i finally was able to track down this citadel access denied error.  Like i mentioned, if i deploy a separate library, and log to the database using the database settings of that library, and then run  my VI, the citadel database then has access.  I'm thinking it has to do with the way I'm creating the database process.

One more note, I was using the evaluation version of the DSC, as I was trying to figure out if the expense of this module would be beneficial for a system logging application we are developing for a series of multiple cRIO's  that are all recording data.  We wanted an easy way to create a database and this seemed to do the trick. With that said, I believe I'm down to 1 day left on my evaluation, so I'm not sure if I'll be able to give much more feedback unless we purchase the module.   Thanks.