Vista - Update on issue with files moving to the FolderShare Trash

Hi FolderShare friends,

PLEASE NOTE: Do not clear your FolderShare Trash folder until you are 100%
sure that you have not been impacted by the recent service issue.

We wanted to send you an update on the bug that has caused some user files
to get moved to the FolderShare Trash folder.

We are working on trying to get exact steps to determine if you have been
impacted by this issue. In the meantime, everyone should look at their
FolderShare Trash folder to see if any files have been moved there.

To check your FolderShare Trash folder:
- Click on the FolderShare tray icon
- Click on "More"
- Click on "View Trash"

Additional Details:

Over the past few days we have been upgrading some of our front end servers.
By yesterday evening about half of the front end boxes had been upgraded
when the issue was discovered.

The updated version of these servers introduced a major regression that
caused files that included some specific characters to get moved to the
FolderShare Trash folder. We are also finalizing the list of characters
could would have been impacted.

We tracked this down last night and removed all of these new servers from
rotation. So the propagation of this problem has been stopped.
Some users on this newsgroup have commented that they auto-recovered. This
may or may not happen, so it is CRITICAL that you check your FolderShare
Trash folder.

Here are the scenarios:

1) Does not recover any data recovery:
- If all of your machines were connected to the old front end servers you
will not be impacted. But you can not confirm this without checking your
FolderShare Trash folder.

2) User Files placed in the FolderShare Trash are "auto-recovered."
- If at least one of your machines was connected to one of the old front
ends through this week, you machines will auto-recover

3) User files are not "auto-recovered"
- If all of your machines had been connected to the new front ends before we
removed them, your files will NOT auto-recover and will remain in the
FolderShare Trash. You can restore them manually from the FolderShare Trash
by dragging them out of the Trash folder and back into their original
folder. In some cases, the original Folder may also have been deleted. In
that case, you will also need to re-create that folder.

The date range in question for all of these is Monday December 3rd through
Thursday December 6th , 2007.

We are working on seeing if we can fix this centrally or if we can provide
you a recovery script as well.

Stay tuned. We are very sorry about this bug.
-Mohammed

Can you provide more details on what characters would have triggered this
bug? E.g. - what EXACTLY are considered non-english characters?

Do these qualify:
! @#$%^&*() or -
I have lots of files with ! or - in them.

Also - will the trash show the files only in column 'date modified' 12/3/07
- 12/6/07 ? Or could the modified date be ANY date (in other words, I'm
wondering if I can just look at files in the trash with that narrow date
range - or if I have to consider everything in the trash as potentially
affected?

"Mohammed Samji" wrote:

David:

Regarding your "date modified" question, my experience has been that you
can't use that date range to filter. I have lots of files with accented
letters and these were moved to the trash folder. However, if I look at
their modifed date, it has not changed. i.e., the act of trashing them
doesn't update the modified date.

-Carlos

"David M" wrote:

Hey David,

Carlos is right, FolderShare preserves the modified date of the original
files and does not change that to the date of deletion. To reiterate on
Mohammed's input, the safest option at the moment is to look through your
trash folder's files.

-Anton


"RonchMan" <RonchMan@xxxxxx> wrote in message
news:47D3383C-FFDE-430D-8F01-BC6976B61B13@xxxxxx

Would someone from MS please answer David M's question:
"Can you provide more details on what characters would have triggered this
bug? E.g. - what EXACTLY are considered non-english characters?

Do these qualify:
! @#$%^&*() or -
I have lots of files with ! or - in them."

Anton Katz: "To reiterate on
Mohammed's input, the safest option at the moment is to look through your
trash folder's files. "

This is not very helpful. There are lots of files in my Trash folder. Should
I look at every single individual file to see whether there remains an
existing original copy of it and whether I need the file? A direct answer to
David M's question would be most helpful in this regard.

Thanks,
David P

"Anton Katz [MSFT]" wrote:

Sorry: I forgot to delete all the irrelevant post history in my previous email!

In terms of which characters cause this to happen, our test team is working
on generating a list.

We are seeing this with several ANSI characters over 127.

As soon as we have a definite list, I or Anton will post it here.

-Mohammed

"powelstock" wrote:

Hi,

I'm puzzled as to what to do. I have numerous files that have been moved to
the "trash" folder, but some of those files (as far as I can tell) are also
still on my hard drive in perfectly good condition. (That is, not *.p2p
files.) So if I delete them from the "trash" folder, what happens to the
files that are currently still there on my hard drive? Should I still move
all files that are in the "trash" folder (due to this bug) back to where they
belong, regardless of whether they appear to be unaffected? In other words,
are the files in my FS "trash" just references to files that will be deleted
when the trash is emptied, or are they supposed to be the original files,
moved?

I'm sorry if this question is so muddy. I guess another way of asking this
question is: What do those "trashed" files represent? What happens to the
originals that appear to be where they belong if the "trash" copies get
deleted for real?

Thanks for any overarching guidance about this.
Katherine

"Mohammed Samji" wrote:

In order to know the files afeccted you must in the Windows Explorer
visualize the 'Creation Date' etiquette. Then you must inspect all files in
range date 12/3/07 to 12/6/07.

I expect this help you.

Augusto.

P.D: I agree this is a very serious failure and Microsoft has acted very
bad. I was informed 12/31/07, 3 weeks later. Also, they delay four days in
detect the failure. Microsoft don't care this very important program, and
don't know the disaster that a failure as this can provoke in the users.

I'm very frustrated at this point. After the update, I still get files
deleted. I can't remember which file belongs to which folder, which makes it
very difficult and annoying to move back. Is there some sort of a permanent
fix for this??

Thanks in advance!

"apardo" wrote: