Excel file locked

[David]

A user tryed to open a excel file when they was no printer
send up it first come up with a memory error, and bomb out
when trying to open again the file was locked,

Thanks for any help any body can give

 

[Bennie Chen]

Hi David,

Thank you for posting!

Here are some questions regarding the problem.

1. What is the error message?

2. Where is the file stored? Is it stored on a file server, or the local
computer?

3. If we restart the computer where the file is stored, does the problem
persist?

Thank you!

Regards,
Bennie Chen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[David]

vent Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 06/08/2003
Time: 11:17:45
User: N/A
Computer: METAFRAME1
Description:
Application popup: Microsoft Excel - Financial
Accounts.XLS: EXCEL.EXE - Application Error : The
instruction at "0x68f21702" referenced memory
at "0x002c1d06". The memory could not be "written".

This was the error the file is stored on a file server,
nobody else uses the file, restarting is not an option at
present

 

[Bennie Chen]

Hi David,

Thank you for your reply. According to the information we have, the
situation is as follows:

One user accessed the file that is on the file server. The application
(Excel) crashed accidentally. However, the file on the server is not
closed. Therefore other users cannot open/write to it normally.

The reason other users cannot write the file is that the previous user
opened a handle for this file but this handle is not closed. Since we
cannot reboot the server, I recommend you try the following tool:

http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

We can use the Process Explorer tool to close the handle to this file on
the server.

1. On the server, run the Process Explorer tool.

2. Click View. Make sure "View Handles" is selected.

3. The window should contain two parts. In the above part, select the
System process. According to my test, when a network user access the shared
file, the file server use the System process to open it.

4. After selecting the System process, let us click the "Name" column in
the below window to sort the handles.

5. Find the handle whose name is the path of the file. For example
D:\Testfolder\testfile.xls.

6. Right click this handle and click Close handle.

When the handle is closed, you can test to see if other users can
open/write to the file normally.

Hope this information helps. Thank you!

Regards,
Bennie Chen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[David]

-----Original Message-----
Hi David,

Thank you for your reply. According to the information we have, the
situation is as follows:

One user accessed the file that is on the file server. The application
(Excel) crashed accidentally. However, the file on the server is not
closed. Therefore other users cannot open/write to it normally.

The reason other users cannot write the file is that the previous user
opened a handle for this file but this handle is not closed. Since we
cannot reboot the server, I recommend you try the following tool:

http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

We can use the Process Explorer tool to close the handle to this file on
the server.

1. On the server, run the Process Explorer tool.

2. Click View. Make sure "View Handles" is selected.

3. The window should contain two parts. In the above part, select the
System process. According to my test, when a network user access the shared
file, the file server use the System process to open it.

4. After selecting the System process, let us click the "Name" column in
the below window to sort the handles.

5. Find the handle whose name is the path of the file. For example
D:\Testfolder\testfile.xls.

6. Right click this handle and click Close handle.

When the handle is closed, you can test to see if other users can
open/write to the file normally.

Hope this information helps. Thank you!

Regards,
Bennie Chen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks for that What a great program the user that had

the problem has not had it occur again, but a user had 4
files open when excel crashed causing a similar problem,
after your advice it only took 10 mins to sort out

THANKS