measurement and automation database connection error

[kpenney]

Hello,

I'm wondering if anyone has had this problem.  I was running a Labview program one evening and everything was fine.  I shut down the computer when I left, and the next morning when I booted up, the labview on my computer isn't communicating with the DAQ chassis. 

When I open up MAX, I am getting the database connection error described here.  http://digital.ni.com/public.nsf/allkb/B9107A7F281F9B408625720B0078E5A8   I appear to have the problem described in #2, where the NI Configuration Manager starts but immediately stops.  However, repairing the program didn't fix it, and my firewall settings haven't changed.  Has anyone had and solved this problem?   

FYI, I'm running labview 8.2 on a very old testing computer without internet access and updates. 

[kosist90]

Did you try to reset NI MAX database, as described here - http://digital.ni.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9? If no, they try it, usually it helps.

Sincerely, kosist90

[Dieboy]

Any updates on this? We are experiencing the exact same problem.

We did reset the database, twice. Fully removed NI max and everything associated. Reinstalled *everything. Exact same issue.

[AvatarAang]

Is NI Configuration Manager still not showing a status other than Started? Is the Startup Type set to Automatic?

Did you get an antivirus or internet security program that has a firewall of its own?

What version of MAX are you using? When you reinstalled, did you configure everything from scratch or did you import the configuration?

[MattBradley]

Unfortunately, I had the same experience.  I went through everything with tech support, and nothing fixed it, including reinstalling it.  I had to start over on a new computer and rewrite the program, though some of this may have been due to the fact it was a very old computer and license.  

Best of luck.

[Dieboy]

Start up is set to automatic.  Also set to restart on any failure, 1st 2nd or 3rd.

Firewall is disabled completely. No antivirus firewall.

No changes on the PC what so ever, just stopped working over the weekend.

What I have found is that the NI Loader service was not running.  I started that, and the configuration manager started by itself, and kept running instead of just failing over and over again.

After I noticed that, I set both services to a delayed start.  Logged off/in/off/in shutdown a few times.  It started and stayed started each time.

I have not the slightest idea on what actually caused it.  The PC is solely used by a few researchers. I tried tracking down if anything had changed/crashed/updated in the system event log, but saw really nothing out of the ordinary.

So its a complete mystery.

We are using a PC provided by a motion capture company and their hardware, with an NI dat card for the controller.  NI Max is version 16.0.1? We wiped the configuration and the services were still not working. Until as mentioned above, I kicked off the NI Loader service (can't remember if that is the correct syntax for that service) and it all worked out.

I'd like to mark this as fixed, but i'm actually not positive on what caused it, and hesitant that my fix will work for an extended period of time.  I'd say this is something to try for sure, but not tried and true solution.  If this continues to work in the long term i will drop by and mark it as fixed. 

Disclaimer:  I'm solely IT, I don't use this software daily, and the blow off to firewall/antivirus irritates me to no end, which the NI support kept telling our researchers when they were calling for support, even after I sent them screen shots to prove the firewall is disabled and the AV is not bothering anything.

[AvatarAang]

Very, very mysterious. I saw some whispers on another forum post hinting that a registry setting becoming corrupted could cause NI Device Loader to fail at reboot, but in that case, the person was seeing different errors from you (1067 process termination), so I don't feel confident in naming it a root cause. I also don't see how the registry settings would have become corrupt without a crash or upgrade.

I'm interested to hear what happens on the next reboot of the computer. Hopefully NI Device Loader will launch automatically without incident.

Sorry about your experience with NI support. That sounds frustrating, but I can see how it would happen... Think of the number of times someone probably assured that the firewall wasn't causing problems and it turned out to be the issue. If you end up calling in the future, make sure you mention early on that you are an IT professional. Hopefully that gets the conversation moving away from, "Can you go to Windows Firewall from the Control Panel?" as soon as possible! 

Take care, good luck, and let us know what happens!

[Dieboy]

Reboots are seemingly fine with the Loader and config service set for a delayed start.

No worries about the firewall/AV deal, I know the scenario you suggest happens frequently.  I did provide our researchers screen shots to show the help desk, but they still were insistent it was a windows update/firewall issue, so that should have been taken into consideration.  The PC is air gaped, so no updates/firewall rules.

I will keep this updated over the next few weeks if something changes.

So in short:

1. Wiped database. Twice.

2. No luck, see #3.

3. uninstalled everything NI related.

4. reinstalled NI packages (NI Max/Drivers/etc).

5. Exact same error.

6. Delay start loader and config services.

7. Tested good.

I'm actually going to offload this software support to our analyst team, as they have more time to learn it and its functionality, but as mentioned I will stop by and post even if its working on the outcome after a few weeks. Post it is already on my monitor to remind myself.