MSI error starting SQL service
Hello. I've been doing deployments for quite some time SMS 2003/SCCM 2007, currently back in SMS 2003 until we migrate shortly, so I was tasked with deploying an MSI that vendor allowed us to modify to include SQL service acct/pw and some basic info...
a little background on me....
I'm NOT a 're-packager' but learning that aspect (used to having a whole team available for that while I focused on heavy deployment, reporting, troubleshooting deployments etc) but I'm learning the re-packaging side on the fly now even though I've worked with our packagers very closely for quite some time.
my msi deployment is successful on two and failed on two, same XP SP3 OS for all windows installer on the failed two appears to be working fine....I get 1603 in SMS logs, but actually a 1920 error in the event viewer saying it cannot start the service....the SQL creds are there as it worked fine for 2 of the test pcs...
SMS using the local system acct for install running as admin....tried going back in and allowing user interaction in case somewhere it required this, pretty much changed every setting trying to get those two to work but cannot figure out the difference on those and the two successes. I'm new to this company and still getting acclimated to their environment, builds etc...so it's like being half-blind. :-)
Any thoughts?
a little background on me....
I'm NOT a 're-packager' but learning that aspect (used to having a whole team available for that while I focused on heavy deployment, reporting, troubleshooting deployments etc) but I'm learning the re-packaging side on the fly now even though I've worked with our packagers very closely for quite some time.
my msi deployment is successful on two and failed on two, same XP SP3 OS for all windows installer on the failed two appears to be working fine....I get 1603 in SMS logs, but actually a 1920 error in the event viewer saying it cannot start the service....the SQL creds are there as it worked fine for 2 of the test pcs...
SMS using the local system acct for install running as admin....tried going back in and allowing user interaction in case somewhere it required this, pretty much changed every setting trying to get those two to work but cannot figure out the difference on those and the two successes. I'm new to this company and still getting acclimated to their environment, builds etc...so it's like being half-blind. :-)
Any thoughts?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
12 years ago
I'd be running ProcMon while you try to start the service. You'll get more information about what's actually happening.
Posted by:
DGD_SCCM
12 years ago
Thanks much for the response. I figured it out shortly after. But I'll use your suggestion going forward in addition to enabling logging as I have been. :-)
Posted by:
anonymous_9363
12 years ago
I figured it out shortly after.It's a secret, right? No sense in sharing your solution with anybody else, eh?
Posted by:
DGD_SCCM
12 years ago
My apologies!I was heading out the door from work and wanted to reply really quick and figured I'd come back to elaborate.
Since it was a 1920 error, the account did not have permissions to actually start the service that was being installed to communicate with the SQL database. So I put it in the local admin group and it ran successfully.
I would have thought that SMS running it with system account, would have had priveleges to start the service?? I guess not.
Thanks for your input though.
Sorry, for not sharing that earlier.
DeAna
Since it was a 1920 error, the account did not have permissions to actually start the service that was being installed to communicate with the SQL database. So I put it in the local admin group and it ran successfully.
I would have thought that SMS running it with system account, would have had priveleges to start the service?? I guess not.
Thanks for your input though.
Sorry, for not sharing that earlier.
DeAna
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.