asked on

Serious Exchange 2000 errors relating to MSExchangeDSAccess and MSExchangeIS

We have had to reboot our exchange server twice of the last week, some of the errors generated are below, is anybody able to shed any loght on the cause of the problem.

We are a single site organisation with 3 DC's and an exchange 2000 server AP 3. All email is filtered for spam and viruses via a gateway server using GFI mail essentials\Security.

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            07/03/2005
Time:            08:24:49
User:            N/A
Computer:      SCOTTIE
Description:
Process MAD.EXE (PID=1976). All Domain Controller Servers in use are not responding:
Spock.bs.local
picard.bs.local
bsph-repdc01.bs.local

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      9153
Date:            07/03/2005
Time:            08:13:13
User:            N/A
Computer:      SCOTTIE
Description:
Microsoft Exchange System Attendant reported an error '0x80005000' when setting DS notification.

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2103
Date:            07/03/2005
Time:            04:15:49
User:            N/A
Computer:      SCOTTIE
Description:
Process MAD.EXE (PID=1976). All Global Catalog Servers in use are not responding:
Spock.bs.local
picard.bs.local
bsph-repdc01.bs.local

Event Type:      Warning
Event Source:      MSExchangeMU
Event Category:      General
Event ID:      1040
Date:            07/03/2005
Time:            03:15:49
User:            N/A
Computer:      SCOTTIE
Description:
Metabase Update failed replication 5 times with error 80004005 (Unspecified error). Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.

Anyone able to provide any pointer... please help. As I suspect this may happen again soon.

ASKER CERTIFIED SOLUTION

Sembee

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Vinnu

ASKER

Thanks for your reply

DNS is set OK and point to our DC's.

I also ran the Microsoft Best Practice analyser and this again found no glaring issues.

I suspect it would not, because the server is OK at the moment. I'm worried it will start messing up in a day or two :(

Vinnu

ASKER

All is now OK, problem resolved itself. I suspect it was a general network error as I found a network port on one of our switch was which was not working properly, replaced switch and no further issue.

Vinnu

ASKER

Please close question. Thanks

Sembee

You have to either close the question yourself by awarding points, or post to the support topic area (top right corner) and ask for another option.

Simon.

Vinnu

ASKER

Thanks Sembee, I'll award the points to you for at least trying to help. Thanks for your advice.

Vin