cancel
Showing results for 
Search instead for 
Did you mean: 

Error: While Connecting SQL Server

ashutosh_tomar
Contributor
0 Kudos

Dear Experts,

While i am connecting SQL Server 2005 on client Machine, Following error is occurring :

Connection Failed:

SQL State: '8001'

SQL Server Error:1326

[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [1326].

Connection Failed:

SQL Server Error:0

[Microsoft][SQL Native Client]Login timeout expiered

Connection failed:

SQL State:'08001'

SQL Server Error:1326

Please suggest solutions.

Best Regards

Ashutosh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Hi There

There's a few things to check..

Ensure that you have both Named Pipes and tcp/ip configured as transport for your SQL server.

The SQL Native client is also a common cause for remote timeouts (ie it isn't installed on the client PC). Lastly you ned to check that there is no firewall or anti virus scanner preventing your connection from the client to the server

These are the usual gotchas.

Please let us know if you still have issues (and maybe let us know what the specifics are ie versions and what you have already done)

Good Luck

Pete

Answers (2)

Answers (2)

senthil_m
Active Contributor
0 Kudos

Hi Ashutosh T,

Check your system has SQL native client. If it is not installed in your machine, Please install SQL native client. Native client is Communication Bridge between SAP and server.

SQL State: '8001'
SQL Server Error:1326
MicrosoftSQL Native ClientNamed Pipes Provider: Could not open a connection to SQL Server 1326.

It means clent unable to establish connection to the server.

Check have you enabled both TCP/IP in your SQL Server and SQL Client?

If you are enabling TCP/IP service, you problem will solve.

To Enable TCP/IP settings in sql server 2005

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

Increase your sql server connection login session period and check it now.

Regards,

Senthil Maruthappan.

ashutosh_tomar
Contributor
0 Kudos

Thanks, Senthil, Peter and Gordan.

Best Regards

Ashutosh

gfeldman
Explorer
0 Kudos

FYI this same error can be created if the Windows Firewall is on in Windows 2008.

Former Member
0 Kudos

Dear Ashutosh,

You may check these threads first:

Thanks,

Gordon