[VI Package Manager- Not connecting after upgrade]

2 minutes ago, Jim Kring said:

After you get the window that VIPM is waiting for LabVIEW to close, what happens? Does LabVIEW close? If you close LabVIEW yourself, manually, does it reopen LabVIEW automatically?  If not, can you try opening LabVIEW manually and see if VIPM can reconnect and verify the connection?

Actually, that did it, Manually closing and manually booting LabVIEW worked and it connected (it would not automatically do it). Thanks

[VI Package Manager- Not connecting after upgrade]

Submitted the debug file as a ticket

[VI Package Manager- Not connecting after upgrade]

5 minutes ago, Jim Kring said:

The error message is showing that it can't reach http://download.ni.com/evaluation/labview/lvtn/vipm/packages/data_ahead_gmbh_lib_xlr8/data_ahead_gmbh_lib_xlr8-2023.4.0.2.spec

I can download this file with my browser, just fine.

It's odd that it's only this one package that shows an error, since I'm sure other packages are hosted on download.ni.com

Additionally, this error is unrelated to VIPM connecting to LabVIEW (other than both of these "features" of VIPM are using TCP-IP).

Sure, LMK if the VIPM upgrade helps and we'll go from there...

Upgrade to 2523 did not work. I'll submit a new export of the log to the support

[VI Package Manager- Not connecting after upgrade]

7 minutes ago, Jim Kring said:

Also, you can send your troubleshooting file to us at support.vipm.io -> submit a request

You may also see something in the `/ProgramData/JKI/VIPM/error` folder that you can open and review/sanitize then copy+paste here.

Attached

 

I'll try the upgrade next

July-26-2023.txt

[VI Package Manager- Not connecting after upgrade]

I exported a troubleshooting file right after replicated the issue.

It's binary so I can't tell if there is anything in it that I shouldn't be posting, so I'll hold off until someone says it's safe to upload publicly.

[VI Package Manager- Not connecting after upgrade]

I had LV2020 and a version of JKI (don't remember the exact version) working and connected previously.

I then installed LV2023 Q3 (64bit) and VIPM 2023.3 (build 2516) and everything broke. Not just the connection to LV2023, but also the connection to LV2020.

When I click verify in Options/LabVIEW, I get the prompt that VIPM will restart LabVIEW and to save VIs. I then get the window that VIPM is waiting for LabVIEW to close. After about 30 seconds, it reopens the prompt that it will restart LabVIEW. It's an endless loop unless I cancel. (Firewall and other settings attached)

Here's what I have done so far

• Verified Windows Firewall settings. No effect
• Turned off windows Firewall. No effect
• Ran both LV2023 and VIPM2023 as admin
• Uninstalled VIPM and Reinstalled (using NI Package Manager)
• Delete everything in /ProgramData/JKI/ and restart VIPM
• Rebooted the computer multiple times across all of these various steps
• Desktop Execution Toolkit can connect over the designated ports (those both use VI Server right?)

[VIPM Package Build Problem]

On a whim, I decided to try and delete the lvlib and rebuild a new one (they weren't that complicated). That seems to have solved the problem.

Some sort of corruption? (although looking at the file in Notepad++, I'm not sure where that could have possibly gone wrong)

 

Either way, thanks a lot for the help.

[VIPM Package Build Problem]

Those are classes within the library.

If I open up that library, it shows no errors. If I open up those message classes, they open up the library fine.

I just tried to open the library and do a save all. Still getting the error.

[VIPM Package Build Problem]

This is the first window that pops up

 

Wouldn't a mass compile of the directory ferret out any broken VI's that are looking for a library in the wrong place? Does this mean I have an external dependency doing this?

[VIPM Package Build Problem]

VIPM 2020.3 (build 2540)

I'm getting a bizarre error. I get a build failure where VIPM claims that the following source library is missing

C:\Common\Generator Interface\Message Interfaces\Gen11 Message Interface\Gen11 Message Interface\Gen11 Message Interface.lvlib

When the library actually is located here.

C:\Common\Generator Interface\Message Interfaces\Gen11 Message Interface\Gen11 Message Interface.lvlib

This library is a collection is actor message interface classes if that makes a difference. I'm also been able to do a mass compile of the entire directory without any errors.

 

This might not be related, or a quirk of the builder that I don't know about: The other weird thing is if I open the project while VIPM is in the failed state, the error list contains a bunch of failed VIs that couldn't find a .NET library located within my project.

(This project is pretty big and contains some proprietary information so I can't upload it. Sorry, that makes it hard to troubleshoot.)