Isa Server 1359 An Internal Error Occurred
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeProductsLibraryLearnDownloadsSupportForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Status: 1359 An internal error occurred. - Help troubleshooting Forefront > Forefront TMG and ISA Server Question 0 Sign in to vote Ive received a lot of complaints that connection to certain HTTPs sites usually fail. After looking at the logs I find a lot of error messages when connecting to an https site. I really have no clue whatcuold becausing this and how to solve it. Any help would be greatly appreciated it. Failed Connection Attempt 4/1/2011 12:48:57 PM Log type: Web Proxy (Forward) Status: 1359 An internal error occurred. Rule: Allow Web Access for All Users Source: Internal (computerIP:50349) Destination: External (InternalIPServer:443) Request: GET www.hsbc.com.mx Filter information: Req ID: 0bb0af03 Protocol: https-inspect User: domain\username Additional information Client agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Object source: Internet (Source is the Internet. Object was added to the cache.) Cache info: 0x2 (Request includes the IF-MODIFIED-SINCE header.) Processing time: 1 MIME type: Juan Carlos Friday, April 01, 2011 7:01 PM Reply | Quote Answers 1 Sign in to vote Hi, HTTPS Inspection is enabled on your TMG Server and HTTPS Inspection is not compatible with alll websites / certificates. You have to exclude teh problematic websites from HTTPS inspection: http://technet.microsoft.com/en-us/library/ee869532.aspx http://blogs.technet.com/b/isablog/archive/2009/10/19/common-problems-while-implementing-https-inspection-on-forefront-tmg-2010-rc.aspxregards Marc Grote aka Jens Baier - www.it-training-grote.de - www.forefront-tmg.de - www.nt-faq.de Marked as answer by Nick Gu - MSFTMicrosoft contingent staff, Moderator Friday, April 08, 2011 2:02 AM Saturday, April 02, 2011 3:30 PM Reply | Quote All replies 1 Sign in to vote Hi, HTTPS Inspection is enabled on your TMG Server and HTTPS Inspection is not compatible with alll websites / certificates. You have to exclude teh problematic websites from HTTPS inspection: http://technet.microsoft.com/en-us/library/ee869532.aspx http://blogs.technet.com/b/isablog/archive/2009/10/19/common-problems-while-implementing-https-inspection-on-forefront-tmg-2010-rc.aspxregards Marc Grote aka Jens Baier - www.it-training-grote.de - www.forefront-tm
| Address Book | Member List | Search | FAQ | Ticket List | Log Out Publishing to a web farm ( internal site name ) Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [ISA 2006 Publishing] >> Web Publishing >> Publishing to a web farm ( internal site name ) Page: [1] Login Message << Older Topic Newer Topic >> Publishing to a web farm ( internal site name ) - 17.Nov.2006 8:53:03 AM hjadkins Posts: 15 Joined: 8.Sep.2006 Status: offline I need help understanding the web farm tab, in particular the internal site name textbox as what it relates to. Is it an internal DNS entry the points to the servers in the web farm? Or is it the IIS header? Also, Im having trouble with proxy requests https://social.technet.microsoft.com/Forums/forefront/en-US/ef85aab8-a930-4b0e-b7c5-16cde65e18bc/status-1359-an-internal-error-occurred-help-troubleshooting?forum=Forefrontedgegeneral option ( requests appear to come the: ) , I would like to use Original client who sent the request, but if I do the firewall throws a failed connection attempt, my guess is I have a network rule which is wrong. Does anyone have a link or doc in how to setup a web farm using ISA 2006 Enterprise?( Edge Mode). When I start Using certs or SSL it starts behaving strangly. . How about this one Error Code: 500 Internal Server Error. An internal error occurred. (1359)" http://forums.isaserver.org/Publishing_to_a_web_farm_(__internal_site_name_)/m_2002032324/tm.htm Thanks John Post #: 1 Featured Links* RE: Publishing to a web farm ( internal site name ) - 20.Nov.2006 10:05:17 AM tshinder Posts: 50013 Joined: 10.Jan.2001 From: Texas Status: offline Hi John, Check out my article series on this site on how to create a Web Farm. HTH, Tom _____________________________Thomas W Shinder, M.D. (in reply to hjadkins) Post #: 2 RE: Publishing to a web farm ( internal site name ) - 27.Nov.2006 2:12:58 PM hjadkins Posts: 15 Joined: 8.Sep.2006 Status: offline Tom, Thanks for the reply, but .. Can you post the link, I can't find an article relating to publishinga web farm for 2006, In particular the internal site name textbox and how it is used. I can only get SSL working if the web servers think ISA server is the requester, not the orginal client. I'm in the middle of a 2004 to 2006 enterprise migration and I'm stuck on a couple of SSL issues. Thanks again john (in reply to hjadkins) Post #: 3 RE: Publishing to a web farm ( internal site name ) - 27.Nov.2006 4:18:56 PM hjadkins Posts: 15 Joined: 8.Sep.2006 Status: offline This is what I think I figured out. The "Internal Site Name" is used as a common nameso the ISA server(s) can matchto a common cert name coming from the backend web servers(s). In other words, the "Internal Site name" matches the name on my internal SSL certusedonmy web site, if not you get thesecond error below. Also what threw me for a while was, when applying rules to e
2009 ‘Error Code: 500 Internal Server Error. An internal error occurred. (1359)' Error when Using ISA Server 2006 Web Farm Publishing On a very similar theme to my last blog entry, http://blog.msfirewall.org.uk/2009/08/error-code-500-internal-server-error.html this is another cryptic error I have seen quite a few times when using Web Farm publishing solutions. An example screenshot of the error is shown below: In my experience, this error is generated when a publishing rule is configured to use server farm publishing and all farm members are unavailable or unreachable. If you look at the ISA Server alerts whilst receiving this error, you should notice a corresponding isa server alert titled Web Farm Servers Unavailable with a description of: A Web publishing rule stopped forwarding requests to a Web farm because there are currently no servers in the Web farm that can accept requests. So, easy when you correlate the browser error with the ISA alert, but again, not the most useful or informative error message for a user to receive… Please Note: This error will only be shown isa server 1359 after authentication; assuming you are following good security practices and pre-authenticating users at the ISA Server level, of course ;) I hope this was useful… Posted by Jason Jones at 08:14 Reactions: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest 1 comment: Anonymous31 May 2012 at 11:31In IE9 i've used "Tool for developers" -> Script's tab -> Start Debug and suddenly it solved my issue.ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Jason Jones I currently work as a Principal Security Consultant for Microsoft Consulting Services (MCS) in the UK. This position involves providing design, architectural and technical consulting to Microsoft's customers and partners. My specialities focus on the Microsoft Security, Identity and Access space with in-depth knowledge of technologies like Active Directory Certificate Services, DirectAccess and Forefront Edge (TMG/UAG). I am also a former Microsoft Most Valuable Professional (MVP). View my complete profile Search This Blog Popular Posts Recommended Network Card Configuration for ISA Firewall Servers (Updated) A common question about ISA Server configuration by people on the forums is: How should I configure the network interfaces on my ISA... Publishing Exchange 2007 Services with ISA Server 2006 - Creating the Publishing Rule for Outlook Anywhere with Transparent Windows Authenticat