Permalink
Cannot retrieve contributors at this time
| title | description | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | ms.assetid | author | ms.author |
|---|---|---|---|---|---|---|---|---|---|
|
Report Server Windows Service (MSSQLServer) 107 | Microsoft Docs |
In this error reference page, learn about event ID 107: Report Server Windows Service (SQL Server) cannot connect to the report server database. |
03/14/2017 |
reporting-services |
troubleshooting |
conceptual |
MSSQLServer 107 error |
52b5704b-27f9-400a-a821-d8fa0786afe4 |
maggiesMSFT |
maggies |
Details
| Category | Value |
|---|---|
| Product Name | [!INCLUDEssNoVersion] |
| Event ID | 107 |
| Event Source | Report Server Windows Service |
| Component | [!INCLUDEssRSnoversion] |
| Message Text | Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. |
Explanation
The [!INCLUDEssNoVersion] Report Server service cannot connect to the report server database. This error occurs during a service restart if a connection to the report server database cannot be established. Conditions under which this error occurs include the following:
-
[!INCLUDEssNoVersion] [!INCLUDEssDE] service is not running when the Report Server service starts.
-
The connection to the [!INCLUDEssDE] service fails because remote connections or the TCP/IP protocol is not enabled.
-
The report server database is not configured correctly.
-
The service account is not configured correctly, or the account no longer has permissions on the report server database. This can occur if you do not use the [!INCLUDEssRSnoversion] Configuration tool to set up the account or the report server database.
User Action
Start the [!INCLUDEssDE] service if it is not running and check that remote connections are enabled for TCP/IP protocol.
Use the [!INCLUDEssRSnoversion] Configuration tool to configure the report server database and service account.
Internal-Only
See Also
Configure the Report Server Service Account (Report Server Configuration Manager)
Report Server Configuration Manager (Native Mode)
Start and Stop the Report Server Service
- Remove From My Forums
-
Question
-
Hi,
After reviewing the top related threads I didn’t find what I’m looking for. People either gave up, or shut down the service. I’d like to solve this.
After investigating the problem on my server, I find the Report Server is doing just fine and this appears to be a transient error during boot as the other MSDN threads have indicated; evidently the SQL server is not yet ready when Reporting Services
looks for it.While we could ignore this error, most of us would like to only see errors that are real, otherwise the real errors can get lost in the noise. So,
1) If the Report Server Windows Service were delayed during boot, would that stop the error event from occurring?
2) Assuming the answer to #1 above is yes, how do I delay the Report Server Windows Service?
Thanks.
Best Regards,
Alan
-
Edited by
Thursday, March 6, 2014 4:05 PM
refined question 2 -
Moved by
Sofiya Li
Thursday, March 13, 2014 3:04 AM
the right forums
-
Edited by
Answers
-
Hello,
Basically this error is related to Reporting service trying to connect to the Report Server database
is not available. The following article shows the recommended user actions:http://technet.microsoft.com/en-us/library/aa337324.aspx
Alternatively, you can set the service to start manually, then create a script that run when the computer start (powershell, batch file) and wait for 90 seconds before starting the service using NET START.
On a batch file yo can use the following statement to wait for 90 seconds.
PING 127.0.0.1 -n 1 -w 90000 >NUL
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
-
Marked as answer by
Katherine Xiong
Friday, March 14, 2014 2:15 PM -
Edited by
Alberto MorilloMVP
Friday, March 14, 2014 8:39 PM
-
Marked as answer by
-
I would recommend you to do with windows task scheduler by invoking a at startup option from trigger tab.
You can also schedule email option in the action tab.
On SVRTFS server, create c:RestartReportServer.bat. Include below two lines
ping -n 60 SVRTFS NET START "ReportServer"
You can also invoke these commands using Powershell. In your case its better to call the bat file from taskscheduler
-Prashanth
-
Edited by
Prashanth Jayaram
Thursday, March 6, 2014 8:38 PM -
Proposed as answer by
Katherine Xiong
Thursday, March 13, 2014 3:07 AM -
Marked as answer by
Katherine Xiong
Friday, March 14, 2014 2:16 PM
-
Edited by
-
Hi Alberto and Prashanth,
I wanted to ‘kind of’ close the loop on this post to confirm for others who are looking for an answer to the error.
I haven’t actually incorporated the delayed start using a batch file according to either of your recommendations simply because I need to spend more time studying the process to chose the method I prefer, and also to ensure I do it right
But, in the spirit of your suggestions, I simply began manually starting my servers (which are all VM’s) in a staggered manner to simulate the delay you both suggested.
The errors went away so that was my problem.
Thanks again for your help. Until next time…
Best Regards,
Alan
-
Marked as answer by
Alan Wheeler
Monday, March 24, 2014 3:54 PM
-
Marked as answer by
- Remove From My Forums
-
Вопрос
-
I have been observing repeat error logs in the Event Viewer (Appln Logs) for event ID 107
Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 4/14/2008
Time: 3:22:28 AM
User: N/A
Description: Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
And also found an information in the error log saying that SQL Server Service started successfully immediately after this error occurred.
Is there any known root cause which makes the service restrat often ? How much is this impacting ?
Are there any methods to resolve this ?
I would be happy to get some more information on this.
Thanks.
mssqlserver 107 | Report Server Windows Service (MSSQLServer) 107 | Report Server Windows Service Event ID 107
| Details: | ||
| Product: | SQL Server | |
| Event ID: | 107 | |
| Source: | Report Server Windows Service | |
| Version: | 9.0 | |
| Component: | Reporting Services | |
| Message: | Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. | |
| Explanation:
The SQL Server Report Server service cannot connect to the report server database. This error occurs during a service restart if a connection to the report server database cannot be established. Conditions under which this error occurs include the following:
User Action: Start the Database Engine service if it is not running and check that remote connections are enabled for TCP/IP protocol. |
||
reaction:
https://www.it-weblog.com IT weblog and IT Blog contain articles for computer, network,security ,adsense,Hosting, google,freeware download from IT blog.
| Details | |
| Product: | SQL Server |
| Event ID: | 107 |
| Source: | Report Server Windows Service |
| Version: | 9.0 |
| Component: | Reporting Services |
| Message: | Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. |
| Explanation | |
|
The Report Server Windows service (MSSQLSERVER) cannot connect to the report server database. This error occurs when a service restarts. It occurs if the SQL Server Database Engine service (MSSQLSERVER) is not running when the Report Server Windows service starts. It also occurs if you do not use the Reporting Services Configuration tool to modify the Report Server Windows service account (for example, if you use Services in Administration Tools) and you restart the service. It can also occur if the account used to run the service no longer has permissions on the database. |
|
| User Action | |
|
Always use the Reporting Services Configuration tool to update the Report Server Windows service account. The Reporting Services Configuration tool automatically updates the symmetric key and database connection settings that use the service identity. |
Event id 107 & 119
Discussion in ‘microsoft.public.sqlserver.server’ started by Brian Vind Borgstrøm, Jan 21, 2008.
-
Event id 107 & 119
Hi!
Due upgrade to a fully licensed version of SQL-server 2005 std.(from 180-
days trial) i got some errors:107: Report Server (MSSQLSERVER) cannot connect to the report server
database.
119: Report Server Windows Service (MSSQLSERVER) has not been granted access
to the catalog content.The SQL-server is a part of a Team Foundation server solution.
Any idéeas out there?
Regards, Brian Vind Borgstrom
-
Advertisements
-
Brian
Any errors in Event Viewer?In SQL Configuration Manager start SQL Server Reportin Services . Check , if
you have two databases started with ReportServer….. name?
http://msdn2.microsoft.com/en-us/library/aa337324.aspx -
Advertisements
-
Hi Uri and tnx. for replying.
The only information in the eventlog is the below written.
I only have one database running./Brian
-
Advertisements
- Ask a Question
Want to reply to this thread or ask your own question?
You’ll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
