Groupwise 7 Webaccess Error 503
Favorite Rating: Installing WebAccess Application on OES2/SLES10SP1+OES2 Add-onThis document (3659157) is provided subject to the disclaimer at the end of this document. Environment Products:Novell Open Enterprise Server 2 (Linux based)Novell SuSE Linux Enterprise Server 10 Support Pack 1Novell Open Enterprise Server 2 Add-onNovell GroupWise 7 Situation Purpose:How to install WebAccess Application on OES2?How to install WebAccess Application on SLES10SP1+OES2 Addon?How to install WebAccess Application on Open Enterprise Server 2 (Linux based)?Symptoms:"Error 503" while trying to accessing WebAccessERROR: "Service unavailable" while accessing WebAccessUnable to get to the WebAccess login page Resolution Corrective Actions:WebAccess Application with GroupWise Instance of Apache and Tomcat on SLES10 SP1To install WebAccess Application with GroupWise Instance of Apache and Tomcat on SLES10 SP1, please select the option "Install WebAccess Application with Apache and Tomcat" and "Configure WebAccess Application" and follow the promptsWebAccess Application with SLES10 SP1's instance of Apache and Tomcat on SLES10 SP1To install WebAccess Application with SLES10 SP1's instance of Apache and Tomcat, please follow the steps listed in the following TIDhttps://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=3248145&sliceId=SAL_Public&dialogID=46319979&stateId=0%200%204632771WebAccess Application on OES2In OES2, there will not be any option to use GroupWise instance of Apache and Tomcat. Follow the steps listed below to make GroupWise WebAccess Application work with novell-tomcat5 though tomcat5 may also be installed on the server1. Launch Shell Konsole2. Browse to the GroupWise Software Directory using the cd command3. Type "./install" without quotes and press Enter4. Click "Install Products"5. Click "GroupWise WebAccess"6. Click "Install WebAccess Application"7. Once it is complete, click OK 8. Click "Configure WebAccess Application"9. Follow the prompts and change the Apache path to"/etc/apache2/conf.d"10. Change the Tomcat path to "/var/opt/novell/tomcat5/webapps" (Make sure that it reads tomcat5 and not tomcat4)11. Follow the prompts to complete the install12. Once completed, edit "/etc/apache2/conf.d/gw.conf" file and comment outJkMount /gw/* ajp13 by putting a # symbol at the beginning of the line13. Below the above line, typeProxyPass /gw/ ajp://localhost:9009/gw/Make sure that it is 9009 and not 8009. 8009 is used in SLES10 without OES2 Addon. In OES2, 8009 port is used by Nov
Favorite Rating: Error: 503 on the Browser when users try to log in to GroupWise WebAccess. (Last modified: 06Apr2006) This document (10100201) is provided subject to the disclaimer at the end of this document. fact Novell GroupWise 6.5 Novell GroupWise 7.0 Novell NetWare 6.5 SP4 Novell GroupWise WebAccess symptom Error: 503 on the Browser when users try to log in to GroupWise WebAccess. Java periodically locks up and goes to high(er) util, though not https://www.novell.com/support/kb/doc.php?id=3659157 necessarily 100%. note Unload JAVA and reload TomCat to temporarily resolve the issue.In some cases you might have to unload Apache and reload Apache to get it working. fix There have been number of fixes put in GroupWise as well as NetWare Winsock Modules to fix the above symptoms. To fix the above issue please apply the http://www.novell.com/support/kb/doc.php?id=10100201 following: Apply the latest NetWare Service Pack. (Service Pack 5 or later).Apply the latest GroupWise Service Packs.(Service Pack 6 for GroupWise 6.5).(Latest field test files for GroupWise 7). note Please make sure that all the GroupWise modules running on aparticular server should be upgraded at the same time to avoid any inconsistences. disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. Document ID: 10100201 Solution ID: NOVL104874 Creation Date: 18Jan2006 Modified Date: 06Apr2006 NovellGroupWise Gateway Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
NW 6.5 and Groupwise 7 for one of my clients. I had a problem making http://ngwlist.com/pipermail/ngw/2011-November/161590.html WebAccess work, and ended up re-installing it. This is working fine now, but since then (as groupwise 7 far as I know), when I go to the welcome page, I get the following: Service unavailable! The server is temporarily unable to service your request due to maintenance downtime or capacity problems. groupwise 7 webaccess Please try again later. If you think this is a server error, please contact the webmaster. Error 503 I have done a java -show, and it is only showing catalina once. I'm guessing this is for the WebAccess pages. Any ideas how I can get both these services working on the same machine? Thanks Paul Edward van der Maas16-Jul-2007, 22:08Paul Bailey wrote: > Any ideas how I can get both these services working on the same > machine? Sounds like mod_jk is broken. Check the apache logs and tomcat logs for any hints. -- Cheers, Edward
by: [ date ] [ thread ] [ subject ] [ author ] Yes to that as well. Any other ideas out there? Sue Susan H. Borgos, J.D., CNE Office Technology Solutions, Inc. 4880 E. Atlantic Place Denver, Colorado 80222 720-334-0231 www.ots-denver.com http://www.linkedin.com/in/sborgos -----Original Message----- From: ngw-bounces+sborgos=ots-denver.com at ngwlist.com [mailto:ngw-bounces+sborgos=ots-denver.com at ngwlist.com] On Behalf Of Kenneth Etter Sent: Monday, October 31, 2011 2:51 PM To: 'NGWList' Subject: Re: [ngw] Groupwise Web Access HTTP 503 errors - report Ok. And another longshot, but you are using: https://