10-25-2013 04:09 PM
My hardware: cRIO9118, cRIO9024, 9853, Laptop Lenovo T530
Software: Labview 2012, MAX5.5
In MAX under 9024 in "Devices and Interfaces" there is a red spot with white cross inside besides "NI cRIO-9118 "RIO0"". The Status of 9118 is:
***********************************************************************************************************************************************************************
Error -63044 (kRIOStatusRioRpcServerMissing):
The RIO server could not be found on the specified remote device. Ensure that NI-RIO software is installed and that the RIO server is running and properly configured.
***********************************************************************************************************************************************************************
When I tried to start the RIO server in the "services", it gives me an error like this:
In a new project, when I tried to "add Targets and Devices" using the option
"Existing target or device" and "Discover an existing target(s) or device(s)",
Labview will be dead. Then I added 9024 manually. I also need to add the Chassis 9118
and the C Series Module manually as if try to discover them there will be an error
"The RIO server could not be found on the specified remote device. Ensure that NI-RIO
software is installed and that the RIO server is running and properly configured."
10-28-2013 08:23 AM
So it appears that this error comes down to the NI-RIO Server service not being able to start which almost always points to the service itself being corrupted. At some point, some of the NI software must have gotten corrupted. There is a rather simple way we typically resolve errors like this. The following KnowledgeBase article addresses an issue very similar to this:
-Why Do I Get Error 1075 when Trying to Start the National Instruments mDNS Responder Service?
http://digital.ni.com/public.nsf/allkb/A05913DE561AB739862579F7005C4F81?OpenDocument
I would recommend first trying to do a repair of the NI-RIO driver and see if this helps to resolve the error. If not, try repairing MAX as described in the linked article above. If you can fix the NI-RIO Server service error then it should be a great help in resolving the -63044 error. Hope that this helps!
10-28-2013 08:41 AM
Thanks for the help.
How to repair of the NI-RIO driver?
I have done the repair for the MAX several time, it doesn't help.
In the original installation I have MAX 5.3, the problem after I install MAX 5.5. Is that the problem? If it is, how can I go back to MAX 5.3?
10-28-2013 09:27 AM
It will be best not to try to go back to MAX 5.3, becuase if you want to do that you would need to uninstall MAX and that would imply that you would need to uninstall almost all NI Software from the computer and that can be very time consuming.
To repair NI RIO you just need to follow the same steps that you see on the link but instead of looking for NI Measurement and Automation Explorer, you need to look for NI-RIO.
10-28-2013 10:01 AM
There is "NI-RIO 12.0" and "NI-RIO 12.0 for Labview Real-Time", which one should I go and what is the diffrence between these two?
10-29-2013 07:59 AM
You should repair both, one is the drivers for the devices and the other is the support for LabVIEW Real Time.
10-30-2013 05:21 PM
I did NI-RIO repair twice, and MAX 5.5 also twice, no help. The I spent 2 days repair all the packages, still no help. Is MAX 5.5 conflict with my Labview 2012 32-bits?
10-31-2013 07:57 AM
According to the System Configuration 5.5 documentation, there should not be any conflicts with LabVIEW 2012:
http://joule.ni.com/nidu/cds/view/p/id/4086/lang/en
06-10-2014 09:07 AM
I am encountering the same problem now. may I ask have you solved it? if so, could you please to help? Thank you very much!
06-10-2014 09:27 AM
Hello, Jeromelei
I have met this issue twice. Once it is because I install too many packages on 9024, which make the real time OS paralysed. The second time it is because of the broken of some library file on the computer. And this time I tortured with reinstall Labview, failed, then reinstall Windows 7 and labview again.
If it is not the first situation I mentioned, I recommend you talk with NI to see if there is some special issue on your application and then go back to reinstallation of Laview and even Windows.
Best Regards,
Tao Wang