I'm running SP 2007 and MOSS (12.0.0.6421) on a single-server Windows Server 03 machine. I'm trying to activate O-SP Publishing Infrastructure at the Site Collection level and receive the error: The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated. On the server, in Central Administration, it indicates I have O-SP Server Standard Web application features active for the Web Application, as well as all of the Web Applications on the server. Based upon searching earlier threads, I've tried changing the AppPool for the web application to the same one used by Central Administration, and that hasn't helped. Neither has trying to activate the feature using the STSADM command. Any ideas? Thanks.

Hi Jett, As there was no further information showed the root cause of the issue, I would like to provide some general actions that should helpful for your issue. 1. Clear the SharePoint configuration caches. To Clear SharePoint configuration caches, please follow the steps: 1) Stop Windows SharePoint Services Timer in Services. 2) On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, locate the configuration cache folder in %allusersprofile%\Application Data\Microsoft\SharePoint\Config\GUID 3) In Windows Server 2008, the configuration cache is in the following location: %allusersprofile%\Microsoft\SharePoint\Config\GUID 4) Back up the Cache.ini file. 5) Delete all the XML configuration files in the GUID folder. 6) Edit the Cache.ini file. Change the content to 1, and then click Save the changes. 7) Start Windows SharePoint Services Timer in Services. See KB 939308 (http://support.microsoft.com/kb/939308) for more detailed steps. 2. Re-active the features following the steps: 1) Deactivate the Office SharePoint Server Standard Web application features by click the Deactivate button in Central Administration > Application Management > Manage Web Application Features 2) Click deactivate this feature in the Warning page. 3) Activate the Office SharePoint Server Standard Web application features by click the Activate button in Central Administration > Application Management > Manage Web Application Features 3. Re-install the features following the steps: 1) Navigate to the %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin folder. 2) Run psconfig -cmd installfeatures command. See Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc263093.aspx) for more information. If these action plans are not helpful for your issue, could you please collect some logs to me for further research? 1. Error logged in the Event Viewer. 2. Information logged in ULS logs. Let me know the result if possible. -lambertLambert Qin | Microsoft Online Support Engineer How to ask a question in the forum (http://support.microsoft.com/kb/555375) Posting is provided "AS IS" with no warranties, and confers no rights.

Hi Lambert Qin, I'm having the same problem as the individual listed above. I'm trying to Create a Site Collection with a Collaboration Portal as the site template for my FIRST top-level site collection on this new installation -- and it throws the same error listed above. Here's the Event Log information that it throws: Log Name: Application Source: Office SharePoint Server Date: 8/1/2009 10:24:58 PM Event ID: 4965 Task Category: Publishing Provisioning Level: Error Keywords: Classic User: N/A Computer: hostname.domain.local Description: 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: 'System.InvalidOperationException: The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated. at Microsoft.SharePoint.Publishing.PublishingResourcesFeatureHandler.<>c__DisplayClass3.<FeatureActivated>b__1() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at Microsoft.SharePoint.Publishing.PublishingResourcesFeatureHandler.<>c__DisplayClass3.<FeatureActivated>b__0() at Microsoft.SharePoint.Publishing.CmsSecurityUtilities.RunWithWebCulture(SPWeb web, CodeToRun webCultureDependentCode) at Microsoft.SharePoint.Publishing.PublishingResourcesFeatureHandler.FeatureActivated(SPFeatureReceiverProperties receiverProperties) 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.SPFeatureCollection.Add(Guid featureId, Boolean force) at Microsoft.SharePoint.SPFeatureCollection.CheckSameScopeDependency(SPFeatureDefinition featdefDependant, SPFeatureDefinition featdefDependency, Boolean fActivateHidden, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependency(SPFeatureDefinition featdefDependant, SPFeatureDependency featdep, Boolean fActivateHidden, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependencies(Guid featidDependee, Boolean fActivateHidden, 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)' Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Office SharePoint Server" /> <EventID Qualifiers="0">4965</EventID> <Level>2</Level> <Task>217</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-08-02T03:24:58.000Z" /> <EventRecordID>1452</EventRecordID> <Channel>Application</Channel> <Computer>hostname.domain.local</Computer> <Security /> </System> <EventData> <Data>The site template was not provisioned successfully. Delete this site collection in Central Administration, and then create a new site collection.</Data> <Data>System.InvalidOperationException: The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated. at Microsoft.SharePoint.Publishing.PublishingResourcesFeatureHandler.&lt;&gt;c__DisplayClass3.&lt;FeatureActivated&gt;b__1() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) at Microsoft.SharePoint.SPSecurity.&lt;&gt;c__DisplayClass4.&lt;RunWithElevatedPrivileges&gt;b__2() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at Microsoft.SharePoint.Publishing.PublishingResourcesFeatureHandler.&lt;&gt;c__DisplayClass3.&lt;FeatureActivated&gt;b__0() at Microsoft.SharePoint.Publishing.CmsSecurityUtilities.RunWithWebCulture(SPWeb web, CodeToRun webCultureDependentCode) at Microsoft.SharePoint.Publishing.PublishingResourcesFeatureHandler.FeatureActivated(SPFeatureReceiverProperties receiverProperties) 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.SPFeatureCollection.Add(Guid featureId, Boolean force) at Microsoft.SharePoint.SPFeatureCollection.CheckSameScopeDependency(SPFeatureDefinition featdefDependant, SPFeatureDefinition featdefDependency, Boolean fActivateHidden, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependency(SPFeatureDefinition featdefDependant, SPFeatureDependency featdep, Boolean fActivateHidden, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependencies(Guid featidDependee, Boolean fActivateHidden, 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.&lt;&gt;c__DisplayClassa.&lt;EnsureFeaturesActivatedAtSite&gt;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[]&amp; userToken, Int32 nZone, Guid siteid, String sFeatures) at Microsoft.SharePoint.Library.SPRequestInternalClass.ApplyWebTemplate(String bstrUrl, String&amp; bstrWebTemplate, Int32&amp; plWebTemplateId) at Microsoft.SharePoint.Library.SPRequest.ApplyWebTemplate(String bstrUrl, String&amp; bstrWebTemplate, Int32&amp; plWebTemplateId) at Microsoft.SharePoint.SPWeb.ApplyWebTemplate(String strWebTemplate) at Microsoft.SharePoint.Publishing.PortalProvisioningProvider.CreatePortal(String xmlFile, SPWeb rootWeb)</Data> </EventData> </Event> I tried all the steps you listed above, but to no avail. Please Help!

I also am having this problem. I read the info in this thread a week or so ago and tried the proposed solutions and didn't get any successful results. I posted details in an MS discussion group (which now all over the place!). It is below. I also am providing part of my PSCDiagnostics log, similar to what is given in the previous thread. Except for the ability to activate the publishing feature, my MOSS installation runs fine. Any help would be great. Thanks in advance. I have an issue where either by a stand-alone MOSS SP2 installation or by manually attempting to activate the OSS Publishing Infrastructure feature, an error surfaces: "The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated." I am installing MOSS SP2 on WS 2008 SP2. In the standalone installation, I run setup.exe as a stand-alone installation. Then I run the configuration wizard and it halts at step 8, creating sample data. The log file gives the error above as the original exception. (In a successful stand-alone install, the publishing feature is activated during the process.) In a farm installation, no error is returned during the configuration wizard (which makes sense since the publishing feature is not activated during the process.), but the same error above is returned when you attempt to manually activate the Publishing Infrastructure feature. All four web application features show up as "Activated" in central admin. Deactivating and re-activating various features doesn't solve the problem, neither through central admin nor stsadm. I have run setup.exe in both stand-alone and farm installations with a MOSS SP2 slipstream. As a note, MOSS SP2 DOES show up as a windows installed update after running setup.exe. Now, if I run Windows Update after running setup.exe for a stand-alone install, Office Servers SP2 is provided as an update selection. Not sure why since it was just installed. If I choose to install the update, then run the configuration wizard, there is no error. Everything works fine, the Publishing feature activates manually too. But if I run Windows Update after running setup.exe for a farm install, the Office Servers SP2 update IS NOT a selection. If I instead run setup.exe against a MOSS SP1 slipstream for a farm install then run Windows Update, I STILL do not get MOSS SP2 as a selection. I'm thinking I should get SP2 as an update selection...that would be good since then I could install it and everything may work just fine, just as it does with the stand-alone install and an SP2 Windows Update update. In short: even though I would like to have this work in a farm installation, the error occurs with a simple "On a WS 2008 machine, run MOSS SP1 or MOSS SP2 setup.exe and then config wizard as a stand-alone install" and the error occurs.Part of my log file. Note: DEV\spadminis a member of the Administrators group on the local machine. 07/29/2009 12:05:17 8 INF The default site url is http://moss64/, port 80 07/29/2009 12:05:17 8 INF The owner account for the default site is DEV\spadmin 07/29/2009 12:05:18 8 INF The owner email for the default site is someone@example.com 07/29/2009 12:05:18 8 INF The db server for the default site is MOSS64\OfficeServers 07/29/2009 12:05:18 8 INF Calling SPGlobalAdmin.ExtendVirtualServer() 07/29/2009 12:05:42 8 INF SPGlobalAdmin.ExtendVirtualServer() succeeded. Now, creating the site using the SPSPORTAL template 07/29/2009 12:05:51 8 ERR Task evalprovision has failed with an unknown exception 07/29/2009 12:05:51 8 ERR Exception: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: The site template was not provisioned successfully. Delete this site collection in Central Administration, and then create a new site collection. OriginalException: The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated. ---> System.InvalidOperationException: The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated.Chris

Hello! I am experiencing the same problems mentioned in the above posts. Used MOSS 2007 SP2 CU June 2009 slipstream installation files unter Windows Server 2008 R2 RTM. Provisioning a collaboration portal or publishing portal results in the errors already mentionend in this thread. Provisioning a WSS team site works fine. Any solutions on this issue?

I have not heard anything since my last posting 3 weeks ago. I am hoping that this issue will be recognized and resolved.

Hi! I solved this one for me! Even though Central Adminstration displays version number 12.0.0.6510, Service Pack 2 and the Cummulative Update Package had NOT been applied correctly for the MOSS Parts (like the Collaboration Portal template). You can check whether this addresses your problem too by extracting the version number of Microsoft.SharePoint.Portal.dllin %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\ISAPI\ Right click the file, click properties and switch to the details tab. If the file version is something other than 12.0.6507.5000 (in my case it was RTM version 4518) do the following: Install the stand-alone Service Pack 2 for MOSS and the Cummulative Update Package again. Run the wizard. After that, it works fine. Investigation on this issue led me to the following theory: Whether slipstreamed Service Packs/CUs are applied correctly depends on whenthe IIS role is added under Windows Server 2008 and 2008 R2. If SharePoint Setup adds the role during setup, the service pack/CUs are NOT applied correctly. If you add the role yourself prior to SharePoint setup (setup adds required role services accordingly), they are applied correctly! Hope this helps.

That's exactly it. The solution is to install the Web Server Role through Server Manager before running SharePoint setup.exe. I verified it as well. I have been letting SharePoint create the web server role all this time. I've been troubleshooting this for a while and following the symptoms that pop up. For instance, installing .NET Framework from Server Manager resolved the problem, but installing .NET Framework from a downloaded package seemed to actually create the problem. But installing .NET Framework from Server Manager also installs the Web Server role. I was eventually going to get to testing in that area, but when you wrote your response I knew immediately that it was the resolution. You were diving into the cause rather than the symptoms. I saw the folowing error: Now, creating the site using the SPSPORTAL template 07/29/2009 12:05:51 8 ERRTask evalprovision has failed with an unknown exception 07/29/2009 12:05:51 8 ERRException: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: The site template was not provisioned successfully. But do not know how to proceed. I'm thinking that you did something like the following: you looked at the error from the config wizard, saw that there was a problem with one of the site provisions, knew which file(s) to look at further, compared the installed files to what was in the update list and saw a problem. What I'm getting at is it's clear that you have experience in the technical troubleshooting of SharePoint. I imagine it's more than just SharePoint itself in many cases. Here's what I've bookmarked over time, but really haven't used since I've been able to avoid technical troubleshooting at the level this particular issue seems to demand: Deploy software updates for Office SharePoint Server 2007 http://technet.microsoft.com/en-us/library/cc263467.aspx Office SharePoint Server 2007 video: Understanding and Deploying Hotfixes, Public Updates, and Service Packs http://www.microsoft.com/downloads/details.aspx?FamilyID=387cdef6-a807-4cf8-ae2c-16f0afccaf3c&DisplayLang=en Updates Resource Center for SharePoint Products and Technologies http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx Windows Server 2008 Resource Center for SharePoint Products and Technologies http://technet.microsoft.com/en-us/office/sharepointserver/bb735844.aspx How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007 http://support.microsoft.com/kb/944267 Passing along any of your valuable insight, resources and places to read further for gaining troublehooting experience would be greatly appreciated so I can start to resolve these issues the right way! AND THANKS FOR RESOLVING THIS ISSUE! Chris

Thanks :)this helped in my case as well.I re-installed Sharepoint and it worked all fineRegards,Anita

thanks Helge-ITaCS I got same problem while setting up on my vista home premium with SQL Server 2008 R2 CTP. I am able to resolve after installing MOSS 2007 SP2. even i did not install CU yet.Thanks,Brahma------------------------ Brahma http://vbrchowdary.info

Hi. I had the issue too. New Server 2008 R2 vm. Installed Sharepoint 2007 x64 with SP2 included (not manual slipstream) and let Sharepoint setup install the IIS role and got the same error "the office sharepoint server standard web application features must be activated at the web application level before this feature can be activated". File version of Microsoft.SharePoint.Portal.dll is 12.0.4518.1014. Re-applied SP2 and it worked :) Thanks :) Jason