FrontPage Server Extensions for Windows - Frontpage server extensions access problems Win2000 and WinXp

This is Interesting: Free IT Magazines  
Home > Archive > FrontPage Server Extensions for Windows > May 2005 > Frontpage server extensions access problems Win2000 and WinXp





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Frontpage server extensions access problems Win2000 and WinXp
Herb Martin

2005-05-04, 5:55 pm

On one Win2000 server I have several webs setup with
FP 2002 Server Extensions -- several work just fine.

One fails various things apparently due to permissions.

Main problems are ...

The web gives this when I attempt to check the FP 2002 extensions
from the IIS MMC locally with right-click->All Tasks->
Check server extensions 2002:

[This site never shows a logon dialog]
http://x.x.x.x/_vti_bin/_vti_adm/fp...page=health.htm
The page cannot be found
(etc.)

Site works correctly for remote browsing. Site fails for remote

Going to (IIS MMC) Site->Properties->FPSE 2002 -> Settings:
shows the configuration which is set to allow authoring. Proceeding
to the Admin page (for all webs) works.


If any of these other web sites on the same server are selected
a logon authentication box, accepts the passwords, and gives a
page with columns of "Detect" and "Repair" checkboxes which
work correctly. Also manageable by FrontPage remotely.

The problem site never gives a logon box but proceeds straight
to a "The page cannot be found" html page.
http://x.x.x.x/_vti_bin/_vti_adm/fp...ge=webadmin.htm
(Looks suspiciously like the "Health" page error above.)

One might expect the discrepancy between the trouble sites and
the working sites is the lack of a secure logon method, but checking
the problem site shows that both Anonymous and Integrated are
checked.

Also, the Internet Explorer (used when one checks the web or
when one goes to FP 2002 Admin) is configured to allow integrated
security (but that was obviously working since the other sites
show the logon box and allow the actual logon.)

(Remote) FrontPage authoring/admin of this site fails as well, but
then I can't even get to the page where the admins/authors/browsers
are set.

Help or a good pointer to a troubleshooting doc would be very
much appreciated.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Herb Martin

2005-05-04, 5:55 pm

Update to my FPSE 2002 problem:

I removed FPSE 2002 from that one virtual site.

Stopped/started the IIS server and used the web admin page
to "Extend" the site again.

At that point the "Check pages" and the "User" pages worked.

I added appropriate users to the Site for admin and browse.

Remote admin/authoring of the site using FrontPage is failing,
even though the admin/authoring of the other sites on the same
server does work.

The site remains browsable.

Initially (after re-installing) I did get the remote FrontPage to
show the dialog for logon (and may have typed a wrong password),
but corrected that.

The site refused to open in FrontPage, giving this error:

"The server could not complete your request.
Contact your Internet service provider or Web
server administrator to make sure that the
server has the FrontPage Server Extensions or
SharePoint Services installed.

On clicking for "more details" a message box came up
with this (partial) error appeared:

"The page cannot be saved There is a problem trying to
save the page to the Web site. This error can be cause if you attempt
to upload to or modify a file in, a directory that does not allow Write
access. ....

Then it is has some more including a "403.3 - Forbidden: Write Access..."

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Herb Martin

2005-05-04, 5:55 pm

[ Never mind and thanks -- I have it working now.
I was going to send the following but found that it
was likely a saved password problem AT THIS
POINT.]

Update to my FPSE 2002 problem:

I removed FPSE 2002 from that one virtual site.

Stopped/started the IIS server and used the web admin page
to "Extend" the site again.

At that point the "Check pages" and the "User" pages worked.

I added appropriate users to the Site for admin and browse.

Remote admin/authoring of the site using FrontPage is failing,
even though the admin/authoring of the other sites on the same
server does work.

The site remains browsable.

Initially (after re-installing) I did get the remote FrontPage to
show the dialog for logon (and may have typed a wrong password),
but corrected that. Don't see the logon dialog now when I try to
access it again, so I suspect it has saved the password (even though
I didn't check the box for that.)

[Ok, I had an alternative name for the site (without www) so I
used that and the logon dialog box appeared and with a correct
username/password it let me in for remote Frontpage. How
the heck do you get a bad logon out of one of the previously
tried web sites?]

The site refused to open in FrontPage, giving this error:

"The server could not complete your request.
Contact your Internet service provider or Web
server administrator to make sure that the
server has the FrontPage Server Extensions or
SharePoint Services installed.

On clicking for "more details" a message box came up
with this (partial) error appeared:

"The page cannot be saved There is a problem trying to
save the page to the Web site. This error can be cause if you attempt
to upload to or modify a file in, a directory that does not allow Write
access. ....

Then it is has some more including a "403.3 - Forbidden: Write Access..."

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]



Herb Martin

2005-05-04, 5:55 pm

[ Never mind and thanks -- I have it working now.
I was going to send the following but found that it
was likely a saved password problem AT THIS
POINT.]

Update to my FPSE 2002 problem:

I removed FPSE 2002 from that one virtual site.

Stopped/started the IIS server and used the web admin page
to "Extend" the site again.

At that point the "Check pages" and the "User" pages worked.

I added appropriate users to the Site for admin and browse.

Remote admin/authoring of the site using FrontPage is failing,
even though the admin/authoring of the other sites on the same
server does work.

The site remains browse-able.

Initially (after re-installing) I did get the remote FrontPage to
show the dialog for logon (and may have typed a wrong password),
but corrected that. Don't see the logon dialog now when I try to
access it again, so I suspect it has saved the password (even though
I didn't check the box for that.)

[Ok, I had an alternative name for the site (without www) so I
used that and the logon dialog box appeared and with a correct
username/password it let me in for remote FrontPage. How
the heck do you get a bad logon out of one of the previously
tried web sites?]

The site refused to open in FrontPage, giving this error:

"The server could not complete your request.
Contact your Internet service provider or Web
server administrator to make sure that the
server has the FrontPage Server Extensions or
SharePoint Services installed.

On clicking for "more details" a message box came up
with this (partial) error appeared:

"The page cannot be saved There is a problem trying to
save the page to the Web site. This error can be cause if you attempt
to upload to or modify a file in, a directory that does not allow Write
access. ....

Then it is has some more including a "403.3 - Forbidden: Write Access..."

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com