Discussion Locked

Excel - Problem in Saving

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have found a machine specific problem with Excel which happens only when saving using "save as" and overwriting an existing document on a network drive. This is happening to two of our users. Both users are Win98 on a Novell 4.11 Network. Whensaving in this manner the machine totally locks with GPFs. It is not a rights issue and we have already completely removed and reinstalled Excel including registry entries. Any other type of save or "save as" to a local drive does not produce thisresult.

6 replies

by stillatit

You need to look at where Excel is putting its temp files for these users, and whether the users have full rights to the directory and files. When Excel edits a file it creates a temporary file. At save or save as time, it wants to rename the temp file to the final name. As far as I know it does NOT delete the old file first. In a save as, if the user rights don't allow the user to clobber the old file by renaming a new file on top of it, the operation dies horribly. Read-only files also cause this sort of problem, for the same reason.

Look at the directory rights of users for whom this works and users for whom this does not work.

Good luck.

by bhall2271

Thanks for your effort but we have checked user rights. Both temp files and originals save to the same directory. One of the two users this is happening to did not have any issues until we upgraded her machine. This did not change her network rights. All users have full supervisory rights to their own directories. Also we are not getting the typical "cannot save file" message, just the blue screen of death.

by delfeye

I have experienced 0246:014747FB on two different machines. Both times it was because of a conflict with Excel and antivirus software (McAfee VScan.) One of them was fixed by upgrading VScan, but the other one was not fixed until I installed NAV instead.

Not sure if this is the answer, but the situation was similar.

by bhall2271

Thanks very much. One of our staff people also found info on this in a recent article. It resolved the problem on both machines. We upgraded to McAfee 4.5 from 4.0.2 which seems to be the worst version.

This discussion is closed to new replies.