An error occurred accessing your Windows SharePoint Services site files.

[Dolphie]

Hi,

Thank you Thomas.

You are correct.

We were not sure where the Sharepoint error message came from.

Apparently, Sharepoint is currently being bundled with Windows 2003 server:
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx


--
-
Because FP extensions related error message indicates SharePoint Services
and confuses a lot of
users.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

SharePoint is not used.

why then post it also to the sharepoint newsgroup?

Mike Walsh, Helsinki, Finland
WSS FAQ http://wss.collutions.com
please reply to the newsgroup only

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.

 

[Thomas A. Rowe]

Joe,

I have removed SP1, however without SP1 install, non of the OWS site numbers match any of the
identifier associated with any of the webs.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

Hello Thomas,

I have been investigating this issue also and I noticed something very
important.

If you go to your Computer Management section and look at the OWC
permissions in the users section. They do not match the site number anymore
after SP1

In IIS 6.0 MMC you can see this by clicking on "web sites" and look to your
right pane You will see the identifier is different than what is in the admin
account in the Computer mangement console.
FYI

Joe

A number of users have indicated that they are having problem with Windows 2003 SP1 and FrontPage
(all versions), the best suggestion I think at this point is to uninstall SP1.

I had to do the same because I was not able to save any edited files within a web without
receiving
error message about permissions, however I had no problem accessing any of the webs on the server
from within FP.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

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.

 

[Thomas A. Rowe]

Actually it is not bundled with Windows 2003 server, it is a separate download and install.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

Hi,

Thank you Thomas.

You are correct.

We were not sure where the Sharepoint error message came from.

Apparently, Sharepoint is currently being bundled with Windows 2003 server:
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx


--
-
Because FP extensions related error message indicates SharePoint Services
and confuses a lot of
users.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

SharePoint is not used.

why then post it also to the sharepoint newsgroup?

Mike Walsh, Helsinki, Finland
WSS FAQ http://wss.collutions.com
please reply to the newsgroup only

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.

 

[Mike Walsh]

Apparently, Sharepoint is currently being bundled with Windows 2003

server:

I wouldn't call it bundled.

1. You can download WSS. If you have Windows 2003 Server you can use it.

2. If you have Windows 2003 Server and run WindowsUpdate you'll be offered
the chance to install WSS.

WSS will be (in my definition of the word) bundled with Win 2003 Server R2
(publically available information) but again will need to be installed. The
difference to the present Win 2003 Server is that it will be on the CD - it
isn't on the Windows 2003 Server CD.

Mike Walsh, Helsinki, Finland

Hi,

Thank you Thomas.

You are correct.

We were not sure where the Sharepoint error message came from.

Apparently, Sharepoint is currently being bundled with Windows 2003
server:
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx


--
-
Because FP extensions related error message indicates SharePoint Services
and confuses a lot of
users.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

SharePoint is not used.

why then post it also to the sharepoint newsgroup?

Mike Walsh, Helsinki, Finland
WSS FAQ http://wss.collutions.com
please reply to the newsgroup only

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.

 

[SuperGumby [SBS MVP]]

also, keep in mind guys (and I only mention because it seems some people may
not know)

Windows Sharepoint Services is a different kettle of fish than Sharepoint
Portal Server.

Apparently, Sharepoint is currently being bundled with Windows 2003
server:

I wouldn't call it bundled.

1. You can download WSS. If you have Windows 2003 Server you can use it.

2. If you have Windows 2003 Server and run WindowsUpdate you'll be offered
the chance to install WSS.

WSS will be (in my definition of the word) bundled with Win 2003 Server R2
(publically available information) but again will need to be installed.
The difference to the present Win 2003 Server is that it will be on the
CD - it isn't on the Windows 2003 Server CD.

Mike Walsh, Helsinki, Finland

Hi,

Thank you Thomas.

You are correct.

We were not sure where the Sharepoint error message came from.

Apparently, Sharepoint is currently being bundled with Windows 2003
server:
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx


--
-
Because FP extensions related error message indicates SharePoint Services
and confuses a lot of
users.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

SharePoint is not used.

why then post it also to the sharepoint newsgroup?

Mike Walsh, Helsinki, Finland
WSS FAQ http://wss.collutions.com
please reply to the newsgroup only

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,

Yes, it is a tad confusing.

Fortunately, we did figure out it was not related to the portal server.

Yet it was a previously unencountered message.

The fact that it contained "Windows Sharepoint Services" is why we posted
to the public.sharepoint.windowsservices in conjunction with the other ngs.

Some of the research we came across implied a bundling of Sharepoint with
Windows 2003 server.

Either way, hopefully, this thread and its valuable information will help
others.

Thank you for your thoughts.


--
-
also, keep in mind guys (and I only mention because it seems some people may
not know)

Windows Sharepoint Services is a different kettle of fish than Sharepoint
Portal Server.

Apparently, Sharepoint is currently being bundled with Windows 2003
server:

I wouldn't call it bundled.

1. You can download WSS. If you have Windows 2003 Server you can use it.

