Can't Find SQL Native Client in ODBC Connection Manager in SQL Server Open Database Connectivit

I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.

I am running Windows XP Pro SP2. I have installed the SQL Native Client for

XP. However, when I try to add a new data source through ODBC Connection

Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the

SQL Native Client to not show up in the list of available ODBC data sources?

Hi, James,

First of all - are you sure that the installation of the SQL Native Client completed successfully? Do you see the packet in the Add/Remove Programs applet? What you can try first is to uninstall (if available) and reinstall the Client, check if any errors or warnings would be reported.

Going further - the ODBC drivers information is stored in the registry. Using regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and check if the SQL Native Client driver is present, the entries in the folder as well as an entry at "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers" folder.

If the SQL Native Client driver is not present in the registry, you might have a permission issue. One possible approach is to run and capture a RegMon log during the installation (http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx) and see if access to the key above failed.

If the SQL Native Client driver is present in the registry, then for some reason the ODBC Administrator fails to enumerate it or it contains invalid entries. First step would be to compare the entries to a "working" machine and then you could probably use RegMon again - this time when running ODBC Administrator.

Based on the findings, you could take corrective actions and start seeing the driver properly.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks for the reply. SQL Native Client does appear in Add/Remove programs, and I am able to uninstall and reinstall. I will do the other checks you mentioned, and let you know the results. Thanks.|||

I am having a very similar problem. I am using Visual C++ 2005 Express and have installed the Microsoft SQL Server Native Client. All the mentioned registrty entries appear to be correct. I have also include all of the ODBC components in my toolbox. When I try to configure the ODBC data adpater, create a new connection, the only types of data sources that are in the possible list are the SQL Server and Access. If I add an OdbcConnection tool to the form and try to modify the connection string to a new connection, I get a message that the data provider identified by guid "all zeroes" could not be loaded. It would appear that csomething is missing.

I have tried to find a "Data" component to reference in the project that might include the missing component, but have had no success.

Can't Find SQL Native Client in ODBC Connection Manager in SQL Server Open Database Connectivit

I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.

I am running Windows XP Pro SP2. I have installed the SQL Native Client for XP. However, when I try to add a new data source through ODBC Connection Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the SQL Native Client to not show up in the list of available ODBC data sources?

Hi, James,

First of all - are you sure that the installation of the SQL Native Client completed successfully? Do you see the packet in the Add/Remove Programs applet? What you can try first is to uninstall (if available) and reinstall the Client, check if any errors or warnings would be reported.

Going further - the ODBC drivers information is stored in the registry. Using regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and check if the SQL Native Client driver is present, the entries in the folder as well as an entry at "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers" folder.

If the SQL Native Client driver is not present in the registry, you might have a permission issue. One possible approach is to run and capture a RegMon log during the installation (http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx) and see if access to the key above failed.

If the SQL Native Client driver is present in the registry, then for some reason the ODBC Administrator fails to enumerate it or it contains invalid entries. First step would be to compare the entries to a "working" machine and then you could probably use RegMon again - this time when running ODBC Administrator.

Based on the findings, you could take corrective actions and start seeing the driver properly.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks for the reply. SQL Native Client does appear in Add/Remove programs, and I am able to uninstall and reinstall. I will do the other checks you mentioned, and let you know the results. Thanks.
|||

I am having a very similar problem. I am using Visual C++ 2005 Express and have installed the Microsoft SQL Server Native Client. All the mentioned registrty entries appear to be correct. I have also include all of the ODBC components in my toolbox. When I try to configure the ODBC data adpater, create a new connection, the only types of data sources that are in the possible list are the SQL Server and Access. If I add an OdbcConnection tool to the form and try to modify the connection string to a new connection, I get a message that the data provider identified by guid "all zeroes" could not be loaded. It would appear that csomething is missing.

I have tried to find a "Data" component to reference in the project that might include the missing component, but have had no success.

sql

Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing th
e
>SQL Native Client to not show up in the list of available ODBC data sources?[/vbcol
]

Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?
MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:

>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing the
>SQL Native Client to not show up in the list of available ODBC data sources?

cant delete odbc tracing file..

Hi all
I can not delete the odbc manager tracing file.
Even after disabling tracing (in the odbc manager)
i get a windows massage saing another program is using the odbc tracing
file...
Can i stop the odbc manager service?
What other programs may be using this log?
There is no other runing programm or sql server job.
Please help, this file is growing so fast!
TIA
Rea
Rea,
Refer the below snippet from :
'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk Space'
http://support.microsoft.com/?id=268591
<start quote>
To turn off ODBC Tracing and remove the associated file, follow these steps:
1.. To disable ODBC Tracing:
1.. For Microsoft Windows NT 4.0:
a.. On the Start menu, click on Control Panel, and then click on Data
Sources(ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. For Microsoft Windows 2000:
a.. On the Start menu, click on Control Panel, click on Administrative
Tools, and then click on Data Sources (ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. Stop all ODBC applications, and stop SQL Server. In some cases it may
be necessary to reboot the server to free up the file so that it can be
deleted.
3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
4.. Restart SQL Server.
<end quote>
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
> Hi all
> I can not delete the odbc manager tracing file.
> Even after disabling tracing (in the odbc manager)
> i get a windows massage saing another program is using the odbc tracing
> file...
> Can i stop the odbc manager service?
> What other programs may be using this log?
> There is no other runing programm or sql server job.
> Please help, this file is growing so fast!
> TIA
> Rea
>
|||Thanks alot !
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uaDVzOHTEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Rea,
> Refer the below snippet from :
> 'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk
Space'
> http://support.microsoft.com/?id=268591
> <start quote>
> To turn off ODBC Tracing and remove the associated file, follow these
steps:
> 1.. To disable ODBC Tracing:
> 1.. For Microsoft Windows NT 4.0:
> a.. On the Start menu, click on Control Panel, and then click on
Data
> Sources(ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. For Microsoft Windows 2000:
> a.. On the Start menu, click on Control Panel, click on
Administrative
> Tools, and then click on Data Sources (ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. Stop all ODBC applications, and stop SQL Server. In some cases it
may
> be necessary to reboot the server to free up the file so that it can be
> deleted.
> 3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
> 4.. Restart SQL Server.
> <end quote>
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
>

cant delete odbc tracing file..

Hi all
I can not delete the odbc manager tracing file.
Even after disabling tracing (in the odbc manager)
i get a windows massage saing another program is using the odbc tracing
file...
Can i stop the odbc manager service'
What other programs may be using this log?
There is no other runing programm or sql server job.
Please help, this file is growing so fast!
TIA
ReaRea,
Refer the below snippet from :
'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk Space'
http://support.microsoft.com/?id=268591
<start quote>
To turn off ODBC Tracing and remove the associated file, follow these steps:
1.. To disable ODBC Tracing:
1.. For Microsoft Windows NT 4.0:
a.. On the Start menu, click on Control Panel, and then click on Data
Sources(ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. For Microsoft Windows 2000:
a.. On the Start menu, click on Control Panel, click on Administrative
Tools, and then click on Data Sources (ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. Stop all ODBC applications, and stop SQL Server. In some cases it may
be necessary to reboot the server to free up the file so that it can be
deleted.
3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
4.. Restart SQL Server.
<end quote>
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
> Hi all
> I can not delete the odbc manager tracing file.
> Even after disabling tracing (in the odbc manager)
> i get a windows massage saing another program is using the odbc tracing
> file...
> Can i stop the odbc manager service'
> What other programs may be using this log?
> There is no other runing programm or sql server job.
> Please help, this file is growing so fast!
> TIA
> Rea
>|||Thanks alot !
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uaDVzOHTEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Rea,
> Refer the below snippet from :
> 'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk
Space'
> http://support.microsoft.com/?id=268591
> <start quote>
> To turn off ODBC Tracing and remove the associated file, follow these
steps:
> 1.. To disable ODBC Tracing:
> 1.. For Microsoft Windows NT 4.0:
> a.. On the Start menu, click on Control Panel, and then click on
Data
> Sources(ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. For Microsoft Windows 2000:
> a.. On the Start menu, click on Control Panel, click on
Administrative
> Tools, and then click on Data Sources (ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. Stop all ODBC applications, and stop SQL Server. In some cases it
may
> be necessary to reboot the server to free up the file so that it can be
> deleted.
> 3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
> 4.. Restart SQL Server.
> <end quote>
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
>

Can't create a ODBC DSN to a remote MSDE instance

Hello,
I need to create an ODBC DNS that points to a remote MSDE instance, but I
can only get it to work if I turn Windows Firewall off. Both the local and
remote machines are WinXP SP2 and have SQL2000 and MSDE, same domain and I
can login as the same person on each machine.
On the remote machine I've enabled TCP/IP and the default port, and I've
added that port to the firewall, but when I try to add a DSN (on the local
machine) in the ODBC control panel it says
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
I've looked at the instance via Enterprise Manager and my domain login has
admin privs, and can connect a DSN to the SQL2000 server on that machine.
Stumped.
Suggestions?
Keith
hi Keith,
Keith wrote:
> Hello,
> I need to create an ODBC DNS that points to a remote MSDE instance,
> but I can only get it to work if I turn Windows Firewall off. Both
> the local and remote machines are WinXP SP2 and have SQL2000 and
> MSDE, same domain and I can login as the same person on each machine.
> On the remote machine I've enabled TCP/IP and the default port, and
> I've added that port to the firewall, but when I try to add a DSN (on
> the local machine) in the ODBC control panel it says
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
> exist or access denied.
> I've looked at the instance via Enterprise Manager and my domain
> login has admin privs, and can connect a DSN to the SQL2000 server on
> that machine.
did you define an exception on the server's firewall on the MSDE used TCP/IP
port or on the service itself?
http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||>
> did you define an exception on the server's firewall on the MSDE used
> TCP/IP port or on the service itself?
> http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
> http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Well, after some reboots and a walk around the block it works now.
I finally got it to work either with firewall port exception, or a service
exception, but neither way seemed very consistent. Making changes to the
firewall while it is running just doesn't seem to work that well; perhaps I
wasn't waiting long enough for the changes to propagate or I just need to
stop/start the firewall after changing something.
And I suspect that some of the changes that don't "require" rebooting really
do.
Anyway, thanks for the quick response and support links.
Keith

can't connect with OLEDB, but ODBC works

I have a local database that I'm having trouble selecting as a source in
DTS. I can connect just fine using "mymachinename", but if I try to use
(local) or an alias in Client Network Utility, I get the error:
Error Source : Microsoft OLE DB Provider for SQL Server
Error Description : [DBNETLIB][ConnectionOpen (Connect()).]
SQL Server does not exist or access denied.
I noticed that if I changed the driver to ODBC, then it works fine. Also, I
can connect using any name in Query Analyzer. However, I need to use OLEDB
and also the alias. I have Windows XP Pro and SQL 2000 Developer Edition w/
SP3. Here's all the different tests I have done with OLEDB:
Server Authentication Result
-- -- --
mymachinename Windows OK
mymachinename SQL login OK
myalias Windows SQL Server does not exist or access denied.
myalias SQL login SQL Server does not exist or access denied.
(local) Windows SQL Server does not exist or access denied.
(local) SQL login SQL Server does not exist or access denied.Can you make an OLE DB connection through a UDL? To create a UDL, just
right-click on your desktop and choose to create a new document. Name it
anything you want. Then rename the extension to .udl. Then double-click on
it. Choose your driver and other connection properties and test it. If it
works from there then most likely OLE DB is fine.
(local) is using shared memory and an alias is using whatever protocol is
defined in cliconfg.exe for that alias. When you get a successful
connection which protocol are you using? For a successful connection you
can do:
SELECT network_library, * from master..sysprocesses where spid = @.@.spid to
see your actual protocol.
It may be that the difference isn't odbc vs. ole db but rather tcp vs.
shared memory vs. named pipes. To force connectivity with each type of
protocol:
for tcp use: tcp:mymachinename
for named pipes use: np:mymachinename
for shared memory use: lpc: mymachinename
You can find more troubleshooting steps in:
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

can't connect to the ODBC database named aspol54

can any one provide any suggestions to help this error i installed automation studion 5.4 and the program will not run on my laptop.

i traced the data below when i try to start the program.

AsProjet db0-b5c ENTER SQLAllocEnv
HENV * 015CF6B0

AsProjet db0-b5c EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x015CF6B0 ( 0x015e1540)

AsProjet db0-b5c ENTER SQLGetEnvAttr
SQLHENV 015E1540
SQLINTEGER 201 <unknown>
SQLPOINTER [Unknown attribute 201]
SQLINTEGER 4
SQLINTEGER * 0x0013E380

AsProjet db0-b5c EXIT SQLGetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 015E1540
SQLINTEGER 201 <unknown>
SQLPOINTER [Unknown attribute 201]
SQLINTEGER 4
SQLINTEGER * 0x0013E380 (1567744)
any help would be great.

tks

I don't know how much help this is, but the '201' attribute is for 'SQL_ATTR_CONNECTION_POOLING'. The weird thing is that the return value seems to be 1567744. It should be returning '0' in this case. Here are possible values (from SQLEXT.H):

/* values for SQL_ATTR_CONNECTION_POOLING */
#define SQL_CP_OFF 0UL
#define SQL_CP_ONE_PER_DRIVER 1UL
#define SQL_CP_ONE_PER_HENV 2UL
#define SQL_CP_DEFAULT SQL_CP_OFF

It looks like you're receiving invalid data, but I don't know why or how. Sorry I can't be of more help.

Perhaps someone else on the alias can shed some light on this?

|||

Hi,

In addition to Warren's comments - what you see in the ODBC trace doesn't indicate an error. Simply an Environment handle was allocated and GetEnvAttr was called to retrieve the Environment's connection pooling attribute setting. Both calls appear to have succeeded. The fact that we get a strange value, probably means that the ODBC driver doesn't support it (it's an ODBC 3.0 attribute). Is the application using the driver directly (without Driver Manager)? Could you post the actual error that you get or is there any additional information in the ODBC trace?

HTH,

Jivko Dobrev - MSFT

---

This posting is provided "AS IS" with no warranties, and confers no rights.

cant connect to sql server, error

hi if someone could help, i appreciate: i have windows 2003 server and sql server 2000, i have a few machines connected via odbc and seems to work fine, my problem is when i try to make a new connection via odbc, appears: sql server odbc error: ConnectionOpen and server does not exist or access denied, i try few things, make a ping to the server and i got response, check the users and passwords, the mdac, check that the port 1433 is established in the client network utility, etc, now when i do a telnet to the server the port 1433, appears and error: couldnt connect,i believe this is why i cant make a odbc connection, but i cant figure it out how to make the port listens my petitions., now if itsa supossed to be closed, why the others machines cant connect just fine?

Do you already review the firewall for sql server ports?

http://support.microsoft.com/kb/287932/en

cant connect to Sql server 2000 sp3a in windows 2003 server

There is a way to find out - I think you should find out if the clients are
using "Named Pipes" or TCP/IP for connectivity.
Bring up the ODBC connection, then on the second page you should see a
button "Client connectivity". Go into this and make the bullet TCP/IP.
Please let me know if this fixed your problem.
=-Chris
On the clients that cannot connect, click the box "Client configuration"
"Rick" <ricardo.blanco@.indap.com.mx> wrote in message
news:ur4WMjStEHA.2688@.TK2MSFTNGP14.phx.gbl...
> hi guys im having troubles to connecto to sql server, my clients are win
xp
> and win 2000 pro, before i had the sql server 2000 on a windows 2000
server
> and all worked fine, but two days ago i changed to windows server 2003
> standard and the problems began...
> when i try to connect to sql by odbc or by another way its the screen that
> appears, the extrange is that in downstair there are 4 pcs and that 4 can
> connect to sql, (all winXP Sp1 in spanish), upstairs there are 3 winXp
> spanish, 2 winxp english(1 with SP2 the other Sp1) and 1 win2000 Sp4 pro
> english and just 1 XP in spanish can connect the other 2 not, i thought it
> was a problem with the server but now i connect a new laptop with winXP
> spanish SP2 and it works fine... so i dont know what to do, all pcs have
> mdac 2.8
> now i thought its problem with clients but i cant find difference between
> pcs except for the language
> what can be'
> i tried to connect by IP, i checked the port and nothing works =(
>
>Chris thanks a lot, but ive found other way to solve it, i know maybe its
not the more correct but i reinstalled the Sql server because i found at
microsofts web a tool to check the ports, its name is PortQuery, with it
you can check for Sql server if it is running on a server, or network
connectivity and other things, i saw that the server doesnt aswer to the
tool, the ports 1433 and 1434 not respond, so i decided to reinstal Sql
server, and it solved the problem =)
the tools url is http://support.microsoft.com/kb/310513/EN-US/
Rick =)
"Christopher Conner" <someone@.someplace.com> wrote in message
news:%23u554sTtEHA.3872@.TK2MSFTNGP15.phx.gbl...
> There is a way to find out - I think you should find out if the clients
> are
> using "Named Pipes" or TCP/IP for connectivity.
> Bring up the ODBC connection, then on the second page you should see a
> button "Client connectivity". Go into this and make the bullet TCP/IP.
> Please let me know if this fixed your problem.
> =-Chris
>
> On the clients that cannot connect, click the box "Client configuration"
> "Rick" <ricardo.blanco@.indap.com.mx> wrote in message
> news:ur4WMjStEHA.2688@.TK2MSFTNGP14.phx.gbl...
> xp
> server
>|||Rick, thanks for the tip about the tool.
Because you had to reinstall to fix it, tells me that next time you have
this problem, on the SQL Server itself, bring up the Server Network Utility
(located in Programs->Microsoft SQL Server) and double check that on the
enabled protocols list that TCPIP and Named Pipes is listed. I am betting
that they were not previously. If you want to stop clients from connecting,
this is the place to do so as you would just remove the protocols.
Cheers!
=-Chris
"Rick" <ricardo.blanco@.indap.com.mx> wrote in message
news:eN8LyBWtEHA.2788@.TK2MSFTNGP09.phx.gbl...
> Chris thanks a lot, but ive found other way to solve it, i know maybe its
> not the more correct but i reinstalled the Sql server because i found at
> microsofts web a tool to check the ports, its name is PortQuery, with it
> you can check for Sql server if it is running on a server, or network
> connectivity and other things, i saw that the server doesnt aswer to the
> tool, the ports 1433 and 1434 not respond, so i decided to reinstal Sql
> server, and it solved the problem =)
> the tools url is http://support.microsoft.com/kb/310513/EN-US/
> Rick =)
> "Christopher Conner" <someone@.someplace.com> wrote in message
> news:%23u554sTtEHA.3872@.TK2MSFTNGP15.phx.gbl...
win[vbcol=seagreen]
can[vbcol=seagreen]
pro[vbcol=seagreen]
have[vbcol=seagreen]
between[vbcol=seagreen]
>

Can't connect to remote MSDE with ODBC

I have been trying on an off for a month to connect to an MSDE (SQL server)
database from a remote computer with ODBC. I can connect just fine from
within the workgroup.
In Cliconfg, I have set up an alias pointing to servername.com\INSTANCENAME.
tcp/ip is set. There is not a firewall in play at this time. The server is
also configured to use TCP/IP.
Is it possible to connect to a remote SQL server with ODBC? This is really
frustrating.
I did the same drill with mysql and it is a piece of cake, but I really need
to use SQL server in this instance.
BradI just figured out my problem.
I reviewed the server logs and found that the server was listening on port
1212. So, with cliconfg I set up an alias to use this same port.
Man, what a relief to finally get this figured out.
Brad
"Brad Dennis" <Brad@.f1csp.com> wrote in message
news:eGiujTq5DHA.2732@.TK2MSFTNGP09.phx.gbl...

quote:

---

> I have been trying on an off for a month to connect to an MSDE (SQL

---

server)

quote:

---

> database from a remote computer with ODBC. I can connect just fine from
> within the workgroup.
> In Cliconfg, I have set up an alias pointing to

---

servername.com\INSTANCENAME.

quote:

---

> tcp/ip is set. There is not a firewall in play at this time. The server

---

is

quote:

---

> also configured to use TCP/IP.
> Is it possible to connect to a remote SQL server with ODBC? This is

---

really

quote:

---

> frustrating.
> I did the same drill with mysql and it is a piece of cake, but I really

---

need

quote:

---

> to use SQL server in this instance.
> Brad
>

---

Can't connect ODBC/SQLSrvr linked table from within COM+ component

I have an Access 2000 database containing an ODBC table linked to a SQL Serv
er 2000 database (using a system DSN).
No problem opening the table Using Access 2000 itself.
No problem even within a VB program (EXE) accessing that table using the fol
lowing code:
Set rs = New ADODB.Recordset
With rs
.ActiveConnection = cnSrc
.Source = "SELECT * FROM " _
& "[ODBC;" & tbODBC.Properties("Jet OLEDB:Link Provider String") & "]."
_
& tbODBC.Name & vbCrLf & "WHERE FALSE"
.CursorLocation = adUseServer
End With
On Error Resume Next
rs.Open ' <-- ERROR RAISES HERE
cnSrc is an ADO Connection with Access2000 DB
tbODBC is an ADOX Table object corresponding to the linked ODBC table
But if the same code is placed in a COM+ component (DLL ActiveX), once invok
ed by any client, when the final "rs.Open" is executed, the following error
raises:
"Connection to <sql server database name> failed"
Number = 0x80004005
SQLState = 3151
I've searched many places but with no results.
Some help will be appreciated.
Thanks in advance
RafThe Jet OLEDB provider does not support distributed transactions since it
does not implement the ITransactionJoin OLE-DB interface.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Raf" <anonymous@.discussions.microsoft.com> wrote in message
news:0377EFF9-6D50-447F-B38F-779100742A52@.microsoft.com...
>I have an Access 2000 database containing an ODBC table linked to a SQL
>Server 2000 database (using a system DSN).
> No problem opening the table Using Access 2000 itself.
> No problem even within a VB program (EXE) accessing that table using the
> following code:
> Set rs = New ADODB.Recordset
> With rs
> .ActiveConnection = cnSrc
> .Source = "SELECT * FROM " _
> & "[ODBC;" & tbODBC.Properties("Jet OLEDB:Link Prov
ider
> String") & "]." _
> & tbODBC.Name & vbCrLf & "WHERE FALSE"
> .CursorLocation = adUseServer
> End With
> On Error Resume Next
> rs.Open ' <-- ERROR RAISES HERE
> cnSrc is an ADO Connection with Access2000 DB
> tbODBC is an ADOX Table object corresponding to the linked ODBC table
> But if the same code is placed in a COM+ component (DLL ActiveX), once
> invoked by any client, when the final "rs.Open" is executed, the following
> error raises:
> "Connection to <sql server database name> failed"
> Number = 0x80004005
> SQLState = 3151
> I've searched many places but with no results.
> Some help will be appreciated.
> Thanks in advance
> Raf
>