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 Connect to SQL 2000 on Win2k3 Server

I am having great difficulty connecting to my sql box, I
vpn'd in from work and connected via remote desktop,
setup the SQL connection locally, and connected fine,
which I am wondering if it was cause I was VPN'd in, but
I disconnected from remote desktop and was still able to
hit my sql server in enterprise manager. Then when I got
home tonight, logged on my XP machine and I cannot get my
sql registration to connect.
SQL Server does not exist or access denied ConnectionOpen
(Connect()
I have no idea what this means...I am just learning SQL
so this is all new to me...please help...I am on a home
network behind a linksys router, both my XP box and the
Win2k3 box are behind the router which has a dynamic ip
for the XP box, and a static one for the 2k3 box.On Windows 2003, if there are any instances of SQL Server installed that
are not on SP3 or higher, TCP will be disabled (there will be messages in
the event logs indicating this). In that case remote connections would fail
because by default clients try to connect with TCP. Upgrade all instances
on the box to SP3 then retry connecting. You can also try to connect from
the remote machines using named pipes (add np: before the machine\instance
in your connection string).
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.