We have a file that cannot be renamed because it is being used by another
process.
But we do not know which one.

How can we find out which one?

Kind Regards,

Robert Gilland.

Use Sysinternals' Process Explorer or Open Handles (oh.exe). Both are
available from the Microsoft.com site.

John

microsoft.news.com wrote:

> We have a file that cannot be renamed because it is being used by another
> process.
> But we do not know which one.
>
> How can we find out which one?
>
> Kind Regards,
>
> Robert Gilland.
>
>

Well... the easy way is to take the file name (which you didn't state)
and Google it. If you made up the file name yourself, well that is
something else entirely. And I don't know, but why do you want to change
a filename that are locked by something else? You know what problems
that could cause, right?

--
Bill

"microsoft.news.com" <rob@rob> wrote in message
news:(E-Mail Removed)
> We have a file that cannot be renamed because it is being used by
> another process.
> But we do not know which one.
>
> How can we find out which one?
>
> Kind Regards,
>
> Robert Gilland.

No it is our own file,
It should not be locked by anyone,
none of our processes are running.

we are currently downloading windows 2003 resource kit.
and will attempt to use oh.exe to identify the culprit.

Regards,

Robert.


"BillW50" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Well... the easy way is to take the file name (which you didn't state) and
> Google it. If you made up the file name yourself, well that is something
> else entirely. And I don't know, but why do you want to change a filename
> that are locked by something else? You know what problems that could
> cause, right?
>
> --
> Bill
>
> "microsoft.news.com" <rob@rob> wrote in message
> news:(E-Mail Removed)
>> We have a file that cannot be renamed because it is being used by
>> another process.
>> But we do not know which one.
>>
>> How can we find out which one?
>>
>> Kind Regards,
>>
>> Robert Gilland.
>

Ouch! Something locking your own file doesn't sound good. I would really
like to know what that was.

--
Bill

"microsoft.news.com" <rob@rob> wrote in message
news:(E-Mail Removed)
> No it is our own file,
> It should not be locked by anyone,
> none of our processes are running.
>
> we are currently downloading windows 2003 resource kit.
> and will attempt to use oh.exe to identify the culprit.
>
> Regards,
>
> Robert.
>
>
> "BillW50" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Well... the easy way is to take the file name (which you didn't
>> state) and Google it. If you made up the file name yourself, well
>> that is something else entirely. And I don't know, but why do you
>> want to change a filename that are locked by something else? You
>> know what problems that could cause, right?
>>
>> --
>> Bill
>>
>> "microsoft.news.com" <rob@rob> wrote in message
>> news:(E-Mail Removed)
>>> We have a file that cannot be renamed because it is being used by
>>> another process.
>>> But we do not know which one.
>>>
>>> How can we find out which one?
>>>
>>> Kind Regards,
>>>
>>> Robert Gilland.

You know... safe mode can do wonders most of the time. And I used to
believe in muliple OS on a machine so one OS can fix the other. But
having a barebones OS on CD or whatever is bootable is far better IMHO.
One I really like right now is BartPE (it's free). So if you really get
stuck, I think you should go this route.

--
Bill

"BillW50" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)
> Ouch! Something locking your own file doesn't sound good. I would
> really like to know what that was.
>
>
> "microsoft.news.com" <rob@rob> wrote in message
> news:(E-Mail Removed)
>> No it is our own file,
>> It should not be locked by anyone,
>> none of our processes are running.
>>
>> we are currently downloading windows 2003 resource kit.
>> and will attempt to use oh.exe to identify the culprit.
>>
>> Regards,
>>
>> Robert.
>>
>>
>> "BillW50" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Well... the easy way is to take the file name (which you didn't
>>> state) and Google it. If you made up the file name yourself, well
>>> that is something else entirely. And I don't know, but why do you
>>> want to change a filename that are locked by something else? You
>>> know what problems that could cause, right?
>>>
>>> --
>>> Bill
>>>
>>> "microsoft.news.com" <rob@rob> wrote in message
>>> news:(E-Mail Removed)
>>>> We have a file that cannot be renamed because it is being used by
>>>> another process.
>>>> But we do not know which one.
>>>>
>>>> How can we find out which one?
>>>>
>>>> Kind Regards,
>>>>
>>>> Robert Gilland.

We have used OH.exe
and it is an unknown system process holding the file open

Process ID 00000004

This is a dead end for us.

We have no Idea what this Process is, or why it would be holding our file
open.

Regards,

Robert.

"BillW50" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> You know... safe mode can do wonders most of the time. And I used to
> believe in muliple OS on a machine so one OS can fix the other. But having
> a barebones OS on CD or whatever is bootable is far better IMHO. One I
> really like right now is BartPE (it's free). So if you really get stuck, I
> think you should go this route.
>
> --
> Bill
>
> "BillW50" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)
>> Ouch! Something locking your own file doesn't sound good. I would
>> really like to know what that was.
>>
>>
>> "microsoft.news.com" <rob@rob> wrote in message
>> news:(E-Mail Removed)
>>> No it is our own file,
>>> It should not be locked by anyone,
>>> none of our processes are running.
>>>
>>> we are currently downloading windows 2003 resource kit.
>>> and will attempt to use oh.exe to identify the culprit.
>>>
>>> Regards,
>>>
>>> Robert.
>>>
>>>
>>> "BillW50" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> Well... the easy way is to take the file name (which you didn't
>>>> state) and Google it. If you made up the file name yourself, well
>>>> that is something else entirely. And I don't know, but why do you
>>>> want to change a filename that are locked by something else? You
>>>> know what problems that could cause, right?
>>>>
>>>> --
>>>> Bill
>>>>
>>>> "microsoft.news.com" <rob@rob> wrote in message
>>>> news:(E-Mail Removed)
>>>>> We have a file that cannot be renamed because it is being used by
>>>>> another process.
>>>>> But we do not know which one.
>>>>>
>>>>> How can we find out which one?
>>>>>
>>>>> Kind Regards,
>>>>>
>>>>> Robert Gilland.
>

"microsoft.news.com" <rob@rob> wrote
> We have a file that cannot be renamed because it is being used by another
> process.
> But we do not know which one.
>
> How can we find out which one?

http://www.dr-hoiby.com/WhoLockMe/

--
Rock [MS-MVP User/Shell]

Oh no! Don't stop now! You have find out what is holding that file open!
Safe mode or something like BartPE is the way to unlock it.

http://www.nu2.nu/pebuilder/

--
Bill

"microsoft.news.com" <rob@rob> wrote in message
news:(E-Mail Removed)
> We have used OH.exe
> and it is an unknown system process holding the file open
>
> Process ID 00000004
>
> This is a dead end for us.
>
> We have no Idea what this Process is, or why it would be holding our
> file open.
>
> Regards,
>
> Robert.
>
> "BillW50" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> You know... safe mode can do wonders most of the time. And I used to
>> believe in muliple OS on a machine so one OS can fix the other. But
>> having a barebones OS on CD or whatever is bootable is far better
>> IMHO. One I really like right now is BartPE (it's free). So if you
>> really get stuck, I think you should go this route.
>>
>> --
>> Bill
>>
>> "BillW50" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)
>>> Ouch! Something locking your own file doesn't sound good. I would
>>> really like to know what that was.
>>>
>>>
>>> "microsoft.news.com" <rob@rob> wrote in message
>>> news:(E-Mail Removed)
>>>> No it is our own file,
>>>> It should not be locked by anyone,
>>>> none of our processes are running.
>>>>
>>>> we are currently downloading windows 2003 resource kit.
>>>> and will attempt to use oh.exe to identify the culprit.
>>>>
>>>> Regards,
>>>>
>>>> Robert.
>>>>
>>>>
>>>> "BillW50" <(E-Mail Removed)> wrote in message
>>>> news:%(E-Mail Removed)...
>>>>> Well... the easy way is to take the file name (which you didn't
>>>>> state) and Google it. If you made up the file name yourself, well
>>>>> that is something else entirely. And I don't know, but why do you
>>>>> want to change a filename that are locked by something else? You
>>>>> know what problems that could cause, right?
>>>>>
>>>>> --
>>>>> Bill
>>>>>
>>>>> "microsoft.news.com" <rob@rob> wrote in message
>>>>> news:(E-Mail Removed)
>>>>>> We have a file that cannot be renamed because it is being used by
>>>>>> another process.
>>>>>> But we do not know which one.
>>>>>>
>>>>>> How can we find out which one?
>>>>>>
>>>>>> Kind Regards,
>>>>>>
>>>>>> Robert Gilland.

I have read the Blurb on this and am at a loss as to how to actually use it.
see the computer we are fixing is 3000 km away from us, we are fixing it via
Remote Desktop

Even if I was there with a bootable CD, how would that help me?

Kind Regards,

Robert.


"BillW50" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Oh no! Don't stop now! You have find out what is holding that file open!
> Safe mode or something like BartPE is the way to unlock it.
>
> http://www.nu2.nu/pebuilder/
>
> --
> Bill
>
> "microsoft.news.com" <rob@rob> wrote in message
> news:(E-Mail Removed)
>> We have used OH.exe
>> and it is an unknown system process holding the file open
>>
>> Process ID 00000004
>>
>> This is a dead end for us.
>>
>> We have no Idea what this Process is, or why it would be holding our
>> file open.
>>
>> Regards,
>>
>> Robert.
>>
>> "BillW50" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> You know... safe mode can do wonders most of the time. And I used to
>>> believe in muliple OS on a machine so one OS can fix the other. But
>>> having a barebones OS on CD or whatever is bootable is far better
>>> IMHO. One I really like right now is BartPE (it's free). So if you
>>> really get stuck, I think you should go this route.
>>>
>>> --
>>> Bill
>>>
>>> "BillW50" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)
>>>> Ouch! Something locking your own file doesn't sound good. I would
>>>> really like to know what that was.
>>>>
>>>>
>>>> "microsoft.news.com" <rob@rob> wrote in message
>>>> news:(E-Mail Removed)
>>>>> No it is our own file,
>>>>> It should not be locked by anyone,
>>>>> none of our processes are running.
>>>>>
>>>>> we are currently downloading windows 2003 resource kit.
>>>>> and will attempt to use oh.exe to identify the culprit.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Robert.
>>>>>
>>>>>
>>>>> "BillW50" <(E-Mail Removed)> wrote in message
>>>>> news:%(E-Mail Removed)...
>>>>>> Well... the easy way is to take the file name (which you didn't
>>>>>> state) and Google it. If you made up the file name yourself, well
>>>>>> that is something else entirely. And I don't know, but why do you
>>>>>> want to change a filename that are locked by something else? You
>>>>>> know what problems that could cause, right?
>>>>>>
>>>>>> --
>>>>>> Bill
>>>>>>
>>>>>> "microsoft.news.com" <rob@rob> wrote in message
>>>>>> news:(E-Mail Removed)
>>>>>>> We have a file that cannot be renamed because it is being used by
>>>>>>> another process.
>>>>>>> But we do not know which one.
>>>>>>>
>>>>>>> How can we find out which one?
>>>>>>>
>>>>>>> Kind Regards,
>>>>>>>
>>>>>>> Robert Gilland.
>