Re: Publishing Error FP2003 to Remote site
From: Ronx (ronx917_at_hotmail.com)
Date: 02/04/05
- Next message: Brad G: "Server not compatible/too old error"
- Previous message: SwC: "Re: Publishing Error FP2003 to Remote site"
- In reply to: SwC: "Re: Publishing Error FP2003 to Remote site"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Feb 2005 17:14:34 -0000
I have 2 machines running Windows XP Pro SP2, with automatic updates. Also
Microsoft Anti-Spyware Beta running. I have no problems with FP2003.
I will not allow Norton/Symantec products (after 2002) on any of my
achines - IMO they are more trouble than useful.
-- Ron Symonds (Microsoft MVP - FrontPage) Reply only to group - emails will be deleted unread. "SwC" <swc@ntlworld.com> wrote in message news:2ad8dca0.0502040855.6e1eab2@posting.google.com... > First of all, I have the same problem. But I can't even publish from > FP to my own laptop - i.e. localhost!! I have tried re-installing > IIS, etc. from the control panel->Add/remove... and I had it all > working up to now. > > I notice, doing a quick Google, that all reports of this in news > groups are around the end of Jan/beginning of Fed. So a pattern > there! > > I did not authorise any Windows updates on my PC (Windows XP Pro with > SP2, up to date on the updates) in that time. However, I have > installed the Beta versions of the MSN search and the MS anti-spyware > software. The latter does update itself regularly. I also have > Norton AV running. > > Anyone else have any of the software listed above? Perhaps we can > narrow it down. > > > Elaine McCubbin <Elaine McCubbin@discussions.microsoft.com> wrote in > message news:<EE07C068-77D4-4D53-A2E5-1E472920BBCF@microsoft.com>... >> I have had exactly the same problem. It started Friday night and then >> sorted >> itself but it's happening again. Sometimes it works, then seconds later >> it >> doesn't. Like you guys, I have checked all the usual things, connection, >> firewall etc. I think it may be an issue with the security of XP Pro. I >> moved to a Windows 2000 machine could publish as usual. Could do with >> getting it sorted out though so any suggestions gratefully received. I >> am >> also having a problem viewing the site in IE, but again on another >> computer >> it's fine. >> >> "§andro" wrote: >> >> > Hmm... this exact same thing has just happend to me. >> > >> > I've been publishing to my client's server all week then one muinite it >> > was >> > working then the next it came up with the error you are getting. >> > >> > I've checked all the same things you have. Created a new vurtual server >> > and >> > new home driectory on the server etc. Nothing seems to fix it. >> > >> > The web sites are all working OK and my clienty can publish to it >> > locally >> > but I can't any more from my office. >> > >> > It seems like a firewall thing but I've checked them all and they seem >> > OK. >> > >> > Any suggestions appreciated. >> > >> > >> > "Vernon Lane" <vklane@cox.net> wrote in message >> > news:u%23MLFmyBFHA.1396@tk2msftngp13.phx.gbl... >> > >I have been using Frontpage 2003 for some web sites, but lately when I >> > > attempt to publish any of these sites to their corresponding remote >> > > (live) >> > > sites Frontpage gives me the following error message. >> > > >> > > >> > > >> > > Unable to open "http://www.the-webstore.com" . Possible causes >> > > >> > > >> > > >> > > 1.. The web server may not have the Frontpage server extensions >> > > installed. >> > > 2.. The web server may be temporarily out of service. >> > > 3.. If you are connecting through a proxy server, the proxy settings >> > > may >> > > be incorrect. >> > > 4.. An error may have occurred in the web server. >> > > >> > > >> > > >> > > >> > > I have Win XP Pro (SP1) (uninstalled SP2) installed on the system and >> > > had >> > > IIS (ver. 5.1) installed and the Frontpage 2000 extensions and at >> > > another >> > > time the Frontpage 2002 extensions installed and extended to the >> > > webs. >> > > >> > > >> > > >> > > I've gone through possibilities for all of the above reasons for the >> > > error >> > > to include, opening the sites in web browsers, pinging the sites by >> > > name >> > > and >> > > number (no problem), checking my connection settings to be sure they >> > > are >> > > in >> > > line with the ISP's directions, shutting down ZoneAlarm, Norton >> > > Anti-Virus. >> > > I have uninstalled and re-installed IIS, Frontpage 2003, the server >> > > extensions, removed all Frontpage info from webs making them >> > > disk-based, >> > > open them in Frontpage and still get the same message when trying to >> > > publish >> > > to a remote http server. The remote sites all have the server >> > > extensions >> > > installed by two different hosting providers, so they all can't be >> > > corrupted. I can publish the sites to IIS locally on my computer but >> > > not >> > > to >> > > the web. >> > > >> > > >> > > >> > > Also something on the system is telling Frontpage all newly created >> > > webs >> > > have to be on the local server even when IIS is not installed. >> > > >> > > >> > > >> > > Short of re-formatting my hard drive, what can I do to fix this? >> > > >> > > >> > >> > >> >
- Next message: Brad G: "Server not compatible/too old error"
- Previous message: SwC: "Re: Publishing Error FP2003 to Remote site"
- In reply to: SwC: "Re: Publishing Error FP2003 to Remote site"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
