Error running report: servercannot

Friday, March 9, 2012

error when attempting to configure a local distributor

i'm getting the following error message when i attempt to configure my server as a local distributor:

TITLE: Connect to Server

Cannot connect to 9A6375C3046246B.

ADDITIONAL INFORMATION:

Failed to connect to server 9A6375C3046246B. (Microsoft.SqlServer.ConnectionInfo)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

this error is occuring despite the fact that i have the server configured to allow remote connections. can someone please help me troubleshoot this error? thanks.

Try after enabling named pipes by default it is only TCP/IP...

Is it default instance or named instance? if it is named instance try to use portnumber along with server name.

ex: servername\instancename,portnumber

|||

MohammedU wrote:

Try after enabling named pipes by default it is only TCP/IP...
Is it default instance or named instance? if it is named instance try to use portnumber along with server name.
ex: servername\instancename,portnumber

i enabled remote connections to be named pipes only and i'm still getting the same error. i'm using a default instance.|||

check whether the server is Firewall enabled. You need to create exception on port

refer

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

Madhu

|||

Madhu K Nair wrote:

check whether the server is Firewall enabled. You need to create exception on port
refer
http://support.microsoft.com/kb/914277

Madhu

the windows firewall is already disabled. do i still need to create an exception?

|||does anyone from microsoft care to chime in? anyone else?|||

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--

and

-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards

Rishi Maini

|||

Rishi Maini SQL DBA wrote:

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--
and
-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards
Rishi Maini

thanks for replying. the correct query is the following:

use msdb

select srvid

from sys.sysservers

where srvname = '9A6375C3046246B'

the query result is: 0

any other ideas? anyone else care to chime in?

|||i still need help with this issue.

thanks in advance|||i'm going to keep bumping this thread until i get a response from someone with microsoft.|||

Duane Douglas wrote:
i'm going to keep bumping this thread until i get a response from someone with microsoft.

|||

Are you trying to setup through UI or sp?

Have you tried to use "sp_adddistributor"?

If this is an urgent matter, please contact customer support, this is a forum.

Gary

Friday, February 24, 2012

Error trying to connect to Reporting Services

When I try to connect to RS through SQL management I get this...

TITLE: Connect to Server

Cannot connect to UKCINT\UKCAZOSQL.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.2047.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<meta name="StackTrace" content />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300; TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300; TEXT-DECORATION:underline}

</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>An internal error occurred on the report server. See the error log for more details. (rsInternalError) <a href="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInternalError&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.2047.00" target="_blank">Get Online Help</a></li><ul>
<li>Could not load type 'Microsoft.Web.Services.ScriptHandlerFactory'. (c:\inetpub\wwwroot\web.config line 45)</li><ul>
<li>Could not load type 'Microsoft.Web.Services.ScriptHandlerFactory'.</li>
</ul>
</ul>
</ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span>
</body>
</html>
--. (Microsoft.SqlServer.Management.UI.RSClient)

BUTTONS:

I can connect to other services and Reporting Services has worked in the past. I have tried to directly connect through the web browser and it works fine.

Thanks for any suggestions.

I encountered the same error as well. The environment is SQL Server 2005 on Windows 2003 Server. Looking for the cause and a solution.|||

I had this problem also. It turned out I had installed SSRS with an account without enough privilages. I re-installed with a account with higher privilages on the server and it worked.

Hope this helps!

|||The only change I made was we recently installed BizTalk to try it out. I wonder if that did something to cause this problem.|||

I uninstalled the BizTalk and still the same error message. I am getting this message from both the direct RS server and a remote client connecting to the server and now all of our reports on our intranet are getting the same error message.

Should I just reinstall Reporting Services?

The error that I am getting trying to connect from a remote machine is: "No Connection could be made because the target machine actively refused it (server)."

|||

I don't know if I found the solution, however I am now able to connect. What I did is to comment out the following lines in the web.config file that resides in the wwwroot folder for IIS:

<!--

</httpHandlers>

-->

UPDATE: Actually, this did not work. This has allowed my SQL Management Studio to now connect to Reporting Services, but our intranet is giving me more error messages:

The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. Add <add verb="*" path="Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> to the system.web/httpHandlers section of the web.config file.

|||

More information:

This problem is driving me nuts. I checked out the Configure Report Server on another machine and the box next to Initialization is check, however greyed-out. For the server instance that is actually having the problem this box is X'ed out and greyed out even though the application says that this instance has been started.

Friday, March 9, 2012

error when attempting to configure a local distributor

Friday, February 24, 2012

Error trying to connect to Reporting Services

Error running report

Blog Archive

About Me