Groove 2007 RTM client stops responding after open

[Lou Zher]

Okay, I killed off all workspaces, rebooted, ran GrooveClean, ran Groove,
created a workspace, added one text file to the file tool, double clicked it
to open it. It opened in notepad, I edited it, saved/closed it. All is fine.
I try to open the same file again... Groove totally locks up. Click close
box to kill it. MOPR reports.

Ran GrooveClean again. Ran Groove again. Opened workspace, double-clicked
file... Groove is locked up again. Killed it again. Ran GrooveClean again.
Ran Groove again... now it is locked up on splash.

Help!
-LZ

 

[Lou Zher]

Okay, tried GrooveClean -all which, for those that aren't aware, basically
resets your Groove data to the point where your identity is gone, which
wasn't pointed out when I saw someone else suggest this for a different
problem and the tool doesn't tell/ask.

I restored my identity, created a workspace, added one text file, opened it,
didn't even edit it, just closed it and tried to open it again. Groove is
locked up.

I got a "Temporary File Warning" saying "Groove cannot delete the temporary
file(s) listed below because they are open in their application(s). If you
want to delete these files now, close these other applications and then
click Retry. If you click Cancel, the files will remain on disk until the
next time you start Groove." and it lists the temp files created when I
opened that file. Trying to look at those files in Explorer, which show
green, even getting the property pane doesn't work and ends up locking up
explorer. Using sysinternal's handle, nothing shows these files open.
Deleting them from the command line seems to work (it doesn't complain), but
it doesn't actually do it. Trying to do that again gives access is denied.

Also, before when Groove died on splash, it couldn't be killed by task
manager (either by end task or end process). Rebooting my machine killed it,
but it took a really long time to shut down.

Grr.. I'm going to try uninstall/reinstall next.
-LZ

 

[Mark Smith]

Hi lou -

Not sure if you've tried setting Groove to NOT start on Windows startup and
then rebooting and nuking your problematic temporary files. Then start Groove.

PS - you saved me a bunch of wasted time last week with a posting about
Groove Web Services and Groove Forms tool definitions, which John Milan
responded to. Props to you!