Not an existing data source name. Invalid DSN.

[Renchan Li]

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.

[Kevin Yu [MSFT]]

Hi Renchan,

Based on your description, I assume that you're logging onto the
workstation using a domain account, which is not an administrator of this
machine. If there is any misunderstanding, please let me know.

The System DSN cannot be configured or removed if you're not in the
administrator group. So, please try to have administrator's privilege and
try again.

Thanks!

Kevin Yu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

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

[Renchan Li]

Hi Kevin,

Thanks for the reply and the following up. Both the user.NewDomain and
Administrator.NewDomain are in the Administrator group and have the
Administrator privilege. However, both accounts can not Configure or Remove
the System DSN's, which had been created using the user ID of the OldDomain,
like user.OldDomain account. Using the local Administrator ID of this
workstation doesn't work either. The displayed errors are as before: "Not
an existing data source name. Invalid DSN."

I worked around this difficulty by creating a new System DSN using the
current active account like user.NewDomain, which is in the Administrator
group; I then am able to created the ODBC connection to MSSQL Server 2005
instance located on Windows Server 2003 of the NewDomain.

This workstation can no longer access the OldDomain or use the previous old
ID's like user.OldDomain since the OldDomain machine is shut down. The
NewDomain controller is on a different machine. Do you have any advices on
how to reactivate or remove the previously created System DSN's (created
with user.OldMain account) using the NewDomain user ID's? Thanks.

"Kevin Yu [MSFT]" <v-k...@online.microsoft.com> wrote in message
news:Hr9CGVFD...@TK2MSFTNGXA01.phx.gbl...

[Kevin Yu [MSFT]]

Hi Renchan,

Configuring and removing a certain DSN is actually doing operations in the
registry. In this case please check the permission of
HKLM->Software->ODBC-ODBC.ini key using regedit. You must have the
NewDomain account or the Administrators group have full control to this
key. If currently not, please add the local admin full control.

Kevin Yu
Microsoft Online Community Support
==================================================

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