Re: inhability to display http://localhost



David, Thank you for your answer, but I tought that this issue was related to
the fact that I can't publish my FrontPage web to my IIS local server anymore.

As you indicate 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 web I
am able to locally browse 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.

Any suggestions will be again appreciated.

Thank you in advance.

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


"David Wang" wrote:

If you see this on XP Pro, just ignore it. IIS is working fine. It's
just that security changes in XPSP2 has broken the sample page, and
since we cannot modify nor remove that page, it is left as-is. In fact,
that error tells me that IIS is working fine to execute ASP and static
file, so there is nothing to worry.

Create your own HTML or ASP page and see if IIS works with them.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//


Alfred Moussali wrote:
My IIS local install is unable to display the localhost .asp page I got this
error on IE7:

"HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Error Type:
Microsoft VBScript runtime (0x800A0046)
Permission denied: 'GetObject'
/localstart.asp, line 40


Browser Type:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET
CLR 1.1.4322)

Page:
GET /localstart.asp"

Help will be greatly appreciated.






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


.



Relevant Pages

  • Re: inhability to display http://localhost
    ... FrontPage web publishing is not a part of IIS but rather a special ... a clean Event Log does not mean the server is functioning correctly. ...
    (microsoft.public.inetserver.iis.security)
  • Re: simple step by step for enableing FPSE?
    ... Let go back...forget about IIS and extensions for the moment, let se about getting your web ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... I think they are there because they show up in IIS) ... if authoring against a web server please contact the webmaster for this sites server. ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: frontpage intranet migration website strategy with a twist
    ... decent experience with Frontpage and publishing to third party WWW ... I have a newly integrated Small Business Server 2003 and I'm ... trying to publish a website via FrontPage. ... Opening IIS and creating a new website using server ip address, ...
    (microsoft.public.frontpage.client)
  • Re: Hey Ronx are you available
    ... You would open the default web in IIS using any of: ... If these fail to open in a browser and/or FrontPage, ... web server you cannot publish to the web server - there is no need to ... I added my userid to the permissions on the inetpub folder with full ...
    (microsoft.public.frontpage.programming)
  • 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)