2. If you have Windows 2003 Server and run WindowsUpdate you'll be offered
the chance to install WSS.

WSS will be (in my definition of the word) bundled with Win 2003 Server R2
(publically available information) but again will need to be installed.
The difference to the present Win 2003 Server is that it will be on the
CD - it isn't on the Windows 2003 Server CD.

Mike Walsh, Helsinki, Finland

Hi,

Thank you Thomas.

You are correct.

We were not sure where the Sharepoint error message came from.

Apparently, Sharepoint is currently being bundled with Windows 2003
server:
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx


--
-
Because FP extensions related error message indicates SharePoint Services
and confuses a lot of
users.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

SharePoint is not used.

why then post it also to the sharepoint newsgroup?

Mike Walsh, Helsinki, Finland
WSS FAQ http://wss.collutions.com
please reply to the newsgroup only

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 Susan,

As a follow-up - post phone call to Microsoft.

They took down the information and then suggested putting things into
written form mailing it to MS as well.
Apparently, written correspondence is given immediate attention and is
incorporated into their monthly reports.


--
-
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <[email protected]>
wrote in message Call Microsoft... you cannot just depend on newsgroup postings.

Calling Microsoft is THE BEST way to put this on a fast track for
resolution. I cannot stress this enough.

 

[Brian Williams]

What is the status of this post.
My server is still broke

 

[Thomas A. Rowe]

The temporary solution is to un-install SP1, at least for those of use that are using FrontPage to
publish or manage site content via the FP extensions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

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.

 

[Thomas A. Rowe]

Let me correct this...

The temporary solution is to un-install SP1, at least for those of us that are using FrontPage to
publish or manage site content via the FP extensions.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

The temporary solution is to un-install SP1, at least for those of use that are using FrontPage to
publish or manage site content via the FP extensions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

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]

Brian,
I strongly recommend following Thomas Rowe's suggestion [uninstall win 2k3
sp1].
If you encounter additional errors, please post back here.
Uninstalling Win 2003 sp1 resolved the main problems - especially the posted
specific error message.
We encountered some residual issues, mostly due to the application of
recommended fixes appropriate to the error message.
Those are now cleaned up as well, thanks again to the Thomas and the other
MVPs on this forum.

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

 

[Michael Middleton]

I may have posted my fix in the wrong thread.

You don't need to uninstall SP1.

You do need to stop checking the loopback connector so that Kerberos
doesn't break for virtual domains.

http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

At least that, and a good sanity check of permissions fixed it for me.
See my previous post under "Win 2003 SP1 FrontPage Problem".

It has been several days now, two servers were having this issue..
hundreds of domains... and zero complaints after we made this change.

Mike Middleton
http://www.m13.net

 

[Michael Middleton]

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.

 

[Thomas A. Rowe]

I had no problems actually accessing any web under Windows 2003 SP1 via FrontPage, however I was not
able to save any existing pages directly after editing, only new pages. Note: I was force in to the
Save As dialog, and 3 or 4 time of clicking Ok, and then finally click Cancel, I discovered that the
page actually had been saved.

I agree that it is a permissions related issues.

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

I may have posted my fix in the wrong thread.

You don't need to uninstall SP1.

You do need to stop checking the loopback connector so that Kerberos doesn't break for virtual
domains.

http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

At least that, and a good sanity check of permissions fixed it for me. See my previous post under
"Win 2003 SP1 FrontPage Problem".

It has been several days now, two servers were having this issue.. hundreds of domains... and zero
complaints after we made this change.

Mike Middleton
http://www.m13.net

Brian,
I strongly recommend following Thomas Rowe's suggestion [uninstall win 2k3 sp1].
If you encounter additional errors, please post back here.
Uninstalling Win 2003 sp1 resolved the main problems - especially the posted specific error
message.
We encountered some residual issues, mostly due to the application of recommended fixes
appropriate to the error message.
Those are now cleaned up as well, thanks again to the Thomas and the other MVPs on this forum.

 

[Guest]

Hello Thomas,

I know this is an old post but I thing I just stumbled upon something?

If you recreate the accounts after SP1 they seem to work e.g. Admin.
Contributor. Advanced author and then assign them to the appropriate people.


Joe

I had no problems actually accessing any web under Windows 2003 SP1 via FrontPage, however I was not
able to save any existing pages directly after editing, only new pages. Note: I was force in to the
Save As dialog, and 3 or 4 time of clicking Ok, and then finally click Cancel, I discovered that the
page actually had been saved.

I agree that it is a permissions related issues.

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

I may have posted my fix in the wrong thread.

You don't need to uninstall SP1.

You do need to stop checking the loopback connector so that Kerberos doesn't break for virtual
domains.

http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

At least that, and a good sanity check of permissions fixed it for me. See my previous post under
"Win 2003 SP1 FrontPage Problem".

It has been several days now, two servers were having this issue.. hundreds of domains... and zero
complaints after we made this change.

Mike Middleton
http://www.m13.net

