ODBC Error Connecting to SQL

What does this mean "The server in the same machine of your client"?
I have the same problem - Only my ODBC Connection tests successfully.
It's my application that won't connect. My server is up and the correct
UID/PWD is being provided. Is this a licensing issue? I have an open
license and was not prompted for an activation code. I was under the
assumption any # of workstations could connect as long as the database being
connected to was under 2 gig.

Please HELP!!

"Bei Zhu [MSFT]" wrote:

 > Looks like you have the server in the same machine of your client. Make
 > sure:
 > 1. The server is up running.
 > 2. You have the correct UID and PWD.
 >
 >
 > "Jaz" <Jaz.RemoveThis@discussions.microsoft.com> wrote in message
 > news:914DF325-FFCD-49EB-9698-0834B356C7DB@microsoft.com...
  > >I very clear that i configured SQL database with no problem but while i
  > >going
  > > to setup DSN in ODBC and this error occured, I do not understand what is
  > > the
  > > problem that keep this error exist.
  > > '
  > > Connection failed:
  > > SQLState: '01000'
  > > SQL Server Error: 2
  > > [Microsft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
  > > (connect()).
  > > Connection failed:
  > > SQLState: '08001'
  > > SQL Server Error: 17
  > > [Microsft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist
  > > or access denied.
  > > '
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ODBC Error Connecting to SQL 

Quote:

What does this mean "The server in the same machine of your client"? I have the same problem - Only my ODBC Connection tests successfully. It's my application that won't connect. My server is up and the correct UID/PWD is being provided. Is this a licensing issue? I have an open license and was not prompted for an activation code. I was under the assumption any # of workstations could connect as long as the database being connected to was under 2 gig.

Try creating a host record that points to the SQL server. I had the same problem the other day. it tested successfully, but the application would not work. So on the server that the application was on I created a host record. Go to WINNT/System32/drivers/etc/host. open it in notepad and at the bottom put in the ip address and computer name of the SQL server. And see if that helps out. It worked for me, so its worth a try.
 >> Stay informed about: ODBC Error Connecting to SQL