NI-Farm internal error - unable to compile FPGA VI

[JefeL]

My main concern was with the non-standard revision number of the Xilinx tools. I didn't know about the custom target so you are right, the version number probably won't have any impact.

[JefeL]

Would it be possible to get additional information about the windows updates  that were applied, triggering this issue?

[Shinton]

Hi Jeff,

Of course.  Attached you will find screenshots of the updates of the day the problems began on both machines. 

But there is news, the compile server on the faster dev PC that I didn't try to perform NI updates on is working again.  As far as I know there were no changes to the machine, it just sat running for a couple of weeks.  The compile server on the slower machine that I did try to perform NI updates on is still not connecting, but at this point I don't know whether to blame the windows updates or the failed NI updates.  So now that we don't have a clear control group and experimental group (or a consistent, reproducible problem for that matter) I'm not sure what to tell you, I can't expect you to continue such a wild-goose-chase investigation.  I'll try loading another VM onto my slow PC and perform the windows updates but not the NI updates and see what happens.

I did notice that the faster machine (that is now working) didn't have any .NET updates, but that may not be relevant.  Good luck if you do continue to investigate!

[Shinton]

So I asked my coworker if he made any changes on the faster PC whose compile server mysteriously works now and he said that all he did was perform a Windows 7 update the host OS.  I guess I must confess that both of the systems that I have been describing in this thread are virutal machines (within different real machines).  So a host OS update fixed the faster PC's VM's compile server, but the slower PC host is my work laptop and I have no control over its OS and updates, so I can't update that and see if it works.  I am currently reloading the original VM to roll back the NI updates I attempted, if the compile server can connect then the original problem is gone and can write off this whole problem as some strange state that hopefully never occurs again.

[Shinton]

I reloaded the backup VM and performed a Win7 update, everything seems fine.  So I deleted the problematic VM, problem solved.

My guess is that the Win7 update had some strange tweak in it that caused the NI compile farm to not connect, but subsequent Win7 updates resolved the issue.  But it doesn't matter much at this point.  Sorry for all the drama!

[Vinal_G]

Hi Jeff,

I was facing same Compilation problem with LV 2013. After following your given steps It got resolved.

I wasted a lot of time to figure out this issue. Finally I saw your post and it helped me to resolve this issue.

A big Kudos already given,

Thanks to you and NI Forum.

[蔡徐坤]

Hello, the first to three steps were successfully completed according to your instructions.

However, when I logged the localhost3580 in the fourth step, I found that the login was failed, "login is forbidden". I donot know the reason

[kdevelle]

Hello

I have the same issue :

I tried the solution proposed by Jeff L on the first page, but it did not help. I have the same issue on 2 PC (both were fine yesterday) and I tried with the account of a colleague, same issue. The same message is return also if I try the "test connection". If I put on purpose bad username/password combination, it does not return me this message but bad password/username combination, so somehow it is still able to reach the cloud service. I can still compile locally but it is a big limitation for me.

Any idea?

Thanks a lot

[wiebe@CARYA]

There seems to be a malfunctioning today (2-12-20).

They are working on it...

[T-REX$]

Just confirming... I've reproduced the problem and it's being investigated now.