Internal Server Error The Target Principal Name Is Incorrect
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
2002 / Last Updated on 20 May 2013] Have you ever seen the "500 Internal Server Error" telling your that the "target principle name" was incorrect? What's up with that? The answer is that you need to fix up your SSL bridging configuration. Check out this article to find out what causes the problem and how to fix it. Solving the Dreaded "500 Internal Server Error – The target principal name is incorrect" Error By Thomas W Shinder M.D. As we close out the year 2003, I want https://support.microsoft.com/en-us/kb/841664 to take this opportunity to thank everyone for the very kind words you’ve had for the ISA Server and Beyond book. While we wanted to make the book a valuable reference on the finer points of ISA Server, I never expected so many people would write in about how much they liked it. While I’m not convinced we deserve it, I do http://www.isaserver.org/articles-tutorials/publishing/error505.html want to let you all know that Debi, Martin and I all appreciate it. One of the subjects I spent a lot of time on in the ISA Server and Beyond book was using SSL with Server Publishing Rules and Web Publishing Rules. This was a topic that we only briefly covered in the Configuring ISA Server book. While the coverage of SSL related topics such as secure OWA publishing and SSL bridging is very complete, but there was one thing I left out: the dreaded 500 Internal Server Error – The target principal name is incorrect" error. You actually encountered this error in our first ISA Server book, but because of time and space considerations for that book, we didn’t have the chance to expand on what the specific problem was that created this condition. That’s was unfortunate because a lot of you have encountered this condition, and a lot more of you will encounter it after you start implementing the cool SSL scenarios you read about in ISA Server and Beyond. Take a look at the figure 1 to refresh your memor
Posts How to add multiple RDC listening Ports? What is a Good Replacement for LogMeIn Free? http://www.sbits.biz/solving-the-dreaded-500-internal-server-error-the-target-principal-name-is-incorrect-error/ Quick Fix Backup Volume Shadow Copy Error SBS2003 SBS2008 SBS2011 Blog Archives Blog Archives Select Month February 2014 January 2014 October 2013 April 2013 February 2013 http://www.exchangedude.net/index.php/2011/10/autodiscover-outlook-anywhere-error-the-target-principal-name-is-incorrect/ January 2013 December 2012 November 2012 October 2012 May 2011 April 2011 March 2011 July 2010 May 2010 April 2010 March 2010 February 2010 January 2010 internal server December 2009 November 2009 October 2009 September 2009 August 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 May 2008 April 2008 March 2008 February 2008 January 2008 December 2007 November 2007 October 2007 September 2007 August 2007 July 2007 June internal server error 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 Solving the Dreaded "500 Internal Server Error – The target principal name is incorrect" Error 11/27/2007 -- Russ Solving the Dreaded "500 Internal Server Error – The target principal name is incorrect" ErrorThe target principal name is incorrect. (-2146893022) http://www.SBITS.Biz - Russ Grover Posted in Uncategorized. RSS feed for comments on this post.. TrackBack URL. Comments are closed. « Extending the ISA Firewall’s SSL Tunnel Port Range (2004) Search Error with Sharepoint 3.0 on SBS 2003 » SBITS.Biz © 1998 - 2015 Official SBS Blog Updated inbox component in Windows Server 2012 R2 Essentials for client connector 07/24/2016Windows SBS 2011, Windows SBS 2008 and impact of MS16-072 07/20/2016Survey – Windows Server Essentials Features 02/23/2016 Downloads Skype for Business Online, Meeting Migration Tool (64-bit)Microsoft® SQL Server® 2014 SP2 Latest Cumulative UpdateMicrosoft® SQL Server® 2014 SP1 Latest Cumulative Update
TMGalexander A very common issue faced with people who buy a wildcard certificate is that Autodiscover and Outlook Anywhere will not work because the Certificate Principal Name *.domain.com doesn't match the name returned by the autodiscover service server.domain.com This issue is a pretty easy fix it is enough to run from Exchange Management Shell to match the Certificate Principal Name with the setting returned by the autodiscover service. Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com You can verify the changes you have done by running Get-OutlookProvider If you have the name mismatch the Exchange Server Remote Connectivity Analyzer tool www.testexchangeconnectivity.com returns the following error. : "An HTTP 500 was returned to ISA because the certificate on the published server doesn't match the name in the publishing rule." OR "Error Code 500 Internal Server Error. The target principal name is incorrect. (-2146893022)." Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided. Post navigation ← Outlook anywhere rpcproxy.dll An HTTP 500 response was returned from ISA NLB - Network Loadbalancing and autodiscover for outlook → One thought on “Autodiscover / Outlook Anywhere error : The target principal name is incorrect” kjstech says: 2 November, 2014 at 23:54 Do you have to do this for all three Outlook Provider services, EXPR EXCH and WEB ? Reply Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Time limit is exhausted. Please reload the CAPTCHA. + nine = eleven Blogroll Exchangerserverpro.com I'm a UC Blog Ivo Beerens Mark Swinkels Matt Landis Windows PBX & UC Pro-Exchange blogs Rene Jorissen Ward Vissers Dilbert of the