v-sallyq
Mon Nov 27 00:44:05 CST 2006
------=_NextPart_0001_29C1D615
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hi there,
Thanks for posting here and sorry for the delay due to the weekend.
Now, let's go ahead with your issue. Based on your log, I find after
upgrading from WSS 2.0 to WSS 3.0, you cannot open the site with the error
code "0x80070005". If I am off base, please feel free to let me know.
Based on my research, I think we can check the following settings. Please
have a check:
Step 1: Check DCOM settings
-----------
1. In Component Services, drill down to 'My Computer.' Right click and
select 'properties', then select 'Default Properties' tab.
2. If 'Enable Distributed COM on this computer' was unchecked, checked it
and rebooted server.
Step 2: Repair .Net Framework 2.0
----------
1. Go to Add and Remove computer.
2. Choose .Net Framework 2.0 and choose repair installation.
Step 3: Check the IIS Settings
---------
1. Open IIS=>website=>right click on the web sites and click properties.
2. On the service tab uncheck Run WWW service in IIS 5.0 Isolation Mode.
3. Restarted IIS
Hope the steps help. In addition, I would like to share with you the
following article and hope they can provide some reference in the future.
WSS B2TR to RTM Upgrade -
http://technet2.microsoft.com/WindowsServer/f/?en/library/0af1c7a4-a054-40c3
-b495-71371bed4af81033.mspx
WSS v3 setup and administration,
http://technet2.microsoft.com/Office/en-us/library/396ee7ae-6dc6-4d48-8448-5
4a0033f39781033.mspx
Thanks for your efforts and have a great day!
Regards,
Sally Qiu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "mlai" <mlai@community.nospam>
References: <4AEEAA6E-BA9C-426B-A4AA-817DCED306C7@microsoft.com>
<OyEYbcKEHHA.1748@TK2MSFTNGP02.phx.gbl>
Subject: Re: Problem with one site after WSS2 -> WSS3 upgrade
Date: Sun, 26 Nov 2006 10:28:23 +0800
Lines: 86
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Response
Message-ID: <eM03MKQEHHA.1012@TK2MSFTNGP04.phx.gbl>
Newsgroups: microsoft.public.sharepoint.windowsservices
NNTP-Posting-Host: ip-202-60-233-092.cyberec.com 202.60.233.92
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.sharepoint.windowsservices:59403
X-Tomcat-NG: microsoft.public.sharepoint.windowsservices
Same but additional information on error on trying to export the site.....
There doesn't seem to be any response and reposting with my Technet
credentials....
Any insight into the problem, though?
"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:OyEYbcKEHHA.1748@TK2MSFTNGP02.phx.gbl...
> Is this the same problem that you talked about in two posts yesterday
with
> the title "Sharepoint site error when access after upgrade from wss2 to
> wss3" ?
>
> Or have you solved that and this is a new problem ?
>
> Mike Walsh
> WSS FAQ www.wssfaq.com / wss.collutions.com
>
> "mlai" <mlai@community.nospam> wrote in message
> news:4AEEAA6E-BA9C-426B-A4AA-817DCED306C7@microsoft.com...
>>I had 2 sites on WSS2 (WS2003 SP1 standalone) and just did the WSS3
>>inplace
>> upgrade. I ran into the Network Service unable to login error but
solved
>> it
>> according to Technet using psconfig.
>>
>> After the upgrade is complete, I am having problems with one of the
>> sites.
>> When I browse to the site, the page will respond with:
>>
>>
>> An unexpected error has occurred.
>>
>> Web Parts Maintenance Page: If you have permission, you can use this
page
>> to
>> temporarily close Web Parts or remove personal settings. For more
>> information, contact your site administrator.
>> Troubleshoot issues with Windows SharePoint Services.
>>
>> I had switched on logging and this is what is shown in the logs:
>>
>> 11/25/2006 10:36:27.44 w3wp.exe (0x12F4) 0x12C8
>> Windows SharePoint Services General 8e2s Medium
>> Unknown SPRequest error occurred. More information: 0x80070005
>>
>> I can find nothing on this error but 0x80070005 seems to indicate a
>> permission problem somewhere........
>>
>> Next I proceed to try exporting the site hoping to import it to a brand
>> new
>> site using stsadm -o export -url <URL>
>>
>> And I have another error in the log file:
>>
>> [11/25/2006 5:39:30 PM]: FatalError: User cannot be found.
>> at Microsoft.SharePoint.SPUserCollection.GetByID(Int32 id)
>> at Microsoft.SharePoint.SPWeb.get_Author()
>> at
>>
Microsoft.SharePoint.Deployment.WebSerializer.GetDataFromObjectModel(Object
>> obj, SerializationInfo info, StreamingContext context)
>> at
>>
Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectDa
ta(Object
>> obj, SerializationInfo info, StreamingContext context)
>> at Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object
>> obj, ISerializationSurrogate surrogate, String elementName, Boolean
>> bNeedEnvelope)
>> at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream
>> serializationStream, Object topLevelObject)
>> at
>>
Microsoft.SharePoint.Deployment.ObjectSerializer.Serialize(DeploymentObject
>> deployObject, Stream serializationStream)
>> at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()
>> at Microsoft.SharePoint.Deployment.SPExport.Run()
>>
>> And the export failed.
>>
>> Will somebody be so kind as to give me a hand and shed some light in
>> this?
>> I can't find anything on technet or internet regarding this.........
>>
>> Please help.......
>>
>
>
------=_NextPart_0001_29C1D615
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi there,
\par
\par Thanks for posting here and sorry for the delay due to the weekend.
\par
\par Now, let's go ahead with your issue. Based on your log, I find after upgrading from WSS 2.0 to WSS 3.0, you cannot open the site with the error code "0x80070005". If I am off base, please feel free to let me know.
\par
\par Based on my research, I think we can check the following settings. Please have a check:
\par
\par Step 1: Check DCOM settings
\par -----------
\par 1. In Component Services, drill down to 'My Computer.' Right click and select 'properties', then select 'Default Properties' tab.
\par
\par 2. If 'Enable Distributed COM on this computer' was unchecked, checked it and rebooted server.
\par
\par Step 2: Repair .Net Framework 2.0
\par ----------
\par 1. Go to Add and Remove computer.
\par 2. Choose .Net Framework 2.0 and choose repair installation.
\par
\par Step 3: Check the IIS Settings
\par ---------
\par 1. Open IIS=>website=>right click on the web sites and click properties.
\par 2. On the service tab uncheck Run WWW service in IIS 5.0 Isolation Mode.
\par 3. Restarted IIS
\par
\par Hope the steps help. In addition, I would like to share with you the following article and hope they can provide some reference in the future.
\par
\par WSS B2TR to RTM Upgrade -
http://technet2.microsoft.com/WindowsServer/f/?en/library/0af1c7a4-a054-40c3-b495-71371bed4af81033.mspx
\par
\par WSS v3 setup and administration,
http://technet2.microsoft.com/Office/en-us/library/396ee7ae-6dc6-4d48-8448-54a0033f39781033.mspx
\par
\par Thanks for your efforts and have a great day!
\par
\par Regards,
\par
\par Sally Qiu
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par \pard\li720 --------------------
\par From: "mlai" <mlai@community.nospam>
\par References: <4AEEAA6E-BA9C-426B-A4AA-817DCED306C7@microsoft.com> <OyEYbcKEHHA.1748@TK2MSFTNGP02.phx.gbl>
\par Subject: Re: Problem with one site after WSS2 -> WSS3 upgrade
\par Date: Sun, 26 Nov 2006 10:28:23 +0800
\par Lines: 86
\par X-Priority: 3
\par X-MSMail-Priority: Normal
\par X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
\par X-RFC2646: Format=Flowed; Response
\par Message-ID: <eM03MKQEHHA.1012@TK2MSFTNGP04.phx.gbl>
\par Newsgroups: microsoft.public.sharepoint.windowsservices
\par NNTP-Posting-Host: ip-202-60-233-092.cyberec.com 202.60.233.92
\par Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
\par Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sharepoint.windowsservices:59403
\par X-Tomcat-NG: microsoft.public.sharepoint.windowsservices
\par
\par Same but additional information on error on trying to export the site.....
\par There doesn't seem to be any response and reposting with my Technet
\par credentials....
\par
\par Any insight into the problem, though?
\par
\par
\par "Mike Walsh" <englantilainen@hotmail.com> wrote in message
\par news:OyEYbcKEHHA.1748@TK2MSFTNGP02.phx.gbl...
\par > Is this the same problem that you talked about in two posts yesterday with
\par > the title "Sharepoint site error when access after upgrade from wss2 to
\par > wss3" ?
\par >
\par > Or have you solved that and this is a new problem ?
\par >
\par > Mike Walsh
\par > WSS FAQ www.wssfaq.com / wss.collutions.com
\par >
\par > "mlai" <mlai@community.nospam> wrote in message
\par > news:4AEEAA6E-BA9C-426B-A4AA-817DCED306C7@microsoft.com...
\par >>I had 2 sites on WSS2 (WS2003 SP1 standalone) and just did the WSS3
\par >>inplace
\par >> upgrade. I ran into the Network Service unable to login error but solved
\par >> it
\par >> according to Technet using psconfig.
\par >>
\par >> After the upgrade is complete, I am having problems with one of the
\par >> sites.
\par >> When I browse to the site, the page will respond with:
\par >>
\par >>
\par >> An unexpected error has occurred.
\par >>
\par >> Web Parts Maintenance Page: If you have permission, you can use this page
\par >> to
\par >> temporarily close Web Parts or remove personal settings. For more
\par >> information, contact your site administrator.
\par >> Troubleshoot issues with Windows SharePoint Services.
\par >>
\par >> I had switched on logging and this is what is shown in the logs:
\par >>
\par >> 11/25/2006 10:36:27.44 w3wp.exe (0x12F4) 0x12C8
\par >> Windows SharePoint Services General 8e2s Medium
\par >> Unknown SPRequest error occurred. More information: 0x80070005
\par >>
\par >> I can find nothing on this error but 0x80070005 seems to indicate a
\par >> permission problem somewhere........
\par >>
\par >> Next I proceed to try exporting the site hoping to import it to a brand
\par >> new
\par >> site using stsadm -o export -url <URL>
\par >>
\par >> And I have another error in the log file:
\par >>
\par >> [11/25/2006 5:39:30 PM]: FatalError: User cannot be found.
\par >> at Microsoft.SharePoint.SPUserCollection.GetByID(Int32 id)
\par >> at Microsoft.SharePoint.SPWeb.get_Author()
\par >> at
\par >> Microsoft.SharePoint.Deployment.WebSerializer.GetDataFromObjectModel(Object
\par >> obj, SerializationInfo info, StreamingContext context)
\par >> at
\par >> Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectData(Object
\par >> obj, SerializationInfo info, StreamingContext context)
\par >> at Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object
\par >> obj, ISerializationSurrogate surrogate, String elementName, Boolean
\par >> bNeedEnvelope)
\par >> at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream
\par >> serializationStream, Object topLevelObject)
\par >> at
\par >> Microsoft.SharePoint.Deployment.ObjectSerializer.Serialize(DeploymentObject
\par >> deployObject, Stream serializationStream)
\par >> at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()
\par >> at Microsoft.SharePoint.Deployment.SPExport.Run()
\par >>
\par >> And the export failed.
\par >>
\par >> Will somebody be so kind as to give me a hand and shed some light in
\par >> this?
\par >> I can't find anything on technet or internet regarding this.........
\par >>
\par >> Please help.......
\par >>
\par >
\par >
\par
\par
\par \pard
\par
\par }
------=_NextPart_0001_29C1D615--