Re: Not an existing data source name. Invalid DSN.
- From: "Renchan Li" <lirenchan@xxxxxxxxx>
- Date: Wed, 22 Nov 2006 07:26:02 -0800
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-kevy@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:Hr9CGVFDHHA.4808@xxxxxxxxxxxxxxxxxxxxxxxx
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.)
.
- Follow-Ups:
- Re: Not an existing data source name. Invalid DSN.
- From: Kevin Yu [MSFT]
- Re: Not an existing data source name. Invalid DSN.
- References:
- Not an existing data source name. Invalid DSN.
- From: Renchan Li
- RE: Not an existing data source name. Invalid DSN.
- From: Kevin Yu [MSFT]
- Not an existing data source name. Invalid DSN.
- Prev by Date: Re: Connect to dBase V files with ODBC?
- Next by Date: Re: Not an existing data source name. Invalid DSN.
- Previous by thread: RE: Not an existing data source name. Invalid DSN.
- Next by thread: Re: Not an existing data source name. Invalid DSN.
- Index(es):
Relevant Pages
|
|