RE: Error while connecting remote SQL server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I had the same problem, then I changed the my connection string earlier I
used the machine name then I tried with IP address it is working fine

before that check remote connection enabled

"Vene" wrote:

I understand your frustration, I have the same problem and I did what you did
and the problem still there
......A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. 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: TCP Provider, error:
0 - An invalid argument was supplied.)

PLEASE WE NEED HELP ASAP......

vene

"shivaranjaniadimulam21@xxxxxxxxx" wrote:

hi all,
I trying to connect remote sql server from my machine. but
it giving me some errors

Here are few errors listed,
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
connection to SQL Server))

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: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

A connection was successfully established with the server, but then
an error occurred during the pre-login handshake. 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: 0 - No process is on the other
end of the pipe.) (Microsoft SQL Server, Error: 233)

A connection was successfully established with the server, but then
an error occurred during the login process.(provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.)

To solve this problem I did following changes in SQL server

Enable the TCP/IP protocol using the Surface Area Configuration
Utility
Make sure the TCP/IP protocol is enabled in the SQL Server
Configuration Utility
start SQL Server browser
Exceptions are added in Firewall
Restart the computer

But still I am getting same errors.
Please give me some solution for this problem....
Thanks in advance.


.



Relevant Pages

  • Re: Disabling ASP.net 2.0 Membership
    ... I checked out the article you referenced and implemented my own provider. ... as a FoxPro database, an Oracle database, or other data sources. ... custom connection string so that I can use the Commerce Server SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Classic ASP connectionstring to SQL Server 2005
    ... So this connection string is in the VB6 dll? ... What is the error message? ... Provider cannot be found. ... can you ping the sql server? ...
    (microsoft.public.inetserver.asp.db)
  • Re: Error while connecting remote SQL server
    ... There might be possoble you have defined aliases for the SQL server in your ... An error has occurred while establishing a connection to the server. ... (provider: Named Pipes Provider,error:40-Could not open ... (provider: Named Pipes Provider, error: 0 - No process is on the other ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Error while connecting remote SQL server
    ... SQL Server does not allow remote connections. ... (provider: TCP Provider, error: ... An error has occurred while establishing a connection to the server. ... (provider: Named Pipes Provider, error: 0 - No process is on the other ...
    (microsoft.public.dotnet.framework.adonet)