500 Internal Server Error Isa 2006
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
Internet Explorer 500 Internal Server Error
that external clients were failing to access an internal Web what does 500 internal error mean server published on ISA 2004 server with HTTP 500 internal error. As usual, I asked the following
Error Code 500 Internal Server Error Invalid Index 1413
logs from our customer when reproducing the problem: - Collecting an ISA data packager while reproducing the problem (as part of ISA Best practices Analyzer log). 500 internal server error the target principal name is incorrect The tool could be downloaded from 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 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 cou
500 Internal Server Error in ISA One of the most difficult errors to troubleshoot when using ISA or TMG is the 500 Internal Server Error. It’s so difficult because it is one of the most generic responses yet it has a number of possible causes. We’ll look at a few of the most common ones in this post, along with what to do to verify the cause and fix the problem. Look closely https://blogs.technet.microsoft.com/nettracer/2012/05/23/getting-http-500-internal-server-error-when-accessing-a-published-web-site-through-isa-2004/ at the response message to see what supporting details are in place, and consider what is going on between the client and the ISA/TMG or between your ISA/TMG and the internal server. Are certificates in use? Check the ISA/TMG logs to see if you find: “A certification chain processed correctly, but one of the CA certificates is not trusted http://www.chicagotech.net/msapps/isa3.htm by the policy provider. 0x800b0112 (-2146762478)” in the logs. If there are certificates in use, check the ISA/TMG server’s certificate store to make sure that the root certificate authority and any intermediate certificate authority are trusted. This includes both the certificates securing HTTPS communications and any client certificates used to authenticate the user. Importing the root and intermediate CA certificates into the ISA/TMG server’s operating system store if they are not already present will resolve most certificate issues. If you are unable to do this immediately, use HTTP to communicate to the internal server and a different form of authentication for the client. Not supported? When the client makes a request that is not supported by the ISA/TMG, or the response from the destination server is not supported, the ISA/TMG may return “Error Code: 500 Internal Server Error. The request is not supported. (50)” to the client. Often, this is caused when a client request doesn’t specify content encoding but the published server responds with a content-encoding specified in the HTTP response header. This is most lik
| 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 http://forums.isaserver.org/Error_Code%3A_500_Internal_Server_Error%25_The_target_principal_name_is_incorrect/m_230059800/tm.htm 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 >> https://www.experts-exchange.com/questions/24400578/Error-Code-500-Internal-Server-Error-The-target-principal-name-is-incorrect-2146893022.html 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 problem:"Error Code 500 Internal Server Error.The target principal name is 500 internal 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 and they have different internal IP adresses. They have different certs obtained from the internal Cert 500 internal server 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 work) (in reply to rodent) Post #: 3 RE: Error Code: 500 Internal Server Error. The target p... - 25.Jun.2005 7:34:00 AM rodent Posts: 11 Joined: 29.Nov.2002 From: Stockholm S
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 Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022) Want to Advertise Here? Solved Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022) Posted on 2009-05-12 MS Forefront-ISA 2 Verified Solutions 3 Comments 2,582 Views Last Modified: 2012-05-06 We have an SBS 2003 Standard R2 environment with ISA Server 2006 Standard on a separate Windows Server 2003 machine (Dual NICs). We cannot figure out how to publish OWA or any other SSL encrypted site hosted on the SBS machine. I have been through everything I can think of and all I get is the error in the question title. Currently the web listener has the 3rd party SSL certificate from Thawte and the web server has a self-signed certificate created using the CEICW. The ISA server is a Domain Member. What am I missing? 0 Question by:dsasc Facebook Twitter LinkedIn Google LVL 35 Best Solution byBembi So, fist at all, you have two certificated, one between the client and the ISA, and a second between the ISA and your web server. The certificates must fit to the accessed domain to be valid. So the certificate Go to Solution 3 Comments LVL 35 Overall: Level 35 MS Forefront-ISA 10 Message Accepted Solution by:Bembi2009-05-12 So, fist at all, you have two certificated, one between the client and the ISA, and a second between the ISA and your web server. The certificates must fit to t