500 Internal Server Error Isa 2004
Contents |
23, 20120 0 0 0 In this post, I’ll be talking about a web publishing problem and how I dealt with it. The problem was that external internet explorer 500 internal server error clients were failing to access an internal Web server published on ISA
What Does 500 Internal Error Mean
2004 server with HTTP 500 internal error. As usual, I asked the following logs from our customer destination server certificate error tmg when reproducing the problem: - Collecting an ISA data packager while reproducing the problem (as part of ISA Best practices Analyzer log). The tool could be downloaded from
The Target Principal Name Is Incorrect.
the below link: http://www.microsoft.com/en-us/download/details.aspx?id=811 - Collecting a network trace from the internal web server - Collecting a network trace and Fiddler trace from an external test client. It could be downloaded at the following link: http://www.fiddler2.com/fiddler2/ Note: Fiddler or similar tools (like HTTPWatch – we also use it) provide useful information even if the connection is the target principal name is incorrect cannot generate sspi context clear text HTTP. For HTTPS connections it’s nearly a requirement to collect it to see what’s going on from client’s perspective. Another possibility is collecting WinInet/WinHTTP ETL traces which I plan to discuss in another post. Troubleshooting: After collecting the logs, I started troubleshooting the problem a) I first checked the Web proxy logs (collected as part of Data packager logs) and saw the same problem there: (I included only a part of the log and also changed the names deliberately) Result code is -2146893022 which is FFFFFFFF80090322 which is SEC_E_WRONG_PRINCIPAL Actually the web listener used by the given web publishing rule doesn’t have authentication configured. But that error might also be seen when certificate related issues are seen. b) Then I decided to check the ETL trace that was also collected as part of ISA data packager. Please note that the ETL trace collected as part of data packager could only be converted to human readable format by Microsoft support but we also provide a l
| Address Book | Member List | Search | FAQ | Ticket List | Log Out Error Code: 500 Internal Server Error. The target principal name is incorrect Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [ISA Server 2004 General ] >> Exchange Publishing >> Error Code: 500 Internal Server Error. The target principal name is incorrect Page: [1] Login Message << Older Topic Newer Topic >> Error Code: 500 Internal Server Error. The target princ... - 23.Jun.2005 7:58:00 AM rodent Posts: 11 Joined: 29.Nov.2002 From: Stockholm Status: offline Hi,I have the following https://blogs.technet.microsoft.com/nettracer/2012/05/23/getting-http-500-internal-server-error-when-accessing-a-published-web-site-through-isa-2004/ problem:"Error Code 500 Internal Server Error.The target principal name is incorrect.(-2146893022)."This error is described in KB: 841664 at: http://support.microsoft.com/default.aspx?scid=kb;en-us;841664and also numerous times on this discussion board. However after i tried all recommendations and possible solutions, i still have the problem.1 ISA 2K4 std with 4 NIC. The external NIC has about 40 public IP adresses. The Exchange 2k3 server is on the internal LAN.The OWA sites are on the Exchange server http://forums.isaserver.org/Error_Code%3A_500_Internal_Server_Error%25_The_target_principal_name_is_incorrect/m_230059800/tm.htm and they have different internal IP adresses. They have different certs obtained from the internal Cert authority.I exported the certs and imported them on the ISA as described in an article published by Thomas Shinder. Any ideas? All three OWA sites behave in the same way although they have different certs. The ISA2k4 is a member of the domain. I also tried to edit the hosts file on the ISA. e.g.:172.26.113.84 webmail.internal.net. the web listener on the ISA uses these certs. Post #: 1 Featured Links* RE: Error Code: 500 Internal Server Error. The target p... - 23.Jun.2005 2:47:00 PM tshinder Posts: 50013 Joined: 10.Jan.2001 From: Texas Status: offline Hi Rodent,What is the actual name on the To tab on the Web Publishing rule?What is the actual name on the Public Name tab on the Web Publishing rules?What is the actual common/subject name on the certificates?Thanks!Tom (in reply to rodent) Post #: 2 RE: Error Code: 500 Internal Server Error. The target p... - 23.Jun.2005 3:27:00 PM techuser Posts: 70 Joined: 11.Jan.2005 Status: offline Hi Rodent and Tom,I had exactly the same error. It looks like something is happening with ISA Server 2004 "Standard" version.Here is a microsoft kb about this:http://support.microsoft.com/default.aspx?scid=kb;en-us;841664HTH,Marcelo (still looking forward Secure OWA to wor
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs https://www.experts-exchange.com/questions/24252385/ISA-2004-OWA-2003-Web-Error-Code-500-Internal-Server-Error-The-target-principal-name-is-incorrect.html Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > ISA 2004 - OWA 2003 - Web Error Code: 500 Internal Server Error. The target principal name is incorrect. Want to Advertise Here? Solved ISA 2004 - OWA 2003 - Web Error Code: 500 Internal Server Error. The target principal name is incorrect. Posted on 2009-03-21 MS Forefront-ISA Exchange 1 Verified Solution 1 Comment 1,540 Views Last Modified: 2012-06-27 I have picked up a client who has an 500 internal ISA 2004 server.. the previous admin was a tinhat type and I am by no means an ISA expert. I added a SSL from godaddy today to the exchange server and followed (mostly) this article: http://technet.microsoft.com/en-us/library/cc713342(printer).aspx I can HTTPS into OWA fine internaly, but not from outside the network I get the Error Code: 500 Internal Server Error. The target principal name is incorrect. Here is from the monitoring of ISA: Failed Connection Attempt NV 3/21/2009 1:41:37 PM Log type: Web Proxy 500 internal server (Reverse) Status: 0x80090322 Rule: Exchange_Web Source: External ( xx.xx.xx.177:0) Destination: (mn.dli.local 192.168.1.229:443) Request: GET https://192.168.1.229:443/exchange Filter information: Req ID: 0b8034ec Protocol: https User: anonymous I have also looked here but this is older ISA and at this point in time over my head. There is a Watchguard Firebox in front of ISA and I have enabled port forwarding for HTTP & HTTPS to the ISA server. Thanks for any help! Capture1.JPG Capture2.JPG 0 Question by:DMTechGrooup Facebook Twitter LinkedIn Google LVL 24 Best Solution byDMTechGrooup Answer was found else where. It required me to put the FQDN in to to box of ISA so I had to make a host file entry for that to be a type of splint DNS. Also I made the mistake of having FBA on the ISA Go to Solution 1 Comment LVL 24 Overall: Level 24 Exchange 10 MS Forefront-ISA 2 Message Accepted Solution by:DMTechGrooup2009-03-21 Answer was found else where. It required me to put the FQDN in to to box of ISA so I had to make a host file entry for that to be a type of splint DNS. Also I made the mistake of having FBA on the ISA and exchange, can only be on one so I changed it to be on the exchange server. PAQ for KB. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with