RE: Cannot contact provisioning server.

[Hrvoje]

You are right, I also don't have this Home GMS
URL http://blugro1gms.groove.microsoft.com/gms.dll and this is obviously the
reason why no connection to the provisioning server can be established...But
how in the world can I correct this?

p.s. I also have Nod32 installed...

"VinceL" wrote:

> My first Groove installation went fine, along with all my comps. Then when i
> had my friends launch groove, both of them got this error. I reduced it to
> both of them had NOD32 and one of them did not have any entry in the HOME GMS
> URL. Both have brand spanking new Windows Xp installations also. Is there a
> way to add in a GMS URL manually? Anyways see if its the same thing go to
> Options -> Communications Manager -> Network Settings. HOME GMS URL should be
> right in the middle with :
>
> Home GMS URL http://blugro1gms.groove.microsoft.com/gms.dll
>
> My friends one is blank. Anyways i hope we can find an answer!
>
> "Hrvoje" wrote:
>
> > Hi! I keep on receiving this error after Groove 2007 install. Error remains
> > after firewall shutdown, anti virus software shutdown and cleargroove tool
> > use. Tried to install on different machines, always the same error. Help!

[no.si...@googlemail.com]

Hi,

I had the same problem mit Groove and NOD32.

Disablind NOD32 at least helps and lets groove connect to the
provisioning server.

Shame there is nothing showing, what nod32 has to argue about.

Cherrs,
Norb

[pkg]

I have the same problem, i UNINSTALLED Nod32, uninstalled groove, cleaned the registry, reinstalled and have the same problem.

Any solution? please it is CRUCIAL for my work! my isp has no idea why it's not working.

I am on a wireless lan, PPPOE connection if that might help.

thank you in advance

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

[Sidney]

I have the problem too. Here's a question for those others with the problem: are you running Office 2007 for your other Office tools?

I'm running Office 2003 except for Groove 2007. I notice that the Relay Server URL is set to a "backwardcompatibility" machine. Since I have removed all traces of Groove 3.2 (as far as I can tell), I'm wondering whether it's the presence of Office 2003 that causes this, and whether that, in turn, is related to the absence of a GMS URL.

Is anyone with this problem running the rest of Office 2007? (That would rule out this suspicion.)

[Sidney Bailin]

There is an inconclusive discussion of this on another list -

http://www.eggheadcafe.com/software/aspnet/29006985/cannot-contact-provisioni.aspx

- but I'm going to try here to see whether anyone can help. Several folks,
iincluding myself, get the periodic error message "Unable to contact
provisioning server" in Groove 2007. Indeed, if we go to
Options->Communications Manager->Network Settings, there is no entry for Home
GMS URL, suggesting that no provisioning server is specified.

The Help for this error message says to check your network, but this is
bogus: the network is fine, and all communications to/from the computer are
fine.

It seems as if Groove 2007 is getting installed without a provisioning
server being specified. We want to use the Microsoft public server, which I
understand should be http://blugro1gms.groove.microsoft.com/gms.dll.

Interestingly, the Relay Server in my system is specified as

grooveDNS://backwardscompatibility.groove.net

while a colleague who does not have this problem has the Relay Server as

grooveDNS://blugro1relay.groove.microsoft.com

I have no idea where the "backwardscompatibility" is coming from on my
system. I removed all traces of groove 3.1 from the system: folders, registry
keys, install files. I am wondering whether it has anything to do with the
fact that the rest of my Office tools are Office 2003.

I have uninstalled and reinstalled Groove 2007 multiple times, creating new
user id's, and nothing has worked. Any insight into what might be causing
this and how to fix it would be most appreciated.

I am using a trial version. I would like to purchase it, but I'm not going
to spend the money if I can't get it to work!

[Jeroen Jansen]

Maybe a strang question but what kind of machine are you using.
Maybe a Lunovo machine. I had this problem only with those machines with the
default installation from the factory.

see ya

Jeroen
"Sidney Bailin" <Sidney...@discussions.microsoft.com> wrote in message
news:48121A41-53BE-481E...@microsoft.com...

[Sidney Bailin]

I'm on a Dell Latitute D620 running XP Pro.

[Gregor]

I have the same problem and I'm running all office 2007 tools.

I found that on one of my machines where everything works, "Home GMS URL" is
specified, and on the machine where Groove doesn't work it isn't specified.
Is there a way to add this field by ourselves. I searched registry but it
looks that it is not specified there.

