Иногда случаются проблемы с подключением по FTP. Для того, чтобы оперативно решить такую задачу, необходимо выполнить диагностические меры, описанные ниже.
Проверка режима FTP
Первым делом стоит проверить, какой режим FTP используется. Рекомендуется использовать Пассивный, к примеру в клиенте Filezilla это настраивается во вкладке Редактирование -> Настройки -> FTP
Если изначально режим используется пассивный, то стоит проверить, не блокирует ли соединение локальный брендмауер (фаервол) или антивирус. Для этого банально отключаем поочередно брендмауер и антивирус и подключаемся еще раз. Если проблема осталась актуальной, то проведём диагностику подключения.
Для начала, проверим подключение к серверу через утилиту telnet, в качестве имени сервера указываем название, которое можно посмотреть в личном кабинете в разделе FTP (в нашем случае — это matrix.beget.com).
telnet matrix.beget.com 21
Если все в порядке, то должно будет появиться приглашение сервера, что-то вроде этого:
Connected to matrix.beget.com.
Escape character is '^]'.
220 Welcome to LTD Beget FTP Server 'matrix'
Ошибка Unable to connect to remote host: Connection refused
Означает, что FTP-клиент не может соединиться с сервером. Обычно ошибка выглядит примерно так:
Trying 81.222.215.42...
telnet: Unable to connect to remote host: Connection refused
Как правило, здесь имеют место быть три причины:
- блокировка ftp-подключения брандмауэром (файерволом) или антивирусом Вашего компьютера;
- блокировка вашего внешнего ip-адреса на нашем сервере;
- проблемы на стороне промежуточных узлов (между нашим сервером и вашим компьютером).
Чтобы попробовать определить на каком узле происходит обрыв, нужно сделать трассировку маршрута командой traceroute:
В Mac OS X команда будет выглядеть так:
traceroute matrix.beget.com
Должно появиться примерно следующее:
1 192.168.2.1 (192.168.2.1) 0.253 ms 0.245 ms 0.231 ms
2 beget-i.cust.smartspb.net (80.79.241.141) 0.516 ms 0.511 ms 0.504 ms
3 k12-lak.ra.smartspb.net (185.42.63.18) 0.756 ms 0.753 ms 0.747 ms
4 beget.spb.cloud-ix.net (31.28.18.90) 1.386 ms 1.366 ms 1.371 ms
5 m1.matrix.beget.com (5.101.156.64) 1.367 ms 1.357 ms 1.362 ms
Также стоит пропинговать хост утилитой ping:
ping matrix.beget.com -n 10
Должно появиться примерно следующее:
PING matrix.beget.com (5.101.156.64) 56(84) bytes of data.
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=1 ttl=60 time=1.44 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=2 ttl=60 time=1.44 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=3 ttl=60 time=1.52 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=4 ttl=60 time=1.23 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=5 ttl=60 time=1.56 ms
--- matrix.beget.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.231/1.441/1.562/0.124 ms
Возможно проблема связана с тем, что Ваш внешний IP-адрес заблокирован на сервере, для проверки идем на сайт http://myip.ru/, он отобразит Ваш внешний IP-адрес. Его нужно сообщить технической поддержке, чтобы специалисты проверили, не заблокирован ли указанный IP-адрес на сервере, к которому идет подключение. Лучше всего обратиться, написав тикет из Личного кабинета (раздел «Связь» или «Помощь и поддержка»). В тикете необходимо предоставить вывод команд ping, tracert (traceroute) и внешний IP-адрес, который Вы узнали на сайте http://myip.ru/. Не лишним будет указать также данные, с которыми Вы пытаетесь подключиться, так как зачастую ошибка в подключении кроется в неверно вводимых данных: логин, пароль, имя сервера.
Ошибка 530 Login incorrect
Очень распространённая ошибка «Login incorrect«. В журнале FTP-клиентов она выглядит примерно так:
220 Welcome to LTD Beget FTP Server 'matrix'
USER username
331 Please specify the password.
PASS *******
530 Login incorrect.
Означает эта ошибка то, что передаваемые логин, пароль или сервер ошибочные. В этом случае перепроверьте правильность введённых данных и исправьте ошибку.
Удачной работы! Если возникнут вопросы — напишите нам, пожалуйста, тикет из Панели управления аккаунта, раздел «Помощь и поддержка».
Problem
— Configured Email Notifications
— Unable to send an email when changing an object workflow state
Symptom
Application Log (LogFiles):
Ibm.CognosDM.BusinessLogic.Notification.Email.EmailPublisher —
CDCGN00080E Mail message with subject ‘Report name: Report Name, Object name: Object Name‘ failed to be sent. ? ? ?
System.Net.Mail.SmtpException: Failure sending mail. —>
System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond nnn.nn.n.nnn:25
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 —
Cause
The 2 servers (CDM and SMTP) aren’t able to communicate
Diagnosing The Problem
From the Cognos Disclosure Management server, ping the SMTP server
> ping smtp.server.name
Response will most probably be a ‘timeout expired’
Notice at the bottom of the command and response the IP address. It should match the IP address mentioned in the error log,
Resolving The Problem
Have your IT/Network department investigate the communication configuration between these 2 servers (CDM application server and SMTP (email server))
[{«Product»:{«code»:»SSQK59″,»label»:»Cognos Disclosure Management»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Component»:»Cognos Disclosure Management»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»10.2.1″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]
I’m able to call a 3rd party vendor’s web service from a Windows form program just fine. When I try to call the same web service and web method and same URL from a WCF web service I get the following error:
ExportValuationPolicyNumber:Exception=System.Net.WebException: Unable to connect to the remote server --->
System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed
because connected host has failed to respond 66.77.241.76: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 System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at TFBIC.RCT.WCFWebServices.ExpressLync.ValuationServiceWse.ExportValuationPolicyNumber(String PolicyNumber) in c:SourceTFBIC.RCT.WCFWebServicesTFBIC.RCT.WCFWebServicesWeb ReferencesExpressLyncReference.cs:line 519
at TFBIC.RCT.WCFWebServices.ValuationService.ExportValuationPolicyNumber(String PolicyNumber) in c:SourceTFBIC.RCT.WCFWebServicesTFBIC.RCT.WCFWebServicesValuationService.svc.cs:line 97
I’m basically trying to write a WCF wrapper for the vendor .asmx/WSE3 service. Let’s not get off point — but Microsoft says WCF can call WSE3, but only with SSL turned on, and my vendor — believe it or not — is not allowing SSL connection. So I’mn stuck writing the wrapper so I can call from BizTalk 2009. Right now, I’m testing the wrapper via a Console program.
What can I even do to debug? I’ve added EventLog traces before and after the WCF service where it calls the .asmx service — so I know that’s where it’s blowing (plus the line number in the error above).
I have the following in my web.config:
<microsoft.web.services3>
<diagnostics>
<trace enabled="true"
input="c:inetpubwwwrootwsetracesInputTrace.webinfo"
output="c:inetpubwwwrootwsetracesOutputTrace.webinfo" />
<detailedErrors enabled="true" />
</diagnostics>
</microsoft.web.services3>
and I have given the directory full-access to everyone — yet no trace appears there.
What are some things I can look for or try next to debug this?
In theory «ping» results should not matter, because the website is working from the Windows form program that calls it just fine.
Nevertheless — here is what Ping shows and it looks a little questionable to me:
C:Usersuxnxw01>ping rct.msbexpress.net
Pinging rct.msbexpress.net [66.77.241.56] with 32 bytes of data:
Reply from 10.193.99.5: Destination net unreachable.
Reply from 10.193.99.5: Destination net unreachable.
Request timed out.
Reply from 10.193.99.5: Destination net unreachable.
Ping statistics for 66.77.241.56:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Thanks,
Neal Walters
WireShark analysis
I did run Wireshark — posted some results in comment below. However, after reading it more, it does not always say «Destination Unreachable». But in the case where it’s failing, I never get any databack. I’m still confused what to do next. I have been comparing packets but it’s slow and confusing. For instance, I still haven’t found the key (a specific policyNum) that I am passing in the request packet. I also see a few «Destination Unreachable» statements in the one that worked.
In the one that works, I never see 66.77.241.76, I only see our company’s proxy. But I can’t see anything in the config (or code) that would tell WSE3 to use or not use the proxy.
Telnet results:
C:Usersuxnxw01>telnet 66.77.241.56 80
Connecting To 66.77.241.56...Could not open connection to the host, on port 80:
Connect failed
C:Usersuxnxw01>telnet 66.77.241.76 80
Connecting To 66.77.241.76...Could not open connection to the host, on port 80:
Connect failed
I’m not sure what this proves. Like I said, I CAN definitely call the same webservice from a Windows form by directly calling its WSE3 interface. I know that I can get there that way.
I’m thinking the main differences in the two programs is that one is running under a Win Form and calling WSE3 directly. That one works. The one that fails is basically 99% same code, published as a WCF service, so it’s running under IIS (then a console program calls the WCF/IIS service on my machine, which in turns calls the WSE3 service).
Is there some reason IIS wouldn’t use the same proxy?
- Remove From My Forums
-
Question
-
Hi,
I have a simple WFC application . When I run the application I’m getting an exception while accessing the service from the client.
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 127.0.0.1:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddre
ss socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Sock
et 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.GetRequestStream()
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStre
am()Can someone please help me out. I have opened the ports in the firewall also. But still I’m getting the error.
Sab
Answers
-
Hi,
I think your service is not all running. Are your service is hosted in IIS or running in the ASP.NET Dev Server or using WCFSVCHOST.exe?
Make sure the service is running using the browser or using WCFTESTCLIENT.EXE.
Regards
Dnana
- Marked as answer by
Thursday, March 11, 2010 6:38 AM
- Marked as answer by
Vista + SQL Server 2005
Reporting Service Configuration Tool: No Red Cross.
http://localhost/reportserver get this error:
HTTP Error 403.1 — Forbidden
You have attempted to run a CGI, ISAPI, or other executable program from a directory that does not allow executables to run.
http://localhost/reports get this error:
w3wp!ui!4!20/02/2008-17:17:04:: e ERROR: Unable to connect to the remote server
w3wp!ui!4!20/02/2008-17:17:04:: 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 127.0.0.1:443
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 System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.SqlServer.ReportingServices2005.ReportingService2005.ListSecureMethods()
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!4!20/02/2008-17:17:06:: 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)
I googled but not found anything useful.
Thanks in advance!!!
Иногда случаются проблемы с подключением по FTP. Для того, чтобы оперативно решить такую задачу, необходимо выполнить диагностические меры, описанные ниже.
Проверка режима FTP
Первым делом стоит проверить, какой режим FTP используется. Рекомендуется использовать Пассивный, к примеру в клиенте Filezilla это настраивается во вкладке Редактирование -> Настройки -> FTP
Если изначально режим используется пассивный, то стоит проверить, не блокирует ли соединение локальный брендмауер (фаервол) или антивирус. Для этого банально отключаем поочередно брендмауер и антивирус и подключаемся еще раз. Если проблема осталась актуальной, то проведём диагностику подключения.
Для начала, проверим подключение к серверу через утилиту telnet, в качестве имени сервера указываем название, которое можно посмотреть в личном кабинете в разделе FTP (в нашем случае — это matrix.beget.com).
telnet matrix.beget.com 21
Если все в порядке, то должно будет появиться приглашение сервера, что-то вроде этого:
Connected to matrix.beget.com.
Escape character is '^]'.
220 Welcome to LTD Beget FTP Server 'matrix'
Ошибка Unable to connect to remote host: Connection refused
Означает, что FTP-клиент не может соединиться с сервером. Обычно ошибка выглядит примерно так:
Trying 81.222.215.42...
telnet: Unable to connect to remote host: Connection refused
Как правило, здесь имеют место быть три причины:
- блокировка ftp-подключения брандмауэром (файерволом) или антивирусом Вашего компьютера;
- блокировка вашего внешнего ip-адреса на нашем сервере;
- проблемы на стороне промежуточных узлов (между нашим сервером и вашим компьютером).
Чтобы попробовать определить на каком узле происходит обрыв, нужно сделать трассировку маршрута командой traceroute:
В Mac OS X команда будет выглядеть так:
traceroute matrix.beget.com
Должно появиться примерно следующее:
1 192.168.2.1 (192.168.2.1) 0.253 ms 0.245 ms 0.231 ms
2 beget-i.cust.smartspb.net (80.79.241.141) 0.516 ms 0.511 ms 0.504 ms
3 k12-lak.ra.smartspb.net (185.42.63.18) 0.756 ms 0.753 ms 0.747 ms
4 beget.spb.cloud-ix.net (31.28.18.90) 1.386 ms 1.366 ms 1.371 ms
5 m1.matrix.beget.com (5.101.156.64) 1.367 ms 1.357 ms 1.362 ms
Также стоит пропинговать хост утилитой ping:
ping matrix.beget.com -n 10
Должно появиться примерно следующее:
PING matrix.beget.com (5.101.156.64) 56(84) bytes of data.
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=1 ttl=60 time=1.44 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=2 ttl=60 time=1.44 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=3 ttl=60 time=1.52 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=4 ttl=60 time=1.23 ms
64 bytes from m1.matrix.beget.com (5.101.156.64): icmp_seq=5 ttl=60 time=1.56 ms
--- matrix.beget.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.231/1.441/1.562/0.124 ms
Возможно проблема связана с тем, что Ваш внешний IP-адрес заблокирован на сервере, для проверки идем на сайт http://myip.ru/, он отобразит Ваш внешний IP-адрес. Его нужно сообщить технической поддержке, чтобы специалисты проверили, не заблокирован ли указанный IP-адрес на сервере, к которому идет подключение. Лучше всего обратиться, написав тикет из Личного кабинета (раздел «Связь» или «Помощь и поддержка»). В тикете необходимо предоставить вывод команд ping, tracert (traceroute) и внешний IP-адрес, который Вы узнали на сайте http://myip.ru/. Не лишним будет указать также данные, с которыми Вы пытаетесь подключиться, так как зачастую ошибка в подключении кроется в неверно вводимых данных: логин, пароль, имя сервера.
Ошибка 530 Login incorrect
Очень распространённая ошибка «Login incorrect«. В журнале FTP-клиентов она выглядит примерно так:
220 Welcome to LTD Beget FTP Server 'matrix'
USER username
331 Please specify the password.
PASS *******
530 Login incorrect.
Означает эта ошибка то, что передаваемые логин, пароль или сервер ошибочные. В этом случае перепроверьте правильность введённых данных и исправьте ошибку.
Удачной работы! Если возникнут вопросы — напишите нам, пожалуйста, тикет из Панели управления аккаунта, раздел «Помощь и поддержка».
I’m able to call a 3rd party vendor’s web service from a Windows form program just fine. When I try to call the same web service and web method and same URL from a WCF web service I get the following error:
ExportValuationPolicyNumber:Exception=System.Net.WebException: Unable to connect to the remote server --->
System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed
because connected host has failed to respond 66.77.241.76: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 System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at TFBIC.RCT.WCFWebServices.ExpressLync.ValuationServiceWse.ExportValuationPolicyNumber(String PolicyNumber) in c:SourceTFBIC.RCT.WCFWebServicesTFBIC.RCT.WCFWebServicesWeb ReferencesExpressLyncReference.cs:line 519
at TFBIC.RCT.WCFWebServices.ValuationService.ExportValuationPolicyNumber(String PolicyNumber) in c:SourceTFBIC.RCT.WCFWebServicesTFBIC.RCT.WCFWebServicesValuationService.svc.cs:line 97
I’m basically trying to write a WCF wrapper for the vendor .asmx/WSE3 service. Let’s not get off point — but Microsoft says WCF can call WSE3, but only with SSL turned on, and my vendor — believe it or not — is not allowing SSL connection. So I’mn stuck writing the wrapper so I can call from BizTalk 2009. Right now, I’m testing the wrapper via a Console program.
What can I even do to debug? I’ve added EventLog traces before and after the WCF service where it calls the .asmx service — so I know that’s where it’s blowing (plus the line number in the error above).
I have the following in my web.config:
<microsoft.web.services3>
<diagnostics>
<trace enabled="true"
input="c:inetpubwwwrootwsetracesInputTrace.webinfo"
output="c:inetpubwwwrootwsetracesOutputTrace.webinfo" />
<detailedErrors enabled="true" />
</diagnostics>
</microsoft.web.services3>
and I have given the directory full-access to everyone — yet no trace appears there.
What are some things I can look for or try next to debug this?
In theory «ping» results should not matter, because the website is working from the Windows form program that calls it just fine.
Nevertheless — here is what Ping shows and it looks a little questionable to me:
C:Usersuxnxw01>ping rct.msbexpress.net
Pinging rct.msbexpress.net [66.77.241.56] with 32 bytes of data:
Reply from 10.193.99.5: Destination net unreachable.
Reply from 10.193.99.5: Destination net unreachable.
Request timed out.
Reply from 10.193.99.5: Destination net unreachable.
Ping statistics for 66.77.241.56:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Thanks,
Neal Walters
WireShark analysis
I did run Wireshark — posted some results in comment below. However, after reading it more, it does not always say «Destination Unreachable». But in the case where it’s failing, I never get any databack. I’m still confused what to do next. I have been comparing packets but it’s slow and confusing. For instance, I still haven’t found the key (a specific policyNum) that I am passing in the request packet. I also see a few «Destination Unreachable» statements in the one that worked.
In the one that works, I never see 66.77.241.76, I only see our company’s proxy. But I can’t see anything in the config (or code) that would tell WSE3 to use or not use the proxy.
Telnet results:
C:Usersuxnxw01>telnet 66.77.241.56 80
Connecting To 66.77.241.56...Could not open connection to the host, on port 80:
Connect failed
C:Usersuxnxw01>telnet 66.77.241.76 80
Connecting To 66.77.241.76...Could not open connection to the host, on port 80:
Connect failed
I’m not sure what this proves. Like I said, I CAN definitely call the same webservice from a Windows form by directly calling its WSE3 interface. I know that I can get there that way.
I’m thinking the main differences in the two programs is that one is running under a Win Form and calling WSE3 directly. That one works. The one that fails is basically 99% same code, published as a WCF service, so it’s running under IIS (then a console program calls the WCF/IIS service on my machine, which in turns calls the WSE3 service).
Is there some reason IIS wouldn’t use the same proxy?
- Remove From My Forums
-
Вопрос
-
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.Would the fact that I can’t browse to the website from the server using
http:\localhost be related to this at all?Log file which contains more details about the error:
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 itat 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)
Ответы
-
We had used the httpcfg.exe to add an IP listener
on port 80 of the server’s IP address while trying to get http endpoints to
work. We rebooted the machine sometime later and from that point on, reporting
services no longer worked.We removed this IP listener and reporting services
now works.
- Remove From My Forums
-
Question
-
Hi,
I have a simple WFC application . When I run the application I’m getting an exception while accessing the service from the client.
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 127.0.0.1:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddre
ss socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Sock
et 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.GetRequestStream()
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStre
am()Can someone please help me out. I have opened the ports in the firewall also. But still I’m getting the error.
Sab
Answers
-
Hi,
I think your service is not all running. Are your service is hosted in IIS or running in the ASP.NET Dev Server or using WCFSVCHOST.exe?
Make sure the service is running using the browser or using WCFTESTCLIENT.EXE.
Regards
Dnana
-
Marked as answer by
Thursday, March 11, 2010 6:38 AM
-
Marked as answer by