06-23-2010 02:08 PM
While creating a TestStand distribution, I get this error:
*****************
Error: Internal error. (Error code -40)
There was a problem getting information about the source distribution for product 'NI .NET Framework 2.0 Language Pack x86 Installer'
*** End Error Report
**************
*** WARNING ***
Skipping deployment information for an unidentified product because error code -40 occurred while loading file: C:\Program Files\National Instruments\Shared\MDF\Manifests\NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml
The .xml file exists and the distribution builds but why am I getting this error?
06-23-2010 05:28 PM
While building a different distribution, I get these additional errors:
*** WARNING ***
Product 'NI Remote Provider for MAX' depends on a product that cannot be found on the system. ID of missing product: {B5171839-26E3-48D9-9FD6-AF7F39055146}
Product 'Broker Aux 8.2' depends on a product that cannot be found on the system. ID of missing product: {B5171839-26E3-48D9-9FD6-AF7F39055146}
Aren't these products supposed to be copied to the Product Cache?
06-24-2010 05:28 PM
Hi Ching-Hwa Yu,
Do you receive the same error if you start with a new sequence file and follow chapter 14 in the TestStand Reference Manual? If you are receiving this error regardles of what you are trying to build it will be a different situation then if it only occurs when trying your current build.
Thanks
06-25-2010 01:27 AM
06-25-2010 12:22 PM
Hi Ryan,
I receive the first error regardless of what I am trying to build. If I create a blank distribution and have no workspace selected and only the TestStand engine, this error will occur. In the Installer Options, I have only LabVIEW 7.1.1. RTE and LabWindows/CVI 2009 RTE selected in the components to include since they are required by the engine. Even if I uncheck "Include .NET Framework Version 2.0 in Installer", this error occurs. I have already tried all of the other suggestions in the the forums such as deleting everything out of the product cache.
For the second error, I have already tried deleting everything out of the Product Cache. It could be that I need to include the hardware configuration however I cannot test that at the moment.
I'm on Windows 7, TS 4.2.1
06-25-2010 01:10 PM
I've narrowed the second error down further. It only occurs when I include either NI-VISA Configuration Support 4.6.2 or NI-CAN 2.6.3.
When searching the registry, the ID of B5171839-26E3-48D9-9FD6-AF7F39055146 appears numerous times as the Data in UpgradeCode keys of other IDs.
What is missing?
07-12-2010 10:08 AM
Ching-Hwa -
I have reproduced the first error that you mentioned and will look into it further. I'm still working on reproducing the second error. I'll let you know if I have further information or questions.
07-16-2010 10:53 AM
Ching-Hwa -
Could you please tell me exactly which errors you are currently receiving when you attempt to deploy? After clearing the ProductCache's, do you still receive the errors:
Error -40: NI .NET Framework 2.0 Language Pack x86 Installer
as well as the
Product 'NI Remote Provider for MAX' depends on a product that cannot be found on the system. ID of missing product: {B5171839-26E3-48D9-9FD6-AF7F39055146}
I look forward to hearing back from you.
07-16-2010 01:03 PM
Hi Manoosh,
Thanks for looking into these errors. Yes, after clearing the ProductCaches, I still receive the errors.
For every deployment I attempt, I always receive "Error -40: NI .NET Framework 2.0 Language Pack x86 Installer".
The other two errors only appear if I include NI-VISA Configuration Support 4.6.2 or NI-CAN 2.6.3 as part of the deployment.
Please let me know if that is not clear.
07-19-2010 12:02 PM
Ching-Hwa -
In my testing to reproduce these errors, I've been able to at least reproduce the first error. To resolve it, I had to repair my DriverDVD installation. Would you please try going to Add/Remove Programs (on Windows XP) or Programs and Features (on Windows Vista/7) and try to repair one of the NI drivers you have installed (I recommend DAQmx). This should prompt a repair of the DriverDVD.
This repair could take some time so you might want to start it when you will be able to walk away from your desk for a bit. This resolved the first error for me and another customer so I'm hoping it resolves the error for you as well.
Please let me know how it goes.