Hi,I have applied the july infrastructure update for MOSS 2007.Now, I'm no longer able to create a collaborative portal, or, more specific, a report center collection or site.Everytime I try to create a site collection using the report center or collaborative template, I'm receiveing this error:The connection point "IFilterValues" on "g_dfa537ff_7804_4616_aaee_e04b333bce4b" is disabled.If I try to create a site using the report center template, I also receive the same error.any idea?The error log in the vent viewer is when I create a site collection: Event Type:ErrorEvent Source:Office SharePoint ServerEvent Category:Publishing Provisioning Event ID:4965Date:30/08/2008Time:11:51:22 AMUser:N/AComputer:SERVERDescription:Event log message was: 'The site template was not provisioned successfully. Delete this site collection in Central Administration, and then create a new site collection.'. Exception was: 'Microsoft.SharePoint.WebPartPages.WebPartPageUserException: The connection point "IFilterValues" on "g_12c1643e_945e_463f_a147_484a5cfbecef" is disabled. at Microsoft.SharePoint.WebPartPages.SPWebPartManager.CanSPConnectWebPartsCore(WebPart provider, ProviderConnectionPoint providerConnectionPoint, WebPart consumer, ConsumerConnectionPoint consumerConnectionPoint, WebPartTransformer transformer, Boolean throwOnError) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.SPConnectWebParts(WebPart provider, ProviderConnectionPoint providerConnectionPoint, WebPart consumer, ConsumerConnectionPoint consumerConnectionPoint, WebPartTransformer transformer) at Microsoft.SharePoint.WebPartPages.SPLimitedWebPartManager.SPConnectWebParts(WebPart provider, ProviderConnectionPoint providerConnectionPoint, WebPart consumer, ConsumerConnectionPoint consumerConnectionPoint, WebPartTransformer transformer) at Microsoft.SharePoint.Portal.ReportCenterSampleDataFeatureReceiver.ConnectFilterToEwr(SPLimitedWebPartManager wpManager, SPSlicerChoicesWebPart filter, ExcelWebRenderer ewr, String paramName, String workbookName) at Microsoft.SharePoint.Portal.ReportCenterSampleDataFeatureReceiver.CreateSampleDashboardWebParts(SPWeb parentWeb, SPFile dashboardFile, String kpiListUrl, String excelWorkbookUrl) at Microsoft.SharePoint.Portal.ReportCenterSampleDataFeatureReceiver.CreateSampleDashboard(SPWeb parentWeb, SPList reportsLibrary, SPFile sampleWorkbook) at Microsoft.SharePoint.Portal.ReportCenterSampleDataFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtWebInternal(SPWeb web, String sFeatures, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass7.<EnsureFeaturesActivatedAtWeb>b__6() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, CodeToRunElevated code) at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtWeb(Byte[]& userToken, Int32 nZone, Guid siteid, Guid webid, String sFeatures) at Microsoft.SharePoint.Library.SPRequestInternalClass.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId) at Microsoft.SharePoint.Library.SPRequest.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId) at Microsoft.SharePoint.SPWeb.ApplyWebTemplate(String strWebTemplate) at Microsoft.SharePoint.SPWeb.CreateWeb(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean bCreateUniqueSubweb, Boolean bConvertIfThere) at Microsoft.SharePoint.SPWeb.SPWebCollectionProvider.CreateWeb(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean bCreateUniqueSubweb, Boolean bConvertIfThere) at Microsoft.SharePoint.SPWebCollection.Add(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean useUniquePermissions, Boolean bConvertIfThere) at Microsoft.SharePoint.Portal.ReportCenterCreatorFeatureReceiver.CreateReportCenter(SPWeb parentWeb) at Microsoft.SharePoint.Portal.ReportCenterCreatorFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtSiteInternal(SPSite site, String sFeatures, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClassa.<EnsureFeaturesActivatedAtSite>b__9() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, CodeToRunElevated code) at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtSite(Byte[]& userToken, Int32 nZone, Guid siteid, String sFeatures) at Microsoft.SharePoint.Library.SPRequestInternalClass.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId) at Microsoft.SharePoint.Library.SPRequest.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId) at Microsoft.SharePoint.SPWeb.ApplyWebTemplate(String strWebTemplate) at Microsoft.SharePoint.Publishing.PortalProvisioningProvider.CreatePortal(String xmlFile, SPWeb rootWeb)' For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Are you running a farm? If so, how many servers?Also, when you installed the infrastructure update, how did you do it? Did you install the WSS first on all servers, then moss on all servers making sure NOT to run sharepoint config wizard, then once installed on all servers, run config wizard on the index server first, then all front ends?Do you notice any errors in the event log about the infrastructure update? anything stating it was successful or there were errors?

Hi, As your issue happened in publishing site, I suggest you to force an activation of the publishing template/features. Please follow the below mentioned commands one at a time on the SharePoint Server: stsadm -o activatefeature -filename \publishing\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishingresources\feature.xml -url http://URL -force stsadm -o activatefeature -filename \navigation\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishingSite\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishingweb\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishinglayouts\feature.xml -url http://URL -force The -url switch is optional, if you want to deploy these feature on a particular subsite or site then you use this switch. you can leave this switch if you intend to provision this feature across the farm. For more information about Activatefeature command, please refer to: Activatefeature: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288160.aspx) Hope the information can be helpful. -lambertPosting is provided "AS IS" with no warranties, and confers no rights.

Hi, As your issue happened in publishing site, I suggest you to force an activation of the publishing template/features. Please follow the below mentioned commands one at a time on the SharePoint Server: stsadm -o activatefeature -filename \publishing\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishingresources\feature.xml -url http://URL -force stsadm -o activatefeature -filename \navigation\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishingSite\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishingweb\feature.xml -url http://URL -force stsadm -o activatefeature -filename \publishinglayouts\feature.xml -url http://URL -force The -url switch is optional, if you want to deploy these feature on a particular subsite or site then you use this switch. you can leave this switch if you intend to provision this feature across the farm. For more information about Activatefeature command, please refer to: Activatefeature: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288160.aspx) Hope the information can be helpful. -lambertPosting is provided "AS IS" with no warranties, and confers no rights.

sorry,this doesn't solve the issue.I still not able to create a report center site.as well as creating a full new virtual server and applying the collaborative template.Jerome

I'm having the same issue without having applied the infrastructure update.Cannot create a "collaboration portal" site, I've drilled down to learn that it specifically fails to create the "Search Center"Farm Info64 Bit MOSS - 4 WFE's / 2 Excel / 1 Index/ 1 SQL ClusteredI've opened a ticket with MS, but I am getting no where. I was able to replicate this issue on 3 new environments. So either I'm not installing this correctly and some feature didnt activate @ the farm level.Event Log Message Eventlogmessagewas:'Failedtocompletelycreatethesubsite'http://w4.xxxx.xx.com/teams/Test/SearchCenter'.'.Exceptionwas:'Microsoft.SharePoint.SPException:Exceptionoccurred.(ExceptionfromHRESULT:0x80020009(DISP_E_EXCEPTION))--->System.Runtime.InteropServices.COMException(0x80020009):Exceptionoccurred.(ExceptionfromHRESULT:0x80020009(DISP_E_EXCEPTION)) atMicrosoft.SharePoint.Library.SPRequestInternalClass.ReleaseResources() atMicrosoft.SharePoint.Library.SPRequest.ReleaseResources() ---Endofinnerexceptionstacktrace--- atMicrosoft.SharePoint.Library.SPRequest.ReleaseResources() atMicrosoft.SharePoint.SPRequestManager.Release(SPRequestrequest) atMicrosoft.SharePoint.SPWeb.CreateWeb(StringstrWebUrl,StringstrTitle,StringstrDescription,UInt32nLCID,StringstrWebTemplate,BooleanbCreateUniqueSubweb,BooleanbConvertIfThere) atMicrosoft.SharePoint.SPWeb.SPWebCollectionProvider.CreateWeb(StringstrWebUrl,StringstrTitle,StringstrDescription,UInt32nLCID,StringstrWebTemplate,BooleanbCreateUniqueSubweb,BooleanbConvertIfThere) atMicrosoft.SharePoint.SPWebCollection.Add(StringstrWebUrl,StringstrTitle,StringstrDescription,UInt32nLCID,StringstrWebTemplate,BooleanuseUniquePermissions,BooleanbConvertIfThere) atMicrosoft.SharePoint.Publishing.PortalProvisioningProvider.CreateChildWebs(WebElementparentWebElement,SPWebparentWeb)'

set the value of callstack property to "false" and try.Please let me know when this gets resolved.

I was getting the same. Adding the Service account for the web application to local Administrator group solved the problem.