Exchange 2010 SP1: Event 1053 in the event log (MSExchange ActiveSync)

Error 1053 (source: MSExchange ActiveSync) is logged if an attempt is made to access a mailbox of a domain administrator via Active Sync or if inheritance has been deactivated on the Active Directory object for other reasons. To resolve the problem, inheritance must be reactivated for the respective user account or the correct rights must be assigned for the "Exchange Servers" group.

MSExchange ActiveSync)

Exchange ActiveSync does not have sufficient permissions to create the container "CN=XXX,OU=XXX;DC=SRV,DC=XXX" under the Active Directory user "Active Directory operation failed on DC. This error is not retriable. Additional information: Access denied.

Active directory response: 00000005: SecErr: DSID-03151E07, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

„.

Ensure that the user has inherited permissions granted to 'domain\Exchange Servers' to execute the 'List Content', 'Create Child Object' and 'Delete Child Object' commands for objects of type "msExchangeActiveSyncDevices" and that the user does not have denied permissions blocking these operations.

Details:%3

Switch on inheritance:

Start the "Active Directory Users and Computers" console on a DC and display "Advanced Functions" under View.

Then open the relevant user and switch to the "Security" tab.

Click on the "Advanced" button. Then check the box "Include inheritable permissions of the parent object".

Alternative: Assign suitable authorizations for the "Exchange Servers" group

Repeat the steps above and switch to the advanced security settings, then search for the "Exchange Servers" group and click on "Edit"

Now allow the following authorizations:

11 thoughts on “Exchange 2010 SP1: Ereignis 1053 im Event Log (MSExchange ActiveSync)”

  1. Nach fast 10 Jahren nachdem du diese Lösung veröffentlicht hast wird sie immer noch benötigt. Heute von mir erfolgreich eingesetzt nach einer Exchange 2013 zu 2019 Migration.
    Frank du bist leider Geil :)

    Gruß
    Alex

    Reply
  2. Warum auch immer die Vererbung weg war, aber hier habe ich unkompliziert die passende Lösung gefunden da die MS Seiten immer sehr weit ausholen bei der Fehlerbehebung.

    Danke und Gruß
    Matthias

    Reply
  3. Pingback: PeTuH

Leave a Comment