-2147220304

[jpenko]

We are trying to format a crio and load an image using the FRC imaging tool 2013.9.25.  The image version FRC_2014_v52.zip, It failed on the older 8 slot FRC cRIO as well as the newer 4 slot unit.  The tool formats the crio and errors on the reboot.  The error message is:

Error -2147220304 occurred at nisyscfg.lvlib:Restart.vi:1680001

Possible reason(s):

NI System Configuration:  (Hex 0x800404B0) Timeout while waiting for reboot. System is offline.

Complete call chain:
     nisyscfg.lvlib:Restart.vi:1680001
     ConfigUtility.lvlib:2012_FormatSystem.vi
     ConfigUtility.lvlib:ReImageTarget.vi
     ConfigUtility.lvlib:Dialog.vi

What do we do?  FRC team 3010.  Thanks!

[Shane-C]

Hello,

This error message can come up for a variety of reasons, but is usually due to a network communication problem.  Try the following troubleshooting steps to see if it makes a difference.

1. Disable all other Network Adapters on the computer. Open the Network Connections window from the Control Panel (see Network Adapter Properties step above), then for each adapter other than the Local Area Connection you are using to image the cRIO, right-click on the adapter and select Disable.
2. Try using a network switch between the cRIO and computer: Some computers have issues reconnecting to the cRIO after the cRIO reboots as part of the imaging process. Placing a switch between the two devices, such as the D-Link DAP-1522 provided in the Kit of Parts typically mitigates this problem.
3. Disable Windows Firewall or other firewalls: Windows Firewall may be blocking the cRIO Imaging Tool, preventing it from detecting the cRIO. If possible, temporarily disable the Firewall by following the steps below.
4. Check that the adapter is set to a single IP address. To do this open the Network Properties as shown in the Configure Computer IP Address steps above. When you reach the last step, click the Advanced button and verify that only one address is listed in the top box. If multiple addresses are present, select the extra addresses and click Remove.
5. If the cRIO is still not detected, try rebooting the cRIO in Safe Mode. To reboot in Safe Mode on an 8-slot cRIO, flip the Safe Mode DIP switch, then reset the cRIO. To reboot in Safe Mode on a 4-slot cRIO, hold the reset button for 5 seconds, then release. If the cRIO is detected by the imaging tool attempt to format. The tool will prompt you to take the cRIO out of Safe Mode, then try again.
6. Try a different PC: If none of the above steps work, try using a different computer to image the cRIO.

If none of these steps help, reply here and we will try to help you troubleshoot this further.

Regards,

Shane C

[Shane-C]

Simply to document this for others - It is worth noting that this error can occur in the NI RAD Utility as well, and apply to PXI targets too  I discovered this today.  As it turns out similar solutions apply.  For me it was the firewall this time around.