LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

CVI9.0 after building distribution disk, getting internal error 001b:104fb24c

programs compiles and builds 2 volumes OK with no errors.

After I press "close" on the build window I get the above error.

After I press "OK" to the error popup I get another popup that says "invalid popup or handle"

 

I noticed that the .cds file is not created. 

 

 

Windows XP Pro

AMD Athlon XP2200+

1.36Ghz 768MB

Using CVI9.0.0 full(build 348) 

NISWITCH3.8

NIDMM2.9

 

Message Edited by rorOttawa on 03-14-2009 12:13 PM
- Make Software User Friendly -
0 Kudos
Message 1 of 20
(4,134 Views)

I get same error even if I just create a new distribution  settings file and just leave the defaults entries...add nothing extra.

It is unable to create the file.

I get above error when I say "save all" in "File" dropdown menu.

Press "ok" then I get popup that says "Panel,popup or menu bar handle invalid"

 

 

- Make Software User Friendly -
0 Kudos
Message 2 of 20
(4,124 Views)

Hello,

 

Does this happen with any distribution that you build, or only with a specific distribution?  Can you build distributions for one of our example programs without problem?  If it is only this project, and you can reproduce it reliably, is there any chance that you can post the project to ftp://ftp.ni.com/incoming (only NI employees can retreive files from this location)?

 

Thanks!

 

NickB

National Instruments 

0 Kudos
Message 3 of 20
(4,084 Views)

In CVI 9.0, the .cds file does not get saved immediately after you create/edit/build the distribution. It typically gets saved when the workspace is unloaded, which happens when you close CVI or load a new workspace. It is possible the problem occurs when trying to save the workspace.

 

If you have  File>>Auto Save Workspace checked, please uncheck it and try building your distribution again. Do you get the same errors after you close the distribution build progress dialog? After that, do you still get the errors when you try to Save All?

 

Mert A.

National Instruments

0 Kudos
Message 4 of 20
(4,066 Views)

I have the same problem as the OP (in CVI 9.0(348)). I have just 'upgraded' from 9.0(330), the uninstaller for the latter trashing my registry twice today.

 

The only way to save a .cds file seems to be to remove it from the list of distributions in the workspace. Saving the workspace or auto-saving on exit doesn't save the .cds file.

 

When the .cds file is reloaded, the 'Import Measurement & Automation Explorer (MAX) Configuration file' option is ALWAYS checked even if I unchecked it before saving the file.

 

Currently, I cannot even build a distribution because CVI says it cannot find all sorts of spurious files (a different file each time I try).

 

I'm supposed to be getting a distribution out this week. Not a happy bunny at all.

Message Edited by msaxon on 03-17-2009 05:18 PM
--
Martin
Certified CVI Developer
0 Kudos
Message 5 of 20
(4,061 Views)

Martin,

 

I'm sorry for your troubles. I have not been able to reproduce the issues you or rorOttawa are running into, except for the MAX config checkbox, which is a previously discovered issue that has been fixed for a forthcoming maintenance release.

 

If we can track down the cause of your other troubles quickly, it's possible it could also be remedied in the maintenance release. Also, I want to try to help you get that distribution out on time. Do you get the same error popups, at the same times, as described by the OP? Do you recognize the 'spurious' files that are being reported missing (i.e. are they files you've specified for inclusion, or seemingly random files)? Could you give some examples of files that are being reported missing? Are any files showing up red in the distribution editor, before the build?

 

A debug log may be helpful. Please enter the distribution editor, select the tab control (should have a dotted rectangle around one of the tab labels), and press ctrl+shift+L. Now attempt to build your distribution. Afterwards, you should find the file c:\Documents and Settings\<username>\Local Settings\Temp\distBuildDbg.txt has been created. Please post that file here.

 

Mert A.
National Instruments

0 Kudos
Message 6 of 20
(4,054 Views)
I've decided to remove everything NI from my PC and start again. If you have a utility for getting rid of everything NI out of the registry, it will save me having to look for it manually.
--
Martin
Certified CVI Developer
0 Kudos
Message 7 of 20
(4,051 Views)
No such utility that I am aware of.
0 Kudos
Message 8 of 20
(4,049 Views)

My problems with not being able to create a distribution at all went away when I un-installed everything NI then re-installed CVI. I am just left with the problem reported by the OP.

 

Note - in passing - that un-installing CVI 9.0 appears to remove something important from Windows. After un-installing CVI neither Internet Explorer or Sophos Anti-Virus would work. They started working again after I re-installed CVI 9.0.

 

After some more investigation, I found that the problem only occurs on distribution created for certain projects. A distribution created for a new project in a new workspace (created using 'new project from template') is saved properly and CVI does not crash on exit. However, adding an existing problematic project to the same workspace, making it active, and creating a distribution for it causes the crash as previously reported (and the .cds file for it is not saved).

 

The only thing I know that is 'special' about my problematic project is that it uses the GPIB libraries.

 

The same behaviour has been observed on two different computers.

--
Martin
Certified CVI Developer
0 Kudos
Message 9 of 20
(4,021 Views)

The uninstallation problem was reported previously and is discussed in this thread. In short, the problem comes from uninstalling the Interface to the Win32 API. To solve the problem, you can either reinstall CVI 9.0 with the Win32 API, or run the .reg file attached in that thread. A permanent fix should be included in the next maintenance release.

 

Would it be possible to zip and post your project to ftp://ftp.ni.com/incoming and let us know the name of the file? That site is only readable by NI.

 

Also, can you confirm the crash address 104fb24c? Is this the address that is reported each time?

 

Thanks. The information you've posted is very helpful.

 

Mert A.

National Instruments

 

0 Kudos
Message 10 of 20
(4,007 Views)