Unable to Connect to Remote Server
in [Reports]
|
From: michelle on 13 Mar 2006 13:01 This worked for quite some time but now it is not and we can't find anything that has changed. We can browse to /ReportServer and get to the folders and generate the reports but if we try to navigate to /Reports/Pages/Folder.aspx We get a red X Error and Unable to connect to the remote server. This is SQL Server 2005 Enterprise Edition on Windows Server 2003. IIS and SQL are both running on this same box. There were some DCOM errors in the event log: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10016 Date: 3/13/2006 Time: 11:11:43 AM User: NT AUTHORITY\NETWORK SERVICE Computer: AFNISQLTEST Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool. But I believe that I have resolved this using dcomcnfg but I'm guessing that it wasn't related because the Reporting Services stuff is still not working. I don't see any other error messages of interest and am not sure what other configuration information to provide. We're supposed to be demo-ing this solution but it's not much of a solution right now. Thanks, Michelle
From: Oleg Yevteyev on 13 Mar 2006 17:15 Well, if you still seeing dcom error messages - that means you still haven't resolved that dcom issue. I just repeat myself from another post: then start dcomcnfg util from the command line, find "netman" under Component Services- My computer-Dcom config and under properties of the "netman" (Launch and activation permissions) grant local launch and local activation permissions to "NETWORK SERVICE". Try it and see how it works after that - at least dcom errors should disappear. That could narrow out any other problems. --------------------- Oleg Yevteyev, San Diego, CA It is OK to contact me with a contracting opportunity. "myfirstname"001atgmaildotcom. Replace "myfirstname" with Oleg. -------------------- "michelle" <michelle(a)nospam.com> wrote in message news:eCVrsgsRGHA.4792(a)TK2MSFTNGP14.phx.gbl... > This worked for quite some time but now it is not and we can't find > anything > that has changed. We can browse to /ReportServer and get to the folders > and > generate the reports but if we try to navigate to > /Reports/Pages/Folder.aspx > We get a red X Error and Unable to connect to the remote server. > > This is SQL Server 2005 Enterprise Edition on Windows Server 2003. IIS and > SQL are both running on this same box. > > There were some DCOM errors in the event log: > > Event Type: Error > Event Source: DCOM > Event Category: None > Event ID: 10016 > Date: 3/13/2006 > Time: 11:11:43 AM > User: NT AUTHORITY\NETWORK SERVICE > Computer: AFNISQLTEST > Description: > The application-specific permission settings do not grant Local Activation > permission for the COM Server application with CLSID > {BA126AD1-2166-11D1-B1D0-00805FC1270E} > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security > permission can be modified using the Component Services administrative > tool. > > But I believe that I have resolved this using dcomcnfg but I'm guessing > that > it wasn't related because the Reporting Services stuff is still not > working. > I don't see any other error messages of interest and am not sure what > other > configuration information to provide. We're supposed to be demo-ing this > solution but it's not much of a solution right now. > > Thanks, > > Michelle > >
From: michelle on 13 Mar 2006 23:16 Thanks, I did eliminate the DCOM errors earlier today - I found a KB article. But, this did not resolve our issue. I don't have much to go on other than this: Event Type: Information Event Source: WinHttpAutoProxySvc Event Category: None Event ID: 12517 Date: 3/13/2006 Time: 9:30:32 PM User: N/A Computer: AFNISQLTEST Description: The description for Event ID ( 12517 ) in Source ( WinHttpAutoProxySvc ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt.. I'm not sure if this has anything to do with our issue or not either! I overlooked it earlier b/c it is of type 'Information' but 'Unable to Connect to Remote Server' is not helping me either. The WinHttpAutoProxySvc messages do not seem to correspond with launching the Reporting Services website and getting the 'Unable to Connect...' message. Any chance that this could have anything to do with 'trust for delegation' in AD or some other DNS/Domain Configuration stuff? We're told that everything is set up correctly on that side but am open to suggestions. If we don't resolve this on Tuesday, we'll likely be reinstalling or contacting MS. Regardless, we'll be noting this issue in our recommendation to proceed (or not to proceed) with 2005. "Oleg Yevteyev" <myfirstname001atgmaildotcom> wrote in message news:OcMbzuuRGHA.5092(a)TK2MSFTNGP11.phx.gbl... > Well, if you still seeing dcom error messages - that means you still > haven't resolved that dcom issue. > I just repeat myself from another post: > > then start dcomcnfg util from the command line, find "netman" under > Component Services- My computer-Dcom config and under properties of the > "netman" (Launch and activation permissions) grant local launch and local > activation permissions to "NETWORK SERVICE". > > Try it and see how it works after that - at least dcom errors should > disappear. > That could narrow out any other problems. > > > --------------------- > Oleg Yevteyev, > San Diego, CA > It is OK to contact me with a contracting opportunity. > "myfirstname"001atgmaildotcom. > Replace "myfirstname" with Oleg. > -------------------- > > "michelle" <michelle(a)nospam.com> wrote in message > news:eCVrsgsRGHA.4792(a)TK2MSFTNGP14.phx.gbl... >> This worked for quite some time but now it is not and we can't find >> anything >> that has changed. We can browse to /ReportServer and get to the folders >> and >> generate the reports but if we try to navigate to >> /Reports/Pages/Folder.aspx >> We get a red X Error and Unable to connect to the remote server. >> >> This is SQL Server 2005 Enterprise Edition on Windows Server 2003. IIS >> and >> SQL are both running on this same box. >> >> There were some DCOM errors in the event log: >> >> Event Type: Error >> Event Source: DCOM >> Event Category: None >> Event ID: 10016 >> Date: 3/13/2006 >> Time: 11:11:43 AM >> User: NT AUTHORITY\NETWORK SERVICE >> Computer: AFNISQLTEST >> Description: >> The application-specific permission settings do not grant Local >> Activation >> permission for the COM Server application with CLSID >> {BA126AD1-2166-11D1-B1D0-00805FC1270E} >> to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security >> permission can be modified using the Component Services administrative >> tool. >> >> But I believe that I have resolved this using dcomcnfg but I'm guessing >> that >> it wasn't related because the Reporting Services stuff is still not >> working. >> I don't see any other error messages of interest and am not sure what >> other >> configuration information to provide. We're supposed to be demo-ing this >> solution but it's not much of a solution right now. >> >> Thanks, >> >> Michelle >> >> > >
From: michelle on 14 Mar 2006 09:00 I logged on to the server and reviewed these WinHTTPProxy events and it doesn't seem like there is a problem. First I see that it was sent a start control, then that it has entered the running state, then that it has been idle for 15 minutes and will be shut down, that it has suspended operation, and finally that it has entered the stopped state. This article explains this service: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winhttp/http/winhttp_autoproxy_support.asp. I used proxycfg.exe to set the proxy settings to the same as my current user (after configuring that in IE correctly). This had no impact on my ability to access http://afnisqltest/Reports/Pages/Folder.aspx and I can still get to: http://afnisqltest/Reportserver and browse the directory/run reports just fine. Still need help! "michelle" <michelle(a)noemail.com> wrote in message news:OFP9p4xRGHA.1576(a)tk2msftngp13.phx.gbl... > Thanks, I did eliminate the DCOM errors earlier today - I found a KB > article. But, this did not resolve our issue. > > I don't have much to go on other than this: > > Event Type: Information > Event Source: WinHttpAutoProxySvc > Event Category: None > Event ID: 12517 > Date: 3/13/2006 > Time: 9:30:32 PM > User: N/A > Computer: AFNISQLTEST > Description: > The description for Event ID ( 12517 ) in Source ( WinHttpAutoProxySvc ) > cannot be found. The local computer may not have the necessary registry > information or message DLL files to display messages from a remote computer. > The following information is part of the event: The event log file is > corrupt.. > > I'm not sure if this has anything to do with our issue or not either! I > overlooked it earlier b/c it is of type 'Information' but 'Unable to Connect > to Remote Server' is not helping me either. > > The WinHttpAutoProxySvc messages do not seem to correspond with launching > the Reporting Services website and getting the 'Unable to Connect...' > message. > > Any chance that this could have anything to do with 'trust for delegation' > in AD or some other DNS/Domain Configuration stuff? We're told that > everything is set up correctly on that side but am open to suggestions. > > If we don't resolve this on Tuesday, we'll likely be reinstalling or > contacting MS. Regardless, we'll be noting this issue in our recommendation > to proceed (or not to proceed) with 2005. > > > > "Oleg Yevteyev" <myfirstname001atgmaildotcom> wrote in message > news:OcMbzuuRGHA.5092(a)TK2MSFTNGP11.phx.gbl... > > Well, if you still seeing dcom error messages - that means you still > > haven't resolved that dcom issue. > > I just repeat myself from another post: > > > > then start dcomcnfg util from the command line, find "netman" under > > Component Services- My computer-Dcom config and under properties of the > > "netman" (Launch and activation permissions) grant local launch and local > > activation permissions to "NETWORK SERVICE". > > > > Try it and see how it works after that - at least dcom errors should > > disappear. > > That could narrow out any other problems. > > > > > > --------------------- > > Oleg Yevteyev, > > San Diego, CA > > It is OK to contact me with a contracting opportunity. > > "myfirstname"001atgmaildotcom. > > Replace "myfirstname" with Oleg. > > -------------------- > > > > "michelle" <michelle(a)nospam.com> wrote in message > > news:eCVrsgsRGHA.4792(a)TK2MSFTNGP14.phx.gbl... > >> This worked for quite some time but now it is not and we can't find > >> anything > >> that has changed. We can browse to /ReportServer and get to the folders > >> and > >> generate the reports but if we try to navigate to > >> /Reports/Pages/Folder.aspx > >> We get a red X Error and Unable to connect to the remote server. > >> > >> This is SQL Server 2005 Enterprise Edition on Windows Server 2003. IIS > >> and > >> SQL are both running on this same box. > >> > >> There were some DCOM errors in the event log: > >> > >> Event Type: Error > >> Event Source: DCOM > >> Event Category: None > >> Event ID: 10016 > >> Date: 3/13/2006 > >> Time: 11:11:43 AM > >> User: NT AUTHORITY\NETWORK SERVICE > >> Computer: AFNISQLTEST > >> Description: > >> The application-specific permission settings do not grant Local > >> Activation > >> permission for the COM Server application with CLSID > >> {BA126AD1-2166-11D1-B1D0-00805FC1270E} > >> to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security > >> permission can be modified using the Component Services administrative > >> tool. > >> > >> But I believe that I have resolved this using dcomcnfg but I'm guessing > >> that > >> it wasn't related because the Reporting Services stuff is still not > >> working. > >> I don't see any other error messages of interest and am not sure what > >> other > >> configuration information to provide. We're supposed to be demo-ing this > >> solution but it's not much of a solution right now. > >> > >> Thanks, > >> > >> Michelle > >> > >> > > > > > >
From: michelle on 14 Mar 2006 12:33
Found log file which contains more details about the error (see below). Would the fact that I can't browse to the website from the server using http:\\localhost be related to this at all? w3wp!ui!7!3/14/2006-11:30:01:: e ERROR: Unable to connect to the remote server w3wp!ui!7!3/14/2006-11:30:01:: e ERROR: HTTP status code --> 500 -------Details-------- 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 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) 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.ReportingServices2005.RSConnection.GetSecureMethods() at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods() at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname) at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection() at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level) at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) w3wp!ui!7!3/14/2006-11:30:04:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() at System.Threading.Thread.Abort(Object stateInfo) at System.Web.HttpResponse.End() at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm) at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal() at System.Threading.Thread.Abort(Object stateInfo) at System.Web.HttpResponse.End() at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm) at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) "michelle" <michelle(a)nospam.com> wrote in message news:eCVrsgsRGHA.4792(a)TK2MSFTNGP14.phx.gbl... > This worked for quite some time but now it is not and we can't find anything > that has changed. We can browse to /ReportServer and get to the folders and > generate the reports but if we try to navigate to /Reports/Pages/Folder.aspx > We get a red X Error and Unable to connect to the remote server. > > This is SQL Server 2005 Enterprise Edition on Windows Server 2003. IIS and > SQL are both running on this same box. > > There were some DCOM errors in the event log: > > Event Type: Error > Event Source: DCOM > Event Category: None > Event ID: 10016 > Date: 3/13/2006 > Time: 11:11:43 AM > User: NT AUTHORITY\NETWORK SERVICE > Computer: AFNISQLTEST > Description: > The application-specific permission settings do not grant Local Activation > permission for the COM Server application with CLSID > {BA126AD1-2166-11D1-B1D0-00805FC1270E} > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security > permission can be modified using the Component Services administrative tool. > > But I believe that I have resolved this using dcomcnfg but I'm guessing that > it wasn't related because the Reporting Services stuff is still not working. > I don't see any other error messages of interest and am not sure what other > configuration information to provide. We're supposed to be demo-ing this > solution but it's not much of a solution right now. > > Thanks, > > Michelle > > |