Seems like you are trying to edit a page that is already
in use.  Shouldn't you have a development copy of your
web to use to make the changes.  Then after you make
changes stop IIS and implement the new page.  I would not
keep trying to edit live pages.



>-----Original Message-----
>I've got a problem with our Windows Web Edition Server,
>IIS 6.0 website.
>Every now and then, authors are complaining that when
they
>go to edit there web or subweb, it stalls (freezes)
after
>hitting 'Edit with Microsoft Frontpage'. I've seen it.
>the only thing that gets the connection going again is a
>restart of the www service on the web server.
>This problem is not affecting the web site. It's fully
>functional at all times from internal and external.
>Something is just stalling the ability to author pages
or '
>edit with Frontpage'.
>Anyone have this problem, or at least can you point me
in
>the right direction to find out what I have to do to
stop
>this behavior? I'm not getting any system errors.
>sometimes I get these three errors in a row in App log,
>but they don't always match up to the time these people
>say they are trying to edit their site/page(s).
>
>event id 1000 Frontpage 5.0
>Microsoft FrontPage Server Extensions:
> http://www.myweb.net - error #2000c Message: Write
error
>on file 'author.log'.
>
>event id 1000 Frontpage 5.0
>Microsoft Frontpage Server Extensions:
> Http://www.myweb.net - error #2000d Message: Cannot
lock
>file 'author.log'. Either the file is in use or the web
>server is temporarily busy.
>
>event id 1000 Frontpage 5.0
> Microsoft Frontpage Server Extensions:
>  (OS Error #11 Message: Resources temporarily
unavailable)
>
>Thanks in advance,
>
>Sandra
>shacker@nhvweb.net
>
>.
>

[ Post a follow-up to this message ]