VIPM update error

[Ben64]

I get the following message when trying to update VIPM to version 2013 SP1

 

Error: The handle is in the wrong state for the requested operation

 

 

I also can't install any package, see attached file for error details.

 

 

LV2012 version 12.0f3 32-bit, Windows 7 Enterprise SP1 64-bit

 

 

Any idea of the cause?

VIPM errors.txt

[Michael Aivaliotis]

That first error message is related to the autoupdate. Perhaps the download is blocked by your company.

You can download the SP1 update directly from here.

 

The other error is something new that I've only seen a few times. VIPM is trying to install a package into LabVIEW and cannot because of permissions problems. This might happen because LabVIEW 2012 was installed with limited permissions.

 

Can you go to:

C:\Program Files (x86)\National Instruments\LabVIEW 2012\vi.lib\addons\

and look at what the permission setting is on that folder? That might give us a clue.

 

Normally LabVIEW is installed with open access to the vi.lib folder. So this is not a problem.

If permissions is an issue then you may be able to get it working by setting VIPM to launch with admin access. You can configure your VIPM to run using "Run As Administrator". You can also set this permanently in the security tab of the shortcut properties page:

[Ben64]

That first error message is related to the autoupdate. Perhaps the download is blocked by your company.

You can download the SP1 update directly from here.

 

The other error is something new that I've only seen a few times. VIPM is trying to install a package into LabVIEW and cannot because of permissions problems. This might happen because LabVIEW 2012 was installed with limited permissions.

 

Can you go to:

C:\Program Files (x86)\National Instruments\LabVIEW 2012\vi.lib\addons\

and look at what the permission setting is on that folder? That might give us a clue.

 

Normally LabVIEW is installed with open access to the vi.lib folder. So this is not a problem.

If permissions is an issue then you may be able to get it working by setting VIPM to launch with admin access. You can configure your VIPM to run using "Run As Administrator". You can also set this permanently in the security tab of the shortcut properties page:

 

 

Thanks Michael, your solutions worked for both issues.

 

Ben