User Profile
manuphilip
MCT
Joined 6 years ago
User Widgets
Recent Discussions
Re: Exchange Server 2013 on prem OWA blank screen after logging in
Hi mark_fad It is taking bit more time, as the usual troubleshooting steps didn't help so far. As the certificate swap has introduced this issue, we will check that direction again. 1. Check eventlog in exchange server and see if you have errors like "An error occurred while using SSL configuration for endpoint 0.0.0.0:444". This will popup immediately after you try to login 2. If this is the case, you have to delete this association by following the steps below in exchange server Open command prompt as administrator Type netsh and enter Type http and enter Again type show sslcert and enter You will see two entries for 443 and 444. We know that 444 is incorrect and to be deleted Delete by running the command delete sslcert ipport=0.0.0.0:444 Add the correct entry add sslcert ipport=0.0.0.0:444 certhash=xxxxxx appid="{yyyyyy}" type show sslcert and check if you see the entries as correct 3. The above steps should fix the issue. 4. Suppose the above steps are not applicable, forward us the error message from event viewer so that we will further bring up troubleshooting stepsRe: Exchange Server 2013 on prem OWA blank screen after logging in
Hi mark_fad , Certificate assignments looks okay. Now, it's some error you can try fixing by a built- in tool provided by Microsoft in your exchange server. Open a command prompt and perform the following steps 1. CD "C:\Program Files\Microsoft\Exchange Server\V15\Bin" and then press <ENTER> 2. Subdirectory will change to the above. 3. Updatecas.ps1, then press <ENTER> Try access OWA again after fixing the cas server as aboveRe: Exchange Server 2013 on prem OWA blank screen after logging in
Hello mark_fad , The issue you found is a common issue pops up after certificate renewal. The major root cause found was related to the certificate assignment to the exchange backend ssl bindings for port 443. So, check this at IIS console and make sure that certificate is not missing or assigned correctly. After the fix, just refresh owa and you should be fine there onRe: Exchange 2013 DAG
Hi Prasant Chettri When you enable circular logging in database, It re synchronizes the logs and it will be purged in all database copies. It may few hours depends on the database size. A 200 GB of database with 300 GB logs takes 3 to 4 hours in Blade servers To Enable circular logging, you may use the following cmdlet : Set-MailboxDatabase “DatabaseName” -CircularLoggingEnabled:$True To Disable: Set-MailboxDatabase “DatabaseName” -CircularLoggingEnabled:$False
