Frontpage 2003 problem w. Apache SE

[Guest]

I had published to an ISP Windows server w SE without probem. I upgraded to FP2003 w.o. problem but then I tried to move to an new ISP running an Apache based server with SE for Unix. Although I have turned off the Sharepoint services option and (as far I know) I have no elements in my site that require WSS (simple site - navigation bar and shared borders nothing else creative) when I try to publish with http option I keep getting an error message that says that Sharepoint Services is not installed on the server. Host support has verified that I have SE installed for my site.

If I try the FTP option, I lose the shared borders, when I can get a file published, but I get lots of "500 RT not understood 500 LPRT not understood" messages or "425 Unable to build data connection: operation timed out" messages. This is tiny site - 7 pages

I'm assuming that the host support folks know what they're doing and I have inadvertantly done something to require WSS? If so how do I figure out what it could be

Joe

 

[Thomas A. Rowe]

Under FP2003, the SharePoint Service option also includes using the
FP2000/2002 extensions, so you need to enable this.

--

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

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

I had published to an ISP Windows server w SE without probem. I upgraded

to FP2003 w.o. problem but then I tried to move to an new ISP running an
Apache based server with SE for Unix. Although I have turned off the
Sharepoint services option and (as far I know) I have no elements in my site
that require WSS (simple site - navigation bar and shared borders nothing
else creative) when I try to publish with http option I keep getting an
error message that says that Sharepoint Services is not installed on the
server. Host support has verified that I have SE installed for my site.

If I try the FTP option, I lose the shared borders, when I can get a file

published, but I get lots of "500 RT not understood 500 LPRT not understood"
messages or "425 Unable to build data connection: operation timed out"
messages. This is tiny site - 7 pages!

I'm assuming that the host support folks know what they're doing and I

have inadvertantly done something to require WSS? If so how do I figure out
what it could be?

 

[Guest]

Enabled sharpoint services in FP2003 no change in results. Does this mean that SE may not be correctly installed at the host end

Joe

 

[Thomas A. Rowe]

Is this a new site? If so are you trying to open it via it's domain name or
IP address?

--

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

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

Enabled sharpoint services in FP2003 no change in results. Does this mean

that SE may not be correctly installed at the host end?

 

[Guest]

I started out using the hosting address (host name). They recommended that I propagate the DNS changes so that's what I did (I use a different registrar than the host service). But no changes to the problems with publishing. On the other hand I can still publish to my old web site (they use Windows servers for hosting) using the ip address

Joe

 

[Thomas A. Rowe]

It can take up to 72 hours for the DNS changes to propagate around the
world. In the meantime if your account has a dedicated IP address, then use
that, if not you will have to wait on the DNS change.

--

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

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

I started out using the hosting address (host name). They recommended that

I propagate the DNS changes so that's what I did (I use a different
registrar than the host service). But no changes to the problems with
publishing. On the other hand I can still publish to my old web site (they
use Windows servers for hosting) using the ip address.

 

[Stefan B Rusynko]

PS - if you have FTP'd (even w/ FP) have the host repair the FP SE

--




| I started out using the hosting address (host name). They recommended that I propagate the DNS changes so that's what I did (I use
a different registrar than the host service). But no changes to the problems with publishing. On the other hand I can still publish
to my old web site (they use Windows servers for hosting) using the ip address.
|
| Joe

 

[Guest]

Host SE has been uninstalled and re-installed several times - at least the hosting control panel says so and the support crew confirms. I've looked at the "_vti_inf.html" file source which I assume is the marker for determining presence of SE - looks okay (from what little I know!) - although the _vti_bin folder is empty. frustrating since these folks explicitly advertize support for FP2003.

 

[jerrye]

*Host SE has been uninstalled and re-installed several times - at
least the hosting control panel says so and the support crew
confirms. I've looked at the "_vti_inf.html" file source which I
assume is the marker for determining presence of SE - looks okay
(from what little I know!) - although the _vti_bin folder is empty.
frustrating since these folks explicitly advertize support for
FP2003. *

Did you get a resolution on this matter?
i'm also getting the same problem suddenly.