Groove client cannot reach the configuration server

[DanA]

We have setup our own Enterprise Groove implementation. For a couple of
months now the account backups have not been working and new accounts cannot
be created. When I enter a configuration code and server name, immediately
after clicking Next I get "Groove Account Configuration Error" "Groove
cannot reach the Configuration Server"

From netstat I occasionally see a socket to port 80 on the Management Server
in a TIME_WAIT state. Once I had an established connection on port 80 but
that was transient while they were rebooting the server (and I still didn't
get the account created).

Pointing a browser at http://<insert management server name here>/gms.dll
gives me an IIS error: HTTP Error 403.4 - Forbidden: SSL is required to view
this resource

Existing clients still communicate, both P2P and through the Relay Server on
port 2492, but new account creation and account backup fails.

I believe something got screwed up when they tightened security in the DMZ
where the servers are deployed, but I'm over a month into this with no
progress to show. Suggestions?

Dan

 

[DanA]

Possibly relevant update: Admins tell me Windows Server 2003 security patches
were installed in July -- between the last time everything was known to work
and when the problems were first observed. (Correlation may not be
causation, but I've found it to be pretty good guide for setting the priors

 

[Gregg Johnston [MSFT]]

Hi Dan,

This really should be opened with Microsoft Support as a ticket. We will
have to look through the logs to see what might be happening. If you look in
the system and Application Event logs, do you see anything relevant? Also,
take a look at the Audit Log in the reporting section of the Management
Server UI – do you see anything there?

Gregg

 

[DanA]

The audit log is uninteresting, but the event log is chock-a-block full of
GrooveManagementServer Event IDs 312 (HTTP method was not a POST or GET) and
200 (Groove Management Server beta period expired). Nobody here believes
they installed beta software but they could believe it was a Trial license
and the error message is misleading us. These error messages date back to at
least April. Problems started in July (but it may have been at least that
long since the server was rebooted).

No one knows how to determine what the license terms are or how to change
them if they need changing. (N.B., The Relay Server is still working fine,
though I do not know when it was last rebooted...)

I'm working with the top doggie in our support shop now to get someone
assigned to work with MS on it.

Dan