Rus exception and not defined in the schema

Olivier Chantraine 96 Reputation points
2023-03-01T09:12:58.23+00:00

Hello,

i'm migrating an exchange 2016 to 2019

the exchange 2016 have several issues, and have a non recommended environment (installed on DC and SQL server for exemple)

the installation of the 2019 ran without issues.

but,

if i try to move mailbox, but it failed :

 Ldap Filter Exception. Details : The attribute type ‎'mailNickname‎' or its syntax is not defined in the schema.

if i try to make an new email address policies i have this error

The following error occurred during validation in agent 'Rus Agent': 'The LdapRecipientFilter is invalid. Ldap Filter Exception. Details : The attribute type 'objectCategory' or its syntax is not defined in the schema.

every try with another option fail with, not definied in the schema.

if i try to update-recipient i have this error

The LdapRecipientFilter "(mailNickname=*)" on Address List or Email Address Policy "Default Policy" is invalid.

Additional information: Ldap Filter Exception. Details : The attribute type 'mailNickname' or its syntax is not

defined in the schema..

could you help me with this issue ?

Thanks,

Olivier

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,173 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,469 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
446 questions
0 comments
Accepted answer
  1. Chantraine Olivier 86 Reputation points
    2023-03-29T12:39:20.1633333+00:00

    The group "authenticated users" had read permission to the schema, but it was only for the top level, i changed to "this to top level and descending".

    that resolved this error (and some other too)

    2 people found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yuki Sun-MSFT 41,006 Reputation points
    2023-03-02T07:25:45.9233333+00:00

    Hi @Olivier Chantraine ,

    i'm migrating an exchange 2016 to 2019

    According to the system requirements for Exchange 2019, the coexistence scenario of Exchange 2016 and Exchange 2019 requires Exchange 2016 CU11 or later, so it's suggested to make sure your Exchange 2016 has already been updated to the supported version.

    However, as you mentioned, installing Exchange server on Domain Controllers is not recommended, see: Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController]. And it might be expected that weird issues could occur in such deployment. Thus, it's suggested that you install Exchange on a member server in the long run.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.