An error occurred accessing your Windows SharePoint Services site files.

[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.
==============================================

any fixes available for this yet?
it been over a month

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

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.

 

[Dana]

Hi Michael,

Actually KBA 896861 was one of the initial 'fixes' we had tried - prior to
uninstalling win 2k3 sp1.
It was not successful.

The only successful solution was to uninstall sp1.

After that - yes, we did have to conduct clean up relative to the other
'fixes' employed prior to the uninstallation of sp1.

Those who uninstalled sp1 directly (post installation outcries from users)
encountered minimal residual issues.

It was only those of us that tried to find an alternative to fully
uninstalling sp1 (as we realize the upgrade patches more than one item and
we do not want our server vulnerable) that experienced residual issues that
had to be remedied via more drastic means post sp1 uninstallation.

In our case - we are leaving sp1 off the machine.

The only reason for this post is to clarify that what you are posing is not
a solution for many of us - much as the comment on the part of Jim Cheshire
above is not a solution.

Thank you for your ongoing posts.

--
-
Dana,

I know that Windows 2003 SP1 servers can host multiple virtual domains
with FPSE on them owned by happy customers. I am sure that uninstalling
SP1 is not the only answer, but in your situation I trust that it was
the best answer and am glad things are finally back to normal for you.

I suspect that you made some other changes, removing the new accounts
perhaps, and went past a point of no return. Uninstalling SP1 may have
been your only choice then, but before you made those other changes, I
bet you could have dealt with the authentication issue(s) and saved
yourself days of "rectifying". I wish I could have been more help.

For others reading this: Make sure the new MSSharePointApp Pool is run
as "Local Service", make sure that the roles.ini files ACL includes
System full control and that the security is not inherited. And remove
the loopback adapter being checked per
http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

Sorry you had so much trouble and that I wasn't more help,

Mike
http://www.m13.net

 

[BobC]

This worked for me!

Hi

I have had exactly the same problem as other users using Frontpage after installing Win2003 SP1. This was further complicated as I also installed the asp.net 2.0 framework immediately after, so I didn't know whether this was the issue.

While idly fiddling with Frontpage (I couldn't do anything else!) I right-clicked the site address (first item in folder list frame). I then decided to click Properties. When I did this I noticed that both the Allow scripts to be run and Allow files to be browsed checkboxes were empty.

I then ticked both of these, clicked OK and hey presto! All my pages/folders suddenly reappeared.

I am not saying it will work for all of you, just that you should give it a try.

BobC