Reporting Service can't start - Event ID 107

Today, one of my clients reported that, the reporting service cannot started.
They didn't change anything and database service is running fine.

Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 12/10/2009
Time: 11:53:21 PM
User: N/A
Computer: ABC
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/27/2008
Time: 7:26:24 PM
User: N/A
Computer: PRODB
Description:
The SQL Server Reporting Services (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The Reporting Services logs mostly just repeat that "The Report Server Windows service 'ReportServer' is not running." ...


This issue was caused by a windows hotfix - KB948109, it changed Windows Internal Database (WYukon) security settings that could make the service start timeout.

There are 2 ways can make it resolved.

        Solution A: Use Add/Remove to uninstall this hotfix KB948109.

        Solution B: Change the registry to increase the timeout value.

        We suggest Solution B.

 

To increase the timeout value in the registry, follow these steps:

  1. Start Registry Editor (Regedit.exe).
  2. To change the value data for the ServicesPipeTimeout DWORD value to 60000 in the Control key, follow these steps:
    1. Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet

    1. Click the Control subkey
    2. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
    3. Click Decimal.
    4. Type 60000, and then click OK.
  1. If the ServicesPipeTimeout value is not available, add the new DWORD value, and then set its value data to 60000 in the Control key. To do so, follow these steps:
    1. Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet

    1. Click the Control subkey.
    2. On the Edit menu, point to New, and then click DWORD Value.
    3. Type ServicesPipeTimeout, and then press ENTER.
    4. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
    5. Click Decimal.
    6. Type a value of 60000, and then click OK.

      The value is 60000 milliseconds and is equivalent to 60 seconds or to one minute.

Note This change does not take effect until the computer is restarted

4 Comments

Hi
Are you interested in building af new HMC 4.5 environment for our company?

Looking for a job?

hi
i want to know where do u live
we are building new HMC 4.5 for ISP

email me plz
person_hk@hotmail.com

Hi Hussein,
I am living in Shenzhen city, Guangdong province, China

Cheers,
Randy

Leave a comment

Recent Entries

  • Lync Server 2010 发布架构报错

    昨天想试试在现有的 OCS 2007 R2 的基础上部署 Lync Server 2010 试试看,装好 Topology Builder 之后,新建了一个拓扑,然后把该填的都填了,发布的时候老是报SQL错,很是郁闷,后来终于在log中找到了错误原因:  Script result: ERROR_VALIDATE_BAD_SQL_VERSION Error: Script failed (code "ERROR_VALIDATE_BAD_SQL_VERSION") when installing "CentralMgmtStore" on "LyncServer01.mail2any.local"....

  • 使用 URL Rewrite 重定向 Http 请求至 Https

    公司部署了个新的 IIS 站点,需要强制在 Https 下面访问,但是又不希望关掉80端口的 Http 请求,这样对用户体验来讲不好,最好是能强制所有的 Http 请求都会被重定向到 Https 上面去,显然, IIS 自带的 "HTTP Redirect" 已经不能满足这个需求,我们这里使用 IIS 7.0 下面的重定向扩展 URL Rewrite Module 来做。1. http://www.iis.net/download/URLRewrite 到这里下载,有分...

  • How to remember your OC and Outlook password

    How to make your computer remember your Microsoft Communicator 2007 R2 and Outlook 2007 password (如何让你的电脑在非域环境中记住 OC 2007 R2 和 Outlook 的密码)我们知道,在域的环境中,使用 OC 和 Outlook...

  • 微软 CRM 2011 Beta 快速安装图解

    微软在9月17日在网站上放出了 CRM 2011 (也就是CRM5.0)的 beta 版本,我就先来个简单的快读安装图解,一睹为快,下个月会写点新版 CRM 的使用感受。 下载: Microsoft Dynamics CRM 2011 Beta Microsoft Dynamics CRM 2011 Software Development Kit (SDK)Microsoft Dynamics CRM 2011...

  • 升级到 Exchange 2010 SP1 后出现的2个小问题

    今天有空把所有的 Exchange 服务器从 2010 RTM 升级到了 2010 SP1 了, 升级完了后发现了2个小问题: OWA打开正常,但是点到 ECP 的时候报 403 访问拒绝错误 某台 Exchange 打开 EMS 时报错如下: [server.mydomain.local] Connecting to remote server failed...

Close