Connection refused (Error 10061)

Error 10061
SAP error messages
Winsock error
When I open SAP, an error is displayed on the screen and says comment connection refused.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Error # 10061 indicates no connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running. Do you have a firewall? If you have a firewall and are not sure if that is the cause of the problem, you could (temporarily) disable the firewall and see if you can make a connection.

The error could also be cause by using a proxy server to make your connection through.
Good Luck!

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • 01017301
    1. Make sure the servername is correct 2. If you are using Ipaddress Make sure the ipaddress is correct 3. Check that theire is no problem with internet connection. To do this. Go to Start -> Run -> Cmd in the command prompt run ping servername 4. Are you connecting to default instance or named instance? Please go to the target machine, to check whether the instance started successfully, you can go to “Service Control Manager”, find out “MSSQLSERVER” or “MSSQL$” whether they are running? 5. Does your target SQL instance enabled TCP and listening on a valid TCP port? a. If it is default instance, on your client machine, try : “telnet 1433″, remember, SQL Server 2005 default instance always use the reserved port 1433, namely, if you modify it to any other port number, the client app can not connect to the sql instance. b. If it is named instance, on your target server machine, go to “SQL Server Configuration Manager”, open “Protocols for MSSQL$“, check TCP enabled, and right click TCP, find out the tcp port number under ‘IPAll”. Then on your client machine, do ” telnet “, see whether it succeeds. 6. Check out IPSec setting if you still face problem. See whether IPSec specification make dropping any packets. 7. If you still face problem, please use “Evenvwr” on the client machine, try to look up the remote server application log, see any info from SQL Server that indicates the sql instance reject client connection. Under this situation, it probably due to invalid client request. Open SQL Profile also can help you dig out which client data operation make server terminate the connection.
    25 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: