Cannot Create System DSN

Hi,
I'm having some difficulty creating a system DSN on a
win2K machine for connecting to a SQL 2000 server. I'm not
sure if this may be a better question for the windows
group, but... Anyway, when I go through the odbc setup in
windows, the DSN does not appear in the list of system
dsn's that are already created. I begin to create it, and
it says it already exists, "overwrite?". (this is because
I have already tried creating it with that name, and am
using the same dsn name. If I use a new name, I don't get
the "already exists" message, but the following problem
still occurs.) I do so, and continue through creating the
dsn and successfully testing the connection. When I
finish the creation, the dsn name still does not appear in
the list of system dsn's. Is this a corrupt odbc database
on the win2K machine? I have no idea!!! PS I am tryiing
to create it with local Administrator priveledges.
Any help would be appreciated.
Thanks
David
Check the permissions on the following registry key:
HKLM\Software\ODBC\ODBC.INI
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I'm also experiencing the same problem. I've checked the permissions on the related key in the registry, and have given Full Permission to all users, but to no avail. Any other suggestions?
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Cannot Create System DSN

Hi,
I'm having some difficulty creating a system DSN on a
win2K machine for connecting to a SQL 2000 server. I'm not
sure if this may be a better question for the windows
group, but... Anyway, when I go through the odbc setup in
windows, the DSN does not appear in the list of system
dsn's that are already created. I begin to create it, and
it says it already exists, "overwrite?". (this is because
I have already tried creating it with that name, and am
using the same dsn name. If I use a new name, I don't get
the "already exists" message, but the following problem
still occurs.) I do so, and continue through creating the
dsn and successfully testing the connection. When I
finish the creation, the dsn name still does not appear in
the list of system dsn's. Is this a corrupt odbc database
on the win2K machine? I have no idea!!! PS I am tryiing
to create it with local Administrator priveledges.
Any help would be appreciated.
Thanks
DavidCheck the permissions on the following registry key:
HKLM\Software\ODBC\ODBC.INI
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I'm also experiencing the same problem. I've checked the permissions on the
related key in the registry, and have given Full Permission to all users, bu
t to no avail. Any other suggestions?
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...

Cannot create DSN to SQL Express

I installed SQL Express and was able to create a new DB using Management Studio. I was able to copy over tables from another DB using DTS, but strangely the Native Client would not work I had to use OLE for SQL Server.

But I am unable to create a DSN to the database using ODBC Administrator. I keep getting Login Timeout expired error message, using both Native Client and SQL Server drivers. What am I missing?

Thanks

Mark

WHat is the exact error message you are getting ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

This is the error message when I try using Native Client:

Attempting connection
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

This when I try SQL Server driver:

Attempting connection
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

BTW this is a local connection, I'm trying to get it all working on my laptop. I also tried playing with the SQLEXPRESS and CLient Protocols. I enabled Shared Memory, Named Pipes and TCP/IP, to no avail.

Thanks

Mark

|||

Finallly I managed to get it to work, when I realized the ODBC Administrator does not display the full name of the server. It displayed MARK_LAP, which is the name of my computer. I realized I needed to type in MARK_LAP\SQLEXPRESS which is the name of the server, and it works now. Connecting to [local] does not work either.

So, I thought I would post this in case someone else has the same problem.

Mark

|||The statement "MARK_LAP\SQLEXPRESS which is the name of the server" is a bit misleading as this is the name of the named instance which the service uses. YOu always have to name the instance with the "\instanceName" snippet if its not a default instance. Otherwise the client tries to connect to a default instance which is probably not installed in all cases.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

Cannot create DSN to SQL Express

I installed SQL Express and was able to create a new DB using Management Studio. I was able to copy over tables from another DB using DTS, but strangely the Native Client would not work I had to use OLE for SQL Server.

But I am unable to create a DSN to the database using ODBC Administrator. I keep getting Login Timeout expired error message, using both Native Client and SQL Server drivers. What am I missing?

Thanks

Mark

WHat is the exact error message you are getting ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

