UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
5177 views

The Post Office Agent might not be configured for SOAP.

I have a virtual server with VMware ESXi 5 running SLES11 sp1, OES11 and GroupWise 12.
The GroupWise system have one domain and one post office with several users.
The users can access the mailbox with the GroupWise Windows Client, but when they try to login in the GroupWise Webaccess, they get the following error: "[9505] Your post office is unavailable. The Post Office Agent might not be configured for SOAP. Please contact your system administrator".

1.- The post office agent have the SOAP option turned on.
2.- I check the java environment variables and they are pointing to the right directory.
3.- The Linux Firewall is turned off.
4.- rcapache2 start and rctomcat6 start don´t show errors.
5.- I check the webacc.cfg file and all IP´s address and ports (POA & DVA) are fine.

Any help, comment or suggestion will be welcome.

Thanks in advance.
Labels (2)
0 Likes
2 Replies
Absent Member.
Absent Member.

Check to see if the port is being used by SLES...

--El

crivera;2194538 wrote:
I have a virtual server with VMware ESXi 5 running SLES11 sp1, OES11 and GroupWise 12.
The GroupWise system have one domain and one post office with several users.
The users can access the mailbox with the GroupWise Windows Client, but when they try to login in the GroupWise Webaccess, they get the following error: "[9505] Your post office is unavailable. The Post Office Agent might not be configured for SOAP. Please contact your system administrator".

1.- The post office agent have the SOAP option turned on.
2.- I check the java environment variables and they are pointing to the right directory.
3.- The Linux Firewall is turned off.
4.- rcapache2 start and rctomcat6 start don´t show errors.
5.- I check the webacc.cfg file and all IP´s address and ports (POA & DVA) are fine.

Any help, comment or suggestion will be welcome.

Thanks in advance.

El LaGrew elbert.lagrew#katun.com elagrew on twitter
0 Likes
Absent Member.
Absent Member.

Thanks El LaGrew for you reply.
The problem was resolved.
We use SSL to establish SOAP connections, for some strange cause the server certificate assigned to the PO agent did not working correctly.
We generate new certificates and the connections to GroupWise WebAccess were re-established normally.
Regards
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.