measurement and automation usb recognize

[ratkindler1]

Spoke too soon.  I rebooted and now it's not working again.  Simulated devices don't work and my DAQ is not recognized even when MAX is run as administrator.

[Seth_B.]

What type of antivirus software are you using?  It's possible that it's deciding to quarantine something that NI-DAQmx and MAX needs.  Can you confirm that you have a C:\Program Files\National Instruments\MAX\Data Dictionaries and can you create a Technical Report in MAX?  To create the report, go to File » Create Report and select "Technical Report".

[ratkindler1]

I was able to create a technical report in MAX.  I'm using Microsoft Security Essentials and Comodo firewall/anti-malware.  Neither of these show any quarantine or blocking of anything obviously NI related.

The first time I had rebuilt the driver database according to the instructions in the previous post, it was able to recognize the DAQ.  I went through several reboot cycles to make sure this was reliable, and after about 5 reboots it stopped recognizing the DAQ.  The windows device manager previously showed the DAQ under Data Acquisition Devices, but now shows USB Firmware Loader instead. 

I don't know where else to go with this.

Thanks for helping me with this problem, by the way. 

[Seth_B.]

Could you type "services.msc" into the search box in the Windows Start Menu and hit Enter.  When the Services window comes up, check the status of the NI Device Loader service, and if it isn't started, try to start it.

[ratkindler1]

The service was not running and the Startup Type was set to Automatic.  I started it and plugged in the DAQ but it still isn't being seen.  I also rebooted the computer and started the service again, but still nothing.

[ratkindler1]

I just noticed that the NI Device Loader service stops immediately after I start it.  It won't stay on.  Is that normal?

[Seth_B.]

Let's see if the Windows Event View has any information we can use to determine why this service is stopping.  In the search box in the Windows Start Menu, please enter "eventvwr.msc" and hit Enter.  In the Overview & Summary box, look in the Summary of Administrative Events to see if there are any errors or warnings related to NI Device Monitor.

[ratkindler1]

There were no errors or warnings directly related to the device loader or monitor.  There were several errors with the NI Variable Engine and nipalu.  The Variable Engine seemed to have 3 recurring errors: 

NI Variable Engine:

ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.

Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318

Failed to initialize PSP XT Server

nipalu:  there are several errors including this one...

[nidevldu] [[nidevldu]] Fatal: p:\Measurements\Infrastructure\devld\trunk\1.12\source\nidevld\tDeviceLoader.cpp:271 - Could not connect to MXS. MAX configuration files may be corrupt!

I noticed that there is a recurring error with the Service Control Manager related to the NI Device Loader.  "The NI Device Loader service terminated unexpectedly. "

[Seth_B.]

Could you attach the Technical Report you created earlier?

Also, could you look in the Control Panel » User Accounts » Manage User Accounts window to see what group your user account is in?

[ratkindler1]

My account is an Administrator account.  I've attached the MAX report.