1359 Internal Error Isa

(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  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

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, 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 alert titled Web https://social.technet.microsoft.com/Forums/forefront/en-US/ef85aab8-a930-4b0e-b7c5-16cde65e18bc/status-1359-an-internal-error-occurred-help-troubleshooting?forum=Forefrontedgegeneral 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 after authentication; assuming you are http://blog.msfirewall.org.uk/2009/08/error-code-500-internal-server-error.html 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 Authentication I originally planned to do a series of blog entries

| Address Book | Member List | Search | FAQ | Ticket List | Log Out Error 1359 w/ request forwarding Users viewing this topic: none Logged in as: Guest http://forums.isaserver.org/Error_1359_w%2F_request_forwarding/m_2002040741/tm.htm Tree Style Printable Version All Forums >> [ISA 2006 Publishing] >> Web Publishing >> Error 1359 w/ request forwarding Page: [1] Login Message << Older Topic Newer Topic >> Error 1359 w/ request forwarding - 16.Mar.2007 11:36:49 AM jtower Posts: 1 Joined: 16.Mar.2007 Status: offline I have ISA 2006 publishing a site on a web farm. For simplicity, the web farm only has one server in it 1359 internal right now (to grow later). The application is supposed to display more features to users originating from my company's public internet IP than it displays to otherinternet users. To support this feature, I need the REMOTE_ADDR which it appears I can only get by turning on request forwarding (Requests appear to come from the: Original client who sent the request). FYI, I also need to support HTTPS and HTTP 1359 internal error awareness at the application level so the application can redirect to/from secure on a page-by-page basis. Finally, it would be nice if I could also use the "forward the original host header..." setting so I could build redirection links off the HTTP_HOST server variable. Everything works fine until I turn on the request forwarding feature. When it's on, I get: Error Code: 500 Internal Server Error. An internal error occurred. (1359) Here's my setup: - ISA 2006 Ent - Listener set up on 80/443 with wildcard cert *.externalsite.com - Individual rules matching each app:client.externalsite.com and binding to successive internal ports: - client1.externalsite.com -> webserver:80/443 - client2.externalsite.com -> webserver:81/444 - etc... - Rules all use internal.domainname.com as internal site name (to later support farm) - Webserver publishes sites on above specified IP/Port combination with corrent client.externalsite.com host header What can I do to fix this? EDIT: I forgot to mention that the webserver's default gateway is the firewall server's private IP. Also, the firewall is actually 2 NLB firewalls responding to a single public VIP. Does that complicate things for the packets on the way back out? < Message edited by jtower -- 16.Mar.2007 11:39:13 AM > Post #: 1 Featured Links* RE: E