LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Network Variable: Failed to commit writes to the configuration database

I seem to get this error from the Network Variable Library kind of sporadically, and I'm wondering if anyone knows how I can fix whatever problem I have.

 

The error I get is:

 

NI Varaible Engine: Error: Failed to commit writes to the configuration database : Operation timed out

 

The error doesn't cause a break on Library error to occur, and it only seems to happen when I first start initializing Network Variable things.

 

Thanks for any advice,

Kevin

0 Kudos
Message 1 of 5
(3,312 Views)

Kevin,

 

Just to confirm the issue, every time you initalize network variable items, you are getting these timeout errors? Is it intermittent, or consistent every time we try to access these? 

 

My first guess would be to try to stop and start several of the NI services. Im not 100% sure which of them handles the network variables, so I would try them and see if one or several are not stopping/restarting properly. If that is the case, we can defintely keep troubleshooting from there.

 

Regards,

 

Kyle Mozdzyn

Applications Engineering

National Instruments

Regards,

Kyle M.
Applications Engineering
National Instruments
0 Kudos
Message 2 of 5
(3,296 Views)

I could've given more details. The problem happens on an RT. It happens inconsistently, but it seems like when it happens it'll take like 2-3 restarts and retries for it to work.

0 Kudos
Message 3 of 5
(3,290 Views)

Kevin,

 

  1. Have you installed the Network Variable Engine on the RT target?
  2. Are you running this application on startup?
  3. If it is not running as a startup app, could you debug the app through CVI and provide a code snippet of the context of the failure? If you are running it as a startup, could you add logging to your application to identify where the application is failing and again post the code snippet?
National Instruments
0 Kudos
Message 4 of 5
(3,264 Views)

1. Yes

2. No

3. I logging and I'm running it in debug mode with break on library errors enabled. The thing is, it doesn't break on the error and it doesn't get logged because whatever function that causes it doesn't return with a negative number. Every CNV function I call, I have my log function around it that looks for a return value of less than 0. It only happens every so often so I haven't caught it happening while stepping through.

0 Kudos
Message 5 of 5
(3,262 Views)