"frontpage.lck"?

C

Carla

Latest chapter in the saga of getting my client side
software to work with our home network... hub downloaded a
newer rev of the O2 extensions last night and installed it.
It seems we are inching closer to having it work, but still
not there yet.

Let's forget about my existing webs and what I can/can't do
with them and just talk about what happens when I try to
create and save a NEW web on the network machine.

As of yesterday, I couldn't do it at all. As of last night,
with new extensions installed, when I try to create a new
web at: "htttp://machinename/newtest2" I get this error
instead:

Server error: The server extensions were unable to
access the file "frontpage.lck". Check file
permissions.

The setup again is FP02, Extensions 02, a desktop with XP
Pro and a home network server running XP Pro as well.

Hub swears that permissions are not the issue. Must he be
wrong, or might there be something else going on?

Thanks again.
 
T

Thomas A. Rowe

You need to create the web on the server via IIS MMC, not FP.

Under Windows XP Pro / IIS you can only have a single root web
(http://localhost or default web), but unlimited number of subwebs.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
J

Jim Buyens

Need you ask? The hub is always wrong! At least, what's
what my wife keeps telling me.

Try the procedure at:

Fixing Permissions in an Extended Web Site
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=32

and see if that solves the problem. If so, permissions
were definitely the source of yuor woe. But don't tell hub
you asked for directions, or he'll accuse you of cheating.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------
 
G

Guest

But don't tell hub
you asked for directions, or he'll accuse you of cheating.<<

ROFL!

I do agree he can get a bad case of tunnel vision when
frustrated, and this whole FP thing has been incredibly
frustrating, especially given that everything else about
his server OS migration has gone just fine (which makes him
even more sure the he's not the one missing a clue <g2>.)
If I hadn't mustered the bandwidth to ask around online,
this whole thing would have been abandoned by now, and I'd
just have to do what I could locally on my own machine.

I'll print out your page Jim and gently insist that this is
the next thing to try. Appreciate the pointer to something
spelled out in 1-2-3 steps.
 
C

Carla

You need to create the web on the server via IIS MMC,
not FP. Under Windows XP Pro / IIS you can only have a
single root web (http://localhost or default web), but
unlimited number of subwebs. <<

Right Tom, I did get that part of the paradigm shift and so
does hub. But he thinks he HAS a root web up and running
off of what was already there at machine/Inetpub/wwwroot
when this all was working with NT (or some subsequent step
he took when re-installing extensions). When you look at
the folders via Explorer and display all, it would seem by
the titles shown that he's correct about that (e.g. the
root folder on that filepath has a globe icon), but we can
assume that any assumption of mine is error prone <g>.

Someone else mentioned something about a need to
"designate" /localhost, and then test it by making a call
to http://localhost with my browser.

Is this what you are talking about or something else? That
part did not ring a bell with hub, and meant even less to
me. I get a "page not found" when I try the localhost
address from my own desk, even though a specific call to
http://machine DOES bring up the page confirming that IIS
is running.

But let's forget our pre=existing files again for a sec,
and just tell me what happens when setting up from scratch.
Does that "single root web" get built in the process of
installing extensions? Or does it take a separate step?
 
T

Tom Pepper Willett

The single root web gets built when installing IIS. Then you must configure
the installed extensions to the root web.
--
-----
Tom Pepper Willett
Microsoft MVP - FrontPage
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
http://msdn.microsoft.com/office/understanding/frontpage/
----
| >> You need to create the web on the server via IIS MMC,
| not FP. Under Windows XP Pro / IIS you can only have a
| single root web (http://localhost or default web), but
| unlimited number of subwebs. <<
|
| Right Tom, I did get that part of the paradigm shift and so
| does hub. But he thinks he HAS a root web up and running
| off of what was already there at machine/Inetpub/wwwroot
| when this all was working with NT (or some subsequent step
| he took when re-installing extensions). When you look at
| the folders via Explorer and display all, it would seem by
| the titles shown that he's correct about that (e.g. the
| root folder on that filepath has a globe icon), but we can
| assume that any assumption of mine is error prone <g>.
|
| Someone else mentioned something about a need to
| "designate" /localhost, and then test it by making a call
| to http://localhost with my browser.
|
| Is this what you are talking about or something else? That
| part did not ring a bell with hub, and meant even less to
| me. I get a "page not found" when I try the localhost
| address from my own desk, even though a specific call to
| http://machine DOES bring up the page confirming that IIS
| is running.
|
| But let's forget our pre=existing files again for a sec,
| and just tell me what happens when setting up from scratch.
| Does that "single root web" get built in the process of
| installing extensions? Or does it take a separate step?
|
|
|
|
| >-----Original Message-----
| >You need to create the web on the server via IIS MMC, not FP.
| >
| >Under Windows XP Pro / IIS you can only have a single root web
| >(http://localhost or default web), but unlimited number of
| subwebs.
| >
| >--
| >
| >==============================================
| >Thomas A. Rowe (Microsoft MVP - FrontPage)
| >WEBMASTER Resources(tm)
| >
| >FrontPage Resources, Forums, WebCircle,
| >MS KB Quick Links, etc.
| >==============================================
| >To assist you in getting the best answers for FrontPage
| support see:
| >http://www.net-sites.com/sitebuilder/newsgroups.asp
| >
| >| >> Latest chapter in the saga of getting my client side
| >> software to work with our home network... hub downloaded a
| >> newer rev of the O2 extensions last night and installed it.
| >> It seems we are inching closer to having it work, but still
| >> not there yet.
| >>
| >> Let's forget about my existing webs and what I can/can't do
| >> with them and just talk about what happens when I try to
| >> create and save a NEW web on the network machine.
| >>
| >> As of yesterday, I couldn't do it at all. As of last night,
| >> with new extensions installed, when I try to create a new
| >> web at: "htttp://machinename/newtest2" I get this error
| >> instead:
| >>
| >> Server error: The server extensions were unable to
| >> access the file "frontpage.lck". Check file
| >> permissions.
| >>
| >> The setup again is FP02, Extensions 02, a desktop with XP
| >> Pro and a home network server running XP Pro as well.
| >>
| >> Hub swears that permissions are not the issue. Must he be
| >> wrong, or might there be something else going on?
| >>
| >> Thanks again.
| >>
| >>
| >>
| >
| >
| >.
| >
 
G

Guest

The single root web gets built when installing IIS.
Then you must configure the installed extensions to the
root web. <<

Thank you Tom W. That helps my understanding of the steps.

I suspect what hub did was just try to re-use the files
that were already there when the server was on NT, since he
keeps insisting "no paths or permissions have changed." But
maybe that's part of the problem.

I am going to tell him to try Jim's tip on fixing
permissions to deal with the *.lck issue, and if that
doesn't work, maybe he should just try to create a NEW root
web on the network drive? If he did try that, should he
also install IIS over again?
 
M

Marc Alexander

We had the same problem on our web server... we received
help with MS tech support and I think the way we solved
this immediate problem with frontpage.lck was to do a
couple of things:

1) Find the exact location of the file and locate it on
your web server, than try to rename or delete it... I
know this sounds scary but it was the solution as the lck
file stands for "locked" and prevents extensions and
frontpage from working correctly.

2) That may solve things, but either way, you may also
want to go into the IIS Microsoft Sharepoint
Administration service and do a "detect and repair" on
the particular web and detect and repair all options
available. I assume you already extended the extensions
on this web.

I'm not a professional but am learning IIS and frontpage
and hope this works for you. good luck,
Marc Alexander
 
M

Marc Alexander

not sure if carla rec'd as posted under wrong area
**************************
We had the same problem on our web server... we received
help with MS tech support and I think the way we solved
this immediate problem with frontpage.lck was to do a
couple of things:

1) Find the exact location of the file and locate it on
your web server, than try to rename or delete it... I
know this sounds scary but it was the solution as the lck
file stands for "locked" and prevents extensions and
frontpage from working correctly.

2) That may solve things, but either way, you may also
want to go into the IIS Microsoft Sharepoint
Administration service and do a "detect and repair" on
the particular web and detect and repair all options
available. I assume you already extended the extensions
on this web.

I'm not a professional but am learning IIS and frontpage
and hope this works for you. good luck,
Marc Alexander
 
Top