The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Database login failed: Named Pipes Provider: Could not open a connection to SQL Server [53]
Posted: 15 Apr 09 12:00 PM
|
Please help!
A client has three servers (one DB server, one LAN server, and one Web Server which is on the DMZ). DB to LAN has port 1433 open. LAN to WEB server has port 1706 open. Can connect to database just fine on the LAN server. When trying to connect to database from web server, I get connection error (either "Data dictionary failed to initialize" or error in subject line). When adding the Data Link, it can see the LAN server and databases, but fails when attempting to login. On web server, SQL Native Client and SLX Ole DB Provider has been installed numerous times. Additionally, SQL Server was set to allow Remote TCP and Named Pipes connections. Any ideas on this would be GREATLY appreciated! Thanks!
C. Burriss |
|
|
| |
|
Re: Database login failed: Named Pipes Provider: Could not open a connection to SQL Server [53]
Posted: 16 Apr 09 2:32 PM
|
Chris:
Just to clarify your post, in case anyone runs into the same sitaution, the problem that you had is that Named Pipes required Authenticate connections to the servers.
What you had done is force the use of the TCP Library, which then uses a specific port to connect, and it makes it much simpler to allow across firewalls.
- There are typically 2 ways to do this:
* Disable the All libraries by the TCP Library
Or
* Create an Alias for the Server forcing it to use the TCP Library.
|
|
|
| |
| |
| |
|