Brian,
I strongly recommend following Thomas Rowe's suggestion [uninstall win 2k3 sp1].
If you encounter additional errors, please post back here.
Uninstalling Win 2003 sp1 resolved the main problems - especially the posted specific error
message.
We encountered some residual issues, mostly due to the application of recommended fixes
appropriate to the error message.
Those are now cleaned up as well, thanks again to the Thomas and the other MVPs on this forum.

 

[Thomas A. Rowe]

I really never set those up originally, all of my sites are set to have full access from the Admin
account. This is a in-house server used for development only.

Plus there should be no reason for SP1 to change those permissions.

Imagine a web hosting service with 100s of server and 1,000s of user accounts, do you really think
they are going to re-create accounts?

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

Hello Thomas,

I know this is an old post but I thing I just stumbled upon something?

If you recreate the accounts after SP1 they seem to work e.g. Admin.
Contributor. Advanced author and then assign them to the appropriate people.


Joe

I had no problems actually accessing any web under Windows 2003 SP1 via FrontPage, however I was
not
able to save any existing pages directly after editing, only new pages. Note: I was force in to
the
Save As dialog, and 3 or 4 time of clicking Ok, and then finally click Cancel, I discovered that
the
page actually had been saved.

I agree that it is a permissions related issues.

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

I may have posted my fix in the wrong thread.

You don't need to uninstall SP1.

You do need to stop checking the loopback connector so that Kerberos doesn't break for virtual
domains.

http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

At least that, and a good sanity check of permissions fixed it for me. See my previous post
under
"Win 2003 SP1 FrontPage Problem".

It has been several days now, two servers were having this issue.. hundreds of domains... and
zero
complaints after we made this change.

Mike Middleton
http://www.m13.net


Brian,
I strongly recommend following Thomas Rowe's suggestion [uninstall win 2k3 sp1].
If you encounter additional errors, please post back here.
Uninstalling Win 2003 sp1 resolved the main problems - especially the posted specific error
message.
We encountered some residual issues, mostly due to the application of recommended fixes
appropriate to the error message.
Those are now cleaned up as well, thanks again to the Thomas and the other MVPs on this forum.

 

[Guest]

No I don't think they will set them up. but you should if you have FP because
I have 5 sites hosted for others and they would be able to get into the
other webs if i did not set these accounts per site. Well anyhow i don't
think it is a "fix" for SP1

I really never set those up originally, all of my sites are set to have full access from the Admin
account. This is a in-house server used for development only.

Plus there should be no reason for SP1 to change those permissions.

Imagine a web hosting service with 100s of server and 1,000s of user accounts, do you really think
they are going to re-create accounts?

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

Hello Thomas,

I know this is an old post but I thing I just stumbled upon something?

If you recreate the accounts after SP1 they seem to work e.g. Admin.
Contributor. Advanced author and then assign them to the appropriate people.


Joe

I had no problems actually accessing any web under Windows 2003 SP1 via FrontPage, however I was
not
able to save any existing pages directly after editing, only new pages. Note: I was force in to
the
Save As dialog, and 3 or 4 time of clicking Ok, and then finally click Cancel, I discovered that
the
page actually had been saved.

I agree that it is a permissions related issues.

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

I may have posted my fix in the wrong thread.

You don't need to uninstall SP1.

You do need to stop checking the loopback connector so that Kerberos doesn't break for virtual
domains.

http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

At least that, and a good sanity check of permissions fixed it for me. See my previous post
under
"Win 2003 SP1 FrontPage Problem".

It has been several days now, two servers were having this issue.. hundreds of domains... and
zero
complaints after we made this change.

Mike Middleton
http://www.m13.net


Brian,
I strongly recommend following Thomas Rowe's suggestion [uninstall win 2k3 sp1].
If you encounter additional errors, please post back here.
Uninstalling Win 2003 sp1 resolved the main problems - especially the posted specific error
message.
We encountered some residual issues, mostly due to the application of recommended fixes
appropriate to the error message.
Those are now cleaned up as well, thanks again to the Thomas and the other MVPs on this forum.

 

[Dana]

Hi Michael,

Although I appreciate your post - that did not serve as a fix for us.

The only full fix was as explained above (uninstall sp1).

We will not be implementing SP1 until we are assured that it will not break
our system again.

We checked all permissions. We even removed and added accounts. We tried
many, many fixes (KBA recommended, Expert recommended, etc)
We followed various bits of advice (albeit good advice, it did not resolve
the issues and when sp1 was uninstalled the 'fixes' left residual damage
that required days of rectifying to enable all webs to be functional).

The main fix for this error is to uninstall Windows 2003 sp1.
Especially if it is uninstalled prior to other 'fixes' have been employed.


D


--
-
I may have posted my fix in the wrong thread.

You don't need to uninstall SP1.

You do need to stop checking the loopback connector so that Kerberos
doesn't break for virtual domains.

http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

At least that, and a good sanity check of permissions fixed it for me.
See my previous post under "Win 2003 SP1 FrontPage Problem".

It has been several days now, two servers were having this issue..
hundreds of domains... and zero complaints after we made this change.

Mike Middleton
http://www.m13.net

 

[Michael Middleton]

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

 

[Brian Williams]

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.