The development team is having a problem when they open an
asp page edit the code and then try to save it they
receive an error.
"The process cannot access the file because it is being
used by another process."
If I reboot the server it breaks the lock. If I reboot the
client it breaks the lock. The only thing that has
changed is their OS from Windows 2000 to XP. The
application they use is Visual Studio.
Alvin Bruney [ASP.NET MVP] - 17 Mar 2005 00:14 GMT
why are your engineers editing files on a production server? did i read you
right or this is just my tired brain?

Signature
Regards,
Alvin Bruney
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
available at www.lulu.com/owc
_________________________
> The development team is having a problem when they open an
> asp page edit the code and then try to save it they
[quoted text clipped - 7 lines]
> changed is their OS from Windows 2000 to XP. The
> application they use is Visual Studio.
anonymous@discussions.microsoft.com - 17 Mar 2005 14:36 GMT
This is strickly a develoment server running windows 2000
sp4
>-----Original Message-----
>why are your engineers editing files on a production server? did i read you
[quoted text clipped - 13 lines]
>
>.
Alvin Bruney [ASP.NET MVP] - 17 Mar 2005 17:03 GMT
is the asp file in use?
to find out for sure, download and install the filemon utility from
www.sysinternals.com. it tracks the open handles and ownership of these
handles. once you know who owns what, you should be able to fix it.

Signature
Regards,
Alvin Bruney
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
available at www.lulu.com/owc
_________________________
> This is strickly a develoment server running windows 2000
> sp4
[quoted text clipped - 20 lines]
>>
>>.
jawadak@gmail.com - 24 Mar 2005 21:52 GMT
You can also use the utility called WhoLockedMe that will let you know
the prcoess who locked the specified file.
http://www.dr-hoiby.com/WhoLockMe/
gabe garza - 29 Mar 2005 02:43 GMT
You should look into using a source control program.
Using utilites to find out who's locking a file is fine, but that doesn't
prevent it from happening again.
> The development team is having a problem when they open an
> asp page edit the code and then try to save it they
[quoted text clipped - 7 lines]
> changed is their OS from Windows 2000 to XP. The
> application they use is Visual Studio.