VIPM 2012 error checking for packages

[dpnsw]

I have checked Firewall and AV and I think they are OK but I can't update package lists properly.

 

Error listed below.

 

I have checked the URL

http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec'>http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec

and it certainly 404's even on my browser.

 

The check for updates under VIPM option says I am on the latest version which is V12.0.0 build 1780

 

Is there some config I am missing or anything else I should check.

 

Could I still have a firewall issue even though I can't see that anything is being blocked?

 

many thanks

 

David

 

 

The log file shows the following:

=========== START of VIPM Error Message ===========

An internal VIPM Error has occured on: Friday November 09, 2012 at 10:21:41 AM

 

= Automated Message Start =

Error 42 occurred at (http response "404". URL Requested:

http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec)

14280DE39C8DAD756B5BEBFD8359AC0C:1 in

78C0506DEFD3CCC86D23FCCA90820135->D030F07D3EB857F827E844D79BB99400->AAEF77B6BF19CEFD015DEA5AD1F9C242

->OGPM Class.lvlib:7F68E4B89D07A5FA02A89CD464F2E4E8->OGPM

Class.lvlib:61E953ABD2F6709B3366915D2B536345->0C2EB955350C6EABE176EFF4F6B989B6->VIPM Main Window.vi

. URL:

"http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec".

Possible reason(s):

LabVIEW: Generic error.

= Automated Message End =

 

= User Defined Message Start =

Check for Package Updates from the network.

= User Defined Message End =

 

= Error Handler Call Chain Start =

VIPM Main Window.vi->

0C2EB955350C6EABE176EFF4F6B989B6

= Error Handler Call Chain End =

=========== END of VIPM Error Message ===========

[Michael Aivaliotis]

The problem is with the LabVIEW Tools Network and VIPM's ability to handle 404 errors gracefully. The 404 handling will be fixed in VIPM 2012.0.1 coming out shortly. However NI nis working on fixing that package.