Getting \"Error\" message box on very simple install

cjoyce · Post by **cjoyce** » Mon Jun 09, 2008 4:31 pm

This is a very simple install that copies files, creates a shortcut and that's about it. This install was working fine and I made a copy of it to build another install. I changed the project name and the GUIDs. When I tried to build the install recently, I get a generic "Error" message box when it gets to copying the files. Pretty worthless message.

So I saved the output to an MSI log. The log appears to be in UNICODE because you can hardly read it. See attached. Am I supposed to view this in a special viewer? This seems different that most MSI logs I've seen before. It is wrapped in an InstallWare XML tag.

The event log in Vista gives an MSI error code of 1013 and then 1033.

Windows Installer installed the product. Product Name: Logical Ink OnDemand. Product Version: 2.0. Product Language: 1033. Installation success or error status: 1603.

Any ideas what happened and how to fix this install? Thanks in advance.

Chris

File Attached:

myappsetup.log

Alex_Ronquillo · Post by **Alex_Ronquillo** » Tue Jun 10, 2008 12:39 pm

Make sure you are changing all three GUID's. In Project Settings --> Project: make sure you change "Product Code" and "Upgrades Product with Product Code" GUID's; and in Project Settings --> Project --> Summary: change the "Revision Code" GUID. After that, Try the solutions described at: http://knowledge.macrovision.com/selfse ... &sliceId=1

cjoyce · Post by **cjoyce** » Tue Jun 10, 2008 7:36 pm

Thanks Alejandro. I had missed one of the GUIDs. I was updating both Product and Upgrade GUIDS but not Upgrade Product with this Product ID GUID. It wasn't on the Application Information/Project Properties page where I was doing my editing and I hadn't noticed the Project Settings dialog has additional options. It looks like everything is working now.

By the way, did you really intend to link to an InstallShield KB article?

Have a good day,
Chris

Alex_Ronquillo · Post by **Alex_Ronquillo** » Wed Jun 11, 2008 10:13 am

Chris,

Even though it is an IS article, it perfectly shows the way to clean the computer from temporary files of old installations. Microsoft talks about this error being a permissions error, but I did not think that was your case.