An error occurred accessing your Windows SharePoint Services site files.

[Dana]

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]

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.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

Is this a SBS box? If it is we don't have "our" SP1 yet.
Just getting a feel for what this system is.

Have you reviewed www.eventid.net for those error messages?


You receive an "Error reading IIS default vroot info" error message when
you use Internet Services Manager to Internet Information Services (IIS):
http://support.microsoft.com/default.aspx?scid=kb;en-us;319305

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.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

And if a number of users are reporting issues....they should call into
Microsoft. It's only when a number of users start bringing it to the
attention to a number of people that it gets fixed.

1-866-pcSafety

 

[Dana]

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files ...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


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

 

[Dana]

Hi,
Thank you for your response.

[Is this a SBS box? If it is we don't have "our" SP1 yet.]
-->>I thought it was - I just double checked and below is the version.
[apologies to the sbs ng group for posting there]
Windows Server 2003, Standard Edition

[Have you reviewed www.eventid.net for those error messages?]
__>>Yes and have met with minimal success. {meaning I have tried all that
has been recommended and it has not resolved the issue}

[You receive an "Error reading IIS default vroot info" error message when
you use Internet Services Manager to Internet Information Services (IIS):
http://support.microsoft.com/default.aspx?scid=kb;en-us;319305]

Yes. It did not help for the following reasons:
1) The Win 2k3 server uses IIS6.0 - not 4.0 or 5.0
2) The settings were already as indicated in the content pertaining to
IIS5.0
{In the Application Protection item list, click Medium (Pooled), and then
click OK.}

Thank you again for your response.


--
-
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <[email protected]>
wrote in message Is this a SBS box? If it is we don't have "our" SP1 yet.
Just getting a feel for what this system is.

Have you reviewed www.eventid.net for those error messages?


You receive an "Error reading IIS default vroot info" error message when
you use Internet Services Manager to Internet Information Services (IIS):
http://support.microsoft.com/default.aspx?scid=kb;en-us;319305

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]

Yes, I uninstalled Windows 2003 SP1 because I was not able to save any edited files from within FP.
Everything else continued to worked under Windows 2003 SP1 that worked prior to SP1.

Actually installing and then uninstalling SP1 solve another issue I was having.

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

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

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files ...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


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

 

[Dana]

Hi,
Thank you.
We will try that and report back to you here.
Hopefully, that will assist you in helping others and for letting MS know.


--
-
Yes, I uninstalled Windows 2003 SP1 because I was not able to save any
edited files from within FP.
Everything else continued to worked under Windows 2003 SP1 that worked prior
to SP1.

Actually installing and then uninstalling SP1 solve another issue I was
having.

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

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

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files ...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


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

 

[Dana]

Hi,

Uninstalling Windows server 2003 sp1 worked.
I can now access all websites, clean up the mess I made assuming it was
something other than the sp1, publish to the remote and local sites, edit
pages, etc.

I truly hope you can communicate this to Microsoft.

I spent the majority of this weekend researching this [google], reading
KBAs, reading MSDN, etc, and applying their 'fixes' - only to discover that
I should have trusted the fact that the main change was the sp1.

I also learned that google does not necessarily have the most up to date
posts and will check here more frequently.

You are wonderful and I thank you immensely for all the time you devote to
helping us on these newsgroups.



--
-
Yes, I uninstalled Windows 2003 SP1 because I was not able to save any
edited files from within FP.
Everything else continued to worked under Windows 2003 SP1 that worked prior
to SP1.

Actually installing and then uninstalling SP1 solve another issue I was
having.

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

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

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files ...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


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

 

[Dana]

Hi Susan,

As indicated below - it turns out that we do not have sbs - but, hopefully,
you will be able to affect the service pack before it is public.
The mess the sp1 makes of the Win 2k3 server's web services is something
most businesses could ill afford.

Good luck and I truly hope this post will benefit the SBS group as well.

Thank you for your kindness.



--
-
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <[email protected]>
wrote in message Is this a SBS box? If it is we don't have "our" SP1 yet.
Just getting a feel for what this system is.

Have you reviewed www.eventid.net for those error messages?


You receive an "Error reading IIS default vroot info" error message when
you use Internet Services Manager to Internet Information Services (IIS):
http://support.microsoft.com/default.aspx?scid=kb;en-us;319305

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]

It has been communicated to MS.

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

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

Hi,

Uninstalling Windows server 2003 sp1 worked.
I can now access all websites, clean up the mess I made assuming it was
something other than the sp1, publish to the remote and local sites, edit
pages, etc.

I truly hope you can communicate this to Microsoft.

