Problem using Winstall Lite to make .MSI packages.

Has anybody worked with the Winstall lite that comes on the Win2k Server CD? I get it to work for some applications but not others. It's weird because it is some of the more simple programs that are causing problems.

Windows Software 5498 This topic was started by ,


data/avatar/default/avatar40.webp

8 Posts
Location -
Joined 2002-12-26
Has anybody worked with the Winstall lite that comes on the Win2k Server CD? I get it to work for some applications but not others. It's weird because it is some of the more simple programs that are causing problems. I just decided to do a test with some simple freeware, like trillian. Everything is fine until Windows Installer tries to install it. (2000 domain, WinXP client) I get errors like these:
 
Error 1406. Could not write value VersionMinor to key UNKNOWN\Products\4D2506DAF3AD3C347A284BB1178E618C\InstallProperties Verify that you have sufficient access to that key, or contact your support personnel.
 
and
 
Error 1406. Could not write value VersionMinor to key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{AD6052D4-DA3F-43C3-A782-B41B71E816C8}. Verify that you have sufficient access to that key, or contact your support personnel.
 
I am logged on as administrator when this happens, though it is supposed to work for any user. This is just an example of the of errors that I am getting with it for a few different programs though they all look very similar. I looked around on MS technet site, but didn't help much. I don't understand why I would get this from such simple install programs. I just need pointed in the right direction, or how to interpret these errors.
 
It must be something wrong with the snapshot because I can click ignore and the program finishes its install and works fine afterwards. However, I cannot assign it to a machine if it has errors in it so I still have to figure out how to fix the install... Tried editing the .msi file to see if I could take out any registry keys that are unrelated to the program. Unfortunately that didn't fix it. Didn't see anything obvious. Any help is greatly appreciated. ;(

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar01.webp

738 Posts
Location -
Joined 2002-12-11
I have yet to play with trillian, though I too have had obstacles in the packaging of software for deployment ... and this includes enterprise level tools from InstallShield, Veritas, Symantec, and Altiris.
 
www.appdeploy.com is a good HQ for some of your more popular business software / tips n tricks / books / etc.
 
Winstall LE comes with plenty of its own problems, I wouldnt necessarily recommend its use beyond a test environment.
 
I can only offer you this advice, most packaging comes through trial and tribulation. VMware has also been a big help.
 
G'Luck.

data/avatar/default/avatar40.webp

8 Posts
Location -
Joined 2002-12-26
OP
You rock, DS3Circuit! I found my answer on that site. That is a great site, going in my favorites. I've been searching microsoft, veritas, and google for this problem off and on for over a week. All that and it was something so stupid.
 
The problem was that you can't use a letter in the application version when you edit the .msi file. I was putting 0.74c on trillian and every other program that was having this same problem also had a letter in the version. I guess it puts the version you give it in a key in the registry that can only accept numerical data. ;( I feel so dumb now, cuz the error makes sense now. They could have made it a little less cryptic though.
 
Did I mention you rock? Thanks.

data/avatar/default/avatar01.webp

738 Posts
Location -
Joined 2002-12-11
LOL
 
Well then my friend, you are more than welcome.