NI 9171 / 9174 / 9211not recognized on one Windows 7 system (works on others)

[mhweber]

My platform is 64-bit Windows 7 with NI-DAQmx 9.5.1. I am using the ANSI C API, and sometimes running MAX to check for device recognition. Devices include an NI 9171, 9174, and 9211.

I have two systems working with no problem, but on my third system, the devices are not recognized by the NI-DAQmx drivers. A few notes:

• The cDAQ device will show up in Windows Device Manager under the Data Acquisition Devices node with the NI logo
• No devices show up in MAX
• Regardless of whether or not devices are plugged, a call to the C API DAQmxGetSysDevNames hangs for 90 seconds and then return no results.

The same devices work on my first two 64-bit Windows 7 with NI-DAQmx 9.5.1 systems. I have tried un-installing / re-installing the NI-DAQmx drivers multiple times.

I have searched for trouble shooting tips but so far have found none that resolve my problem. There was another recent thread about an 9174 not working on Vista ("NI cDAQ-9174 Not recognized"). Midway through that thread, there was the recommendation to delete the MAX Data folder. That solved the problem for the original poster, but it did not solve the problem for user kmeloy who posted subsequenty. Deleting the MAX Data folder had no impact on my problem either.

I would gretaly appreciate help trouble shooting this strange failure of the drivers one of three similar systems. I can did whatever diagnostic information you need out of the registstry and control panel, etc.

regards,

Michael

[SunainaK]

Hi Michael,

I believe NI Device Loader may not be started. If you go into the Control Panel>>Administrative Tools>>Services>> NI Device Loader and check what the status is. If it is not started, right click and press start.

[mhweber]

Thank you, that temporarily resolves the problem for the sesssion. But now I need to manually start the service every time I reboot.

The real problem, then, is that on this computer, the NI Device Loader service does not start by itself. The drivers were installed in exactly the same fashion, and the service is set to start automatically. However, it is not running after a reboot.

I had a quick look in the Windows Event Viewer and I found the messages below, but nothing specifically related to a startup problem with the NI Device Loader. 

Is there a way to diagnose why it won't start by itself?

thanks for your help,

Michael

Event Viewer messages. These messages appear after logging on, without any explicit execution of any NI applications. We do not have LabView installed on that computer, only the NI-DAQmx driver package set to default settings (with MAX, etc.).

Application Log:

Source: LabVIEW
Event ID: 3299
Message: LabVIEW information: Error: 404 "Not Found" for "national instruments/ninetworkdiscovery", file "c:/program files (x86)/national instruments/shared/ni webserver/www/national instruments/ninetworkdiscovery": Can't access URL .

Source: LabVIEW

Event ID: 3299
Message: The description for Event ID 1 from source niZeroconfService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

mDNSResponder started

The specified resource type cannot be found in the image file

[mhweber]

I found a more relevant message in the Event Viewer about he NI Device Loader failing to start:

The NI Device Loader service depends on the National Instruments mDNS Responder Service service which failed to start because of the following error: 
The service has returned a service-specific error code.

And

The National Instruments mDNS Responder Service service terminated with service-specific error %%-65549.

full details:

Log Name: System
Source: Service Control Manager
Date: 6/13/2012 12:14:38 PM
Event ID: 7001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: CACARTHOST-X64.Kardium.local
Description:
The NI Device Loader service depends on the National Instruments mDNS Responder Service service which failed to start because of the following error:
The service has returned a service-specific error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2012-06-13T19:14:38.427030500Z" />
<EventRecordID>47276</EventRecordID>
<Correlation />
<Execution ProcessID="584" ThreadID="588" />
<Channel>System</Channel>
<Computer>CACARTHOST-X64.Kardium.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">NI Device Loader</Data>
<Data Name="param2">National Instruments mDNS Responder Service</Data>
<Data Name="param3">%%1066</Data>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 6/13/2012 12:14:38 PM
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: CACARTHOST-X64.Kardium.local
Description:
The National Instruments mDNS Responder Service service terminated with service-specific error %%-65549.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7024</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2012-06-13T19:14:38.427030500Z" />
<EventRecordID>47275</EventRecordID>
<Correlation />
<Execution ProcessID="584" ThreadID="680" />
<Channel>System</Channel>
<Computer>CACARTHOST-X64.Kardium.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">National Instruments mDNS Responder Service</Data>
<Data Name="param2">%%-65549</Data>
</EventData>
</Event>

[SunainaK]

Hi Michael,

There is a beta version of MDNs Responder which should fix this problem. It should be posted shortly.

[mhweber]

Thanks for the update, Sunaina.

If there are any additional diagnostic details I can gather to help your developers, let me know. I am a software developer myself, and I understand the difficulty in diagnosing uncommon problems that only affect specific customers.

regards

Michael

[SunainaK]

Hi Michael,

You're welcome! I appreciate that. I am still speaking with R&D to see when we can get the beta version to you. If we do need more information, I will let you know!

Have a great weekend!

[mhweber]

Hello Sunaina, 

I installed the mDNS Responder beta version and there is no change in behaviour -- the problems persist. However, I have done some more troubleshooting, and I learned the following: on this particular computer (only), the mDNS Responder Service and the Device Loader service fail to start if the computer is NOT hooked up to a network with a physical ethernet cable. Even if we use a wireless USB network adapter, if the the ethernet cable is unplugged, then the services fail to start.

On the other hand, I've tested this on other computers, and the services both start fine even if the computer's network cable is unplugged, either with or without a wireless USB adapter. In our lab environment, computers on carts move around, and they are not always physically connected to a network. Therefore, the normal behaviour of these services starting successfully in the absence of a network is very desirable. In our particular configuration, we are not using any of the networked device control functionality.

Again, if there is any additional diagnostic information I can collect, let me know.

best regards

Michael Weber

[SunainaK]

Hi Michael,

Thank you so much for all this troubleshooting. I am glad you were able to hone in on the problem. This is an ongoing issue, and your diagnostic information will help research this issue.

[Edzard]

I had this same problem. I just resolved it, with a little help from this topic.

I found out that the service closed itself after it started. To prevent this, I used the following steps:

In the registry editor (press start and type regedit, press enter), I deleted the entry linked to the failing service:

-click ctrl + f to search

-search for: "nidevldu"

-delete the entire folder

Then, to replace this folder, use the following link:

http://dl.dropbox.com/u/78170455/Labview/nidevldu.reg

Execute this file, to add it to the registry.

Then place the following file, that is associated with this service, in C:\windows\system32\

http://dl.dropbox.com/u/78170455/Labview/nipalsm.exe

Reboot, and it should be fixed.