Infinite loop after moving files in Groove

[Jazzesq]

I've moved a large number of files to new workspaces, to unload some old
workspaces. Altogether I moved maybe 1 gig. Everything looked fine until I
opened up Groove after the move and there was a great number (maybe 800+ mg)
of files to be uploaded again. Since then it's been a week or so and now the
constant number I see every day is 105 mg. How do I get this transfer to
stop uploading, and where are all these files going? Thanks.

 

[c1sbc]

My experience in moving a large number of files within Groove workspaces has
been to do it individually (for large files) or small groups (of smaller
files).
Are the other members of the workspace on your local network installation or
outside it?

SBC

-------------------

sbc111 atspamnot gmail dotty com

weblog:
http://weblogs.asp.net/sbchatterjee

Pickup Groove Developer workspaces:
http://www.ctdotnet.org (bottom of page)

 

[Jazzesq]

I've moved files and folders in Groove for years and know it has to be done
slowly and individually. All the files are where they're supposed to be in
the other computers, but I'm left with this infinite loop and so is one other
computer. As for the "local network installation", we are in three different
locations, two are working wirelessly.

 

[Aaron Suoja [MSFT]]

Hi Jazzesq,

Do you run your account on several different computers and if so do those
computers have all the files in the space? You also mention there are other
members of this workspace - do they run their account on multiple computers
and if so have they received all the files on their boxes?

The communications you see there is likely the data being sent or trying to
be sent to the other computers/users that may not have been online to receive
all the data. If one or more of these computers has been offline and
continues in that state then that machine may likely appear as suspended for
that user.

 

[Jazzesq]

Aaron, thank you for your reply. In my previous post I said "all the files
are where they're supposed to be in the other computers." By that statement
I meant all the files have been received in the correct workspaces on the
other computers. There are no suspended computers.

Kay~

 

[Michael M[MSFT]]

In the future if you need to split a workspace tha requires that much data it
may be best to archive the space and restore it. The space can then be
renamed and you can delete the files from the original space. Once the
deletes are clear you can invite users to the new space. This way the
operations are handled seperately and will have a smaller impact on your
performance. Aaron's comments about users/computer accounts being online will
impact performance in either scenario.

 

[Jazzesq]

Thanks, Michael, I've copied these notes and kept them for future reference.
Any other suggestions about my current problem? Any way to check computers
for wild accounts that I don't know about?