This is the error message when I try using Native Client:

Attempting connection
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

This when I try SQL Server driver:

Attempting connection
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

BTW this is a local connection, I'm trying to get it all working on my laptop. I also tried playing with the SQLEXPRESS and CLient Protocols. I enabled Shared Memory, Named Pipes and TCP/IP, to no avail.

Thanks

Mark

|||

Finallly I managed to get it to work, when I realized the ODBC Administrator does not display the full name of the server. It displayed MARK_LAP, which is the name of my computer. I realized I needed to type in MARK_LAP\SQLEXPRESS which is the name of the server, and it works now. Connecting to [local] does not work either.

So, I thought I would post this in case someone else has the same problem.

Mark

|||The statement "MARK_LAP\SQLEXPRESS which is the name of the server" is a bit misleading as this is the name of the named instance which the service uses. YOu always have to name the instance with the "\instanceName" snippet if its not a default instance. Otherwise the client tries to connect to a default instance which is probably not installed in all cases.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

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.

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?

Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

When I try to create a System DSN connection to our SQL Server 2000
database that is installed on a Windows 2000 machine, I keep on
getting the following error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
We do not have IIS or any web server installed on the database server
machine or the Windows XP Professional machine that is trying to
connect to the Windows 2000 machine. The machines can all see each
other, and we are actually have the machines networked via the
Workgroup setting, not using the Domain setting. Anyone have any ideas
as to what can be the issue?
Thanks,
Jay
(patel@.cs.utk.edu)
Hi Patel,
Since you're not in a domain, Windows Authentication works very
differently. Windows Authentication is commonly used while you're in a
domain and the client has been authenticated on the domain. The error
message "null" indicates that we're unable to "impersonate" the client in
order to make a Windows Authenticated connection.
You have two optioins.
1. Duplicate the nt username & password on both machines and Use Named
Pipes to Connect.
2. Use SQL Standard Security instead of using Windows Authentication.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
How do I create a named pipe? I am not sure as to how to do that.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Named pipes are not created, but rather enabled - with both the
Client and Server Network Utilities.
For the Client Network Utility, start it by Start>Run>cliconfg.exe.
The left pane shows disabled protocols. The right pane shows enabled
protocols. In the left pane, click on Named Pipes and then use the
Enable button between the two panes.
For the Server Network Utility (at least for an MSDE version) find the
file SVRNETCN.EXE. Double click to start and the perform the same
actions as in the Client Network Utility, but for the server instance
in question. If you have installed the server as the default instance,
it will have no name, so its just the computer name that will appear
in the server name pull-down list.
If you have a firewall installed on the machines in question, please
say so, since there will be rules to create to open ports if you have
not done so already.
You should also see the article:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/default...06&Product=sql
Lou Arnold
Ottawa, Canada.
On Wed, 21 Jul 2004 21:15:32 -0700, Jay Patel <patel@.cs.utk.edu>
wrote:

