LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

LoadPanel fails with error -100 Badly formed pathname

Hi folks,

 

I have a release build that is giving me problems.  My tester tries to run it and it errors out most of the time at the start with LoadPanel.  The error is -100, "Badly formed pathname."  Not sure what the issue is.  I have built it several times with the LoadExternalModule on and off (on is default), the uir file embedded and not embedded (still testing this, but I've done many embedded builds with no problems).  We've been running into issue with the CVIRTE for 9.0 not being compatible with older run time engines on the same machine, but my tester has removed all older software.  I'm about to have him dump the cvirte.dll file and install again.  This is so strange because it's on a project I've built many times and the edits I've made to the code are simple - add a control to a panel and put the callback in place.  It's erroring out before it even reaches the panel I've edited.

 

Any ideas?

 

Thanks,

 

Judy Harrigan

0 Kudos
Message 1 of 5
(4,415 Views)

If you have the CVI ADE installed in the PC where you're having this error, then I'd suggest the following:

 

1. Run C:\Program Files\National Instruments\CVI90\bin\ConfigCVILogging.exe

2. Select "Runtime Engine", "Warning" and "File" as in this screenshot:

 

18647iD66C7CA8470BE566

 

3. After running an instance of the program that results in error, look for the file specified in the logging utility and post its contents here. This might give us, here at NI, a clue about where the error is coming from.

 

Luis

0 Kudos
Message 2 of 5
(4,400 Views)

Hi Luis,

 

I did get around it by not embedding the uir file into the release build of the executable.  Then, the install worked fine.  I also noticed that I have 9.0 on my machine without the 9.0.1 upgrade, so I downloaded and installed the upgrade.  I'm wondering if that was causing the issue.  Anyway, on the next build I do, I will try embedding the uir file again to see if that is still giving us trouble.  I've not heard of CVI ADE before.  I will check it out in your support pages.  Is it a download that I can put on the test machine?  I was advised not to install a release build on the same machine on which I develop, so all of our release builds go on the tester's PC which has no other CVI tools on it.

 

Thanks for your help,

 

Judy

0 Kudos
Message 3 of 5
(4,389 Views)

Judy,

ADE stands for "Application Development Environment", that is... the CVI installation you are currently usign to develop your applications! Smiley Wink

 

In order to give Luis some more informations on your case:

- does the application run correctly on the development machine?

- where it is installed in the target machine? Do the folder pathname contains spaces or some special characters? (brackets, spaces, punctuations...) In some occasions I had problems with my customers' installations due to imaginative pathnames



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 4 of 5
(4,378 Views)

Hi Roberto,

 

The application runs fine in debug mode on my development machine.  I use all the default directories on the installation as I have been doing for years with no issues.  I also removed the cvirte.dll file from the test machine in case it was an older version and we have not seen the problem since.  I think we're good for now.

 

Thanks again to you and Luis for your time,

 

Judy

0 Kudos
Message 5 of 5
(4,329 Views)