One of the Updates released on that date is the KB 2716440 http://support.microsoft.com/kb/2716440 which resolves a vulnerability in the SQL server. To make sure that this update specifically caused this behavior. I uninstalled this update and after that I was able to start the SRSS (Reporting services) without any problem.
This issue could occur by a missing registry key and a common solution to such problem is to add this key as follows:
- Open Regedit on the Problematic Server
- Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- In the Right Pane create the following Key (If not already created)
- Value: DWORD (32-bit)
- Name: ServicesPipeTimeout
- Value Data, Click Decimal and type 60000 (Not less than 60000)
- Reboot the server
After reboot the SQL Server Reporting services was started normally without any problem.
0 comments:
Post a Comment