Re: unable to publish to local IIS

With your disk based site open in FP, go to File Menu | Publish Site and enter
http://localhost/romet or http://127.0.0.1/romet

Change the name in IIS, does not update any references under Network Places.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
==============================================
Agents Real Estate Listing Network
http://www.NReal.com
==============================================


"Alfred Moussali" <AlfredMoussali@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A41BC5EF-3700-40C1-865F-3A5BB59C4EBF@xxxxxxxxxxxxxxxx
Thomas, I did as instructed, I rename the web romet.us to romet in the IIS
console, I am still getting the same error.

If I click on "Browse" on the "Remote Web Site Properties" screen to locate
my web through my network places in the "New Publish Location Screen" where
now lists as "romet on my desktop" I am getting like berfore, the same error
screen. "unable to open. . . etc."

Your help is very welcome

Thank you again
--
I belive that in helping others, you help yourself


"Thomas A. Rowe" wrote:

Rename or recreate your subweb / subsite without the .us then you should be able to publish to
it.
Then thereafter you should just work directly in the server based web (http://my_desktop/romet)
and
not the disk based web

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
==============================================
Agents Real Estate Listing Network
http://www.NReal.com
==============================================


"Alfred Moussali" <AlfredMoussali@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F67DEB37-421A-48CC-9D34-1DE38C80F61C@xxxxxxxxxxxxxxxx
I am unable to publish my web pages to my local IIS 5 INSTAL Through FrontPage.

If I type the URL http://MY_DESKTOP/romet.us where "My_Desktop" is the name
of my computer and "romet.us" the name of my local web to my browser, I can
locally access them. but then again I can't publish the Web changes to my web
server through FrontPage like I was able to, I got a:

'unable to open 'http://my_desktop/romet.us'.
Server Error: An error occurred accessing your Windows SharePoint Services
site files. Authors -if authoring against a Web server please contact the
Webmaster for this server's Web site. WebMasters -please see the server's
application event log for more details.
Possible causes:
1. The web server may not have theFront Server Extensions installed.
2. The 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.

If the server does not support the FrontPage Server Extensions, FrontPage
may still be able to publish via FTP or WebDav. Please select one of this
options and try again.

If I try to publish in WebDav I get the same error screen.

I checked the event viewer everthing looks clean. The system is running
server extensions Version 4.0.2.8912

Any suggestions will be again appreciated.

Thank you in advance.

--
I belive that in helping others, you help yourself





.

Relevant Pages

  • Re: unable to publish to local IIS
    ... Microsoft MVP - FrontPage ... Agents Real Estate Listing Network ... "Thomas A. Rowe" wrote: ... Then thereafter you should just work directly in the server based web ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: Server Extensions Administrator
    ... To avoid the error in FrontPage, you must open the web in FrontPage, ... http://machine:8080 as the web address then the extensions are ... Try running server health, and see if that makes a difference. ... At this point I am at the limit of my knowledge of installing ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: Server Extensions Administrator
    ... This is still a disc based web even if it is used by the web server as ... You can build webs in FrontPage using either system, ... this web to a web server that has the FrontPage Server Extensions ... administration programs and the server extensions on the web ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: FP 2003 what features to use
    ... > - shared borders sounded like an interesting alternative to SSI but it ... > appears to be tied to FP server entensions. ... I've come across some cases where FrontPage falsely detects conflicts ... If you turn source control off and on, ...
    (microsoft.public.frontpage.client)
  • visual studio.net 2003 and asp.net????
    ... Frontpage has detected a web server conflict on port 80, ...
    (microsoft.public.vsnet.general)
Quantcast