Solved

Event 565 Directory Service Access event log failure every minute for Exchange 2000

Posted on 2007-03-27
4
913 Views
Last Modified: 2013-12-05
Event Type:      Failure Audit
Event Source:      Security
Event Category:      Directory Service Access
Event ID:      565
Date:            3/27/2007
Time:            12:31:04 PM
User:            COMPANYNAME\MAILEXCH$
Computer:      MAINSERVER
Description:
Object Open:
       Object Server:      DS
       Object Type:      configuration
       Object Name:      CN=Configuration,DC=COMPANYNAME,DC=LOCAL
       New Handle ID:      -
       Operation ID:      {0,19320975}
       Process ID:      260
       Primary User Name:      MAINSERVER$
       Primary Domain:      COMPANYNAME
       Primary Logon ID:      (0x0,0x3E7)
       Client User Name:      MAILEXCH$
       Client Domain:      COMPANYNAME
       Client Logon ID:      (0x0,0x126D072)
       Accesses            Control Access
                  
       Privileges            -

 Properties:
SYNCHRONIZE
List Contents
Write Property
Delete Tree
            Manage Replication Topology

Getting error every minute. I've searched and tried a few things with the permissions but didn't have much luck. Errors are on Windows 2000 DC, coming from Exchange server. The email server used to be a BDC pretty long time ago and has been demoted since with no errors afterwards, and these started up out of nowhere some time ago

Thanks folks
0
Comment
Question by:Spawn_X
  • 2
  • 2
4 Comments
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
Let me get this correct, the Exchange server used to be a domain controller and you demoted it?
That is an unsupported action and will often break Exchange.
I suspect that the errors are in relation to its former role. There will probably be little that you can do about it - the only thing I would suggest would be to swing the data out to a new machine and rebuild the original as a member server.

Simon.
0
 

Author Comment

by:Spawn_X
Comment Utility
Yes - we have a main server/DC, and for a couple months I kept the exchange 2000 machine as a DC as well - it worked without a problem, but then i read up that its not recommended to keep exchange 2000 as DC, so I demoted it. We have two servers total, the main / DC and the exchange. Everything still continued to run fine

This was maybe 8 months ago? We haven't had any issues but now there's some odd glitches with regards to sending / opening email with someone else's credentials, and this event log failure, so I figured I'd start with this

I do have some new larger faster hard drives that I need to put in, so do you just suggest I rebuild it from scratch?

Any comments as far as what to name the new server? can it create glitches if i name it the same as what it currently is, or better to use a new name?

Thanks sembee the exchange guru!
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
Comment Utility
When it comes to rebuilding I tend to suggest swinging the data out to another machine.
http://www.amset.info/exchange/migration.asp

The alternatives are too high a risk.
If you want to change the hard disks as well, then it would seem that you have the perfect excuse, if you can find another machine that can take the data while you make the move. You could use the same machine name, as long as you remove Exchange in the correct way and drop the machine from the domain before you wipe the machine. It is something I do for clients a couple of times a year - it just takes careful planning.

Simon.
0
 

Author Comment

by:Spawn_X
Comment Utility
The main server is an SBS 2000 install (1 server setup when i came here) so moving mailboxes there isn't a problem, and per your advice, I will do that.

Disjoin machine from domain before wiping it? Ok, got it. Going to do it this weekend

Appreciate the help, Thanks
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Know what services you can and cannot, should and should not combine on your server.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video discusses moving either the default database or any database to a new volume.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now