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 ===
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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?
Answered 01/22/2008 by: VBScab
Red Belt

Please log in to comment
0
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
Answered 01/22/2008 by: bkelly
Red Belt

Please log in to comment
0
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!
Answered 01/27/2008 by: justinSingh
Blue Belt

Please log in to comment
0
If I recall the package is installed through the system account when deploying through SMS.
So it could be a problem with the profile access.
Install with verbose log to find out some more info or was the log info from your first post all you got?
Answered 01/28/2008 by: AngelD
Red Belt

Please log in to comment
0
AngelD - The log I posted up in my first post is the only contents in the log file. I don't know much about what actually is wrong from the log file, but does the "DisableUserInstalls=0" = Yes ? Any ideas would be appreciated.

Thanks alot!
Answered 01/28/2008 by: justinSingh
Blue Belt

Please log in to comment
0
Setting the DisableUserInstalls policy to 1 prevents any per-user installation which doesn't seem to be the case in your situation.
Could you try installing the package through SMS while the user is logged in if not already done?
Is the ALLUSERS property defined?
Try setting it to 1.

Hope it helps
Answered 01/29/2008 by: AngelD
Red Belt

Please log in to comment
0
I know next to nothing about SMS deployment but, from what I've read over recent days, I now know that there's an option to have SMS copy files locally before running the install. That has to be worth a shot, right?
Answered 01/29/2008 by: VBScab
Red Belt

Please log in to comment
0
I also have access to marimba which is giving me the same log file as above. Any thoughts on marimba VBScab?

Thanks in advance!
Answered 01/29/2008 by: justinSingh
Blue Belt

Please log in to comment
0
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!
Answered 01/29/2008 by: justinSingh
Blue Belt

Please log in to comment
0
Marimba copies the files locally to run them - in a similar way to the option in SMS.

You haven't mentioned what the application is - is it a packaged app, or a vendor MSI?

Thanks,

Dunnpy
Answered 01/29/2008 by: dunnpy
Red Belt

Please log in to comment
0
This application is a component part of a bigger application called Teradata Tools and Utilities. I extracted the MSI i'm having problems with (Teradata GSS Client nt-i386) by choosing to do a network install.

Let me know if there is anything you guys want me to try.

Thanks!
Answered 01/29/2008 by: justinSingh
Blue Belt

Please log in to comment
0
it runs fine if I run the package directly and use the /qb command, but won't run with SMS depolyment tool Clearly 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?
Answered 01/30/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity