error 1603
Hi guys, I have a application that gives me error 1603 when I ty to deploy it using SMS. I did some research and found that by turning on verbose logging i would be able to find out what the problem was, but I'm not a very good troubleshooter so can anyone tell me what the problem is by looking at the log file below.
Thanks!
=== Verbose logging started: 1/21/2008 22:28:06 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:\program files\marimba\Castanet Tuner\lib\jre\bin\java.exe ===
MSI (c) (34:D8) [22:28:06:849]: Resetting cached policy values
MSI (c) (34:D8) [22:28:06:849]: Machine policy value 'Debug' is 0
MSI (c) (34:D8) [22:28:06:849]: ******* RunEngine:
******* Product: {BC455A2E-803D-4CF3-8592-BBB4F73AC1FC}
******* Action:
******* CommandLine: **********
MSI (c) (34:D8) [22:28:06:849]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (34:D8) [22:28:06:859]: Grabbed execution mutex.
MSI (c) (34:D8) [22:28:06:859]: Cloaking enabled.
MSI (c) (34:D8) [22:28:06:859]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (34:D8) [22:28:06:859]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (08:EC) [22:28:06:879]: Grabbed execution mutex.
MSI (s) (08:88) [22:28:06:879]: Resetting cached policy values
MSI (s) (08:88) [22:28:06:879]: Machine policy value 'Debug' is 0
MSI (s) (08:88) [22:28:06:879]: ******* RunEngine:
******* Product: {BC455A2E-803D-4CF3-8592-BBB4F73AC1FC}
******* Action:
******* CommandLine: **********
MSI (s) (08:88) [22:28:06:879]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (08:88) [22:28:06:879]: MainEngineThread is returning 1605
MSI (c) (34:D8) [22:28:06:889]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (34:D8) [22:28:06:889]: MainEngineThread is returning 1605
=== Verbose logging stopped: 1/21/2008 22:28:06 ===
Thanks!
=== Verbose logging started: 1/21/2008 22:28:06 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:\program files\marimba\Castanet Tuner\lib\jre\bin\java.exe ===
MSI (c) (34:D8) [22:28:06:849]: Resetting cached policy values
MSI (c) (34:D8) [22:28:06:849]: Machine policy value 'Debug' is 0
MSI (c) (34:D8) [22:28:06:849]: ******* RunEngine:
******* Product: {BC455A2E-803D-4CF3-8592-BBB4F73AC1FC}
******* Action:
******* CommandLine: **********
MSI (c) (34:D8) [22:28:06:849]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (34:D8) [22:28:06:859]: Grabbed execution mutex.
MSI (c) (34:D8) [22:28:06:859]: Cloaking enabled.
MSI (c) (34:D8) [22:28:06:859]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (34:D8) [22:28:06:859]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (08:EC) [22:28:06:879]: Grabbed execution mutex.
MSI (s) (08:88) [22:28:06:879]: Resetting cached policy values
MSI (s) (08:88) [22:28:06:879]: Machine policy value 'Debug' is 0
MSI (s) (08:88) [22:28:06:879]: ******* RunEngine:
******* Product: {BC455A2E-803D-4CF3-8592-BBB4F73AC1FC}
******* Action:
******* CommandLine: **********
MSI (s) (08:88) [22:28:06:879]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (08:88) [22:28:06:879]: MainEngineThread is returning 1605
MSI (c) (34:D8) [22:28:06:889]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (34:D8) [22:28:06:889]: MainEngineThread is returning 1605
=== Verbose logging stopped: 1/21/2008 22:28:06 ===
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
First, is it 1603 or 1605 you're after?
Second, ever heard of Google? The search term (including the quotes)
"windows installer" +1605
was useful, as was substituting '1603' for '1605'.
http://consumer.installshield.com/kb.asp?id=Q108474
http://consumer.installshield.com/kb.asp?id=Q111019
Is it me? Is it?
Second, ever heard of Google? The search term (including the quotes)
"windows installer" +1605
was useful, as was substituting '1603' for '1605'.
http://consumer.installshield.com/kb.asp?id=Q108474
http://consumer.installshield.com/kb.asp?id=Q111019
Is it me? Is it?
Posted by:
bkelly
16 years ago
Log files can be a bit overwhelming if you are looking at them for the first time. And the dialog may report one error and then the log file will show another. Error 1603 in particular is pretty much no help. I like to see the questions being asked here even when the answer is just a link elsewhere so it is that much easier to find. There is also a community contributed database of Windows Installer errors maintained right here at AppDeploy: http://www.appdeploy.com/msierrors/
1603: http://itninja.com/question/help-with-msi-131
1605: http://itninja.com/question/help-with-msi-1319
1603: http://itninja.com/question/help-with-msi-131
1605: http://itninja.com/question/help-with-msi-1319
Posted by:
justinSingh
16 years ago
Alright guys, so i've tried everything from setting the REINSTALLMODE="omus" to even deleting the REINSTALLTEXT and verifying that I do have the install script it requires to work. What confuses me about this vendor package is that it runs fine if I run the package directly and use the /qb command, but won't run with SMS depolyment tool. Any suggestions you guys may have would be higly appreciated.
Thanks in advance!
Thanks in advance!
Posted by:
AngelD
16 years ago
Posted by:
justinSingh
16 years ago
Posted by:
AngelD
16 years ago
Posted by:
anonymous_9363
16 years ago
Posted by:
justinSingh
16 years ago
Posted by:
justinSingh
16 years ago
AngelD - I tried having the user log on while receiving the push and I got the same result. I also took a look at the 1033.mst provided by the vendor and ALLUSERS property is set to 1 so I went ahead and pushed out the package with the 1033.mst and I got the same result. Can there be a CA some where that may prevent me from deploying the package?
Thanks for the help!
Thanks for the help!
Posted by:
dunnpy
16 years ago
Posted by:
justinSingh
16 years ago
Posted by:
anonymous_9363
16 years ago
it runs fine if I run the package directly and use the /qb command, but won't run with SMS depolyment toolClearly SMS thinks the package is already installed. Run a process or registry monitor while the package deployment is attempted. That will show you if the Product Code is being interrogated and returned.
As I believe I've mentioned, I don't know SMS at all but I'm thinking...do packages have to be 'registered' in SMS? Could it have picked up the product code from another package which *is* already installed?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.