I have a virtual installation of Server 2003 Web using Virtual PC 2004 with
Office SharePoint Portal Server 2003 installed.

I was able to setup (or extend) a local virtual server as a top level site
and point at an Sql 2000 installation on another machine. However, after
choosing a template (any template I have found) and browseing to the default
home of the top level site, I get the following error:
===========================
An unexpected error has occurred.

Web Parts Maintenance Page: If you have permission, you can use this page to
temporarily disable Web Parts or remove personal settings. For more
information, contact your site administrator.


Troubleshoot issues with Windows SharePoint Services.

===========================

When I check the application event log I see the following two errors:

"The safe mode service of Windows SharePoint Services has failed to
initialize because of an unknown error."

Followed by:

"Request failed."


I've tried messing with permissions, but everything more or less has domain
administrator access ... So as of now I'm going to rebuild the virtual
installation and see if I have any luck with that.

Any ideas otherwise?

TIA//

Re: Problem running Top-Level website by Bob

Bob
Fri Nov 11 16:26:59 CST 2005

Have you tried running an additional IISReset? Have you checked your
AppPools? Have you checked your virtual server against its app pool.. look
in the Documents folder on the bottom and you will see if your lined up with
the App pool you specified during the initial setup.

I do alot of work / testing in the realm you are having a problem with as I
like to test my sites before i deploy to live.. Let me know if your still
having an issue.
--
Bob Fox
http://www.mycblog.com/blog/Foxhole/default.aspx
"Chris Newby" <Chris.Newby@Rockcreekglobal.com> wrote in message
news:e0tL7su5FHA.3432@TK2MSFTNGP10.phx.gbl...
>I have a virtual installation of Server 2003 Web using Virtual PC 2004 with
>Office SharePoint Portal Server 2003 installed.
>
> I was able to setup (or extend) a local virtual server as a top level site
> and point at an Sql 2000 installation on another machine. However, after
> choosing a template (any template I have found) and browseing to the
> default home of the top level site, I get the following error:
> ===========================
> An unexpected error has occurred.
>
> Web Parts Maintenance Page: If you have permission, you can use this page
> to temporarily disable Web Parts or remove personal settings. For more
> information, contact your site administrator.
>
>
> Troubleshoot issues with Windows SharePoint Services.
>
> ===========================
>
> When I check the application event log I see the following two errors:
>
> "The safe mode service of Windows SharePoint Services has failed to
> initialize because of an unknown error."
>
> Followed by:
>
> "Request failed."
>
>
> I've tried messing with permissions, but everything more or less has
> domain administrator access ... So as of now I'm going to rebuild the
> virtual installation and see if I have any luck with that.
>
> Any ideas otherwise?
>
> TIA//
>



Re: Problem running Top-Level website by Chris

Chris
Fri Nov 11 17:22:45 CST 2005

Hey Bob,

Yeah I tried all that and a few other things as well. One thing that I
didn't mention in my original post was that I had initially installed Sql
Server 2005 Beta on my Server 2003 emulation *before* I installed
SharePoint. This of course installed .Net 2.0 Beta as well. As a result all
my SharePoint applications were mapped to the 2.0 Asp.Net isapi. Well ...

I changed all the mappings, uninstalled Asp.Net 2.0, changed the mappings to
Asp.Net 1.1 ... that didn't work
I uninstalled all Asp.Net versions, then re-installed Asp.Net 1.1 ... that
didn't work
I uninstalled Sql Server 2005 Beta and the .Net RT 2.0 ... that didn't work

Finally, I uninstalled SharePoint Portal 2003 and everything else except for
Server 2003 itself ... then I reinstalled Asp.Net 1.1 and reinstalled
SharePoint ... and voila, I finally got a heart beat.

I'm still not sure what was wrong exactly with the original configuration
... but I seem to be in business now.


"Bob Fox" <bfox11b@comcast.net> wrote in message
news:q-mdnewmMvkuh-jeRVn-tg@comcast.com...
> Have you tried running an additional IISReset? Have you checked your
> AppPools? Have you checked your virtual server against its app pool..
> look in the Documents folder on the bottom and you will see if your lined
> up with the App pool you specified during the initial setup.
>
> I do alot of work / testing in the realm you are having a problem with as
> I like to test my sites before i deploy to live.. Let me know if your
> still having an issue.
> --
> Bob Fox
> http://www.mycblog.com/blog/Foxhole/default.aspx
> "Chris Newby" <Chris.Newby@Rockcreekglobal.com> wrote in message
> news:e0tL7su5FHA.3432@TK2MSFTNGP10.phx.gbl...
>>I have a virtual installation of Server 2003 Web using Virtual PC 2004
>>with Office SharePoint Portal Server 2003 installed.
>>
>> I was able to setup (or extend) a local virtual server as a top level
>> site and point at an Sql 2000 installation on another machine. However,
>> after choosing a template (any template I have found) and browseing to
>> the default home of the top level site, I get the following error:
>> ===========================
>> An unexpected error has occurred.
>>
>> Web Parts Maintenance Page: If you have permission, you can use this page
>> to temporarily disable Web Parts or remove personal settings. For more
>> information, contact your site administrator.
>>
>>
>> Troubleshoot issues with Windows SharePoint Services.
>>
>> ===========================
>>
>> When I check the application event log I see the following two errors:
>>
>> "The safe mode service of Windows SharePoint Services has failed to
>> initialize because of an unknown error."
>>
>> Followed by:
>>
>> "Request failed."
>>
>>
>> I've tried messing with permissions, but everything more or less has
>> domain administrator access ... So as of now I'm going to rebuild the
>> virtual installation and see if I have any luck with that.
>>
>> Any ideas otherwise?
>>
>> TIA//
>>
>
>