Internal Server Error. An Internal Error Occurred. 1359
Contents |
games Xbox 360 games Windows the page must be viewed over a secure channel iis 6 games Games for Windows phone PC games Entertainment
500 Internal Server Error
All entertainment Movies & TV Music PC games Business & Education Business Store Education Store Developer Deals Sale Microsoft Surface deals Xbox deals Free shipping. Free returns. Gift cards Find a store Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive MSN Bing Microsoft Groove Microsoft Films & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC Accessories Xbox & games 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 the 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 (Canada) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
| Address Book | Member List | Search | FAQ | Ticket List | Log Out Custom Error HTML pages with 1359 (500) error Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [ISA 2006 General] >> General >> Custom Error HTML pages with 1359 (500) error Page: [1] Login Message << Older Topic Newer Topic >> Custom Error HTML pages with 1359 (500) error - 27.Nov.2009 4:14:13 AM rickyjohn Posts: 10 Joined: 21.Oct.2008 Status: offline Hi all, https://support.microsoft.com/en-ca/kb/912122 When on ISA 2004 we used to usetwo particular customised error html files (12002R and 12028R)for both intermittent errors of our published website(file cannot be found etc.) and planned outages, as this is what ISA would throwwhen URLs weren't accessible. However since going to ISA 2006 EE, we've started usingweb server farms and of course ISA uses connectivity verifiers to check availability of http://forums.isaserver.org/Custom_Error_HTML_pages_with_1359_(500)_error/m_2002095354/tm.htm the website. Now, when theapplication is deliberately takendownISA no longer throws either of these errorhtmls when users try to access, but instead the following error - Error Code: 500 Internal Server Error. An internal error occurred. (1359). It seems as if because ISA is using connectivity verifiers to check website/server availability, when it is actually unavailable it throws this 500 internal server error when users access (i.e. when we weren't using web server farms and connectivity verifiers in 2004, taking the app down would cause ISA to throw either the 12002R or 12028R errors which we could customise). So my question isdoes anyone know anything aboutthis particular 500 (1350) error andhow I use the errorhtmls to capture this specific error (when the web server farm is taken down). Thanks in advance. Post #: 1 Featured Links* RE: Custom Error HTML pages with 1359 (500) error - 27.Nov.2009 6:29:09 AM Jason Jones Posts: 4663 Joined: 30.Jul.2002 From: United Kingdom Status: offline I think this is an internal error, not HTML pages, but I could be wrong... Cheers JJ _____________________________Jason Jones | Forefront MVP | Silversands Ltd
500 Internal Server Error in ISA One of the most difficult errors to troubleshoot http://www.chicagotech.net/msapps/isa3.htm 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 at internal server 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 by the internal server error 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 likely to happen when co