09-18-2017 12:51 PM
Hi,
I am getting intermittent failures when building a deployment / installer on a PC other than the one on which is was edited.
Does the error message below look familiar to anyone? If so, what's the fix / workaround.
"Unexpected internal error while setting the upgrade code and product version in the installer (_MDFBuildDevPart_SetUpgradeInfo)"
Full Status Log file attached.
09-19-2017 12:59 PM
Are you using hardware with this deployment? If so please ensure that the MAX configuration of that hardware is included in the deployment.
If that does not work, does this error occur when you do not include additional installers?
09-19-2017 01:57 PM
No, I am not using any hardware.
This deployment consists solely of an (almost) empty sequence, and a few Property Loader files.
Right now, I'm just trying to prove the principle that a TSD created / edited on one machine, checked in and out of source code control, and subsequently built on a second machine.
09-20-2017 01:09 PM
Does any portion of TestStand work on the second machine? Can you make an empty sequence and open that? If not, please check NI License Manager on the second machine to see if you have an active license on that machine for TestStand.
09-21-2017 10:23 AM
Yes, the Sequence Editor, and other components work without any issues.
In fact, the TSDU works without issues some of the time. Even when I get the error, the File Analysis and Build Deployment stages seem to work fine. It's only the Installer Generation step that causes the problem (as you will see in the log file I attached initially).
My suspicion is that there is a Windows write privilege issue on some critical file that the TSDU needs to update when producing an installer, or something like that.
I was just wondering if anyone else had encountered it, before I sink too much time into investigating.
09-21-2017 01:13 PM
I've never seen this error before, but maybe i can provide some insight on it:
MDF = Meta Deployment Framework, which is an underlying component used by NI products to create distributions.
upgrade code and product version can be specified in the Advanced Options... section of the Installer Options tab.
The first thing I would try is disabling the "Install TestStand Runtime" option, and unchecking all other additional installers in the "Drivers and Compontents" section. If the error goes away, then it's likely a problem with one of the installers in your product cache... Slowly add back installers to the build until you find the culprit, then remove it from the product cache and TSDU will prompt you for a path to the installer when you build. Give it the path to the correct disk or downloaded copy of the installer.
If the error still happens with no additional installers, then you should open up a service request with NI support so we can get the appropriate log files and investigate this further.
Trent
National Instruments