Forum Discussion

RicardoGDR's avatar
RicardoGDR
Copper Contributor
Apr 11, 2024

Problems after upgrade to CU14

Hi,

 

I'm in the process of migrating from Exchange 2013 CU23 to Exchange 2019.

 

I installed Exchange 2019 CU13 on Win2022 Server, in coexistence with our 2013 and everything was looking good. Before starting with the testing to route emails through 2019, I checked that CU14 was released recently, so I download/install the CU14 in upgrade mode (with the no EP flag) to have the last build, and now I'm having problems with virtual directories, mailboxes, and so ON.

 

Already run the healtchecker powershell scripts and nothing out of the ordinary.

 

Some of the problems I'm having:

 

1. When I clic on the 'authentication' tab in any Virtual Directory (ECP, OWA, EWS) I got this error:

"The task wasn't able to connect to IIS on the server <FQDN>. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable."

The other tabs don't throw me any errors, but almost all options are greyed-out.

 

2. In SERVERS > DATABASES, when entering the properties of any Database that are on the new EX2019, I got this error:
'Exchange can't connect to the Information Store service on server <FQDN>. Make sure that the service is running and that there is network connectivity to the server.'

I cannot create a new Database neither and the status of the currents 2019 Mailbox databases says Uknown and BadCopyCount = 1.

 

3. SERVERS > CERTIFICATES:

Cannot see any Cert here for the EX2019. The error I get:

"Cannot connect to the remote procedure call service on the server named <servername>. Verify that a valid computer name was used and the Microsoft Exchange Service Host service is started."

 

Already check:

- Binding of the Certificate 'Microsoft Exchange 'on the BackEnd and our Public Certificate on the Frontend Server.

- All  Exchange Services are up and running.

- Restart of IIS.

 

It appears that is something with permissions and/or with IIS that breakdown after the installation, but still don't know what it is.

 

Al things related to the 2013 environment appears to be normal and functioning. according. 

 

Something I noticed, on the Certificate error it says the name of the server, and in the other errors, it says the FQDN of the server.

 

Please guide me here, what could be the problem and what to check/confirm.

 

Thanks in advance.

 

3 Replies

  • JeyakumarD's avatar
    JeyakumarD
    Copper Contributor

    Hello RicardoGDR​,

    I'm running into the same issue and errors after installing Exchange SE servers in a Exchange 2016/2019 co-existence environment. If you can share any information on how this is resovled, that would be helpful

  • RicardoGDR Please Exchange Server 2019 try add "Exchange Trusted Subsystem group","Organization Management" of local administrators groups Permission!

  • AnneSexton's avatar
    AnneSexton
    Iron Contributor

    If the service crashes:

    powershell
    Test-ServiceHealth | Where {$_.Status -ne “Running”}  
    Then check for IIS conflicts: focus on MSExchangeFrontEndAppPool to see if it's jerking around
    Rollback command:

    powershell
    Setup.exe /m:uninstall /IAcceptExchangeServerLicenseTerms  
    Don't forget to backup TransportConfig.xml.

Resources