FPGA Compile error - regardless of Firewall settings!

[io io]

I have tried many things:  1) disable firewall on XP machine completely - still fails "Error Contacting Server"

                                    2) I added TCP port 96 on XP to firewall exception - still fails "Error Contacting Server"

                                    3) Disable firewall on 2nd Vista machine  - still fails "Error Contacting Server"

SO two different computers (XP and Vista) which I can ping the compile server "localhost"  or  "192.168.0.5" and get returns data but still fails "Error Contacting Server"

What more is going on?   I have spent some 40 hours trying all these things. 

 

[WillD]

Not really enough information about your setup...

Are you using two computers, one to develop and one to compile?

If this is the case on the computer you are using to compile you need to explicitly run the compile server first, and then fire off your compile from the development box.

[Ben_S]

io io,

It seems you've gone throught the steps in this document, Why Do I Get FPGA Compile Server Errors?, to disable windows firewall and adding port 96 to the firewall. Do you have any other programs that could be causing security issues such as a Virus Scanner?

What versions of LabVIEW and LabVIEW FPGA are you using? Are you using 32-bit or 64-bit Windows XP and Vista? Also, are you the administrator on these computers? 

[io io]

I have a virus (AdWare) scanner and I have disabled the scanner.   Windows XP (has Officescan) and I can not disable.   Vista Machine. (OneCare Firewall  and Virus - off) - same problem.  "cannot contact compile server" What happens in the background when Labview transfers control to compile server?   because compile server does get launch 

[WillD]

You neglected my question.

Are you trying to launch the compile server on a different computer than you are developing on?

 

---

io io wrote:
I have a virus (AdWare) scanner and I have disabled the scanner.   Windows XP (has Officescan) and I can not disable.   Vista Machine. (OneCare Firewall  and Virus - off) - same problem.  "cannot contact compile server" What happens in the background when Labview transfers control to compile server?   because compile server does get launch 

---

Does it work okay if you manually launch the compile server?

[io io]

The same computer that is running labview is running the compile server. 

[io io]

You where right!   When I started the compile server manually it did work. (Complie server and Labview are on same machine)

 firewall - off

virsus scanner - off

os-Vista

os-XP

Same machine for both Labview and compile server

any clues?  why?

[WillD]

You could try and repair your LabVIEW installation.

If you compile on the same machine LabVIEW should automatically launch the compile server, not sure why it isn't.

[Mustanghipo65]

I'm having this same issue using a PXI-8184 embedded controller. I recently had to reload absolutely everything by holding down "alt" during boot. We has a cooling fan go out, caused multiple overheated shutdowns. Our tech ignored the problem untill WIN-DOZE would hang on boot. Max has no problem seeing the 7831R but the compile server errors out. This version of XP is pre-sp2, which i think included the windows firewall utility. We really need to run MAC systems but TestStand isn't supported. 😞 If reparing LabView and the FPGA module doesn't work I'll try to manually fire the server.

Running LV 7.0 with FPGA 1.0. We do have a few licenses for LV2009 but I'm reluctant to intall it on this box.

[KittF]

Hopefully this will save hours for someone.

Symptom: LV 2009 sp1.  Run FPGA vi. Intermediate files created. FPGA Compile Server launched and sitting "Idle ...".  Time out with Error Contacting Server on localhost.

Cause: NI Service Locator  missing from Windows services!

Solution: Run the msi installer for NI Service Locator:  ...Products\Service_Locator\svcloc

I noticed that the LabVIEW Example Finder reported NI Service Locator was not running.  This lead to the trial and error solution.  I'm not sure why this happened, but I believe it was because of a bad install of sp1 that failed to stop and subsequently install services.  Ugh.  Perhaps a repair on SP1 install would have worked.  I tried a repair on the FPGA Compile Server with no luck.