question

CrisKolkman-8299 avatar image
0 Votes"
CrisKolkman-8299 asked CrisKolkman-8299 commented

Exchange 2016 EMS stopped working

Hello,

We had a failed Exchange 2016 server and decided to build a new one.
Fresh Server 2016 install with Exchange 2016 CU20.

After having a lot of trouble moving (read: create a new database on the new server, copy the old database to the new server and create a recovery database using the old database, move everything from the recovery database to the new database) the database via EMS we are now having issues with EMS, it just won't start anymore and shows below error:

95863-image.png

I have checked the time on the server, it's correct.
SSL certificate seems to be fine as well.

WinRM seems to be fine and the needed services are running.

What could be wrong here?


office-exchange-server-administration
image.png (32.9 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CrisKolkman-8299 avatar image
0 Votes"
CrisKolkman-8299 answered CrisKolkman-8299 commented

Also after a reboot, emails cannot be delivered anymore with following error message:

SMTP error from remote mail server after end of data: host 192.168.200.45 [192.168.200.45]: 451 4.7.0 Temporary server error. Please try again later. PRX4

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The SMTP error seemed to be caused by faulty DNS config.
For the new server I used an IP address of an old server but that old server still had DNS records in our domain.
After removing that record, mails started to float in and out again.

Now only the EMS error left...

0 Votes 0 ·
EricYin-MSFT avatar image
0 Votes"
EricYin-MSFT answered EricYin-MSFT commented

Great.
Have you tried re-creating the powershell VD?
1 Open windows powershell and run add-pssnapin Microsoft.Exchange.Management.PowerShell.SnapIn

2 Remove the VD:

 Get-PowerShellVirtualDirectory -Server <Server>| Remove-PowerShellVirtualDirectory

3 Create the VD:

 New-PowerShellVirtualDirectory -Server <Server> -Name Powershell -RequireSSL $false -BasicAuthentication $false -WindowsAuthentication $false -InternalUrl http://<server.fqdn>/powershell

4 Run IISreset.

Also, check if any errors in Event log.


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.



· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the suggestion, but it didn't seem to help:

95906-image.png

Also that command doesn't remove the VD under Exchange Back End, is that normal?

95859-image.png

When I go to Echange Back End > PowerShell-Proxy > Modules, I get below error, is that normal behavior and maybe related to this?

95860-image.png



0 Votes 0 ·
image.png (79.1 KiB)
image.png (24.4 KiB)
image.png (66.4 KiB)

Yes, it's expected. And the second error you mentioned, found in my lab as well, I don't think it's the reason.
Would you try another account to login?
In a similar thread, it seems due to account things.


0 Votes 0 ·
CrisKolkman-8299 avatar image
0 Votes"
CrisKolkman-8299 answered CrisKolkman-8299 commented

SMTP error is back as well :(

SMTP error from remote mail server after end of data: host 192.168.200.45 [192.168.200.45]: 451 4.7.0 Temporary server error. Please try again later. PRX4

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Rebooted and mails are being delivered again... Hope this will not keep going like that :(

0 Votes 0 ·
CrisKolkman-8299 avatar image
0 Votes"
CrisKolkman-8299 answered CrisKolkman-8299 commented

It seems like the failing mail delivery and the EMS failing was caused by the failed Exchange server (still didn't figure out how but oh well...).

After I shut the failing Exchange server down I could connect to the EMS of the new server.
Removed everything from the old server using EMS (the VD's) and removed all the connectors for the old server in ECP.
After that I disjoint the domain and removed all the DNS records pointing to the old server and removed it's AD account.

I then followed this guide (https://techgenix.com/removing-exchange-server-mailbox-your-environment/#:~:text=When%20removing%20a%20server%20that,on%20Uninstall%20(Item%202).) from the section Removing manually... using ADSI Edit.
As last step I removed the databases from the old in ADSI Edit as well.

Leaving this open for a little while in case it goes wrong again :)


· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
Did you point mail.domain.com to the old server?
You can feed back when you think it's stable.

0 Votes 0 ·

No, we have mail.domain.com pointing to another server.
We have pointed webmail.domain.com and autodiscover.domain.com to the new server now.

Well at least we can see at unstable as....
We got the same SMTP and the EMS error again which made me decide to install the newest CU on the old server which broke the server.

After a reboot the mails started floating in and EMS is working again but don't know how long this will last...

0 Votes 0 ·

May I know how the old server was broke?
I would check if the DC is running normally by runing DCdiag and the connection by running repadmin /showrepl. The time on dc also needs to sync with your servers.
Go to Event log and see if any unnormal error exists, for example the back pressure events 15004- 15007.
Besides, check your IIS-Exchange Backend, are the Virtual Directories listed as below picture showing? And the physical path, does it point to correct ClientAccess folder?96304-3.png


0 Votes 0 ·
3.png (147.6 KiB)
Show more comments