Not an existing data source name. Invalid DSN.
- From: "Renchan Li" <lirenchan@xxxxxxxxx>
- Date: Fri, 17 Nov 2006 13:46:28 -0800
Hi, I would greatly appreciate any advice on resolving the following issue.
After changing a Windows XP Pro SP2 workstation's access domain from domain1
to domain2, this workstation's existing System DSN's pointing to a MSSQL
Server 2005 on Windows Server 2003 Standard cannot be removed or
reconfigured. Clicking on either Remove or Configure function generates the
following error messages (The example System DSN is like) xxx:
xxx is not an existing data source name.
Invalid DSN
The Server is Windows Server 2003 Standard (machine name Win2003) running an
instance like GP9 in MSSQL Server 2005 Standard.
This Windows XP Pro workstation can still connect to the instance GP9 on
server Win2003.
Creating a new System DSN on this workstation to access the GP9 instance on
Win2003 works.
I am just wondering what security issues are involved in changing a
workstation's domain access.
Do I need to login the workstation locally (vs. to the domain having this
issue) using the local administrator and remove the SystemDSN names that are
having issues with? Thanks.
.
- Follow-Ups:
- RE: Not an existing data source name. Invalid DSN.
- From: Kevin Yu [MSFT]
- RE: Not an existing data source name. Invalid DSN.
- Prev by Date: RE: [ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send(
- Next by Date: VFP ODBC Driver install gives error on WIN2003 SP1
- Previous by thread: How can I automate an odbc connection
- Next by thread: RE: Not an existing data source name. Invalid DSN.
- Index(es):
Relevant Pages
|
|
