sql server login failure

(0) Share

Report

Posted on by SGibbs

435

Every time we reboot our sql server and our terminal server, Great Plains fails to login from the terminal server after reboot.

Terminal Server is Server 2008 64bit

ODBC connection is using 32bit as outlined in GP documentation

SQL is on Server 2003 using what looks like SQL Server Express (8.xxxx)

I can ping the ip and the server name from the client.

When I go to test the ODBC connection I get:
Connection Failed:

SQLState: '01000'

SQL Server Error: 67

[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()).

Connection failed:

SQLState: '08001'

SQLServer Error: 17

[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

It exists because I can go into Management Express and open it up. Any ideas on why it fails after reboot? As of right now I am sitting with no users being able to connect from the terminal server.

*This post is locked for comments

I have the same question (0)

All responses (1)

Answers (0)

SGibbs 435 on at

Like (0)

Report

More information. I decided to try and set up a x64 connection just to see if I could connect to the database. The Terminal Server is not seeing the named instance of GP at all in either x64. If I try and set up a x32 it does see the named instance but won't connect. . However, the instance is there, I can log into it from Management Express.

Was this reply helpful? Yes No