|
Home > Archive > FrontPage Server Extensions for Windows > June 2005 > An error occurred accessing your Windows SharePoint Services site files.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
An error occurred accessing your Windows SharePoint Services site files.
|
|
|
| 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 2005-04-10, 5:50 pm |
| 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)
http://www.ycoln-resources.com
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
"Dana" <publicngs@hotmail.com> wrote in message news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
> 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.
>
>
| |
|
| 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.
--
-
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message
news:%23nptScgPFHA.2132@TK2MSFTNGP14.phx.gbl...
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)
http://www.ycoln-resources.com
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
"Dana" <publicngs@hotmail.com> wrote in message
news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
> 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.
>
>
| |
|
|
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/defaul...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]" <sbradcpa@pacbell.net>
wrote in message news:42598697.6030206@pacbell.net...
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/defaul...kb;en-us;319305
Dana wrote:
> 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 2005-04-10, 5:50 pm |
| 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)
http://www.ycoln-resources.com
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
"Dana" <publicngs@hotmail.com> wrote in message news:uWvzk0gPFHA.1396@TK2MSFTNGP10.phx.gbl...
> 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.
>
>
> --
> -
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:%23nptScgPFHA.2132@TK2MSFTNGP14.phx.gbl...
> 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)
> http://www.ycoln-resources.com
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message
> news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
>
>
>
| |
|
|
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.
--
-
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message
news:uVSG4FhPFHA.3296@TK2MSFTNGP15.phx.gbl...
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)
http://www.ycoln-resources.com
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
"Dana" <publicngs@hotmail.com> wrote in message
news:uWvzk0gPFHA.1396@TK2MSFTNGP10.phx.gbl...
> 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.
>
>
> --
> -
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:%23nptScgPFHA.2132@TK2MSFTNGP14.phx.gbl...
> 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)
> http://www.ycoln-resources.com
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message
> news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
>
>
>
| |
|
| 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.
--
-
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message
news:uVSG4FhPFHA.3296@TK2MSFTNGP15.phx.gbl...
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)
http://www.ycoln-resources.com
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
"Dana" <publicngs@hotmail.com> wrote in message
news:uWvzk0gPFHA.1396@TK2MSFTNGP10.phx.gbl...
> 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.
>
>
> --
> -
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:%23nptScgPFHA.2132@TK2MSFTNGP14.phx.gbl...
> 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)
> http://www.ycoln-resources.com
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message
> news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
>
>
>
| |
|
| 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]" <sbradcpa@pacbell.net>
wrote in message news:42598697.6030206@pacbell.net...
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/defaul...kb;en-us;319305
Dana wrote:
> 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 2005-04-10, 5:50 pm |
| It has been communicated to MS.
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
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
"Dana" <publicngs@hotmail.com> wrote in message news:ewmoOkhPFHA.2788@TK2MSFTNGP09.phx.gbl...
> 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.
>
>
>
> --
> -
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:uVSG4FhPFHA.3296@TK2MSFTNGP15.phx.gbl...
> 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)
> http://www.ycoln-resources.com
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message
> news:uWvzk0gPFHA.1396@TK2MSFTNGP10.phx.gbl...
>
>
>
| |
| Thomas A. Rowe 2005-04-10, 5:50 pm |
| Dana,
You are welcome, and glad that you have everything back to normal.
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
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
"Dana" <publicngs@hotmail.com> wrote in message news:ewmoOkhPFHA.2788@TK2MSFTNGP09.phx.gbl...
> 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.
>
>
>
> --
> -
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:uVSG4FhPFHA.3296@TK2MSFTNGP15.phx.gbl...
> 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)
> http://www.ycoln-resources.com
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message
> news:uWvzk0gPFHA.1396@TK2MSFTNGP10.phx.gbl...
>
>
>
| |
| Thomas A. Rowe 2005-04-10, 5:50 pm |
| 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)
http://www.ycoln-resources.com
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
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message news:OO3k7thPFHA.1932@tk2msftngp13.phx.gbl...
> It has been communicated to MS.
>
> --
> ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
> WEBMASTER Resources(tm)
> http://www.ycoln-resources.com
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message news:ewmoOkhPFHA.2788@TK2MSFTNGP09.phx.gbl...
>
>
| |
|
| Hi,
We will call them tomorrow.
Thank you again.
--
-
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message
news:OSWsjzhPFHA.3788@tk2msftngp13.phx.gbl...
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)
http://www.ycoln-resources.com
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
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message
news:OO3k7thPFHA.1932@tk2msftngp13.phx.gbl...
> It has been communicated to MS.
>
> --
> ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
> WEBMASTER Resources(tm)
> http://www.ycoln-resources.com
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message
> news:ewmoOkhPFHA.2788@TK2MSFTNGP09.phx.gbl...
>
>
| |
|
| Hi,
We will call them tomorrow.
Thank you again.
--
-
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
wrote in message news:eeiG8aiPFHA.1884@TK2MSFTNGP15.phx.gbl...
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 wrote:
> 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.
>
>
>
| |
| Mike Walsh 2005-04-11, 2:49 am |
| >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
"Dana" <publicngs@hotmail.com> wrote in message
news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
> 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 2005-04-11, 2:49 am |
| Because FP extensions related error message indicates SharePoint Services and confuses a lot of
users.
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
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
"Mike Walsh" <englantilainen@microsoft.com> wrote in message
news:euS1K2kPFHA.3384@TK2MSFTNGP10.phx.gbl...
>
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
>
>
| |
| Dolphie 2005-04-11, 2:49 am |
| 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/windowsser...nt/default.mspx
--
-
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message
news:eVqz16kPFHA.3788@tk2msftngp13.phx.gbl...
Because FP extensions related error message indicates SharePoint Services
and confuses a lot of
users.
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
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
"Mike Walsh" <englantilainen@microsoft.com> wrote in message
news:euS1K2kPFHA.3384@TK2MSFTNGP10.phx.gbl...
>
> 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
>
> "Dana" <publicngs@hotmail.com> wrote in message
> news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
>
>
| |
| Thomas A. Rowe 2005-04-11, 2:49 am |
| 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)
http://www.ycoln-resources.com
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
"Dolphie" <publicngs@hotmail.com> wrote in message news:um5b6MlPFHA.2252@TK2MSFTNGP15.phx.gbl...
> 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/windowsser...nt/default.mspx
>
>
> --
> -
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:eVqz16kPFHA.3788@tk2msftngp13.phx.gbl...
> Because FP extensions related error message indicates SharePoint Services
> and confuses a lot of
> users.
>
> --
> ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
> WEBMASTER Resources(tm)
> http://www.ycoln-resources.com
> 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
>
> "Mike Walsh" <englantilainen@microsoft.com> wrote in message
> news:euS1K2kPFHA.3384@TK2MSFTNGP10.phx.gbl...
>
>
>
| |
| Mike Walsh 2005-04-11, 2:49 am |
| > 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
"Dolphie" <publicngs@hotmail.com> wrote in message
news:um5b6MlPFHA.2252@TK2MSFTNGP15.phx.gbl...
> 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/windowsser...nt/default.mspx
>
>
> --
> -
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:eVqz16kPFHA.3788@tk2msftngp13.phx.gbl...
> Because FP extensions related error message indicates SharePoint Services
> and confuses a lot of
> users.
>
> --
> ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
> WEBMASTER Resources(tm)
> http://www.ycoln-resources.com
> 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
>
> "Mike Walsh" <englantilainen@microsoft.com> wrote in message
> news:euS1K2kPFHA.3384@TK2MSFTNGP10.phx.gbl...
>
>
>
| |
| SuperGumby [SBS MVP] 2005-04-11, 2:49 am |
| 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.
"Mike Walsh" <englantilainen@microsoft.com> wrote in message
news:u%23m1SclPFHA.2384@tk2msftngp13.phx.gbl...
>
> 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
>
> "Dolphie" <publicngs@hotmail.com> wrote in message
> news:um5b6MlPFHA.2252@TK2MSFTNGP15.phx.gbl...
>
>
| |
|
| 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.
--
-
"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:uRD$%23glPFHA.508@TK2MSFTNGP12.phx.gbl...
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.
"Mike Walsh" <englantilainen@microsoft.com> wrote in message
news:u%23m1SclPFHA.2384@tk2msftngp13.phx.gbl...
>
> 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
>
> "Dolphie" <publicngs@hotmail.com> wrote in message
> news:um5b6MlPFHA.2252@TK2MSFTNGP15.phx.gbl...
>
>
| |
|
| 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]" <sbradcpa@pacbell.net>
wrote in message news:eeiG8aiPFHA.1884@TK2MSFTNGP15.phx.gbl...
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 wrote:
> 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.
>
>
>
| |
| Brian Williams 2005-04-13, 8:50 pm |
| What is the status of this post.
My server is still broke 
"Dana" <publicngs@hotmail.com> wrote in message
news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
> 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 2005-04-13, 8:50 pm |
| 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)
http://www.ycoln-resources.com
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
"Brian Williams" <hidemyemail@hotmail.com> wrote in message
news:%23eTdRjIQFHA.3880@tk2msftngp13.phx.gbl...
> What is the status of this post.
> My server is still broke
>
> "Dana" <publicngs@hotmail.com> wrote in message news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
>
>
| |
| Thomas A. Rowe 2005-04-14, 2:49 am |
| 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)
http://www.ycoln-resources.com
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
"Thomas A. Rowe" <tarowe@mvps.org> wrote in message news:uSMOaYJQFHA.2584@TK2MSFTNGP15.phx.gbl...
> 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)
> http://www.ycoln-resources.com
> 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
>
> "Brian Williams" <hidemyemail@hotmail.com> wrote in message
> news:%23eTdRjIQFHA.3880@tk2msftngp13.phx.gbl...
>
>
| |
|
| 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.
--
-
"Brian Williams" <hidemyemail@hotmail.com> wrote in message
news:%23eTdRjIQFHA.3880@tk2msftngp13.phx.gbl...
What is the status of this post.
My server is still broke
"Dana" <publicngs@hotmail.com> wrote in message
news:%23afH4WgPFHA.1088@TK2MSFTNGP14.phx.gbl...
> 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 2005-04-27, 2:47 am |
| 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)
http://www.ycoln-resources.com
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.
========================================
======
"Michael Middleton" <mike@m13.net> wrote in message news:smCbe.22791$Xg.17127@okepread02...[vbcol=seagreen]
>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/defaul...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
>
>
| |
|
| 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
--
-
"Michael Middleton" <mike@m13.net> wrote in message
news:smCbe.22791$Xg.17127@okepread02...
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/defaul...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 2005-05-03, 2:47 am |
| Technical support is available from Microsoft Product Support
Services at 1-866-PC SAFETY (1-866-727-2338). There is no
charge for support calls associated with security updates.
International customers can get support from their local Microsoft
subsidiaries. Phone numbers for international support can be found
at: http://support.microsoft.com/common/international.aspx
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
========================================
======
"Brian Williams" <hidemyemail@hotmail.com> wrote in message
news:uwycPk4TFHA.544@TK2MSFTNGP15.phx.gbl...
> any fixes available for this yet?
> it been over a month
>
> "Michael Middleton" <mike@m13.net> wrote in message news:9oCbe.22792$Xg.13442@okepread02...
>
| |
|
| Hi Michael,
Actually KBA 896861 was one of the initial 'fixes' we had tried - prior to
uninstalling win 2k3 sp1.
It was not successful.
The only successful solution was to uninstall sp1.
After that - yes, we did have to conduct clean up relative to the other
'fixes' employed prior to the uninstallation of sp1.
Those who uninstalled sp1 directly (post installation outcries from users)
encountered minimal residual issues.
It was only those of us that tried to find an alternative to fully
uninstalling sp1 (as we realize the upgrade patches more than one item and
we do not want our server vulnerable) that experienced residual issues that
had to be remedied via more drastic means post sp1 uninstallation.
In our case - we are leaving sp1 off the machine.
The only reason for this post is to clarify that what you are posing is not
a solution for many of us - much as the comment on the part of Jim Cheshire
above is not a solution.
Thank you for your ongoing posts.
--
-
"Michael Middleton" <mike@m13.net> wrote in message
news:Ytsde.3$fx3.2@okepread02...
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/defaul...kb;en-us;896861
Sorry you had so much trouble and that I wasn't more help,
Mike
http://www.m13.net
> 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'm experiencing the same issues. I can publish with no problems directly
to the web site, but can't sucessfully push/pull to the local machine. I
hope MS comes out with a fix ASAP.
"Michael Middleton" <mike@m13.net> wrote in message
news:Ytsde.3$fx3.2@okepread02...[vbcol=seagreen]
> 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/defaul...kb;en-us;896861
>
> Sorry you had so much trouble and that I wasn't more help,
>
> Mike
> http://www.m13.net
>
>
>
>
|
|
|
|
|