January 21, 2009 at 9:43 am
Hi Mike I'm a little perplexed.. What your saying is that the install chokes but keeps running?
See my installation simply states that database services failed and keeps going. All the rest are a success. But after I start the services manually the verion of the database is SP3 verion 4035. So it appears to fail because it cannot start the service not because it cannot update the sql server instance it appears to be doing that.
Is that how yours is working?
January 21, 2009 at 10:23 am
Well, the database patch fails, but the other components update ok. Much like yours, it looks like the patch tries to start the database service, but fails. Yet, when I start the services after the patch it denotes the correct version number. Looking at the logs (posted above) you can see where the database fails to start. You will also see that nothing happens after the database fails to start execpt for some error messages. I presume that if the database did not start that it did not update the sql data dictionary. I see in your logs that it does do some updates, so... that's what has me worried.
January 21, 2009 at 10:30 am
I'm hoping someone smarter than me will stumble accross this post because I still have the production servers to do and I would hate to run into the same issue at that time. I thought the update was occuring and then the services where being stopped to copy some files. I assumed the event when it attempts to restart the service was simply an after affect of the patch. I assumed since the patch could not start the service that it would say it failed because of the service not starting not because it couldn't actually patch part of the server.
But when I reinstall SP3 over a server that failed and then i install again it appears to identify the database instance as SP3. Isn't that enough proof?
I'm hoping someone comes through with some input sorry i cannot be of more help.
January 21, 2009 at 12:44 pm
I'm in the same boat as you sounds like. I have some more experienced folks looking at it right now. Guess what? They got the same errors I did!
You work at Randolph as a contractor? I'm guessing as your username for this forum uses the same format as my email address, with the .ctr on the end.
January 22, 2009 at 8:41 pm
Little update. At our site they are deploying the MacAfee intrusion detection software on our servers. An initiative called HBSS (forget what it stands for). So far we are seeing a connection between having the MacAfee intrusion installed and the ability or lack there of for installing sp3. Even trying to uninstall sql and reinstall was giving errors. So... we are currently looking on how to remove the MacAfee intrusion detection software and/or associated windows policy to see if we can do sp3. By the way, those servers that did not have MacAfee installed, sp3 installed fine.
January 24, 2009 at 8:54 am
Sorry, meant to get right back on this thread, insane work week however....
The AV software could certainly cause this. Have you attempted to just disable that prior to install, rather than having to uninstall the entire suite?
MacAfee could be thinking that you are some kind of an automated process that's trying to run a new process related to some kind of virus/trojan/spyware item.
February 5, 2009 at 10:14 am
I had the same SP3 Install problems on some of my test servers. I just realized that I should have disabled my Server Level Trigger. I noticed in my audit log that the install tried to create, use and then drop the following account '##MS_AgentSigningCertificate##'. Do you have any server level triggers on your server??
February 13, 2009 at 8:12 am
Going back to amira's original post: "MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly."
Check to see if the mssqlsystemresource.ldf is in the proper location. If you have placed your data and log files on a different drive than the installer expects, your (MSSQLSERVER) service will not find the right .ldf at startup.
DK
February 13, 2009 at 11:08 pm
I do recall reading a thread on moving the main mdf files. I did have to move some of my other database files from their original location, but not any of the main db files (master, etc...). Currently we are looking into the McAfee intrusion detection software, looks like it may be preventing the application of SP3. Air Force was kind enough to push it down to our servers, better then any virus.....
March 25, 2009 at 6:09 pm
Did you ever get this resolved? I have been struggling with this problem on my cluster for over a month now.
March 26, 2009 at 12:00 pm
Hi Michael, Funny finding you on this site. I'm having the same issue. I also have McAfee running. Did you ever resolve this. Would uninstalling McAfee and then reinstalling after the SP3 update help?
March 26, 2009 at 8:33 pm
Yes, we found that we had to uninstall the McAfee Intrusion detection. Though... our sys admins had some issues (don't know all the details) with the uninstall. Somehow the server got dropped from the domain, but they were able to add it again. We have only done one so far and hope to do the rest of your systems/databases over the next few months.
March 26, 2009 at 8:35 pm
Oh, one more thing, we have not reinstalled McAfee yet.
March 26, 2009 at 8:40 pm
I got it installed today. In my case it was the Report Services in SQL. When going to the install log file it showed that the SP3 had installed on everything but report servces. Report Services was not running and not configured properly. Once it was up and running SP3 installed without a problem. I'm in the middle of backing everything up before rebooting. Now if I could get the rest of problems fixed. Lol! Thansk for the info.
March 28, 2009 at 5:12 pm
Just for clarification, did you uninstall McAfee intrusion detection, install SP3, then reinstall McAfee?
Viewing 15 posts - 16 through 30 (of 31 total)
You must be logged in to reply to this topic. Login to reply