measurement and automation usb recognize

[Seth_B.]

I'm still looking into this.  I'll post back when I have a recommendation.

[Seth_B.]

I'm going to send you a private message regarding an internal tool we use that we don't generally release.

[ratkindler1]

I ran the program as an administrator and rebooted but the problem is still there.  The DAQ is not showing up in MAX and as before, adding a simulated DAQ gives an error on the self-test saying the device is not present: error -88705

[Seth_B.]

Well this is frustrating...

Can you check the status of the "NI Device Loader" and "National Instruments mDNS Responder" services?

[ratkindler1]

The NI Device Loader is off and its startup type is set to Automatic.  If I start it and then refresh the view, it's immediately shut off.  The National Instruments mDNS Responder is "started" and its startup type is also on Automatic.

[Seth_B.]

Okay, I've been doing some research on this and these symptoms don't add up right.  Lets get try the following to see if we can better isolate where the issue is occuring:

1. Rename the mxdiag.ini file to mxdiag.bak in this directory: C:\ProgramData\National Instruments\MAX\Data
2. Copy the attached mxdiag.ini to that directory and restart their system
3. Navigate to MAX and see if your device shows up
4. If it doesn't, verify that NI Device Loader isn't running
5. If it isn't, post back with the C:\ProgramData\National Instruments\MAX\Logs directory zipped up and attached.
6. Delete the new mxdiag.ini file and rename the existing one back to mxdiag.ini

Thanks, and apologies for the trouble.

[ratkindler1]

I did as instructed and the DAQ still isn't recognized.  The device loader isn't running and won't stay started.  I've attached a zip file with the logs directory.

I also installed NI-MAX on my friend's laptop running Windows 7 and it recognized the DAQ without any trouble.  I'm going to try his again later in the week to see if it's consistent.

[Seth_B.]

Hello ratkindler1,

I apologize for the delay.  We've been looking through the logs and the technical report that you sent us and trying to find the root cause of this issue.  It's possible this error is being thrown because the NI Service Locator service is also having issues.  Could you open a new browser window and type "http://localhost:3580/dumpinfo?" into the address bar?  If the request works, you should see a table of requested connections.  If it doesn't, there may be an issue with NI Service Locator.  If it doesn't work, try issuing the command "net start nisvcloc" in a command prompt window, running as administrator.

Thank you for your continued patience.

[ratkindler1]

I've attached a screen capture of the requested connections.  The command prompt response says that the services has already been started.

[Seth_B.]

Hello ratkindler1,

The only thing that we can think of that could be causing this is a firewall or antivirus program blocking ports 51700, 57616, or 62602.  Can you confirm that your firewall isn't taking any action on these ports?