Re: 565 errors after in-place upgrade

Tech-Archive recommends: Fix windows errors by optimizing your registry

??? Shouldn't need to sign up. After everything loads, scroll to the bottom
of the web page to view the answer(s).

--
Merv Porter [SBS-MVP]
============================

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:Obaz2wRRIHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Merv,

I don't know if it would help. I always refused to sign up on that site.
Long story.....

--
Claus
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23PB2%23hMRIHA.5288@xxxxxxxxxxxxxxxxxxxxxxx
Any help here?

Failure Audit Event ID 565
http://www.experts-exchange.com/Security/Win_Security/Q_21503494.html

--
Merv Porter [SBS-MVP]
============================

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:%23V6tHbLRIHA.4128@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I'm getting about 20 of these errors each day after an in-place upgrade
from SBS2000 Premium to SBS2003 Premium. I turned Object Auditing off
and they still show up. Has anybody come across this? The only relevant
KB I could find just states that MS is aware of the issue.

EventID: 565
Source: Security
Category: Object Access
Type: Failure Aud

Object Open:
Object Server: Microsoft Exchange
Object Type: Microsoft Exchange Database
Object Name: /o=DomainName/ou=first administrative
group/cn=Configuration/cn=Servers/cn=ServerName/cn=Microsoft Private MDB
Handle ID: 0
Operation ID: {0,1293970828}
Process ID: 4784
Process Name: C:\Program Files\Exchsrvr\BIN\store.exe
Primary User Name: ServerName$
Primary Domain: DomainName
Primary Logon ID: (0x0,0x3E7)
Client User Name: JGuillen
Client Domain: DomainName
Client Logon ID: (0x0,0x4D2051B9)
Accesses: Unknown specific access (bit 8)

Privileges: -
Properties:
---
%{a8df74ba-c5ea-11d1-bbcb-0080c76670c0}
Unknown specific access (bit 2)
Unknown specific access (bit 3)
Unknown specific access (bit 5)
Unknown specific access (bit 6)
Modify public folder admin ACL
SYNCHRONIZE
Unknown specific access (bit 1)
Unknown specific access (bit 2)
Unknown specific access (bit 3)
Unknown specific access (bit 5)
%{d74a8774-2289-11d3-aa62-00c04f8eedd8}
WRITE_DAC
SYNCHRONIZE
Unknown specific access (bit 0)
Unknown specific access (bit 4)
Unknown specific access (bit 5)
Modify public folder quotas
DELETE
Unknown specific access (bit 0)
Unknown specific access (bit 1)
Unknown specific access (bit 2)
Unknown specific access (bit 6)
Administer information store
DELETE
READ_CONTROL
WRITE_DAC
SYNCHRONIZE
Unknown specific access (bit 1)
Unknown specific access (bit 2)
Unknown specific access (bit 3)
Unknown specific access (bit 5)
Mail-enable public folder
DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
SYNCHRONIZE
Unknown specific access (bit 2)
Unknown specific access (bit 3)
Unknown specific access (bit 4)
Unknown specific access (bit 6)
Modify public folder expiry
DELETE
WRITE_OWNER
Unknown specific access (bit 2)
Unknown specific access (bit 3)
Unknown specific access (bit 5)
Unknown specific access (bit 6)
Modify public folder replica list
DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
Unknown specific access (bit 0)
Unknown specific access (bit 2)
Unknown specific access (bit 3)
Unknown specific access (bit 5)
Unknown specific access (bit 6)
Modify public folder deleted item retention
DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
Unknown specific access (bit 1)
Unknown specific access (bit 4)
Unknown specific access (bit 5)
Unknown specific access (bit 6)
View information store status
DELETE
READ_CONTROL
SYNCHRONIZE
Unknown specific access (bit 0)
Unknown specific access (bit 1)
Unknown specific access (bit 2)
Unknown specific access (bit 4)
Unknown specific access (bit 5)
Unknown specific access (bit 6)
Create top level public folder
WRITE_DAC
SYNCHRONIZE
Unknown specific access (bit 1)
Unknown specific access (bit 2)
Unknown specific access (bit 3)
%%1557
%%1558
%{d74a8769-22b9-11d3-aa62-00c04f8eedd8}
Access Mask: %18


--
Claus







.

Relevant Pages

  • Re: What is the release date for SBS 2008?
    ... Being at least 8 months away from launch, prices are unknown. ... Merv Porter [SBS-MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: 565 errors after in-place upgrade
    ... Sorry about the confusion. ... solution how to "make them go away" (disable Object Auditing in policy). ... Unknown specific access ... Modify public folder admin ACL ...
    (microsoft.public.windows.server.sbs)
  • Re: 565 errors after in-place upgrade
    ... Failure Audit Event ID 565 ... Client User Name: JGuillen ... Unknown specific access ... Modify public folder admin ACL ...
    (microsoft.public.windows.server.sbs)
  • 565 errors after in-place upgrade
    ... SBS2000 Premium to SBS2003 Premium. ... Client User Name: JGuillen ... Unknown specific access ... Modify public folder admin ACL ...
    (microsoft.public.windows.server.sbs)
  • Re: 565 errors after in-place upgrade
    ... Failure Audit Event ID 565 ... Client User Name: JGuillen ... Unknown specific access ... Modify public folder admin ACL ...
    (microsoft.public.windows.server.sbs)