Discussion:
Error: No Context configured to process this request
(too old to reply)
Kauko Laurinolli
2009-09-30 18:13:21 UTC
Permalink
After updating the latest corrections to NW6.5SP7 our webmail has
stopped working and comes up with the following error:

message _No Context configured to process this request_

description _The server encountered an internal error (No Context
configured to process this request) that prevented it from fulfilling
this request._

------------------------------------------------------------------------
Apache Tomcat/4.1.36-LE-jdk14

Can anyone offer help how to fix this?
Michael Bell
2009-09-30 21:52:21 UTC
Permalink
Post by Kauko Laurinolli
After updating the latest corrections to NW6.5SP7 our webmail has
message _No Context configured to process this request_
description _The server encountered an internal error (No Context
configured to process this request) that prevented it from fulfilling
this request._
------------------------------------------------------------------------
Apache Tomcat/4.1.36-LE-jdk14
Can anyone offer help how to fix this?
Reinstall webaccess. This means the appropriate stuff (directory
corresponding to your context) is missing under tomcat\4\webapps
Kauko Laurinolli
2009-10-01 17:52:50 UTC
Permalink
Post by Michael Bell
Post by Kauko Laurinolli
After updating the latest corrections to NW6.5SP7 our webmail has
message _No Context configured to process this request_
description _The server encountered an internal error (No Context
configured to process this request) that prevented it from fulfilling
this request._
------------------------------------------------------------------------
Apache Tomcat/4.1.36-LE-jdk14
Can anyone offer help how to fix this?
Reinstall webaccess. This means the appropriate stuff (directory
corresponding to your context) is missing under tomcat\4\webapps
I did re-install webaccess and now it comes up with:
*Service unavailable!
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.
If you think this is a server error, please contact the webmaster
<mailto:***@your.address>.
Error 503*

Restarting apache2 and tomcat4 don't seem to help as it did before?
Michael Bell
2009-10-01 19:24:50 UTC
Permalink
Post by Kauko Laurinolli
Post by Michael Bell
Post by Kauko Laurinolli
After updating the latest corrections to NW6.5SP7 our webmail has
message _No Context configured to process this request_
description _The server encountered an internal error (No Context
configured to process this request) that prevented it from fulfilling
this request._
------------------------------------------------------------------------
Apache Tomcat/4.1.36-LE-jdk14
Can anyone offer help how to fix this?
Reinstall webaccess. This means the appropriate stuff (directory
corresponding to your context) is missing under tomcat\4\webapps
*Service unavailable!
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.
If you think this is a server error, please contact the webmaster
Error 503*
Restarting apache2 and tomcat4 don't seem to help as it did before?
I recommend you start reading tomcat.apache.org, because tomcat
configuration is very unpleasantly complcated. A 503 is just a generic
error, probably spat out a nasty one in tomcat.log or catalina.out
(sys:\tomcat\4\logs
Kauko Laurinolli
2009-10-02 13:06:21 UTC
Permalink
Post by Michael Bell
Post by Kauko Laurinolli
Post by Michael Bell
Post by Kauko Laurinolli
After updating the latest corrections to NW6.5SP7 our webmail has
message _No Context configured to process this request_
description _The server encountered an internal error (No Context
configured to process this request) that prevented it from
fulfilling this request._
------------------------------------------------------------------------
Apache Tomcat/4.1.36-LE-jdk14
Can anyone offer help how to fix this?
Reinstall webaccess. This means the appropriate stuff (directory
corresponding to your context) is missing under tomcat\4\webapps
*Service unavailable!
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.
If you think this is a server error, please contact the webmaster
Error 503*
Restarting apache2 and tomcat4 don't seem to help as it did before?
I recommend you start reading tomcat.apache.org, because tomcat
configuration is very unpleasantly complcated. A 503 is just a generic
error, probably spat out a nasty one in tomcat.log or catalina.out
(sys:\tomcat\4\logs
Thanks.
Unfortunately there are no tomcat.log or catalina.out anywhere on the
server drive?
Only logs: admin_localhost_log.2009-09-30.txt and
localhost_admin_log.2009-09-30.txt etc for every day.
Kauko Laurinolli
2009-10-02 13:43:11 UTC
Permalink
Post by Michael Bell
Post by Kauko Laurinolli
Post by Michael Bell
Post by Kauko Laurinolli
After updating the latest corrections to NW6.5SP7 our webmail has
message _No Context configured to process this request_
description _The server encountered an internal error (No Context
configured to process this request) that prevented it from
fulfilling this request._
------------------------------------------------------------------------
Apache Tomcat/4.1.36-LE-jdk14
Can anyone offer help how to fix this?
Reinstall webaccess. This means the appropriate stuff (directory
corresponding to your context) is missing under tomcat\4\webapps
*Service unavailable!
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.
If you think this is a server error, please contact the webmaster
Error 503*
Restarting apache2 and tomcat4 don't seem to help as it did before?
I recommend you start reading tomcat.apache.org, because tomcat
configuration is very unpleasantly complcated. A 503 is just a generic
error, probably spat out a nasty one in tomcat.log or catalina.out
(sys:\tomcat\4\logs
Found it!
sys:/tomcat/4/bin/startup.ncf was replaced with tcadmup.ncf in
Autoexec.ncf for some reason.
As soon as I started it webaccess started to work.

Continue reading on narkive:
Loading...