RE: MOSS 2007 / TopAnswer.webpart

2011-03-17 Thread Daniel Brown
Hi Nigel,

 

That's for the info, the whole concept of WSS /SPF  MOSS/SP2010 patches
really is silly I think, to have to install them both separately vs. just a
single package is a thorn L

 

Will continue to look into this and post back, ill double check that the
right media was used  supplied and see what I can dig up J

 

Cheers,

 

DB

 

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf
Of Nigel Hertz
Sent: Thursday, 17 March 2011 3:13 PM
To: ozMOSS
Subject: RE: MOSS 2007 / TopAnswer.webpart

 

I used the Feb 2010 CU for most of last year, and never had any such issues
(we also rebuilt a dev server during that time, and applied the same CU) I
think the google article is possibly referring to the fact that the WSS
updates must be applied before the MOSS updates (i.e. WSS SP2 then MOSS SP2
then WSS CU then MOSS CU)

 

Looking at MSDN and Technet, I found this which may be relevant:

http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/8
ea9b475-2b68-4180-8424-072195e167e7

http://social.technet.microsoft.com/Forums/en/sharepointadmin/thread/6cbc827
6-bd7e-4f81-acc2-f8da22ace432

 

 

 

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf
Of Daniel Brown
Sent: Thursday, 17 March 2011 11:52 AM
To: ozmoss@ozmoss.com
Subject: MOSS 2007 / TopAnswer.webpart

 

Howdy all,

 

Doing an install of MOSS 2007 SP2+Feb2010 CU and when provisioning the My
Site collection, SharePoint is coming back with

 

The IIS Web Site was extended with Windows SharePoint Services, but the
following error occurs in creating the default site
http://my.contoso.lan/;. Please correct the input and try to create the
default site again. Error: Failed to instantiate file TopAnswer.webpart
from module WebPartPopulation: Source path dwp\TopAnswer.webpart not
found.

 

Google is telling me it is to do with MOSS 2007 SP2 not being applied while
WSS SP2 is only applied, however have applied everything possible and still
getting this problem.

 

Has anyone else seen this or fixed it?

 

Could it be a Feb 2010 CU problem?

 

Cheers,

 

Daniel

 



  _  



Stockland Notice: If this communication has been sent to you by mistake,
please delete and notify us.  If it has been sent to you by mistake, legal
privilege is not waived or lost and you are not entitled to use it in any
way. Stockland and its subsidiaries reserve the right to monitor e-mail
communication through its networks.

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: MOSS 2007 / TopAnswer.webpart

2011-03-16 Thread Nigel Hertz
I used the Feb 2010 CU for most of last year, and never had any such issues (we 
also rebuilt a dev server during that time, and applied the same CU) I think 
the google article is possibly referring to the fact that the WSS updates must 
be applied before the MOSS updates (i.e. WSS SP2 then MOSS SP2 then WSS CU then 
MOSS CU)

Looking at MSDN and Technet, I found this which may be relevant:
http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/8ea9b475-2b68-4180-8424-072195e167e7
http://social.technet.microsoft.com/Forums/en/sharepointadmin/thread/6cbc8276-bd7e-4f81-acc2-f8da22ace432



From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Daniel Brown
Sent: Thursday, 17 March 2011 11:52 AM
To: ozmoss@ozmoss.com
Subject: MOSS 2007 / TopAnswer.webpart

Howdy all,

Doing an install of MOSS 2007 SP2+Feb2010 CU and when provisioning the My Site 
collection, SharePoint is coming back with

The IIS Web Site was extended with Windows SharePoint Services, but the 
following error occurs in creating the default site http://my.contoso.lan/;. 
Please correct the input and try to create the default site again. Error: 
Failed to instantiate file TopAnswer.webpart from module WebPartPopulation: 
Source path dwp\TopAnswer.webpart not found.

Google is telling me it is to do with MOSS 2007 SP2 not being applied while WSS 
SP2 is only applied, however have applied everything possible and still getting 
this problem.

Has anyone else seen this or fixed it?

Could it be a Feb 2010 CU problem?

Cheers,

Daniel


_

Stockland Notice: If this communication has been sent to you by mistake, please 
delete and notify us.  If it has been sent to you by mistake, legal privilege 
is not waived or lost and you are not entitled to use it in any way. Stockland 
and its subsidiaries reserve the right to monitor e-mail communication through 
its networks.
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss