Path/File access error: '\VB*.tmp'

[dave]

Hi all,
I have a user getting this error message when attempting to copy sheets
within a single Excel 2003 workbook. She's opening the XLS file within a
network folder for which she has proper permissions to read and write, but
the root directory of the network drive she's on does not give her those
permissions. From the path given, it appears that Excel is trying to write
a temporary file to the root of the current drive, thus causing the problem.

I've verified that her default XL document folder is correctly set, as well
as set the startup directory for her Excel icons to be local directories in
which she has full permissions. Is there some other setting that will allow
me to force these temp files to be in a specific location?

Also, I've already tried a complete reinstall of Office 2003. She also has
the same problem on two different PCs. No other users have the same
problem, however.

Thanks in advance,
Dave

 

[Dave Peterson]

Saved from a previous post--Your file names look close to the AVG suggestion:
==========

If those .tmp files look like: ...\VB*.tmp

I searched google again for "\vb" and .tmp and got a few hits.

One of them:
http://groups.google.co.uk/group/mi...caad1c774cc?lnk=st&q=&rnum=3#061eecaad1c774cc
or
http://snipurl.com/1339g

One person posted that they saw files that had names like: ~RF26c83af.TMP.

It was caused by AVG.

You can read her description in this thread:
http://groups.google.co.uk/group/mi...ct:autorecover"&rnum=2&hl=en#cccd4eed0638e395

or
http://snipurl.com/jyus

A while ago, someone posted back that uninstalling something called "Panda
ClientShield" fixed a similar problem.

Even if you're not running "Panda ClientShield", you could try disabling this
program to see if the problem goes away.

===============================
ps. I didn't remember correctly. That thread from Wendy (#7) does indeed point
to AVG as the culprit.

 

[dave]

Dave,
I had seen similar postings, but since we weren't using AVG on her
particular workstation, I kind of blew them off. We are using AVG on the
server where these files exist, so I've adjusted it per Wendy's post, and
now it's time to wait and see. I'm dying to know why it affects only this
one user...

Thanks for your help,
Dave

 

[Dave Peterson]

I'd double check that user's AV software. Maybe AVG got installed on that
pc????