LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error -31

I was having trouble building an application.  The advice I recieved was to repair my LabVIEW installation.  This I did, and then succeeded in building the application.  I then tried to create an installer, and I got the attached error message.

Jim

LV 2020
0 Kudos
Message 1 of 8
(3,492 Views)

Have you tried to Create a Debug Log of a LabVIEW Installer Build?

 

There is an indication in the dialog that it's language-related. Are you trying to install for multiple languages? Does this happen for just this project, or for simple projects as well?

0 Kudos
Message 2 of 8
(3,480 Views)

I don't get to the point of actually creating the installer.  The error message appears after I right click on "Build Specification" and select "New" and "Installer".  It also happens on a single VI project.

Jim

LV 2020
0 Kudos
Message 3 of 8
(3,467 Views)

Hi lmtis,

 

Did you recently upgrade your version of LabVIEW?

 

If so, you might try out the procedure on this KnowledgeBase article: http://digital.ni.com/public.nsf/websearch/8E5E6C58C625B88A8625786A005B21E0?OpenDocument (Error -30 Occurred at CDK_CreateNewWizard_Invoke.vi.ProxyCaller When Trying To Build a LabVIEW Installer)

 

It's obviously not the same error number, but it does appear that it is the same call.

 

Have a great day,

 

Chris

Applications Engineer
National Instruments
0 Kudos
Message 4 of 8
(3,452 Views)

Chris,

 

Thanks for the suggestion.  Unfortunately this error doesn't create an entry in the _edit.log file.

 

Jim

Jim

LV 2020
0 Kudos
Message 5 of 8
(3,449 Views)

Hi Jim,

 

Darn, sorry to hear that that didn't work for you.

 

What version of LabVIEW are you seeing this error in?  I notice you list 8.6.1, 2009, and 2010.

 

Have a great day,

 

Chris

Applications Engineer
National Instruments
0 Kudos
Message 6 of 8
(3,439 Views)

Hi Chris,

 

While I do have all 3 installed, I only use 2010 now.

 

Jim

LV 2020
0 Kudos
Message 7 of 8
(3,431 Views)

Hi Jim,

 

After doing some more research, it appears that sometimes this can occur if you are performing any kind of localization programming.  Are you aware of an localization that you are doing?

 

It also looks like in the few cases where other customer have run into this issue, upgrading to LabVIEW 2010 SP1 has sometimes fixed the problem.

 

Have a great day,

 

Chris

Applications Engineer
National Instruments
0 Kudos
Message 8 of 8
(3,417 Views)