FrontPage publishing Problem

N

Neil Ogden

I have many websites hosted across four servers owned by my host. Two are
working fine, on the other two I get the following error:

An error occurred accessing your front page web files. Authors - if
authoring against a web server, please contact the webmaster for the
server's site. WebMasters -please see the server's system log for more
details.

This has been referred to cpanel who say they can publish fine, and the fpse
have been reset and uninstalled and reinstalled. The same error happens
when trying to publish from expression (apart from the words front page
which are placed by "sharepoint".

I don't know what to do next. I am convinced this is a server problem, yet
my host says everything tested OK so it must be.

Any ideas? Has anyone ever come across this before?

Thanks

Neil
 
N

Neil Ogden

That doesn't work - I got someone else to try publishing from their computer
elsewhere in the country but they got the same error. I think it is the
server but my host says that the server has been rebuilt this morning and
the fpse have been reset and reinstalled as well.
 
N

Neil Ogden

I have about 14 web sites affected by this. I have looked at one of these
as described below by looking at
http://www.hrbasingstoke.co.uk/_vti_inf.html

I get the following:
FrontPage Configuration Information
In the HTML comments, this page contains configuration information that the
FrontPage Explorer and FrontPage Editor need to communicate with the
FrontPage server extensions installed on this web server. Do not delete this
page.

There is nothing else on the page although when viewing source, I get the
following:

<!-- _vti_inf.html version 0.100>
<!--
This file contains important information used by the FrontPage client
(the FrontPage Explorer and FrontPage Editor) to communicate with the
FrontPage server extensions installed on this web server.

The values below are automatically set by FrontPage at installation.
Normally, you do not need to modify these values, but in case
you do, the parameters are as follows:

'FPShtmlScriptUrl', 'FPAuthorScriptUrl', and 'FPAdminScriptUrl' specify
the relative urls for the scripts that FrontPage uses for remote
authoring. These values should not be changed.

'FPVersion' identifies the version of the FrontPage Server Extensions
installed, and should not be changed.
--><!-- FrontPage Configuration Information
FPVersion="5.0.2.4803"
FPShtmlScriptUrl="_vti_bin/shtml.exe/_vti_rpc"
FPAuthorScriptUrl="_vti_bin/_vti_aut/author.exe"
FPAdminScriptUrl="_vti_bin/_vti_adm/admin.exe"
TPScriptUrl="_vti_bin/owssvr.exe"
-->
<p><!--webbot bot="PurpleText"
preview="This page is placed into the root directory of your FrontPage web
when FrontPage is installed. It contains information used by the FrontPage
client to communicate with the FrontPage server extensions installed on this
web server. You should not delete this file."
--></p>

I'm not sure if this is correct or not.

Neil
 
T

Tom Willett

That is correct. And, it's the FP 2002 extensions.

--
===
Tom Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/
===
|
| I have about 14 web sites affected by this. I have looked at one of these
| as described below by looking at
| http://www.hrbasingstoke.co.uk/_vti_inf.html
|
| I get the following:
| FrontPage Configuration Information
| In the HTML comments, this page contains configuration information that
the
| FrontPage Explorer and FrontPage Editor need to communicate with the
| FrontPage server extensions installed on this web server. Do not delete
this
| page.
|
| There is nothing else on the page although when viewing source, I get the
| following:
|
| <!-- _vti_inf.html version 0.100>
| <!--
| This file contains important information used by the FrontPage client
| (the FrontPage Explorer and FrontPage Editor) to communicate with the
| FrontPage server extensions installed on this web server.
|
| The values below are automatically set by FrontPage at installation.
| Normally, you do not need to modify these values, but in case
| you do, the parameters are as follows:
|
| 'FPShtmlScriptUrl', 'FPAuthorScriptUrl', and 'FPAdminScriptUrl' specify
| the relative urls for the scripts that FrontPage uses for remote
| authoring. These values should not be changed.
|
| 'FPVersion' identifies the version of the FrontPage Server Extensions
| installed, and should not be changed.
| --><!-- FrontPage Configuration Information
| FPVersion="5.0.2.4803"
| FPShtmlScriptUrl="_vti_bin/shtml.exe/_vti_rpc"
| FPAuthorScriptUrl="_vti_bin/_vti_aut/author.exe"
| FPAdminScriptUrl="_vti_bin/_vti_adm/admin.exe"
| TPScriptUrl="_vti_bin/owssvr.exe"
| -->
| <p><!--webbot bot="PurpleText"
| preview="This page is placed into the root directory of your FrontPage web
| when FrontPage is installed. It contains information used by the
FrontPage
| client to communicate with the FrontPage server extensions installed on
this
| web server. You should not delete this file."
| --></p>
|
| I'm not sure if this is correct or not.
|
| Neil
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | > To check if the FrontPage Extensions are really installed open your
| > browser and type in your Domain Name + _vti_inf.html Ex:
| >
| > http://www.yourdomain.com/_vti_inf.html
| >
| > --
| > David Berry
| > Microsoft MVP - FrontPage
| > FrontPage Support: http://www.frontpagemvps.com/
| > -----------------------------------
| > To assist you in getting the best answers for FrontPage support see:
| > http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > -----------------------------------
| >
| >
| > | >> That doesn't work - I got someone else to try publishing from their
| >> computer
| >> elsewhere in the country but they got the same error. I think it is
the
| >> server but my host says that the server has been rebuilt this morning
and
| >> the fpse have been reset and reinstalled as well.
| >>
| >>
| >> | >>> Try FP Cleaner at http://www.95isalive.com/fixes/fpclean.htm
| >>>
| >>> --
| >>> David Berry
| >>> Microsoft MVP - FrontPage
| >>> FrontPage Support: http://www.frontpagemvps.com/
| >>> -----------------------------------
| >>> To assist you in getting the best answers for FrontPage support see:
| >>> http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| >>> -----------------------------------
| >>>
| >>>
| >>> | >>>>I have many websites hosted across four servers owned by my host. Two
| >>>>are working fine, on the other two I get the following error:
| >>>>
| >>>> An error occurred accessing your front page web files. Authors - if
| >>>> authoring against a web server, please contact the webmaster for the
| >>>> server's site. WebMasters -please see the server's system log for
more
| >>>> details.
| >>>>
| >>>> This has been referred to cpanel who say they can publish fine, and
the
| >>>> fpse have been reset and uninstalled and reinstalled. The same error
| >>>> happens when trying to publish from expression (apart from the words
| >>>> front page which are placed by "sharepoint".
| >>>>
| >>>> I don't know what to do next. I am convinced this is a server
problem,
| >>>> yet my host says everything tested OK so it must be.
| >>>>
| >>>> Any ideas? Has anyone ever come across this before?
| >>>>
| >>>> Thanks
| >>>>
| >>>> Neil
| >>>>
| >>>
| >>>
| >>
| >>
| >
| >
|
|
 
N

Neil Ogden

I think the problem is that the extensions are not functioning properly. I
can see that, I have asked someone else to try and they get the same error
however my host and cpanel don't get an error, but I have a feeling they are
not using publish but using ftp instead. In fact I don't even think my host
is doing that because the test page he tried to publish never appeared.

Neil
 
S

Steve Easton

If someone has used ftp:// to publish, they have broken the extensions and they need to be
repaired / reinstalled.

CPanel doesn't use extensions, it simply tells you whether they are installed or not.
However if they are corrupt, cpanel will show them as installed even though they aren't
working.
If you have the option on cpanel to install extensions, use it.
Then do not allow any one to publish using ftp://

--

Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm
 
N

Neil Ogden

I've thought of all that and done it. The server has been rebuilt this
morning including apache. The fpse have been reinstalled.

Neil
 
N

Neil Ogden

The site was deleted completely and recreated but not the error is

"404 Not Found
Not Found The requested URL /_vti_bin/shtml.exe/_vti_rpc was not found on
this server.
Additionally, a 404 Not Found error was encountered while trying to use an
ErrorDocument to handle the request. "

which I also believe to be related to the extensions.

This particular site is now being moved to another server where it will
hopefully be OK, but I really don't want to have to go through moving 13
others. Some are complicated with other things installed. I just find it
frustrating that so called tech support never likes front page.

Neil
 
G

Guest

When my server helped me out yesterday, we published to ftp://, then we
published it to http:// and I didn't lose my frontpage extensions.
 
D

David Berry

Your web host needs to re-install the FP Extensions or repair the ones on
your site
 
N

Neil Ogden

Ok - it looks like it's solved.

The solution was to reinstall the fp mail extensions.

All's well that ends well. The solution has been documented for next time,
I've learnt a few things but also wasted the best part of a week trying to
sort it out.

Don't you just love FP, MS and rubbish tech support!

Neil
 
G

Guest

Can't find a discussion link form this topic - wondered if you could help?

Just purchased a vista system. Using Frontpage '03. Hyperlinks to imported
Word documents cause the entire program to have to shut down and restart.
Worked fine with Windows xp. Any thoughts?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top