THIS MAY BE THE FIX! I'm going to try to contact MS now to get it and see if
it resolves the problem:
http://support.microsoft.com/kb/935663/en-us
"Bill Wood" wrote:
> Almost forgot, this is a Vista Business to XP-SP2 machine. Main file
> location is on the XP machine. Wireless sync, but I don't think it matters,
> however I probably should try the hard wired route to eliminate that variable.
>
> "Bill Wood" wrote:
>
> > I've never seen a fix for this problem, but every time I try to work with
> > offline files, I end up with bunches of {GUID}.tmp files, and when I try to
> > Sync, I also end up with the message "Access is denied."
> >
> > I have been able to re-produce it, repeatedly. After fixing the mess that
> > is created, I tried to manually go offline, watched the file share in
> > Explorer, and when I opened a document, saved a small change, then went
> > online and "synced" something VERY strange happened.
> >
> > 1. The INSTANT I re-connected the first {GUID}.tmp file was created
> > immediately.
> > 2. When I "synced" again, a duplicate of the .tmp file was created, exact
> > same byte size, but with a new {GUID} label.
> > 3. Every time I sync, same thing, a new duplicate of the .tmp file (exact
> > same byte size), with a new {GUID} is created.
> >
> > ~~~~~~~~~~~~~~~~~
> >
> > Since this was an MS Word Doc, I changed the .tmp extension to .doc, and the
> > file WAS THERE and in tact, it just didn't complete the update for some
> > reason. Also, even when I try to sync, even after deleting the .tmp files,
> > the Sync continues to produce new {GUID}.tmp files. It is almost as if the
> > Sync is attempting to do the file update, places the .tmp file in the folder,
> > and then fails to set even a local registry? flag to show that it copied the
> > file over. So every time you try to sync, it keeps copying another .tmp file.
> >
> > About 6 months ago, I abandoned Vista for this very same reason. Offline
> > file folders are absolutely CRITICAL for me... I just got another laptop and
> > thought I'd give it a try again, HUGE MISTAKE!!! Come on MS, get this fixed!
> > It's posted all over the web... Someone has got to address this...