June 20, 2011 at 12:19 pm
Just curious (as well as soliciting input on this) if anyone else had a SQL 2008 R2 (x64 in our case) instance go down or become unusable after the Security Update for Windows 2008 R2 KB 2525694 ran on the server hosting the SQL instance?
I'm currently awaiting a call from MS Support on this but I did try manually troubleshooting/fixing earlier and what I have foudn out sao far is that it looks like the Windos Update ran a SQL Server specific update (even though we do not have those kinds of updates enabled in our Windows Updates per our IT guys) which failed to cmplete when it ran the post script updates against the system DB's which is why we get the below now wehn trying to connect via SSMS:
Login failed for 'sa'. Reason: Server is in script upgrade mode. Only Administartor can connect at this time.
I can enable the 902 Trace Flag and restart her and get connected to examine everything and I found in the error log that the exact failure entry had the message (from the SQL error logs):
SQL Server blocked access to procedure 'sys.xp_qv' of component 'Agent XPs' because this component is turned off as part of the security configuration for...'
From what I can tell it looks like this is realted to "SQL 2008 R2 security hotfix 2494088 fails if UCP installed " whici is reported at Microsoft Connect (http://connect.microsoft.com/SQLServer/feedback/details/675794/sql-2008-r2-security-hotfix-2494088-fails-if-ucp-installed"> http://connect.microsoft.com/SQLServer/feedback/details/675794/sql-2008-r2-security-hotfix-2494088-fails-if-ucp-installed )
I've followed the suggested fix steps in that item but I can't get the post update scritps to run because the attempt to enable the Agent XPs fails.
Has anyone else had to deal with this and if so were you able to get past where I am stuck?
NOTE: Due to less critcial issues we have no usable backup of the master DB for this particular SQL Server Instance and so my options are limited to working with teh existing master DB which thankfully shows no problems when runnig DBCC CheckDB against it or against msdb.
Kindest Regards,
Just say No to Facebook!June 20, 2011 at 12:22 pm
Additional note:
The SQL Server instance in question has UCP which appears to be what causes all the trouble. If disabling UCP on the server can enable this pain to go away let me know because we don't need UCP on this.
Thanks
Kindest Regards,
Just say No to Facebook!Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply