11-13-06 01:59 PM
I need to first set your expectations - this is not a problem with
displaying http://localhost.
FrontPage web publishing is not a part of IIS but rather a special
application running on top of IIS (much like the way FrontPage is not a
part of Windows but rather a special application running on top of
Windows). If you have problems with FrontPage/Sharepoint, you will want
to query their newsgroups or support forums for help.
Re: your other questions --
1. the /localstart.asp issue is ignorable and unrelated to your
FrontPage and WebDAV issue - it tells you that IIS is working, but says
nothing about FrontPage or WebDAV. Remember, IIS is a server with a
million different functionality, some related, others are not related.
So, the fact one thing is broken may/not have relevance on another
functionality. How does one know whether two functionalities are
related? Experience.
2. a clean Event Log does not mean the server is functioning correctly.
In particular, IIS logs all request processing status in its log file
separate from the Event Log for many, many good reasons. For example,
if you get a 500 server error which breaks the functionality of your
application (it's not running), that 500 is logged in the IIS log but
not in the Event Log. So, the fact that the Event Log is clean does not
mean your application is functional.
I suggest that you chase down the suggestions offered by FrontPage for
possible errors. I also suggest you report the IIS log entry(s)
corresponding to the error displayed by FrontPage. Read my following
blog entry as a primer:
http://blogs.msdn.com/david.wang/ar.../>
ooting.aspx
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Alfred Moussali wrote:[vbcol=seagreen]
> 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 anym
ore.
>
> 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:
>
[ Post a follow-up to this message ]
| 
