April 10, 2014 at 2:46 am
Out of the blue, my program cannot get connection to a remote SQL 2012 server
When it tries to connect, it comes with an error message about 'Named pipes'.
OK, first try is firewall - it is disabled by Norton
Next try was to disable Norton - as i belive it is blocking the connection.
No difference.
Next try was to open the connection from my own PC - too remote, and it works as it should.
Running Windows 8 on the client.
Any suggestions for where to look?
Best regards
Edvard Korsbæk
April 10, 2014 at 2:50 am
Open up SQL Server configuration manager and check if the named pipes protocal is enabled.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 10, 2014 at 3:09 am
It is enabled on all IP possibilities including the one we are using.
April 10, 2014 at 3:10 am
Edvard Korsbæk (4/10/2014)
It is enabled on all IP possibilities including the one we are using.
OK. What is the exact error message?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 10, 2014 at 3:20 am
The exact error message is:
Cannot connect to database
Error :08001 - Named pibes Provider. Could not open a connection to SQL server [53]
April 10, 2014 at 3:21 am
How are you trying to make the connection?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 10, 2014 at 3:28 am
From trace, on a location that works:
05FCH(1) 11:25:23.263 Version: 6.300.01.9059
05FCH(1) 11:25:23.265 Allocating Environment Environment 01AF8C48H Time Taken:0.00 secs
05FCH(1) 11:25:23.715 Allocating Connection 01FFD838H Time Taken:0.00 secs
05FCH(1) 11:25:23.715 Connecting to Server=**.**.**.**;Database=EP_vejlebro;UID=ep_vejlebro;PWD=********
05FCH(1) 11:25:23.926 Warning: 01000 [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'EP_vejlebro'.
05FCH(1) 11:25:23.926 Time Taken:0.22 secs
April 10, 2014 at 7:34 am
Solved
Error 40...
Mismatch in password
Thanks for help, and sorry for the time you have used.
Best regards
Edvard Korsbæk
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply