none
Exchange 2016 - CU8 ECP - Only showing text RRS feed

  • Question

  • We have an Exchange server 2016 with CU8 that only shows text when logging on to ECP.

    We installed CU8 after this error occured, hoping that it would fix it, which it didn't.

    OWA and Powershell is working.

    We tried with another Exchange server, and that one could open ECP, and manage the server in question. That server is now gone again.

    We use public certificates from Comodo.

    Have read a lot of forums and articles, but still can't get this to work.

    We have tried resetting and reinstalling the web services with no luck.

    Any tips to how to get this server to work again?

    Wednesday, April 4, 2018 5:28 AM

All replies

  • Hi Finn,

    Can you please share us the snapshot for detail?


    Cheers,
    Aerrow
    Blog: pdhewaju.com.np
    Please remember to mark the replies as answers.

    Thursday, April 5, 2018 3:31 AM
  • Have it ever worked? What is .Net version installed on the server?

    Is problem same with all browsers?Tried to add site to trusted sites in IE and see if it helps?

    Does this url give same error? https://localhost/ecp/?ExchClientVer=15


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Thursday, April 5, 2018 5:42 AM
  • Here is the snapshot.
    Monday, April 9, 2018 5:32 AM
  • Yes it has worked. The picture above is from the server we installed Friday.

    The .NET version is 4.7.1.

    The problem is the same for all browsers, and we tried to add the sites to Trusted Sites in IE.

    We have tried https://localhost/ecp/?ExchClientVer=15 and https://localhost/ecp/?ExchClientVer=15.1

    We installed a new server on Friday, and that worked perfectly until we moved it to the correct OU.

    Today we got the same error on the new server. 
    We are going to install another server and leave it in the Install OU to see if it's the OU that does it.


    Monday, April 9, 2018 5:39 AM
  • If it stopped working after you moved the server to new OU, please check your group policy. Run Group policy results on the affected computer and confirm which settings have been applied to it

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Monday, April 9, 2018 8:14 AM
  • That's what we are going to do. Add one GPO, test, add another, then test again ect.

    Just installed the third server, and right now it's working locally, but not from other servers/clients that has gotten hardened.

    Tuesday, April 10, 2018 7:54 AM
  • Today the new server stopped working, even if we didn't add any GPOs.

    The pages came up ok, then with CTRL F5, it failed.

    Wednesday, April 11, 2018 11:46 AM
  • Have you Run Group policy results on the affected computer just to check which policies have been applied?

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Wednesday, April 11, 2018 4:33 PM
  • gpresult showed that we had no GPO applied.

    Today we ran Windows Update, and after that we get the HTTP Error 500 on the server. So now It's even worse than it was yesterday.

    We also added CU9 but that didn't help.

    Thursday, April 12, 2018 9:52 AM
  • Which .net version is your server on?

    https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed

    Please update it to 4.7.1 that is supported version for that CU.

    Also check IIS and that correct certificate is binded to the site.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Thursday, April 12, 2018 10:20 AM
  • The servers are now on Exchange 2016 CU9 and .NET 4.7.1

    We even installed a new Windows Server 2016 with Exchange 2016 CU9, and we can't get it to work properly.

    After the updates this week, we get Error 500 on all our servers after logging on the ECP.

    If we run these commands

    Get-EcpVirtualDirectory | Set-EcpVirtualDirectory - FormsAuthentication $false -BasicAuthentication $true -WindowsAuthetication $true

    and

    Get-OwaVirtualDirectory | Set-OwaVirtualDirectory - FormsAuthentication $false -BasicAuthentication $true -WindowsAuthetication $true 

    we are able to start the ECP, but then we never get the logon page. 

    Monday, April 16, 2018 8:29 AM
  • Hi Finn,

    When you access the EAC on the server via the following url, what's the result now?

    https://localhost/ecp

    Did you check the certificate which is binded to the site in IIS? Is it correct?

    By default, authentication settings should be as below in Exchange server, try to revert back to the default settings and check again:


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    Thursday, April 19, 2018 9:25 AM
    Moderator
  • We have a vaild certificate.

    Turned on Forms authentication again.

    Now when I start ECP, it starts with the logon page, and I managed to log on as intended.
    Will try this with the other two servers.

    Friday, April 27, 2018 7:51 AM
  • On Friday after turning on Forms Authenication, the servers worked. Got back to work today (Monday) and both servers give me this after logging on EAC:

    Monday, April 30, 2018 5:23 AM
  • Which url did you try with, mail.domain.com or localhost?

    Try this: https://localhost/ecp/?ExchClientVer=15

    You get login page, but after entering username and password you get the above error?

    Do you see anything in event viewer?


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work


    • Edited by Off2work Monday, April 30, 2018 7:12 AM Edit
    Monday, April 30, 2018 7:12 AM
  • I tried with both https://localhost/ecp/?ExchClientVer=15 and https://localhost/ecp/?ExchClientVer=15.1

    Then https://server.domain.com/ecp/?ExchClientVer=15 and https://server.domain.com/ecp/?ExchClientVer=15.1

    The strange thing is that this worked on Friday, and nobody has done anything to the servers during the weekend.

    I get the login page, and the 500 error comes when logging in.
    Monday, April 30, 2018 7:34 AM
  • Ran this one again:

    Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -FormsAuthentication $false -BasicAuthentication $true -WindowsAuthentication $true 

    and 

    Get-EcpVirtualDirectory | Set-EcpVirtualDirectory -FormsAuthentication $false -BasicAuthentication $true -WindowsAuthentication $true

    and now I can open ECP, but never get the login page. 


    The I ran 

    Set-EcpVirtualDirectory -identity "Server\ecp (default web site)" -FormsAuthentication $tr
    ue -BasicAuthentication $true -WindowsAuthentication $false

    and

    Set-OwaVirtualDirectory -identity "Server\Owa (default web site)" -FormsAuthentication $tr
    ue -BasicAuthentication $true -WindowsAuthentication $false

    and get the 500 page. The settings are like this:

    Monday, April 30, 2018 8:02 AM
  • can normal users login to OWA and ECP?

    When user login to ECP (mail.domain.com/ecp) using external URL, they will be able to login ,but interface is different.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Monday, April 30, 2018 8:11 AM
  • Created a test user on one of the servers we are testing on. I managed to logon to OWA as that user.

    I got the 400 with the :( when trying to logon ECP. This user doesn't have the permissions to logon to ECP.

    Tried again with my user that has permission, and got HTTP 500

    Monday, April 30, 2018 9:13 AM
  • can you test same login from another pc using external url? They should be able to login to ECP, but different menu and layout.

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Monday, April 30, 2018 9:45 AM
  • From an external computer I get the options page for the user.

    Monday, April 30, 2018 10:07 AM
  • YEs, that is correct view. Can you login with admin account to ECP using external computer as well?

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Monday, April 30, 2018 11:40 AM
  • Then I get the HTTP 500 Error.

    Monday, April 30, 2018 12:00 PM
  • Hi,

    for me the following works:

    Open Powershell as administrator:

    cd $exscripts

    updatecas.ps1

    BTW: Problem at CU9 Exchange 2016 Server 2016

    greetings Thomas


    Thursday, July 5, 2018 8:09 AM
  • HI,

    This is posible solution for on premis Exchange.

    You could try to with F12 developer tools. Open ECP in Internet Explorer and pres F12 to open developer tools. Then refresh ECP page and go to developer tools. There you shoud see all request that go to exchange ecp. Click one file. for example list.js. Under column Resoult/Description you will probably see error 404 - not found.

    You should check if the path exist on the server. For example: https://mail.company.com/ecp/15.1.1415.x must be on the exchange server  (default path C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp\15.1.1415.x. Each CU has his own folder. Folder size shoud be few MB. If this folder is emty than this is the reason for scrumbled text. For test yust copy data from one previous CU folder.

    If you look on developer tool on the right under tab Headers for example file list.js you shoud see under Request Headers - Cookie: x-BEResource=your server name - This is the server where you account has Exchange database. In this case you should check IIS ECP on that server.

    Hope this helps.













    • Edited by Damjanc Monday, July 16, 2018 6:39 AM
    • Proposed as answer by Myles37 Tuesday, October 23, 2018 12:43 PM
    • Unproposed as answer by Myles37 Tuesday, October 23, 2018 12:43 PM
    • Proposed as answer by 0Zz D Wednesday, May 8, 2019 8:43 PM
    Monday, July 16, 2018 6:13 AM
  • Hi,

    in my case, it took a long time to troubleshoot this problem - but finally, I found a solution:

    In IIS-Manager, there were two options which were set for „Default Web Site“ as well as for „Exchange Back End“.

    Deleting

    „Content-Security-Policy = frame-ancestors <your domain name>“

    and

    „X-Content-Type-Options = nosniff“

    as HTTP answer headers made my EAC work again!

    • Proposed as answer by Kole Perkins Thursday, November 1, 2018 5:21 PM
    Monday, August 27, 2018 1:05 PM
  • Could you please provide some more details on how you did it. Which option in IIS Manager. I see Http Response header but do not see the above options. 

    Any help here would be highly appreciated. I have been struggling for this for a month now, but in vain.  Not sure how to contact Microsoft help ..as I understand its a paid service. At least for new versions Microsoft should provide prompt help. I have a fresh installation of Exchange 2016 CU9/10 but its getting impossible to get it working. Facing the same issue as above, ECP windows shows as text/links. 

    Wednesday, September 5, 2018 3:53 AM
  • We encountered this same issue after upgrading to U10. Of coarse after reading a few hundred articles I was not about to rebuild the production servers or start "rebuilding" back-ends that seemed like it could do more damage and not fix the issue.

    After reading this post I navigated to:

     (default path C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp\) 

     I noticed that I had two folders 15.1.1531.3 and 15.1.1531.7 the second folder was created on the day I upgraded to U10 and besides the folder structure was completely empty. I copied everything from the 15.1.1531.3 folder into the 15.1.1531.7 folder and hit refresh. everything worked like new.

    Hope this helps someone having this issue.


    • Proposed as answer by mike68w Tuesday, January 8, 2019 1:26 PM
    Tuesday, October 23, 2018 12:53 PM
  • After much troubleshooting and research, removing the "X-Content-Type-Options" from the HTTP Response Headers resolved this issue for me as well. Our customer is running Exchange Server 2016 CU11.

    The only option for "X-Content-Type-Options" is "nosniff", therefore, there are not alternative values for this setting.

    Documentation from Microsoft and Mozilla:

    https://msdn.microsoft.com/en-us/ie/gg622941%28v=vs.94%29?f=255&MSPPError=-2147217396

    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options

    Thursday, November 1, 2018 5:32 PM
  • Could you please provide some more details on how you did it. Which option in IIS Manager. I see Http Response header but do not see the above options. 

    Any help here would be highly appreciated. I have been struggling for this for a month now, but in vain.  Not sure how to contact Microsoft help ..as I understand its a paid service. At least for new versions Microsoft should provide prompt help. I have a fresh installation of Exchange 2016 CU9/10 but its getting impossible to get it working. Facing the same issue as above, ECP windows shows as text/links. 

    If you do not see anything in the HTTP Response Headers page, then the values discussed in this thread are not being set. The HTTP Response Headers can be set at either the IIS server or site level.

    See this link for instructions: https://support.microsoft.com/en-us/help/954002/how-to-add-a-custom-http-response-header-to-a-web-site-that-is-hosted


    Friday, November 2, 2018 2:44 PM
  • Oh, and it happened after the update to CU11 borked itself.


    • Edited by mike68w Tuesday, January 8, 2019 1:30 PM
    Tuesday, January 8, 2019 1:28 PM
  • We encountered this same issue after upgrading to U10. Of coarse after reading a few hundred articles I was not about to rebuild the production servers or start "rebuilding" back-ends that seemed like it could do more damage and not fix the issue.

    After reading this post I navigated to:

     (default path C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp\) 

     I noticed that I had two folders 15.1.1531.3 and 15.1.1531.7 the second folder was created on the day I upgraded to U10 and besides the folder structure was completely empty. I copied everything from the 15.1.1531.3 folder into the 15.1.1531.7 folder and hit refresh. everything worked like new.

    Hope this helps someone having this issue.

    I created a profile just to give this answer a vote! After working on this issue for 8 hours, this was the fix that worked.

    Thank you Myles37 for saving at least part of my weekend.


    Tuesday, January 8, 2019 1:29 PM
  • Thank you Damjanc,

    I had exactly the same issue where the ECP showed only scrambled text.

    This was after an auto-update and a restart of our 2016 Exch server.

    Very frustrating, as it took us days to troubleshoot all scenarios.

    @Microsoft, can't you test your updates properly before release?  Precisely the reason why I prefer to keep updates turned-off if a server works.

    Thursday, May 2, 2019 10:04 PM
  • Yeap, that worked for me.

    I was confused because I saw the files on the server that I was troubleshooting. Then I noticed the Backend server was another of the Exchange servers. Make sure to copy all the files into the correct folder and worked successfully.

    Wednesday, May 8, 2019 8:43 PM
  • Worked great for me. I found that the HyperV server updated and reboot at the same time the Exchange server ran some kind of update. This script finished updating the OWA and ECP files. Thanks
    Sunday, June 9, 2019 2:50 PM