Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MSExchangeDSAccess, event 2114

151 views
Skip to first unread message

wagih@discussions.microsoft.com may wagih

unread,
Jan 5, 2006, 8:18:01 AM1/5/06
to
Dear All,

we have Window Active directory 2003, Exchange 2003 service pack 1
exchange server stopped suddenly users unable to login with this events in
the event log althought the active directory is working fine

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2114
Date: 1/5/2006
Time: 9:21:54 AM
User: N/A
Computer: MAIN
Description:
Process INETINFO.EXE (PID=1860). Topology Discovery failed, error 0x80040931.


Regards
May

Ben Winzenz [Exchange MVP]

unread,
Jan 5, 2006, 9:43:06 AM1/5/06
to
Sounds like Exchange is having a tough time contacting Active Directory.

Where are your DC's in relation to the Exchange server?

Check internal DNS as well. What other errors appear in the Exchange server
event logs?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"may wagih" <may wa...@discussions.microsoft.com> wrote in message
news:8374B894-759D-40EF...@microsoft.com...

Andy David - MVP

unread,
Jan 5, 2006, 9:45:54 AM1/5/06
to


What does "working fine" mean exactly?

I would turn up diags to max on DSAcess Logging in ESM.

may wagih

unread,
Jan 7, 2006, 2:38:02 AM1/7/06
to
below are the other errors apearing : 1053, 1005
Event Source: Userenv
Event ID: 1053
User: NT AUTHORITY\SYSTEM
Description:
Windows cannot determine the user or computer name. (Access is denied. ).
Group Policy processing aborted.
----
Event Source: MSExchangeSA
Event Category: (1)
Event ID: 1005
User: N/A
Description:
The following information is part of the event: Logon failure: unknown user
name or bad password. Facility: Win32 ID no: 8007052e Microsoft Exchange
System Attendant .

Ben Winzenz [Exchange MVP]

unread,
Jan 9, 2006, 12:28:59 AM1/9/06
to
Have you (or someone else) recently changed Security settings, applied any
security patches or any other security tools?

Have you looked in Active Directory for any disabled computer or user
accounts? Is you Exchange server running ON your DC? Which account are you
logging on with?

What it looks like to me is that the computer can't access Active Directory
to determine which Group Policy to apply. I still think this could be a DNS
problem. Did you make any changes at all prior to this happening? Can you
run DCDiag at the command prompt and post back with any errors that it logs?

Also, follow the steps in this article and see if you find anything.
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=1005&EvtSrc=MSExchangeSA&LCID=1033

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"may wagih" <mayw...@discussions.microsoft.com> wrote in message
news:0C930A92-D6E4-4C26...@microsoft.com...

Curt Spanburgh

unread,
Feb 6, 2006, 7:59:29 PM2/6/06
to
I experienced the same error on a clients forest. And sure enough, the
machine account for the exchange server was disabled.

Since a global account was used to start the CRM Exchange connector, that
service would not start as well.

DSACCESS is working fine again, and MSCRM is working too.

How this helps some of you who are implementing MSCRM in your enviroments.
\:>

0 new messages