Unable to access receive connector in ECP - Exchange 2016

Mohamed Muaweya 21 Reputation points
2021-09-07T09:01:37.297+00:00

After New installation of exchange 2016 , I wasn't able to access receive connector tab in ECP giving the below error :

500 unexpected error :(

an error occurred and your request couldn't be completed. please try again

The following actions had been done with no success:
* Server had been restarted
* Services had been restarted

I tried also to use Exchange Management Shell with the following command:

Get-ReceiveConnector

And it list the receive connectors

but we get the below error:

Property PermissionGroups can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).

Please advise ..

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,332 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,873 questions
Accepted answer
  1. Andy David - MVP 141K Reputation points MVP
    2021-09-07T12:11:18.497+00:00

    You've got an old legacy connector in AD. Is there an old server listed?

    Check through ADSIEDIT
    CN=Configuration -> CN=Service -> CN=Microsoft Exchange -> CN=Domain Name -> CN=Administrative Group -> CN=Servers -> CN=Server name -> CN=Protocols -> CN=SMTP Receive Connectors

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Joyce Shen - MSFT 16,641 Reputation points
    2021-09-08T02:05:39.46+00:00

    Hi @Mohamed Muaweya

    Agree with the suggestion above from Andy, the error informtion "Property PermissionGroups can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0)." indicates that there is an old Exchange object still left in AD.

    What's you newly installed Exchange server version and how many Exchange servers are there in your environment currently?

    Check the path in ADSIEdit provided above to remove the legacy connector then verify the result again. And if the operation still not work, try the below steps:

    1. Recycle MSExchangeECPAppPool in Application Pools from IIS Manager. Application Pools > MSExchangeECPAppPool > Recycle.
    2. Run UpdateCas.ps1 and UpdateConfigFiles.ps1 from the exchange bin directory C:\Program Files\Microsoft\Exchange Server\V15\Bin.
    3. Restart IIS by running iisreset /noforce from a command prompt window and check the result.

    We could also have a go by recreating the ecp virtual directory and see the results. 

     Remove-EcpVirtualDirectory -Identity <ecpvirtualdirectory>  
 New-EcpVirtualDirectory -Server <servername> -ExternalURL <externalurl> -InternalURL <internalurl>

    Restart IIS

    If an Answer is helpful, please click "Accept Answer" and upvote it.

    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.