Reporting Services Windows Service will not start after applying MS08-052


We have been seeing a few cases where the Windows Service for Reporting Services will not start after applying the following fix:

 

MS08-052: Description of the security update for GDI+ for SQL Server 2005 Service Pack 2 GDR: September 9, 2008

http://support.microsoft.com/kb/954606/

 

You may also see the following in the Application Log:

 

Event 1

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7000

 

The ServiceName service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.

 

Event 2

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7011

 

Description:

Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service.

 

 

There are two flavors of this fix.  The first is a standalone fix for SP2 with the build number of 3073.  The second is included with Cumulative Update 9 for SQL Server 2005 SP2 (http://support.microsoft.com/kb/953752/ – Build 3282).  The issue only appears to be with the 3073 build.

 

If you find yourself in the position of not being able to start the Windows Service after installing this fix, you can try one of the following workarounds.

 

1. Upgrade to CU9.  This issue does not appear to occur with Cumulative Update 9.

2. Increasing the ServicesPipeTimeout to 60 seconds appears to alleviate the issue.  Be aware that this affects all windows services and not just Reporting Services.

 

A service does not start, and events 7000 and 7011 are logged in Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;EN-US;922918

 

3. Uninstall the GDR.  If you are unable to do the above two items, this should get you up and running until you have the time to test the release of CU9.

 

We are investigating the causes of this and hope to have an update in the near future as to the status of this issue.  If you feel you need a resolution to this without doing the options listed above, please create a support incident so that we can work with you towards a resolution.

 

Adam W. Saxton

Support Escalation Engineer

Comments (4)

  1. paul storm says:

    I seem to have this issue with SQL Server 2005 on Windows Server 2008 (Enterprise, x64). I’ve tried extending the key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWaitToKillServiceTimeout from 20000 to 60000, but still without success.

    Would we expect to see this issue on Server 2008?

    Am I changing the correct key?

    thanks,

    Paul

  2. Wolfen says:

    Many thanks! Saved a production machine from being reloaded!

  3. Dhiraj says:

    kindly follow below site to get the answer regarding to sql reporting services.

    answers-free.blogspot.in/…/unable-to-start-sql-server-reporting.html