Sql server 2005 patch

• surya.uppala

  Grasshopper

  Points: 17

  More actions

  August 10, 2009 at 1:48 pm

  #213268

  Hi,

  I am dsperately in need of of help.

  Initially we installed Sql Server 2005 SP2 patch: 'Initial SP2 release which is faulty.

  As a consequence our Maintenance Plans stopped working.

  As suggested on Microsoft website, in order to fix this problem , we installed 'General Distribution Release'(GDR) update which was downloaded from the Microsoft Download Center:: Critical Update for SQL Server 2005 Service Pack 2

  The patch appears to unpack itself and run a number of smaller patch files. One of these is "sqlrun_sql.msp". During it's installation, a Dr. Watson window appears titled "hotfix.exe". The event surrounding this and the crash data can be found in the hotfix.log file attached. The events occur during the period 11/26/2008 10:37:25.764 to 11/26/2008 10:39:37.963

  At the time when the error occurs, an SQL error is logged in the corresponding log file (SQL9_Hotfix_KB933508_sqlrun_sql.msp.log) where it states:

  C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql

  Open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql in Unicode mode

  SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch

  sqlstate=01000, level=0, state=1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.

  SQL_ERROR (-1) in OdbcStatement::execute_batch

  sqlstate=42000, level=16, state=1, native_error=15151, msg=[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.

  sqlstate=42000, level=16, state=1, native_error=15151, msg=[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_memory_grants', because it does not exist or you do not have permission.

  A previous issue with MS SQL server updates (KB918695) suggests an issue with location problems of the master and resource databases (They have checked and this is not our problem.) We are starting to believe that the maintenance plan problem we have observed is to do with an incorrect master or resource database version compared to that which the SQL server is.

  We have checked some file versions after the GDR hotfix and they appear to have been updated OK. We have started the SQL server and so far - so good. The maintenance plan issue still exists and has not changed.

  Could ypu please look into it and give suggestions to get back Maintenance plans working?

  If you need any further information, please let me know.

  Kind Regards,

  Surya U