You may want to try it, but I believe the size of that particular registry value can only be up to 200 characters. This is not enough for a nicely formatted page, but you could return a redirect header to redirect the browser to a nicely formatted page.
FoxWeb Support Team
Sent by Steve Moore on 04/15/2015 05:30:29 PM:
I'm interested in #2. #12 I got covered nicely. This is exactly the informatyion I was looking for I think. Question: Is there a size limit on this key? I would prefer to return a nicely formatted page instead of just a short unformatted string. You example shows just the <body> part of the message. Can I include and entire page including <Head>?
Sent by FoxWeb Support on 04/14/2015 03:09:20 PM:
FoxWeb can return two different types of errors:
- Script errors are returned by FoxWeb channels, during script execution. These script errors can be formatted by using a different Error Template, as described in the FoxWeb Configuration page.
- Errors that are returned by the ISAPI/CGI modules: These errors are returned when the CGI/ISAPI modules are unable to communicate with FoxWeb channels (e.g. when the FoxWeb service has not been started), or when these modules fail to receive a result from a channel within the script timeout. To customize these errors you will need to add a new value named "StubError" in the FoxWeb registry key (hklm\software\Wow6432Node\Aegis Group\FoxWeb\CurrentVersion or hklm\software\Aegis Group\FoxWeb\CurrentVersion, depending on your version of Windows). FoxWeb will return exactly what you enter in this value. The string "%error%" can be used to merge in the actual error message:
StubError="<body><h3>An Error has Occurred</h3>Message: %error%</body>"
FoxWeb Support Team
Sent by Steve Moore on 04/14/2015 02:59:11 PM:
Can you point me to some specific information on returning alternate error pages for "foxweb not started", "foxweb no channels active" and "foxweb timed out" errors in IIS7?