Environment
Novell GroupWise 8
Novell GroupWise 8 Calendar Publishing
Novell GroupWise 8 Calendar Publishing
Situation
When accessing http://calendar_host/gwcal/calendar
or a link from a published calendar, the user receives a message
that the services is not available.
On the server, running calendar publishing, Java is using much CPU.
When checking the logs (loglevel on diagnostic) from the calendar host, the last line is:
<html><head><title>Error 404</title></head><body><h1>HTTP: 404 URL not found - ical/getuserlist</h1></body></html>
In the GroupWise system there is a Post Office without users.
On the server, running calendar publishing, Java is using much CPU.
When checking the logs (loglevel on diagnostic) from the calendar host, the last line is:
<html><head><title>Error 404</title></head><body><h1>HTTP: 404 URL not found - ical/getuserlist</h1></body></html>
In the GroupWise system there is a Post Office without users.
Resolution
The problem is caused by a Post Office without user.
When the loglevel is on diagnostics, the log file (found under: /var/opt/novell/groupwise/calhost/logs) will show which Post Office is causing the problem. At the end, there will be the following line:
<html><head><title>Error 404</title></head><body><h1>HTTP: 404 URL not found - ical/getuserlist</h1></body></html>
A few lines higher there will be an entry Host: with the IP-address of the Post Office with the problem.
There are to ways to fix this issue:
When the loglevel is on diagnostics, the log file (found under: /var/opt/novell/groupwise/calhost/logs) will show which Post Office is causing the problem. At the end, there will be the following line:
<html><head><title>Error 404</title></head><body><h1>HTTP: 404 URL not found - ical/getuserlist</h1></body></html>
A few lines higher there will be an entry Host: with the IP-address of the Post Office with the problem.
There are to ways to fix this issue:
- The preferred solution is to disable Calendar Publishing for this PO. To do this open the properties sheet of the POA, go to "Agent Settings" and remove the checkbox for "Enable Calendar Publishing". Restart apache and tomcat on the server the Calendar Publishing Host.
- Another solution would be to create an user in the Post Office.