Re: problem to connect sql server 2005 from localhost (W2k3)

I have no idea what that dialog is. Where do you find this dialog to set that?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Markus" <satmax (at) gmx.at> wrote in message news:%23p4WSYMNIHA.5208@xxxxxxxxxxxxxxxxxxxxxxx
Hi Andrea,

when I set my Programm "compatible with XP" (in Programm properties), then the connection works!

But its not a real solution, so I have to Connect from 2 Servers and the property dialog for compatible mode is only on a local drive availible.


Any Ideas?

Thx
Markus





"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> schrieb im Newsbeitrag news:%23Thl67qMIHA.484@xxxxxxxxxxxxxxxxxxxxxxx
Markus,

Sorry but I don't know where else to look. I can't decipher the error message but this post seems to be related.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2240369&SiteID=17


Are you sure the account that you log onto the local server has permissions to properly access SQL Server? The only other thing I can suggest is to place a call to MS PSS but it will cost you about $225 US if this is not a bug.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Markus" <satmax (at) gmx.at> wrote in message news:OuIIQ3pMIHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
Hi Andrew!

Thanks for your assitent!


Driver={SQLServer};Server=Your_Server_Name;Database=Your_Database_Name;

Another way, same error.

I had a big frustration, now I am work 5-6 Days on the same Problem. :( I have absolut no Ideas what can I do at next....


It's possible to connect the sql server via telnet? Only for test the communication.

Thx
Markus


"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> schrieb im Newsbeitrag news:uPEaQLpMIHA.2432@xxxxxxxxxxxxxxxxxxxxxxx
Try using SERVER or DATA SOURCE instead of DSN and see if that makes a difference. Also you might want to specify the driver in the string:

http://www.connectionstrings.com/?carrier=sqlserver
http://www.sqlstrings.com/SQL-Server-connection-strings.htm

You might want to see if the versions of MDAC are the same across each. Sorry but other than that I can't say.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Markus" <satmax (at) gmx.at> wrote in message news:e9dTBeoMIHA.3852@xxxxxxxxxxxxxxxxxxxxxxx
I have try to connect via MSSMS to connect from a w2k3 serve to the other w2k3 Server (SQL Server), this works.

The only thing is, I cannot connect via ODBC from local host or any other W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP Workstion without problems.

The ODBC - Driver Config is the same on XP ans W2k3. I think the only differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00

I am not use the native client, shared memory and tcp/ip is on, the rest off, SQL Native Client: all is off



\\sqlserver\myprog is always map to s:\

myprog.exe and myprog.ini is always the same

My connection string looks like this (with and without integratet security):

DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;


Any Ideas?

THX in advanced
Markus


"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> schrieb im Newsbeitrag news:OxqXTGhMIHA.2208@xxxxxxxxxxxxxxxxxxxxxxx
It doesn't matter. If the client is on the host server it will try to use Shared Memory by default.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Markus" <satmax (at) gmx.at> wrote in message news:eMcWwsgMIHA.6060@xxxxxxxxxxxxxxxxxxxxxxx
It hast only a Flag: enable/disable. I think here is nothing to make wrong.

I use only TCP/IP normal Client, no native client.


Markus

"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> schrieb im Newsbeitrag news:%23gjbaVgMIHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
But you are sure it is enabled correct? Although I can't read most of the error message it definitely has something to do with Shared Memory so I would start there.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Markus" <satmax (at) gmx.at> wrote in message news:ePX%23obfMIHA.820@xxxxxxxxxxxxxxxxxxxxxxx
I have tried both, same problem.

Markus

"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> schrieb im Newsbeitrag news:%23EJv0SfMIHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
Do you have shared memory enabled in SQL Configuration Manager?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Markus" <satmax (at) gmx.at> wrote in message news:u8uM1OfMIHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
Hi ng!

The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every XP-Clients can connect to SQL Server via ODBC without any problems.

The problem
From the localhost I cannot connect to SQL-Server, AND from 2 other W2K Server in the same Domain I cannot connect to SQL Server.


Here is the original error message, in german:

SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler



Have you any hints for me? I worked since 5 Days on this Problem...

The solution: :)

THX
Markus
PS: my german is much better...





















.

Relevant Pages
Loading