Synchronization Issues with Files view

[Richard]

For several workspaces that I am a member of, Groove is failing to display
the Files tab of the workspaces.

I am fairly confident that during the original synchronization, the files
were downloaded - it took a heck of a time to download - but the tab is not
available.

I am also getting messages about user mapped locations for other workspaces
during the initial sync.

I formatted my computer just a day ago, so I am redownloading all my
workspaces, hence why I'm getting a lot of errors. However, these issues were
present before the format, and I had hoped the format would solve them.

Courses of action I've tried, include:
- using the Groove clean application.
- deleting the account from the computer in question and re-using a fresh
backup (from a second machine that is working fine).
- formatting the computer and reinstalling everything.

I have a second machine which doesn't seem to have any issues. The machine I
am having issues with is: Vista 64bit Ultimate, Office Ultimate 2007.

However, I have had complaints from a colleage who is experiencing similar
issues with an XP 32bit machine and Office Ultimate. I should also say that I
did eventually get a work around for this problem, by creating a temporary
account using my other machine to add this account to the workspace, download
the workspace and then redownload it using the "faulty" account, but this is
an unacceptable solution.

I am looking for absolutely any guidance/thoughts/solutions to this problem,
and what could be causing it.

Before you ask the workspaces are not over the 2GB "limit".

Many thanks in advance,
Richard.

 

[Gregg Johnston [MSFT]]

Hi Richard,

A couple of things to look at:

1. If the spaces are larger than 2 GB, you will have a problem downloading
them correctly. If the create new spaces and transfer the data from the old
space to the new spaces to break down the size of the old large space.
2. If the spaces are older spaces, consider creating new Groove 2007 version
spaces and migrating the data from the old space to the new space.

Gregg

 

[Richard]

Hi Gregg,

thanks for the response.

I've checked the workspaces and they're not individually over 2GB.
Additionally, the workspaces have all been created using Groove 2007 so it's
not a problem with older versions of groove.

I've also noticed something new. When I start the process of downloading the
workspaces in question, if I double click to open the workspace it opens,
with the message saying that it still needs to download the files, but it
does show all the correct view tabs. It's only when it's completed
downloading everything, and I'm fairly confident that the files are included,
does it update the views of the workspace, upon which the files view tab is
missing.

Thanks again, but have you got any other thoughts?

Regards,
Richard

 

[Gregg Johnston [MSFT]]

Hi Richard,

Is this universal for all the spaces, or just a few?

As a test, can you go to the computer that has the right version of the
space and right click it in the Launchbar. Select Save As > Archive. Move
the Archive file to the problem computer and double click the file. A copy
of the original space should be present with all the tools and all of the
data – is that so? If so, invite the original non-problem computer to the
space. Do all the data and tools show up?

Gregg

 

[Richard]

Hi Gregg,

Again thanks for getting back to me.

This is not a universal thing, but it does effect about 90% of my workspaces
(I have approx 25-30 currently).

I followed your instructions. When I restored the workspace on the "faulty"
workstation, the files were present and accounted for. I then invited the
"healthy" workstation and the files were present and accounted for also.

I hope this helps you pinpoint the issue(s)...

Just in case you were thinking it, I cannot go through this process for all
the workspaces, as that would require all my colleagues to redownload the
workspaces from me, and that's not an acceptable solution.

Thanks again Gregg.

 

[Gregg Johnston [MSFT]]

Hi Richard,

In my experience, that method is the only way to resolve this issue. Either
that or creating brand new spaces and then exporting the data from the old
space into the new space – which is more work.

Gregg