I spent the majority of this weekend researching this [google], reading
KBAs, reading MSDN, etc, and applying their 'fixes' - only to discover that
I should have trusted the fact that the main change was the sp1.

I also learned that google does not necessarily have the most up to date
posts and will check here more frequently.

You are wonderful and I thank you immensely for all the time you devote to
helping us on these newsgroups.



--
-
Yes, I uninstalled Windows 2003 SP1 because I was not able to save any
edited files from within FP.
Everything else continued to worked under Windows 2003 SP1 that worked prior
to SP1.

Actually installing and then uninstalling SP1 solve another issue I was
having.

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

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

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files ...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


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

Dana,

You are welcome, and glad that you have everything back to normal.

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

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

Hi,

Uninstalling Windows server 2003 sp1 worked.
I can now access all websites, clean up the mess I made assuming it was
something other than the sp1, publish to the remote and local sites, edit
pages, etc.

I truly hope you can communicate this to Microsoft.

I spent the majority of this weekend researching this [google], reading
KBAs, reading MSDN, etc, and applying their 'fixes' - only to discover that
I should have trusted the fact that the main change was the sp1.

I also learned that google does not necessarily have the most up to date
posts and will check here more frequently.

You are wonderful and I thank you immensely for all the time you devote to
helping us on these newsgroups.



--
-
Yes, I uninstalled Windows 2003 SP1 because I was not able to save any
edited files from within FP.
Everything else continued to worked under Windows 2003 SP1 that worked prior
to SP1.

Actually installing and then uninstalling SP1 solve another issue I was
having.

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

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

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files ...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


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

Users with any problems occurring after the install Windows 2003 SP1, also need to call MS Product
Support as well as posting in the appropriate MS newsgroup for any effected applications.

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

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

It has been communicated to MS.

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

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

Hi,

Uninstalling Windows server 2003 sp1 worked.
I can now access all websites, clean up the mess I made assuming it was
something other than the sp1, publish to the remote and local sites, edit
pages, etc.

I truly hope you can communicate this to Microsoft.

I spent the majority of this weekend researching this [google], reading
KBAs, reading MSDN, etc, and applying their 'fixes' - only to discover that
I should have trusted the fact that the main change was the sp1.

I also learned that google does not necessarily have the most up to date
posts and will check here more frequently.

You are wonderful and I thank you immensely for all the time you devote to
helping us on these newsgroups.



--
-
Yes, I uninstalled Windows 2003 SP1 because I was not able to save any
edited files from within FP.
Everything else continued to worked under Windows 2003 SP1 that worked prior
to SP1.

Actually installing and then uninstalling SP1 solve another issue I was
having.

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

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

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files ...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


--
-
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.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

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.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

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.

 

[Dana]

Hi,
We will call them tomorrow.
Thank you again.


--
-
Users with any problems occurring after the install Windows 2003 SP1, also
need to call MS Product
Support as well as posting in the appropriate MS newsgroup for any effected
applications.

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

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

It has been communicated to MS.

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

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

Hi,

Uninstalling Windows server 2003 sp1 worked.
I can now access all websites, clean up the mess I made assuming it was
something other than the sp1, publish to the remote and local sites, edit
pages, etc.

I truly hope you can communicate this to Microsoft.

I spent the majority of this weekend researching this [google], reading
KBAs, reading MSDN, etc, and applying their 'fixes' - only to discover
that
I should have trusted the fact that the main change was the sp1.

I also learned that google does not necessarily have the most up to date
posts and will check here more frequently.

You are wonderful and I thank you immensely for all the time you devote
to
helping us on these newsgroups.



--
-
Yes, I uninstalled Windows 2003 SP1 because I was not able to save any
edited files from within FP.
Everything else continued to worked under Windows 2003 SP1 that worked
prior
to SP1.

Actually installing and then uninstalling SP1 solve another issue I was
having.

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

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

Hi,

Thank you for your response.

[I had to do the same because I was not able to save any edited files
...
FP]

Do you mean you uninstalled SP1?

Thank you in advance.


--
-
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.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

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,
We will call them tomorrow.
Thank you again.

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

 

[Mike Walsh]

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

 

[Guest]

You are correct!
Before I posted I read most of the strings in this post to see about the
same issue.

I installed SPI on Server2003 enterprise edition and I cannot access the
administration locally on the domain. I can however access my webs via
FrontPage itself. Weird? You would think if it wouldn't let you in on a
machine locally why remotely.
Thanks everyone for the participation and help. I will call

Joe

 

[Thomas A. Rowe]

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.

 

[Guest]

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.