500 Internal Server Error Technet
Contents |
2, 20153 0 0 0 Over the past several months, I've seen an increased number of Exchange 2013 cases where certain admin users received a 500 status error when attempting to log in to ECP:
The first question I ask whenExchange 2013 Ecp Http 500 Internal Server Error
I get these specific cases is "Does the admin account have a mailbox"? In pretty exchange 2013 ecp 500 unexpected error much every case that I can remember, the response is "No". And immediately, I know exactly where to look! A little history… exchange 2013 owa http 500 internal server error As you may know, because of the design of Exchange 2013 - the CAS role simply locates your mailbox, then proxies the request back to your mailbox server - an "anchor mailbox" is used. This anchor mailbox
Exchange 2013 Ecp Error 500
is simply your Exchange GUID, and is used for a number of reasons in Exchange 2013 connectivity. The most obvious, though, are: As mentioned above, so that an Exchange 2013 CAS knows what mailbox server to proxy a request to To prevent the 'Your administrator has made a change so you must restart Outlook' message that you get when a mailbox is moved to a different site. You can see evidence of the anchor
Exchange 2013 Owa Error 500 After Login
mailbox when you configure an Outlook profile for an Exchange 2013 mailbox:
Notice the ExchangeGuid is used as the 'Server' in the outlook profile, instead of an actual server name. OK that's great and all, but what does that have to do with thisstatus 500that I'm getting? Well, let's think about it. If the Exchange 2013 CAS needs to know where to proxy a request, but the request is coming from an account that has no mailbox, and thus no ExchangeGuid associated with it, how does Exchange know which mailbox server to proxy? In instances like this, Exchange 2013 uses the ExchangeGuid of system mailboxes to determine where to proxy the requests. In this specific scenario, Exchange uses the system mailbox SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} Note: When pulling up the system mailbox(es) using Get-Mailbox you must specify the -Arbitration parameter or the command will not work. So how do I fix this? Typically, what I've found is that this is caused by either the database with the system mailbox is unavailable, or some attribute on the system mailbox account has become corrupt or is missing. Many times, this issue is accompanied by another - such as users unable to connect to Exchange, and the 500 error is discovered when the admin attempts to log in to ECP to try a2013, Exchange 2010 SP1, OCS 2007 R2, Exchange 2010 and OC 2007 R2 Getting Internal Server Error 500 when creating New-CsPartnerApplication for Exchange exchange 2016 ecp error 500 2013 ★★★★★★★★★★★★★★★ Jens Trier Rasmussen [MSFT]November 22, 20129 0 0 0 One
Exchange 2016 Ecp 500 Unexpected Error
of the steps in creating OAuth integration between Lync Server 2013 and Exchange Server 2013 is to create a exchange 2016 http 500 internal server error New-CsPartnerApplication on Lync 2013 referencing the OAuth metadata document from Exchange 2013 (http://technet.microsoft.com/en-us/library/jj688151.aspx): New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl "https://autodiscover.litwareinc.com/autodiscover/metadata/json/1" When running this cmdlet you might get the error https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ "New-CsPartnerApplication: Cannot bind parameter ‘MetadataUrl' to the target. Exception setting "MetadataUrl": "The metadata document could not be downloaded from the URL in the MetadataUrl parameter or downloaded data is not a valid metadata document, error: The remote server returned an error: (500) Internal Server Error." When you look in the IIS log on the CAS server you will see a corresponding https://blogs.technet.microsoft.com/jenstr/2012/11/22/getting-internal-server-error-500-when-creating-new-cspartnerapplication-for-exchange-2013/ entry similar to this "2012-11-20 14:03:57 192.168.200.40 GET /autodiscover/metadata/json/1 - 443 - 192.168.200.35 - 500 0 0 265″. I have seen this in a couple of cases and the common root cause has been that the "Microsoft Exchange Server Auth Certificate" has been missing from Local Computer\Personal certificate store. The "Microsoft Exchange Server Auth Certificate" certificate is used by the OAuth implementation on Exchange 2013. You can see it referenced in the output of Get-AuthConfig: Get-AuthConfig RunspaceId : b7de8683-bd90-4e24-a78f-d6933871cd48 CurrentCertificateThumbprint : A33E4C629AE9553E186F93474E796D598B1F7424 PreviousCertificateThumbprint : NextCertificateThumbprint : NextCertificateEffectiveDate : ServiceName : 00000002-0000-0ff1-ce00-000000000000 Realm : Name : Auth Configuration The certificate with CurrentcertificateThumbprint needs to be listed, when you do Get-ExchangeCertificate on the Exchange 2013 servers. If it is not, there you will see the problem with Internal Server Error. The fix is to create a new "Microsoft Exchange Server Auth Certificate" by using the following sequence of cmdlets In EMS on the MBX server: New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName "cn= Microsoft Exchange Server Auth Certificate" -FriendlyName "Microsoft Exchange Server Auth Certificate" -Services smtp Do not accept to replace the SMTP cer
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions https://technet.microsoft.com/en-us/library/jj219455.aspx TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training exchange 2013 Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business 500 internal server For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States - English Sign in Downloads & Updates Products Support Forums Library We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Office 2013 Office Web Apps Deploy the infrastructure: Office Web Apps Server Deploy the infrastructure: Office Web Apps Server Deploy Office Web Apps Server Deploy Office Web Apps Server Deploy Office Web Apps Server Overview: Office Web Apps Server Plan Office Web Apps Server Deploy Office Web Apps Server Technical reference TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Deploy Office Web Apps Server Office Web Apps Applies to: Office Web Apps Server Topic Last Modified: 2016-03-23 Summary: Explains how to deploy Office Web Apps Server on-premises for use by SharePoint 2013, Lync Server 2013, and Exchange Server 2013. Audience: IT Profess