Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts

Sunday, March 11, 2012

Cannot create an ODBC connection to SQl 2000.

Hi all,

I have SQL 2000 enterprise edition(no service pack) installed on a Windows Server 2003 machine. I can remote access into the server and run SQL but I cannot create an ODBC connection to this from my desktop. From some research it looks like installing service packs might correct this but here is the error:

--connection failed

--sqlstate '01000'

--sql server error 10061

--connection failed

--sqlstate 08001

--sql server error 17

--SQL server does not exist or access denied

Any help would be appreciated.

Verify whether the SQL Server is listening on a TCP port. If it's a default instance it is by default 1433, so you can use

netstat -an | findstr 1433

If not but the TCP protocol is turned on for the server (and set to port 1433) then upgrading to the latest service pack will most likely solve your problem.

|||

It'd better for you to upgrade SQL Server 2000 to latest service pack 4 from here:

http://support.microsoft.com/kb/290211#EOADAA

then make sure following things before you make connection:

1) SQL Service is running

2) If make remote connection, make sure named pipe or TCP was enabled and try Peter's suggestion if you want to connect through tcp.

HTH.

Cannot create a valid ODBC DSN to SQL Server Express

Hello All,

I've just spent the better part of a day trying to configure SQL Express to allow me to create an ODBC connection. When I do create one via Control Panel/Admin/ODBC it tells me that its timing out on the connection (localhost) and the problem is probably that SQL Server Express comes configured NOT to allow remote connections. I've enabled TCP/IP and named pipes, allowed remote connections, enabled the SQL Browser, and just about everything I;ve read in the docs and forums.

Am I missing the obvious?

Kind Regards,

Pat.

Pat,

I guess you are using (localhost) as the target server which is invalid. Either you can use (local)\sqlexpress or localhost\sqlexpress to connect to local sql express instance, a name instance.

Thanks,

Nan

|||

Nan,

You are bang on! Thank you very much.

I've created a test user database, but when i attempt to "get external data/link tables" in access, I can't see my database, only all the system tables.

Any thoughts?

Kind Regards,

Pat.

|||

Did you specify your database name while creating DSN?

It's under 'Change the default dabase to' checkbox.

|||

Thank you, gavrilenko_s - that did it.

To both you and Nan, if in Dublin, send me an email - there are pints of guinness woith your names on them.

appreciatively,

Pat Backowski

Consider this thread closed and solved - well done, lads!

|||Holy Telemundo, Batman! If I hadn't found this thread, I was seriously considering just using MySQL for my app. I've talked to a few guys who have had this problem too. You may want to include a hint about this solution in the next revision of the connectivity tools so people don't go wasting so much time on what could have been a simple solution.

Cannot create a valid ODBC DSN to SQL Server Express

Hello All,

I've just spent the better part of a day trying to configure SQL Express to allow me to create an ODBC connection. When I do create one via Control Panel/Admin/ODBC it tells me that its timing out on the connection (localhost) and the problem is probably that SQL Server Express comes configured NOT to allow remote connections. I've enabled TCP/IP and named pipes, allowed remote connections, enabled the SQL Browser, and just about everything I;ve read in the docs and forums.

Am I missing the obvious?

Kind Regards,

Pat.

Pat,

I guess you are using (localhost) as the target server which is invalid. Either you can use (local)\sqlexpress or localhost\sqlexpress to connect to local sql express instance, a name instance.

Thanks,

Nan

|||

Nan,

You are bang on! Thank you very much.

I've created a test user database, but when i attempt to "get external data/link tables" in access, I can't see my database, only all the system tables.

Any thoughts?

Kind Regards,

Pat.

|||

Did you specify your database name while creating DSN?

It's under 'Change the default dabase to' checkbox.

|||

Thank you, gavrilenko_s - that did it.

To both you and Nan, if in Dublin, send me an email - there are pints of guinness woith your names on them.

appreciatively,

Pat Backowski

Consider this thread closed and solved - well done, lads!

|||Holy Telemundo, Batman! If I hadn't found this thread, I was seriously considering just using MySQL for my app. I've talked to a few guys who have had this problem too. You may want to include a hint about this solution in the next revision of the connectivity tools so people don't go wasting so much time on what could have been a simple solution.

Thursday, March 8, 2012

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.
Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for
sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed f
or sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Wednesday, March 7, 2012

Cannot connect with ODBC using TCP/IP?