[Rich]

Has anyone solved this Issue? Two more of us with the same issue, we
installed Groove on IBM Think Pads and get messages that Groove cannot
contact provisioning server. Both of our machines list the backward
compatibility that you described, instead of the default Microsoft site. How
can we change it and get this product to work?

[Balthazor@discussions.microsoft.com Andrew Balthazor]

I've got this issue as well, on two separate computers.

One a clean install vista ultimate x64 on an existing computer (installed
myself) with a clean install of Office Ultimate 2007.

The other a clean install vista ultimate x84 on an existing computer with a
clean installation of Office Ultimate 2007.

Same issue with both computers; I have the backwards compatibility DNS relay
instead of the public relay. No idea how to change it.

[andrewbalthazor]

Nod32 was the culprit. I'll be writing them next.

I had the same problems listed as others in this thread.

Fixed by adding Groove.exe to the exception list for the IMON module of Nod32 (under the misc. tab. of the IMON module setup options.)

After doing this, create a new account. The new account will have the correct public relay server DNS entry, instead of the backwardcompatibility nonsense.

You have to keep groove.exe on the exception list to allow it to continue to communicate with the public relay server. If you remove it it will prevent communication, even if your account has the correct DNS information.

Tried and tested. You will have to close out Groove and restart it after changing the settings in Nod32; after that, make a new account, and you should be good.

[Andrew Balthazor]

[sidneybailin]

Thank you very much indeed. I added groove.exe to nod32 imon, went ahead and uninstalled/reinstalled groove 2007 just for the heck of it, then created a new account on groove, and the right servers now appear, and no error message.

[Sidney Bailin]

Andrew Balthazor's solution worked for me too. I deviated slightly from his
recommendation in that after adding groove.exe to the NOD32 IMON exclusion
list, I went ahead and uninstalled groove 2007, removed left-over folders
under my name, and reinstalled it, creating a new i.d. for myself. I'm now
getting the correct servers, and no more error message.

Thank you Andrew!

[Andrew Balthazor]

Update for Case #17259 - "IMON interfering with Microsoft Office Groove 2007"
An ESET Customer Care Representative has updated this case with the
following information:
Hello-

Thank you for the info! I apologize for the inconvenience.

The next version of NOD32 will be sans IMON. It's being totally eliminated
from the program for this very reason.

In 1992, when NOD32 was introduced, very few programs operated at the
Winsock level. Today, in addition to Google and Microsoft, 100's of other
developers are creating software in this manner. That would be fine, except
for the fact that any app that operates here needs the top spot in the stack,
and only one program can have it.

As it is now, it can't be enabled at all on a server.

IMON was just the first layer of defense, a supplement. The strengths of
NOD32 are AMON, which scans every file that performs an action, as it
performs that action and the advanced heuristics which is stopping 90%+ of
all new threats, before a definition is even written.

Thank you,
ESET Tech Support

[Walsh@discussions.microsoft.com Richard Walsh]

Thanks Andrew
It turned out NOD32 (an otherwise excellent product) was the culprit for me
too.
Same symptoms and same solution.

[eriknaesstrom]

I just tried to get groove woeing and I'm recieving the same error... I'm not using NOD32 but Avast but so are my coworker and it's working great for him... I tried to reinstall it but that didn't help either, installed it on my other comp and there it worked but not on my work laptop...

Any more suggestions what might be causing this?

[Schaaf@discussions.microsoft.com Forrest Schaaf]

Thank you! This is brilliant. I was going nuts.

I love the little twist that the server becomes
"backwardscompatibility.groove.net" (which doesn't exist), just to confuse
everyone.

Nod32 is awfully popular and there must be countless others in this boat.
It would be nice if MS released an update to fix or warn users about this.

[Ed]

Hi,

I've just installed Groove 2007 and as soon as I try to log in I get the
'Cannot contact provisioning server' error appearing by the systray. Could
this be a firewall issue (Windows firewall has allowed Groove through but I
do have anotehr firewall)?

Thanks,Ed.

[Ed]

Ignore this - it was the problem with NOD32 !

"Ed" <edavi...@hotmail.com> wrote in message
news:O5n9md%23bHH...@TK2MSFTNGP03.phx.gbl...

[jowolf]

What was the problem with Groove and NOD32? When I shut down NOD32 I still cannot connect with Groove.
Please describe in short what you've found.
Regards,
Jo