• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 794
  • Last Modified:

MSADC Event ID# 8026 Application event log errors

I am getting the following Application Event Log entry on my Exchange Server 2003 after I tried to stop and restart the SMTP service.  The service wouldn't stopfor a long time, then didn't start well either.   I ended up having to reboot the server to get SMTP back up.  After that I get a MSADC error (See Below) every couple minutes.  Server functioning ok, mail is happy, but I'm not sure why this message keeps coming up.  Both our 2003 AD DC's are up and happy, AFAIK.  Any help?

LDAP Bind was unsuccessful on directory EXCHSERV.domainname.com for distinguished name 'NTGROUP\Administrator'. Directory returned error:[0x51] Server Down.   (Connection Agreement 'Config CA_man_EXCHSERV' #1596)
0
patmoli
Asked:
patmoli
  • 4
  • 3
1 Solution
 
Netman66Commented:
Are you using a Mail Connector for something?  This error would indicate the connector can't bind to the other exchange directory it's setup with.

Likely the Administrator password changed on the other site if you are using one.
0
 
patmoliAuthor Commented:
Not that I know of...  One site.  The only thing thats not "out of the box" is SRS, which has been left on the server since the migration from 5.5,  2 years ago. (I'm afraid to remove it, I don't want to mess anything up)  We have rebooted the server quite a few time in that period without that error ever popping up.  What kind of problems can I expect with this issue not being dealt with?

As you can probably tell, I'm still learning 2003, I was ok at best on 5.5.
0
 
Netman66Commented:
I think that may have been in place to migrate from 5.5.

My bet is that you can safely delete that connection object.

0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
patmoliAuthor Commented:
Do you think thats whats causing the Application Error?  I'd love to fix this and go home...getting late here.
0
 
Netman66Commented:
If the SRS service is still there, start the service.  This should rid you of the errors.

SRS was used to sync directories between 5.5 and 2003.  If you aren't doing that any longer, then uninstall it and the connector.

I believe it is, yes.  It's also very likely causing the long delays.

0
 
patmoliAuthor Commented:
It's been a bit now since I started the SRS service, no more errors.  I'll close this off, but I'll let you know that I'm not going home, I'm off to the pub to lift a pint for you!

Cheers!
0
 
Netman66Commented:
Awe...I wish I could join you!

Enjoy!!!

0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now