redirect for webspeed error page

webguy

Member
I've been using webspeed for quite some time and I still have never been able to get this to work correctly. How the heck can you specify your own redirect page to replace the webspeed yellow screen of death pages? We are not running everything on windows. Only the messenger is on windows so we never use the progress explorer. our database is on unix, the transaction server is on unix, we maintain and modify settings in the ubroker.properties file in unix. Is there some way to manually set this somewhere in a file on the windows side where the messenger resides? I know when you install the messenger it installs an openedge folder and there is a ubroker.properties file in that folder.

We are on 10.1C. Messenger is on IIS7.5.
 

Casper

ProgressTalk.com Moderator
Staff member
You can easily do that:

Look at KB P11509:

Status: Verified

GOAL:

How to customize error messages without running internal command on
messenger

FACT(s) (Environment):
OpenEdge 10.x
WebSpeed 3.1x

FIX:
1. Create a file called wsCusErr.txt and put it in your Work dir.
2. Edit the file in the following manner:
Every error has the following format:
[error number] [error type]
[message or url]
Where
[error number] is the number of the error, or 0.
0 = catch-all (if no other message is caught, this will be)
[error type] is 0, 1, or 2.
0 = off
1 = custom message
2 = redirect to url

Examples:

To catch error 8239 and put custom text when the error occurs:
8239 1
Name Server is not responding. Please contact administrator.

To do the same, but redirect any other message:
8239 1
Name Server is not responding. Please contact administrator.
0 2
http://www.progress.com

3. If you are using cgiip messenger restart your web server to pick up
the changes in the file (using wsisa.dll or wsnsa.dll, you don't have
to restart your web server)

HTH,
Casper.
 

webguy

Member
Thanks Casper. I actually already tried that without any success. I'll have to tinker with this some more.
 

Casper

ProgressTalk.com Moderator
Staff member
Thanks Casper. I actually already tried that without any success. I'll have to tinker with this some more.

We use it actually and never had problems. What problems you encounter then?
We use it with apache on Linux. I never tried this with IIS on windows though.
 

webguy

Member
We use it actually and never had problems. What problems you encounter then?
We use it with apache on Linux. I never tried this with IIS on windows though.

We are running the messenger on IIS 7.5. transaction server on unix.

On the windows side I created a wsCusErr.txt file and put it in the WRK directory
With the messenger on windows progress defaults the WRK dir in the following path
C:\OpenEdge\WRK

Perhaps I have the format of my wsCusErr.txt entries incorrect. I basically just want to show the same error page for any webspeed error. Just so our users dont see the webspeed error screen. I assume 0 2 designates replace for all errors.


Entry in the file:
 
Top