This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 0%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
I am trying to upgrade from exchange server 2013 to exchange server 2019 - I installed the exchange server 2019 software onto a 2019 standard box.
Everything went flawlessly - no errors during the installation.
When I try to connect to OWA or ECP - I receive the nondescript HTTP 500 error.
EMS connects just fine - no issues.
10 virtual processors, 16GB of RAM and 1 TB of hard drive space.
Any help would be greatly appreciated.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 87%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIG%3C/text%3E%3C/svg%3E)
hello Chris-7026..I'm having the same issue with a rebuilt exchange server ...log on to the ecp page with admin creds but the get the error 500...dont get the exchange admin page.
Have you had any joy fixing this? - thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 28.000000000000004%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
The issue was DNS (it’s always dns) - I corrected the issue by making sure both exchange servers had the correct dns entries and that the dnd server had correct records for the servers.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 2%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBR%3C/text%3E%3C/svg%3E)
How did you make sure both entries were correct and the correct records? TIA.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 23%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDG%3C/text%3E%3C/svg%3E)
DNS on your network interface needs to be setup correctly, it is DNS not binded to your localhost and DNS manager as your local host name, local IP address, it will never work until your DNS, AD, Network Card DNS settings is binded and setup, diskspace, etc nothing todo with it. I can fix this for you if you need it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 48%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
Good day, am having the same issue, can i be assisted with the steps as to how it was resolved
@Tshepo Magabane On my DNS server (which also serves as my active directory server) I deleted the auto created DNS entries for the two exchange servers, and I added them back as static entries. Then I made sure that the only DNS entry on the exchange servers were the active directory server. I deleted the auto created DNS entries for the two exchange servers, and I added them back as static entries. Then I made sure that the only DNS entry on the exchange servers were the active directory server.
If that step hadn’t resolved the connectivity issue, my next step would’ve been to edit the host files on both the exchange servers to make sure they had the correct information for each other and the active directories/DNS server
Ultimately; I deleted the auto created DNS entries my domain name server/active directory server, and I added them back as static entries. Then I made sure both exchange servers had the active directory server as the one and only domain name server. If that hadn’t had worked, I would have edited the host files on both exchange servers to reflect the fully qualified domain names of each server and the active directory server, along with their static IP addresses.