Win 2003 Small business server with IIS being used as a web server.
Our client app can log in and run queries, but our web app when trying to log in gets the message,
'SQL server does not exsist or access denied'
The system DSN's are both sql drivers and the configuration is name pipes. Our recomended specs use TCP/IP, but when I try to change it, it craps out on me. He's opened up his firewall completely to this new box and his old box, a Win2k machine can connect using TCP/IP. This machine is in a work group.
Any suggestions on what it might be? :confused:instead of dsn, try dsn-less:
http://www.connectionstrings.com/

Friday, February 24, 2012

Cannot connect to SQL Server from localhost (no problem from any xp client)

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 any (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...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> 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 any (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...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> 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 any (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...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> 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 any (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...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>|||Hi Kevin!
SSMS with tcp/ip works.
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
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> 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 any (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...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> 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
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so try
>> with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> 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 any (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...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>|||Hi Kevin,
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 availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hi Kevin!
>> SSMS with tcp/ip works.
>>
>> 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
>>
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so
>> try with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server
>> config manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> 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 any (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...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>>
>

Cannot connect to SQL Server from localhost (no problem from any xp client)

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 any (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]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheits
fehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution:
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> 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 any (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]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherhei
tsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution:
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>|||Hi Kevin!
SSMS with tcp/ip works.
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;E
ncrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> 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
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>|||Hi Kevin,
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 availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>

cannot connect to sql server 2005 from xp client when trying to create ODBC dsn

Newbie here,

I am trying to link tables from an access 2003 frontend to sql server 2005 backend.

I am doing this in a vmware test environment. I am using vmware server and running sbs 2003 and xp sp2 client. Both virtaul machine can talk to each other(using local host connection).

I have tried to create a dsn to the sql server but i cannot connect. I can ping the sbs server through the command interface but the error i get when i try to connect is :

Connection failed:
Sql state: hyt00
sqlserver error: 0
microsoft odbc sql server driver timeout expired.

spent a day trying various combinations - still no joy.

Any help would be much appreciatedvirtual machines are nothing but trouble. open a query window and execute SELECT @.@.SERVERNAME|||Thank you for your reply,

I would agree vmware is not the best scenario - but as i am new to sql server - and i am about to upsize an access mdb backend to sql server 2005 so I thought some sort of test environment was required. I didn't fancy multiple installs on our production sbs until i got it right.

So from your post - is it possible to create a linked table between access 2003 and sql server 2005 from an access 2003 query window? If so, what would the syntax be if the sbs server was called 'sbs1' and the database on the sql server's default instance was named 'db1'? Or was your code to simply test the connectivity of the sql server?

The ultimate goal is a distributed access mde residing on xp sp2 clients created from an access mdb stored on a restricted network share that has linked tables to sql server 2005.

I do not even wish to go down the dsn road - would prefer the dsn-less road if possible - but i cannot proceed much further with that until i learn more about server logins, user id's and application roles etc and how passwords and user id's will be transferred accross network or stored on local machines. Hence I'm starting with dsn's and testing how to link the tables.

Any advice/guidance would be appreciated.|||I was eventually able to connect using named pipes - syntax had eluded me until i got lucky - server name 'sbs1' and pipe name was 'sbs1'.

So thats one hurdle - the next is which dsn settings to use - which server logins to use and which server roles to use.

The ultimate goal is a distributed access mde residing on xp sp2 clients created from an access mdb stored on a restricted network share that has linked tables to sql server 2005. Approx 4 users will have the abilty to link and import tables from sql server - all other users will be using an mde.

Any advice?

Tuesday, February 14, 2012

Cannot connect to remote SQL 2k5 server in local network

My SQL 2005 Dev Edition hosted on WinXP.
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search/default.aspx?spid=2855&query=sql+server+error+53&catalog=LCID%3D1033&pwt=true&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>

Sunday, February 12, 2012

Cannot connect to Database

HI,
I have a simple report which i am trying to execute. The ODBC datasource
returns success when the tested.
I get the following error when i try to run the report :
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) Get Online Help
ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does
not exist or access denied. ERROR [01000] [Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionOpen (Connect()).
----
How do i go about debugging it.
regards
-sarabsarab wrote:
> An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection) Get Online Help
> ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
> does
> not exist or access denied. ERROR [01000] [Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionOpen (Connect()).
On the machine with sql-server ->klick start -> run -> type
svrnetcn.exe ->enter
a window with sql-server-network-configuration appears->watch into right
window
there should be ("normally") two activated protocolls (named pipes and
tcp/ip)
If not activate the missing protocoll
Hope that helps
regards
Frank