Issue with NI-Switch Driver (Error – 1074135030)

[Josh_B1]

Hey Greg,

We would like you to use the Windows partition of your controller to test the switch. Do you have LabVIEW and the drivers installed on the Windows partition? We would like you to run your LabVIEW program on the Windows partition of your controller. If you are still getting the error then there could be something wrong with your hardware and we can focus on that. If you do not receive an error than we will know to focus on the connection to the controller.

Regards,

Josh B

[Greg_Campeau]

The 'NI-Switch Relay' VeriStand Add-on worked fine on the PXI-8110.  See below for details.

I performed the following actions in the order as listed:

1. Installed a USB Mouse and a USB Keyboard into two of the available USB ports on the PXI-8110.
2. Powered-on the PXI-1045 Chassis, then immediately entered the PXI-8110 Embedded Controller's BIOS setup utility.
3. Within the BIOS setup utility, I switched the boot OS to Win7-Professional.
4. Allowed the PXI-8110 to restart and boot-up into Windows.
5. Installed a USB DVD drive (Gear Head Mobile Slim, Model# CDSL07U2S)
6. Installed the LabVIEW 2011 Professional Development System (Evaluation License)
7. Restarted Windows, when prompted.
8. Installed NI-Switch 4.4.0
9. Restarted Windows, when prompted.
10.  Installed VeriStand 2011 (Evaluation License)
11.  Restarted Windows, when prompted.
12.  Installed the NI VeriStand Add-on - NI-Switch Relay, according to the procedure in its Readme file.
13.  Opened VeriStand.
14.  Once VeriStand was open, I opened the 'Sinewave Delay' demo project.
15.  From the Project Explorer, I opened the Sinewave Delay.nivssdf system definition file.
16.  Right-clicked on 'Custom Devices' under 'Controller' in the selection tree, then selected 'NI-Switch Relay'.
17.  Entered 'PXI1Slot9' in the 'Resource Name' field.
18.  Selected '2586/10-SPST' from the 'Topology Name' field's drop-down menu.  [After about 10 seconds, the 'Available Relay' array-field automatically populated.  No error message appeared!  :-)]
19.  Disconnected the USB Drive.
20.  Restarted the PXI-8110, then immediately entered its BIOS setup utility.
21.  Within the BIOS setup utility, I switched the boot OS back to 'LabVIEW RT'.
22.  Allowed the PXI-8110 to restart and boot-up. (Both, NI-RIO Server 4.0 and NI-VISA Server 5.1 started successfully)
23.  Powered-off the PXI-1045 chassis.
24.  Disconnected the USB Mouse and the USB Keyboard.

[Andrew_B]

Hello Greg,

I appreciate the clarification on running the NI-Switch Relay add-on on the Windows side of the PXI 8110. Due to Josh being OOO, I have taken ownership of this issue. I have been briefed on the work done so far and read through the discussion forum. I understand that your end goal is still to use your corporate PC with VeriStand and target the PXI 8110 running LabVIEW Real-Time. At this point, we have verified that:

• The software set installed on your corporate PC should be functional (using your laptop as a test case)
• The software installed on the Real-Time side of the PXI 8110 is functional (connected to the laptop for testing)
• The switch hardware on the PXI controller is functional (using the Windows boot-up partition on the PXI 8110)

However, errors are still being thrown relating to NI-Switch on your corporate PC. As mentioned by StephenB in the initial community discussion, this indicates an issue with the NI-SWITCH driver on this system. Steps to remedy this issue are:

1. Uninstall NI-SWITCH from your system

2. Install NI-SWITCH 4.4 from your National Instruments download

This should give us a clean install of NI-SWITCH on your system. However, more drastic options are available if this does not work.

Regards,

Andrew Brown

[Greg_Campeau]

No luck.

Here's what I did:

1.  Tried downloading another copy of the NI-Switch 4.4 driver, but the same download issues occurred as in (  https://decibel.ni.com/content/thread/10833  3. Jan 8, 2012 2:09 PM ).  Will use the copy that I previously downloaded.  It should be fine, since it worked okay on my personal netbook (See  http://forums.ni.com/t5/LabVIEW/Issue-with-NI-Switch-Driver-Error-1074135030/td-p/1834483/page/2   01-26-2012 01:04 PM ).

2.  Uninstalled the existing NI-Switch 4.4 driver from my work PC.

3.  Powered-off the PC.

4.  Powered-on the PC.

5.  Confirmed in both, Windows 'Add/Remove Programs' and in NI-MAX, that the NI-Switch 4.4 driver was no longer installed on the Work PC, but still installed on the PXI-8110.

6.  Installed the NI-Switch 4.4 driver.

7.  Powered-off the PC.

8.  Powered-on the PC.

9.  Confirmed in both, Windows 'Add/Remove Programs' and in NI-MAX, that the NI-Switch 4.4 driver was now installed again on the Work PC, and still installed on the PXI-8110.

10. Opened VeriStand.
11. Once VeriStand was open, I opened the 'Sinewave Delay' demo project.
12. From the Project Explorer, I opened the Sinewave Delay.nivssdf system definition file.
13. Right-clicked on 'Custom Devices' under 'Controller' in the selection tree, then selected 'NI-Switch Relay'.
14. Entered 'PXI1Slot9' in the 'Resource Name' field.
15. Selected '2586/10-SPST' from the 'Topology Name' field's drop-down menu.  [After about 30 seconds, the same error message appeared as in  http://forums.ni.com/t5/LabVIEW/Issue-with-NI-Switch-Driver-Error-1074135030/td-p/1834483   01-12-2012 07:51 PM]

[Frank-L]

Greg,

How long is the system running before you operate these commands?

Can you try running the "init sim switch (scratch).vi" in a different topology (such as 2586/5-DPST)?

Additionally, can you try using another device (since this example is actually simulating the device, having the hardware would not matter)? How about trying "2575/1-Wire 196x1 Mux"? 

Is this a hypervisor systems or a desktop PC connecting to an external PXI chassis?

When you ran with your home laptop did you do any additional RT reformatting/reinstalling, or just targeted the same PXI chassis and hit run?

The error that you are getting from the "init sim switch (scratch).vi" may mean that device loader on your desktop is not functioning properly (since this example does not target a specific piece of hardware). Can we try and restart the device loader service on the desktop and then re-run that example? (http://digital.ni.com/public.nsf/allkb/0819391CA91B3EB38625731D00024649)

[Greg_Campeau]

We're making some progress...

Here's what went down, when I followed your last post's questions and suggestion:

How long is the system running before you operate these commands?

- Anywhere from 5 minutes to a couple of days.

Can you try running the "init sim switch (scratch).vi" in a different topology (such as 2586/5-DPST)?

- Same result as previous posts with 2586/10-DPST

Additionally, can you try using another device (since this example is actually simulating the device, having the hardware would not matter)? How about trying "2575/1-Wire 196x1 Mux"? 

- Same result as previous posts with 2586/10-DPST

Is this a hypervisor systems or a desktop PC connecting to an external PXI chassis?

- Hypervisor is non installed.  But, the PC is connected to an external PXI chassis.

When you ran with your home laptop did you do any additional RT reformatting/reinstalling, or just targeted the same PXI chassis and hit run?

- Just targeted the same PXI chassis and hit run

The error that you are getting from the "init sim switch (scratch).vi" may mean that device loader on your desktop is not functioning properly (since this example does not target a specific piece of hardware). Can we try and restart the device loader service on the desktop and then re-run that example? (http://digital.ni.com/public.nsf/allkb/0819391CA91​B3EB38625731D00024649)

Given this, here are the screenshots of what I found and did:

NI Device Loader (nidevldu) Service not started.jpg

NI Device Loader (nidevldu) Service, No restart attempts selected.jpg

NI Device Loader (nidevldu) Service now Started (Running).jpg

init sim switch (scratch).vi is now working, before PC Restart.jpg

VeriStand 2011 NI Switch Relay now works, before PC Restart.jpg

NI Device Loader (nidevldu) Service not started, after PC shutdown and restart, even with all fail cases set to restart.jpg

[Andrew_B]

Hello Greg, 

I'm glad that we have narrowed down the root cause to the NI Device Loader. To clarify exactly what is happening, we can check:

1. What (if any) other "NI" or "National Instruments" services are not started? (such as National Instruments mDNS Responder)

The NI Device Loader has several dependencies, and if one of them fails, it can cause the Device Loader to fail too. To fix a common dependency issue, steps you can follow are:

• Install the latest version of JAVA from their site
• Open the Windows start button, search for command prompt, right click on it and choose "Run as Administrator"
• Type 'netsh int ip reset' into the command prompt and hit return
• Ensure that UDP port 5353 is open for communication in the security software
• Reboot the PC and see if the problem persists

Regards,

Andrew Brown

[Greg_Campeau]

Getting closer...

Narrowed-down the ‘un-started’ driver issue to the 'National Instruments mDNS Responder' driver.

See below for what I did:

1. Updated JAVA from:

     Version 6 Update 21 (build 1.6.0_21-b07) to:

           Version 6 update 31 (build 1.6.0_31-b05)

2. Selected ‘Run as Administrator’ to open the Command-Prompt window.

3. At the command prompt, entered ‘netsh in tip reset c:\resetlog.txt’

    a. Referred to: http://support.microsoft.com/kb/299357

    b. The resetlog.txt file showed that several registry entries were either added, deleted, or reset.

            i. I won’t include the file’s output here, since it contains GUIDs.

4. UDP port 5353 did not appear to be blocked by my PC’s McAfee security software.

5. Rebooted the PC.

    a. Result: No change. The ‘NI Device Loader’ driver still did not load.

6. Repeated steps 1 – 5 a few times. But, the same result kept occurring.

7. Noticed that the driver you mentioned, 'National Instruments mDNS Responder', did not load either.

    a. Also noticed that the ‘National Instruments mDNS Responder’ driver was a prerequisite for the ‘NI Device Loader’ driver to load.

            i. Verified that the prerequisite driver for ‘National Instruments mDNS Responder’ (‘NI System Web Server’ driver) had started successfully, during boot-up.

[Andrew_B · Accepted solution]

Hello Greg,

I have developed a simple workaround to start up the "National Instruments mDNS Responder" and "NI Device Loader" services. A batch file is attached that uses command line tools to start these two services. You can view the contents of the batch file using Notepad or any other text editor. 

The one major restriction to this process: batch file needs to be run as an administrator to start up the services. However, we can set up a shortcut that simplifies this restriction:

1. Place the batch file somewhere it won't be deleted 
2. Right-click on the batch file and select "Create shortcut"
3. Right-click on the shortcut and go to Properties
4. Within the shortcut properties, go to the "Shortcut" tab and click the "Advanced" button 
5. Check the "Run as administrator" box in the window that appears

At this point, you can can start up both services by double-clicking on the shortcut. This shortcut can be moved to your desktop ( or any other convenient location).

An extension of this idea is to place the shortcut in your Startup folder. This would run the batch file each time your system boots. However, you would need to verify this process on your system as boot order & service restart time could affect the results. 

Regards,

Andrew Brown 

[Greg_Campeau]

The workaround worked!  🙂

Here's what I did/encountered, when I followed your steps:

1.  I placed the batch file on my desktop.

2.  I created a shortcut for it.

3.  I right-clicked the Shortcut to open it properties window.

4 & 5.  When I opened the Shortcut's, advanced properties tab, no 'Run as Administrator' option was available.  See the screenshot below.  (I believe this option wasn't available, because I already have administrator privileges.)

6.  I ran the shortcut and both services started successfully.

7.  I placed the shortcut in my Startup folder.

8.  I shutdown and restarted the PC.

9.  The batch file successfully started the services during startup.

10.  Under the recovery tab of the properties window for both of the services, I returned the first, second, and subsequent failure settings to their default states of ‘Take No Action’.

11.  I shutdown and restarted the PC.

12.  The batch file successfully started the services during startup.

13.  I shutdown and restarted the PC, again.

14.  The batch file successfully started the services during startup, again.

15.  The NI Switch Relay VeriStand Add-on successfully ran.  🙂