As far as I can see there is a soap issue. Do you have configured your POA to support Soap? Secure soap (preferred; i.e. port 7191). Did you try to connect GMS server with POA on command line? I.e telnet poa-server 7191 ...

Check your POA's SOAP logs for other clues,   from the http console,   POAip:7181/eventlog  MMDDsoa.00#   logging in with admin level GW creds.

Assuming this is a replacement GMS, is the old one still working?

The main issue seems to be as the error mentioned "Setting "soapServer" is empty!"

As you mentioned all is set in the Web interface under Config what exactly is set in "POA SOAP Address:Port" on th Config, GroupWise tab?

This needs to be the IP/hostname of a POA and the port number this POA has SOAP enabled with SSL, also the firewall must allow the GMS server to access this port.

Hi Andy,

Sorry I was away for a few days. Yes this is a replacement GMS and our old one is working. This one isn't.

They each have their own  trusted application keys.

SOAP is enabled on the POA:

07:44:14 3A70   SOAP Agent: Enabled
07:44:14 3A70   SOAP Port for Incoming SOAP requests: 7191
07:44:14 3A70   SOAP over SSL: Enabled

I can telnet from the new GMS to the POA on 7191

gms02:# telnet POA_IP 7191
Trying POA_IP...
Connected to POA_IP.
Escape character is '^]'.
^]

Connection closed by foreign host.

What I see in the POA SOAP logs is a lot of this (Since the 2nd GMS was configured):

05:58:38 6D98 Shutdown of Threads
05:58:38 6D98 Waiting for GWSOAP-MRLP-Handler_80 to terminate...


So can I have 2 GMSes temporarily talk to the same POA?

thanks,
Andrew

Hi Rob,

I've tried hostname and IP address in GMS with no luck.

The POA it talks to has secure SOAP enabled on 7191 and I can telnet to the POA from the GMS server on 7191. The firewall has TCP 8120,4500, and 7191 allowed on the GMS.

I an wondering if two GMSes can talk to the same POA.

thanks,

Andrew

Yes, POA can talk to more than one SOAP connection or more than one GMS. However I recommend not to overlap users in two different GMS.

Normally yes, don't overlap users on multiple GMS, but with one exception, when getting a new GMS ready to replace the old one, so that you can do it without user downtime. (those switches are so nice when they go well)

So far, when I've done the replace GMS hop, I've just reused the old Trusted App.

What are the SOAPs threads looking like on the POA's http console's main page, example from my oh 'so busy' lab

If you can do a POA restart with the new GMS off, watch a regular day, then fire up the new GMS and see what it does.

How many SOAP threads are configured?  Should be maxed to 40

Perhaps comparing the POA's SOAP logs from before you started the new GMS and since for other clues.

on the POA's http console, Configuration tab,  take a look at these three

I forget exactly what to look for in them, but searching should come up with some useful hits,  and again, comparing to just one GMS up, vs both. (post reno cleanup in very muggy heat, 28, feels like 37 at the moment. Brain a bit misted over as I try to relax here ;)

Have you looked into /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/groupwise/connector.xml ,

if the soap-server and the trusted app and the tusted app key are correct.

And you need port 4500 incoming open as the gms listens on that port. I don't know, if in GMS 18.4 port 8191 has to be open, too, that was necessary in older builds, but I don't remember, when that changed, but probably before 18.4.

Our max number of SOAP threads is 40 and looking at the POA now we are using 26 right now. 

At the moment only the old GMS is talking to the POA so all I see in the three Configuration  --> *Lists is the old GMS talking on behalf of all our mobile users and nothing from the new one.

The one thing that stands out to me in the groupwise connector.xml is these three fields are empty:

<groupwiseAdminAddress/>
<groupwiseAdminUser/>
<groupwiseAdminPassword/>

But I don't see a way to put those values in via the web interface.

thanks,

Andrew