VIPM LabVIEW 2013

[StevenHowell]

***SOLVED***

I figured it out, I changed one of the settings but not both of them, that did the trick

I recently installed LabVIEW 2013 and VIPM 2013. I am trying to install several add ons to LabVIEW 2013, and keep getting this error. I have already gone into the settings and made sure that the local host is set up for VIPM, and I also changed the TCP/IP port for VI Server to 3363 as it was 3365 before. I have received the error with both ports entered into the VI Server field. 

Any help would be greatly appreciated.

Steven

[Craig_]

What did you do to fix it?

[StevenHowell]

Craig,

I had added the "localhost" to the "exported VIs list" box, but not the "machine access list" box. This seemed to fix the problem. I also noticed that at the top of the page that the TCP/IP address is now defaulting to 3365 where it was 3363 in LabVIEW 2012, and 2011. 

Steven R Howell

Certified LabVIEW Associate Developer (Waiting on results of CLD)

Arcus Technology Services, LLC.

[cnguyen10]

I tried that but still got the same error.

Any ideas?

[JÞB]

---

@cnguyen10 wrote:

I tried that but still got the same error.

Any ideas?

---

Those settings require LabVIEW to close and restart to be applied.

[Bob_Schor]

Here is the method that I use, and it has always worked.

• Set up LabVIEW options first.  Enable TCP/IP, use the default address of 3363.  Check Machine Access List -- it should (by default) show the IP of your machine.  If it is blank, you can put in "localhost", but if it is "filled in", you can use that value.  Exported VIs should be *.  Make sure that "Allow Access" is checked.
• Close LabVIEW, and open VIPM.  Under the Edit menu, choose Configure LabVIEW Versions.  Make sure the LabVIEW Version TCP/IP Port is set to 3363.  I've noticed that VIPM 2013 seems to give each version of LabVIEW (assuming you have more than one version installed) its own TCP/IP port.  My own practice is to set them all the same, to 3363.  I suspect this means that you should be sure that no version of LabVIEW is running when you start VIPM.
• Choose your LabVIEW version in VIPM and install packages.  This should work for you, as it works for me ...

Bob Schor

[cnguyen10]

I switched my laptop wireless off and used the LAN line and it worked.

Not sure why.

[Bob_Schor]

That's an interesting twist!  I can see that having two NICs, both active, could "confuse" VIPM.  My Work PC has a second active NIC, but I might not have had it enabled when I just recently "rebuilt" my PC -- certainly in the past, with earlier releases of VIPM, both NICs were on.

My Laptop has both Wireless and Ethernet.  I usually disable Ethernet, largely to save battery power (as almost all the time I'm using Wireless), so "by accident" I didn't encounter your difficulty.

I'm assuming that the folks at JKI who maintain VIPM will see this post and will think about how/if this situation can be addressed -- they're pretty good about that.

BS

[Silvino.Presa]

Hi all,

It's been a while since the last post but I encountered the problem and I was able to fix it. First of all I tried all the steps, set "localhost", "127.0.0.1", etc and it didn't work. Then, I look my computer IP (you can see here how to find it in windows 7), I copy the address and everything works.

[FilipeP]

http://digital.ni.com/public.nsf/websearch/88275613105A4E7286257A5B00720DA1?opendocument&Submitted&&...