[Company Logo Image] 

Home Up Contents Coffee Break Credits Glossary Links Search

 
w3wp.exe (0x1B08)

 

 

Home
Analysis Services
Azure
CLR Integration
High Availability
Open Source
Security
SQL Server 2008
SQL Server 2012
SQL Server 2014
SQL Server 2016
Tips
Troubleshooting
Tuning

w3wp.exe (0x1B08).


Applies to: SQL Server 2008 R2 Enterprise Edition, SharePoint Server 2010.
 

Problem Description.
 

The SharePoint Farm administrator at my job told me one morning that he was receiving errors on SharePoint 2010 about SQL Server Reporting Services. He shared with me the following entries he found on SharePoint logs:

12/30/2013 07:53:41.67 w3wp.exe (0x1B08) 0x1AC8 SQL Server Reporting Services SOAP Client Proxy 0000 High Exception encountered for SOAP method GetSystemProperties: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.XXX.XXX.XXX:80 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) --- End of inner exception stack trace --- at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SetConnectionProtocol() at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper... 4c0cd160-82b6-4d8c-ab78-f25d9898c557
12/30/2013 07:53:41.67* w3wp.exe (0x1B08) 0x1AC8 SQL Server Reporting Services SOAP Client Proxy 0000 High ...`1.ExecuteMethod(Boolean setConnectionProtocol) 4c0cd160-82b6-4d8c-ab78-f25d9898c557

12/30/2013 07:53:44.91 w3wp.exe (0x1B08) 0x1AC8 SQL Server Reporting Services HTTP Redirector aaaf High A WebException occured System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.XXX.XXX.XXX:80 at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at Microsoft.ReportingServices.SharePoint.Soap.RSBaseHttpHandler.AsyncGetResponse(HttpWebRequest request, HttpContext context) at Microsoft.ReportingService... 6242a58d-04c8-4323-a2ca-e667cfd83864
12/30/2013 07:53:44.91* w3wp.exe (0x1B08) 0x1AC8 SQL Server Reporting Services HTTP Redirector aaaf High ...s.SharePoint.Soap.ReportBuilderHttpHandler.<>c__DisplayClass3.<GetRelayResponse>b__0() at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c__DisplayClass1.<Run>b__0(Object state) at System.Security.SecurityContext.Run(SecurityContext securityContext, ContextCallback callback, Object state) at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.Run(ContextBody callback) at Microsoft.ReportingServices.SharePoint.Soap.ReportBuilderHttpHandler.GetRelayResponse(HttpWebRequest relayRequest, HttpRequest clientRequest, HttpContext context) at Microsoft.ReportingServices.SharePoint.Soap.RSBaseHttpHandler.ProcessRequest(HttpContext context) 6242a58d-04c8-4323-a2ca-e667cfd83864.


Cause.

The SQL Server Reporting Services (MSSQLSERVER) service was not started.

The SharePoint administrator tried to start the service using SQL Server Configuration Manager but the service did not install successfully and the following errors were logged on the system logs on Event Viewer:

Log Name: System
Source: Service Control Manager
Date: 1/2/2014 10:18:44 AM
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: spserver.domain1.com
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.

Log Name: System
Source: Service Control Manager
Date: 1/2/2014 10:18:44 AM
Event ID: 7009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: spserver.domain1.com.do
Description:
A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.



Solution.


We opened Reporting Services Configuration Manager on the database server (using Windows Start menu) and performed the following steps:

1. On the Reporting Services Configuration Connection dialog, we provided the name of the report server instance name to configure.

2. On the left side panel, we make a click on the Service Account option, and then provided proper credentials (account and password) for the Reporting Services service account.

3. On the left side panel, we clicked on the name of the server (SPSERVER\MSSQLSERVER in our scenario) adn started the Reporting Service service by clicking on the Start button on the right side.



 

 

.Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.