database connection error

[wdarin]

I have been having problems with the connection to the database when trying to load my VI logger task.

Occasionally when starting up I receive a runtime error that causes MAX to "terminate in an unusual way". This has happened often since we installed the software and is never a problem except on initial startup. Once I receive this error I restart MAX and everything works fine. Lately however, I have been getting a MAX database connection error on subsequent attempts to load my VI logger task. This problem will go away after 15 minutes or so, and everything will load fine. Does this have something to do with a possible ENET device that is not connected? We have never used the software while connected to the internet, but it was most likely installed while connected. If there is an ENET device referenced, how can I remove this? or if this could be caused by something else, what could that be?

Any help would be appreciated

Wes

[NI-Bongo]

Hi Wes,

Definitely take a look at #3 on this list of causes of the MAX Database Connection Error, see this KnowledgeBase article:

Why Do I Get a Measurement & Automation Explorer (MAX) Database Connection Error?
http://digital.ni.com/public.nsf/allkb/B9107A7F281F9B408625720B0078E5A8?OpenDocument

The ENET device is probably the cause.  You should be able to remove it from your MAX configuration by right-clicking on it and selecting Delete.

If the VI Logger Task has a reference to it, delete it there as well.

[wdarin]

Under the devices and interfaces tab in MAX the only thing I have is the SCC Carrier. If there is an ENET device would it be under this tab, and what would it be called?

If it would not be under this tab, then where?

Wes

[NI-Bongo]

Hi Wes,

If the instrument were still present, it would be under Devices and Interfaces in MAX.  It would be shown as in the attached jpg.

Do you have a VI Logger Task that references an ENET device?  This could be a reason for the error.

If not, your database may have been corrupted.  You can try solution 4 from the KnowledgeBase article referenced above to remove the corruption:

How Do I Recover From MAX Database Corruption?
http://digital.ni.com/public.nsf/websearch/86256F0E001DA9FF86256FFD005B827C?OpenDocument

This would delete your configuration in MAX, but should fix the problem.  If your configuration is not extensive and is easily recreateable, this can be a quick solution.