Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
 Posted - 2005-09-21 : 13:39:40
|
| Have since recovered. Has anyone experienced similar problem and can provide details re: what might have happened. Pls. don't ask why the update was pushed without my knowledge. Oh the absurdity of it all. I have disabled patchlink.====================================================at approx. 11:29am 9/21/05 both my servers, along with my PC, simultaneously rebooted without my intervention. It was discovered that MS patch 891861 had been auto-pushed to these machines from central servers.following the auto-reboot, both servers failed to start the MSSQLserver service (this is SQL Server 7.0 running on win 2k server), various error message appeared in the error logs but the gist of the messages was that access was being denied on key sql server files and this is why the SQL server service would not start. I eventually updated permissions on the SQL server folders, located on drive C: and D:, giving full control to the same account that starts the MSSQLserver service. Prior to the auto-install of the patch, this account did not have permissions to these folders, nor should it need these permissions since its job is only to start and run the services. Following these permissions updates, the server booted clean and I was able to run my web apps. However, when I tested web connectivity from one of my user's PCs, I saw that db connections were failing for certain pages. I was able to determine that recent permissions updates I had made on specific db objects (stored procedures) had been lost following the unattended patch upgrade, and this is why the users could not access the db via the web. Once I updated permissions, things worked fine. I cannot determine at this time why these permissions setttings were lost. It is possible this happened during database recovery or it could have happened as a result of the patch upgrade. |
|
|
Thrasymachus
Constraint Violating Yak Guru
483 Posts |
Posted - 2005-09-22 : 09:44:43
|
| Ok I won't ask that but I will ask why you have not joined the rest of in the 21st century.====================================================Regards,Sean Roussyaka the merciless black hearted capitalist troublemaker"pimpin ain't easy, but someone has to do it" -- Pimpin Whitefolks(?) |
 |
|
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
Posted - 2005-09-22 : 15:02:24
|
| if you're referring to my use of SQL 7.0, I'm planning the migration, I'll get to it soon, I promise ;-) |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-09-22 : 15:27:04
|
| yeah, you are only ~6 years out of date. :)you might as well hold off until SQL 2005 arrives..-ec |
|
|
|
|
|
|
|
|
MS KB 891861 torpedoed my SQL 7.0!!