"File cannot be saved, loaded by another user at the moment."

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When editing a document users are getting the error in Powerpoint 2002

"The file cannot be saved right now because the file is
loaded by another user at the moment. You can wait a few
moments and try the save again, or you can cancel this
save and resave uning a a different file name." (Try
again, Cancel).

If they 'try again' it is an endless loop. If they cancel then Powerpoint crashes
These are powerpoint (.PPT) files on a network share
 
Hi Tony,

You have multiple persons accessing the files at the same
time on your network share. This is a bad situation for
sharing files that are edited by a lot of folks. A better
solution is to route the presentation file among the folks
who need to edit it.
If you can't do that, you need to have them save the file
as a different name. And then someone will need to merge
all the edits from all the files. You might be able to
use some of the Version features, but I'm not that
familiar with it, so you might want to check the help file.

HTH,
Glenna
-----Original Message-----
When editing a document users are getting the error in Powerpoint 2002:

"The file cannot be saved right now because the file is
loaded by another user at the moment. You can wait a few
moments and try the save again, or you can cancel this
save and resave uning a a different file name." (Try
again, Cancel).


If they 'try again' it is an endless loop. If they
Click to expand...
cancel then Powerpoint crashes.
 
PowerPoint does not allow for multiple users to edit it simultaneously (like
Access or Excel). The best suggestion would be to break the presentation up
into units that can be worked on independently, then re-assembled at a later
date.

Also, PowerPoint does not play well with networks, consider making a copy of
the main file to your local hard drive prior to editing/showing.

B
===============
Please spend a few minutes checking vestprog2@
out www.pptfaq.com This link will yahoo.
answer most of our questions, before com
you think to ask them.

Change org to com to defuse anti-spam,
ant-virus, anti-nuisance misdirection.
..
..
 
When editing a document users are getting the error in Powerpoint 2002:
"The file cannot be saved right now because the file is
loaded by another user at the moment. You can wait a few
moments and try the save again, or you can cancel this
save and resave uning a a different file name." (Try
again, Cancel).

If they 'try again' it is an endless loop. If they cancel then Powerpoint crashes.
These are powerpoint (.PPT) files on a network share.
Click to expand...

As others have mentioned, it's not a good idea to have multiple people editing a file
at once. But this is a bit odder than that ... generally, if User A has a file open,
when User B tries to open it also, PowerPoint tells them that the file's in use and
offers to let them open it as Read Only. They can then save the file under another
name if they like, but not back to the original filename.

Are your users trying to force PPT to save back to the original filename while
somebody else has the file open? That's what you might call a DDT. Don't DO That.

PPT shouldn't crash on them no matter how often they try, but if it does, it does;
can't be helped, I suppose, other than "If it hurts when you do that, don't do that."

But are they not getting the message about the file already being in use when they
open these files?
 
Ah, I see now that I wasn't clear enough about the exact nature of the problem
There is only one user of the file. This is on a network share with individually shared folders

In the case of one of the admin assists, she was the only person who had access to the file
So there was no "another user" locking the file. We set permissions on each folder for 1 user only
These are not powerpoint files that are meant to be shared among multiple users. This is a folder that we use for users to house their files

To fix the problem on one PC I upgraded the Powerpoint to the most recent version using the office XP site; I deleted all the office temp files from her 'Documents and Settings' folder, and I rejoined her computer to the domain
The problem appears to be resolved

Considering we were not sharing the files, it was strange to get errors that other users were locking files on proprietary folders. The error message caused a bit of confusion at first
 
Thanks for letting us know -
To fix the problem on one PC I upgraded the Powerpoint to the most recent version using
Click to expand...
the office XP site; I deleted all the office temp files from her 'Documents and
Settings' folder, and I rejoined her computer to the domain.
The problem appears to be resolved.

Considering we were not sharing the files, it was strange to get errors that other
Click to expand...
users were locking files on proprietary folders. The error message caused a bit of
confusion at first.

Sometimes just rebooting the PC or forcibly logging it off from the server can fix these
glitches. For example, if the PC crashes while a PPT file is open (and PPT will
sometimes hold files open far longer than it has any reason to) the file may remain open
as far as the server's concerned. Then the next time the user attempts to open the file,
the server won't give PPT a lock on the file (somebody's using it already, after all!)
and PPT gives you that message.
 
Except that in this case, this was an ongoing issue for several months, not affected by a single crash or reboot.

It was more likely the way in which Office itself communicated with the server. We've had similar problems with other office applications and unix based file storage servers. (It is a windows shell on top of unix). I don't know much about how those communications are handled, but I think the secrets lies in that.
 
Tony said:
Except that in this case, this was an ongoing issue for several months,
Click to expand...
not affected by a single crash or reboot.
It was more likely the way in which Office itself communicated with the
Click to expand...
server. We've had similar problems with other office applications and
unix based file storage servers. (It is a windows shell on top of unix).
I don't know much about how those communications are handled, but I think
the secrets lies in that.

That could well be the case. Office apps seem to be fairly well behaved
on NT-based networks, but they can get cranky on others (Novell, NFS,
etc.) In cases like that, it's generally best to save/open from the local
drive and copy to the server using Windows Explorer or DOS if you're
really old and creaky like me. ;-)
 
Back
Top