10-23-2013 03:43 PM
My hardware: cRIO9118, cRIO9024, 9853, Laptop Lenovo T530
Software: Labview 2012, MAX5.5
When I run the fpga VI, it tries to compile with the error: "An error occurred attempting to connect to this compile server. Details: NI-Farm: Farm server is not responding. Be sure the specified hostname is correct, the server is running and configured to accept remote requests."
My colleague told me to put a name on "RIO Alias on My System" and "RIO Alias on 169.254.84.198", e.g. "RIO0" in MAX under 9024's Devices and Interfaces, the 9118 "RIO0". It doesn't help.
For all the time I can't close MAX normally, I must kill it in "task manager" to end it process. Actually I added 9024 manually, since MAX can't find it. The "searching" is always there, and sometime never end. There is also a warning "VISA Error":
**************************************************************************************************************
VISA error code:
0xBFFF00A8 (VI_ERROR_NPERMISSION)
Description of error:
viFindRsrc returned 0xBFFF00A8 (Access to the resource or remote machine is denied. This is due to lack of sufficient privileges for the current user or machine.)
Please check the remote machine's settings and make sure you have added this machine's network address to the permission list.
Possible causes for this error:
1.The remote machine you are accessing has not granted you permission.
2. The remote machine you are accessing has denied you permission to access its resources.
3. You may have set up your server with a specific IP address and configured your client machine to different IP address rather than the machine name (ie, the client's IP address is assigned by a DHCP server).
**********************************************************************************************************************
In "Project Exploer" when I tried to "add targets and devices" with the option "Existing target or device", 9024 can never be found and Labview will be "Not Responding". And these days, when I exit from Labview, always ask me to send a error report.
10-25-2013 06:07 AM
Hi wt70707,
The VISA error means that "VISA access to the remote target is denied." This is caused by incorrect VISA permission settings on the RT host. To change the permissions, do the following:
As for the compile error, have you been able to compile FPGA code in the past? Is there an error number associated with this? Here is a forum thread similar to this error.
Running a "Repair" of MAX through the Windows Add/Remove Programs may help with the MAX issues.
10-25-2013 01:13 PM
Hello, David
Thanks for your answer.
The set of RIO is out for field test now. I am using another one set which there is no this VISA error and I checked the VISA option, there is a "*" there. I will check this when the one with VISA error comes back.
For the compile error, it can be compiled before and also I have tested with a desktop instead of my laptop, it also can be compiled and can be written into the fpga. I have ever read the link you send to me. There is no solution actually to the problem. The guy just uninstalled all the program and installed a new version of Labview. However, we are not that waste to upgrade the newest version of Labview after only one year use of the old one.
10-25-2013 07:27 PM
Hello, David
For the VISA error, I " Add "*" to the Remote Access List" both under RIO 9024 but also under "my computer", now the VISA error has gone.
10-30-2013 05:23 PM
Though this error is fixed, the fpga vi compilation is still no success.
10-31-2013 06:02 AM
Hi wt70707,
Are you trying to compile locally on the computer or using a compile farm? Is there any error number associated with this error message? Here is a KnowledgeBase that includes a portion of the error text you are seeing. Here is another resource that describes the different FPGA compilation options. If trying to compile locally, reinstalling Xilinx Compile Tools on your computer will help. If using a compile farm, is that compile farm working when accessed by other computers?
10-31-2013 08:27 AM
Hello, David
Thanks for your message. Actually, I have repaired MAX 5.5, NI RIO, Xilinx Compile Tool several times and repair all the packages once, but no help. My original MAX 5.3 works well with my Labview 2012 32bits. Till now I only use local compiler server. Since I want to change the time clock in 9024, I installed NI System Configuration 5.5, then MAX is also updated to 5.5. All the problems come out: the RIO Server can't be started (error -1075); fpga VI can't be compiled (An error occured attempting to connect to this server. Details: NI Farm: Farm server is not responding. Be sure the specified hostname is correct, the server is running and configured to accept remote requests. No error code); MAX can't be closed normally, always needed to kill it with its process in Task Manager (I noticed MAX never stop searching the remote systems); 9024 and 9018 can't be find automatically, always need to be added manually in MAX and in projects; when close Labview always there is a error report needed to be sent.
I started the compile worker manually, it always says: "After x tries, the compile worker can't communicate with the server,..."
When I run Labview FPGA Server Configuration, there is an error: "There was an error connecting to the farm. Error: kNIFarmResulteServerNotResponding Labview Error Code: -123011".
I have spendt two days repairing all the packages, but still all the above errors. What can I do now?
Best Regards,
Tao Wang
11-01-2013 08:12 PM
Hi Tao,
It appears that this issue has been resolved as you were working with one of my colleagues. For the benefit of forum users, the issue had to do with the NI Service Locator Windows Service being uninstalled. This is associated with Error 1075. If you encounter this error, please contact us to receive troubleshooting steps.
11-01-2013 08:52 PM
Hello David,
I don't think it is a NI Service Locator issue as the "NI Service Locator" has been started automatically successfully. It's the "System Web Server" and "NI-RIO server" failed to start. I have explained how I struggled on this issue in my Service Request #7392878.