T
Thomas A. Rowe
Technical support is available from Microsoft Product Support
Services at 1-866-PC SAFETY (1-866-727-2338). There is no
charge for support calls associated with security updates.
International customers can get support from their local Microsoft
subsidiaries. Phone numbers for international support can be found
at: http://support.microsoft.com/common/international.aspx
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
Services at 1-866-PC SAFETY (1-866-727-2338). There is no
charge for support calls associated with security updates.
International customers can get support from their local Microsoft
subsidiaries. Phone numbers for international support can be found
at: http://support.microsoft.com/common/international.aspx
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
Brian Williams said:any fixes available for this yet?
it been over a month
Michael Middleton said:http://support.microsoft.com/default.aspx?scid=kb;en-us;896861
Email me off the list is you need to.
Mike
http://www.m13.net
Brian said:What is the status of this post.
My server is still broke
Hi,
I am not sure which forum to post this to, thus it is crossposted.
That way redundant help is not received and others are not taxed timewise
over something already being resolved.
Thank you in advance.
Until the Windows server 2003 sp1 update was applied - all of our sites
worked fine.
Currently we receive errors when we try to publish the webs to the server.
[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.]
The websites are located on a small webserver.
It is a windows 2003 server, IIS6.0 with FPSE 2002.
SharePoint is not used.
FP2003 is used on a local computer to work on some of the client sites.
The edited content is then published to the above webserver with minimal to
no issues - (until the update on Thursday evening).
We have worked the full weekend trying to resolve this - following advice
from uninstalling IIS,
FPSE, Asp.net and reinstalling it - to changing permissions on sites.
We can no longer publish from local computer to remote [meaning the server]
and can not publish from the
server to local machine.
If you can help - I would deeply appreciate it. I rely on the one website
for my local clients and
the webserver for some other clients.
1) 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.
server's application event log:
-->
Event Type: Warning
Event Source: FrontPage 5.0
Event Category: None
Event ID: 1000
Date: 4/10/2005
Time: 2:11:05 PM
User: N/A
Computer: NS2
Description:
Microsoft FrontPage Server Extensions:
Error #3005f Message: Unable to read configuration for Microsoft Internet
Information Server.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--->
Event Type: Information
Event Source: FrontPage 5.0
Event Category: None
Event ID: 1000
Date: 4/10/2005
Time: 2:11:05 PM
User: N/A
Computer: NS2
Description:
Microsoft FrontPage Server Extensions:
Error reading IIS default Vroot info
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.