>Kevin,
> How do I create a named pipe? I am not sure as to how to do that.
>-Jay
>(patel@.cs.utk.edu)
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!
|||Kevin,
Your option 1 below implies that you need Named pipes if you have no
domain controller and want Windows Authentication mode. Is that
correct? If so, is this requirement documented somewhere?
Lou Arnold
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Hey There,
When I try to connect using the Named Pipes, I have pipes enabled on
both the client and server end, with the server pipe being
"\\.\pipe\sql\query" and trying to keep the client pipe the same as
above. When I try to connect, I get this error:
Attempting connection
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not
exist or access denied.
TESTS FAILED!
I have added the user and password that I am logged into now on XP Pro
onto the Windows 2000 Server machine. What do you think I am missing?
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hey There,
I have tried the procedure that was suggested. I have added the user name
and password that I am logged in as on my Windows XP Pro machine to the
Windows 2000 Server machine that has SQL Server 2000 installed on it. I have
also created the same username and password on SQL Server 2000 as a valid
user. I have enabled pipes on the server and client with the server pipe
being the default pipe: "\\.\pipe\sql\query" and I have set the client pipe
to the same value. Now I get this error when I try to do a test connection:
Attempting connection
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or
access denied.
TESTS FAILED!
What else could I be missing?
-Jay
(jay@.doityourself.com)
Lou_Arnold@.nospam.com (Lou Arnold) wrote in message news:<40ff4f17.8220370@.nntp.flfrd.phub.net.cable.r ogers.com>...[vbcol=seagreen]
> Kevin,
> Your option 1 below implies that you need Named pipes if you have no
> domain controller and want Windows Authentication mode. Is that
> correct? If so, is this requirement documented somewhere?
> Lou Arnold
> On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
> McDonnell [MSFT]) wrote:
|||Jay...
I can't help you further with your problem, sorry. However at least
you have an error messge. Perhaps Kevin can help.
I am slowly coming to the conclusion that Windows Authentication
doesn't work unless you operate a domain controller. If your situation
permits, you may want to try connecting those two computers into a
network with a domain controller.
My only other suggestion is that you try this same test with the sql
server in mixed or SQL Server mode (the alternatives to Windows
Authentication) and see what happens . I'm not sure how to change the
mode after installation.
Lou.
PS Whatever happens, please let us know. It would be of great value to
me to have the information.
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Lou,
Thanks for the advice. The reason I would really like to use Windows
Authentication is that when I use the SQL Server Authentication, with
some of the machines, it will prompt you to input the password every
single time you select a database table, or click a form button. It
seems that every move that is made requires that SQL needs to have the
password input.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi Patel,
Let's try to get a better error message. Try to make the Named Pipe
connection using a Test ODBC Data Source.
When you create a new ODBC DSN, the wizard will walk you through and
generate a much better error message if it fails.
What we need is the OS Error number.
Example: OS Error 53 == Network name not found
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

When I try to create a System DSN connection to our SQL Server 2000
database that is installed on a Windows 2000 machine, I keep on
getting the following error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
We do not have IIS or any web server installed on the database server
machine or the Windows XP Professional machine that is trying to
connect to the Windows 2000 machine. The machines can all see each
other, and we are actually have the machines networked via the
Workgroup setting, not using the Domain setting. Anyone have any ideas
as to what can be the issue?
Thanks,
Jay
(patel@.cs.utk.edu)Hi Patel,
Since you're not in a domain, Windows Authentication works very
differently. Windows Authentication is commonly used while you're in a
domain and the client has been authenticated on the domain. The error
message "null" indicates that we're unable to "impersonate" the client in
order to make a Windows Authenticated connection.
You have two optioins.
1. Duplicate the nt username & password on both machines and Use Named
Pipes to Connect.
2. Use SQL Standard Security instead of using Windows Authentication.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
How do I create a named pipe? I am not sure as to how to do that.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Named pipes are not created, but rather enabled - with both the
Client and Server Network Utilities.
For the Client Network Utility, start it by Start>Run>cliconfg.exe.
The left pane shows disabled protocols. The right pane shows enabled
protocols. In the left pane, click on Named Pipes and then use the
Enable button between the two panes.
For the Server Network Utility (at least for an MSDE version) find the
file SVRNETCN.EXE. Double click to start and the perform the same
actions as in the Client Network Utility, but for the server instance
in question. If you have installed the server as the default instance,
it will have no name, so its just the computer name that will appear
in the server name pull-down list.
If you have a firewall installed on the machines in question, please
say so, since there will be rules to create to open ports if you have
not done so already.
You should also see the article:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/defaul...306&Product=sql
Lou Arnold
Ottawa, Canada.
On Wed, 21 Jul 2004 21:15:32 -0700, Jay Patel <patel@.cs.utk.edu>
wrote:

>Kevin,
> How do I create a named pipe? I am not sure as to how to do that.
>-Jay
>(patel@.cs.utk.edu)
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!|||Kevin,
Your option 1 below implies that you need Named pipes if you have no
domain controller and want Windows Authentication mode. Is that
correct' If so, is this requirement documented somewhere?
Lou Arnold
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>