Spawn_X
asked on
Event 565 Directory Service Access event log failure every minute for Exchange 2000
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=COMPAN YNAME,DC=L OCAL
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
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=COMPAN
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
ASKER
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!
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!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
Disjoin machine from domain before wiping it? Ok, got it. Going to do it this weekend
Appreciate the help, Thanks
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.