When i created a web app then created top site collection.Error occured the error information as below:
error:The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated.
After some searching I learned that MOSS SP2 was not correctly applied, re-installing MOSS SP2 solved the issue.But when i tried to re-install MOSS SP2,the message show that I have installed MOSS SP2.I cann't re-install it and uninstalled.I need to solve the error throught upgrade log file.(C:/Program Files/Common Files/Microsoft Shared/web server extensions/12/LOGS)
Then i checked the upgrade file, i found the error:
[SPManager] [ERROR] [12/28/2010 3:21:57 PM]: CanUpgrade [SPFarm Name=SharePoint_Config] failed.[SPManager] [ERROR] [12/28/2010 3:21:57 PM]: Value cannot be null.
I searced and then found the solusion here.
http://www.chaholl.com/archive/2009/08/10/connection-string-error-when-installing-moss-sp2.aspx
Connection String error when installing MOSS SP2
About 6 weeks ago I set about upgrading a few neglected dev servers to MOSS SP2, the process completed but reported errors similar to the following:
Event Type: Error Event Source: SharePoint Products and Technologies Configuration Wizard Event Category: None Event ID: 104 Date: 8/10/2009 Time: 1:49:23 PM User: N/A Computer: MYSERVERNAME Description: Failed to initiate the upgrade sequence. Failed to upgrade SharePoint Products and Technologies. Further information regarding this failure can be found at C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/LOGS/Upgrade.log. An exception of type System.ArgumentNullException was thrown. Additional exception information: Value cannot be null. Parameter name: connectionString System.ArgumentNullException: Value cannot be null. Parameter name: connectionString at Microsoft.SharePoint.Portal.Topology.SqlConnectionString..ctor(String connectionString) at Microsoft.SharePoint.Portal.Upgrade.Utility.GetV2ConfigurationDatabaseConnectionString() at Microsoft.SharePoint.Portal.Upgrade.FarmSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.Initialize() at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
Also, in the upgrade log file I found:
[SPManager] [DEBUG] [8/10/2009 1:49:18 PM]: Using cached [SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False. [FarmSequence] [DEBUG] [8/10/2009 1:49:19 PM]: Check to see if this is the child farm and the master has already been upgraded [SPManager] [ERROR] [8/10/2009 1:49:19 PM]: CanUpgrade [SPFarm Name=SharePoint_Config] failed. [SPManager] [ERROR] [8/10/2009 1:49:20 PM]: Value cannot be null. Parameter name: connectionString [SPManager] [ERROR] [8/10/2009 1:49:20 PM]: at Microsoft.SharePoint.Portal.Topology.SqlConnectionString..ctor(String connectionString) at Microsoft.SharePoint.Portal.Upgrade.Utility.GetV2ConfigurationDatabaseConnectionString() at Microsoft.SharePoint.Portal.Upgrade.FarmSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) [SPManager] [ERROR] [8/10/2009 1:49:20 PM]: SPManager.Initialize failed. [SPManager] [ERROR] [8/10/2009 1:49:21 PM]: Value cannot be null. Parameter name: connectionString [SPManager] [ERROR] [8/10/2009 1:49:21 PM]: at Microsoft.SharePoint.Portal.Topology.SqlConnectionString..ctor(String connectionString) at Microsoft.SharePoint.Portal.Upgrade.Utility.GetV2ConfigurationDatabaseConnectionString() at Microsoft.SharePoint.Portal.Upgrade.FarmSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
At the time I tried Googling the problem but never really got anywhere, it wasn’t important so I set it aside. It’s been annoying me ever since so today I decided to get to the bottom of it.
The registry holds the connection string information for the configuration database under:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Shared Tools/Web Server Extensions/12.0/Secure/ConfigDB in a string value called dsn
If you check this out you’ll see that it all looks correct. (BTW, messing with the registry can seriously ruin your evening, blah blah, standard disclaimer).
However, there is another key at:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Shared Tools/Web Server Extensions/Secure/ConfigDb
After some research, it seems that this key was used by WSS 2.0 to store the connection string for the configuration database so you’d be forgiven for thinking that it was ok that there was no value in here. Unfortunately some examination with RegMon reveals a different story!
In order to resolve the issue described, take the following steps:
Create a new string value called dsn under the HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Shared Tools/Web Server Extensions/Secure/ConfigDb keyCopy the value of the dsn node from HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Shared Tools/Web Server Extensions/12.0/Secure/ConfigDB into this new valueSpark up a command prompt and type: psconfig -cmd upgrade -inplace b2b -wait –forceJob done - as Hannibal famously said, “ I love it when a plan comes together”after run psconfig -cmd upgrade -inplace b2b -wait –force,i run into error:
[WebApplicationSequence] [ERROR] [2/9/2011 11:48:19 AM]: Action 12.0.4.0 of Microsoft.SharePoint.Portal.Upgrade.WebApplicationSequence failed.[WebApplicationSequence] [ERROR] [2/9/2011 11:48:19 AM]: Feature '20477d83-8bdb-414e-964b-080637f7d99b' is not installed in this farm, and can not be added to this scope.
Then I found the solusion under the link.
http://blog.answermyquery.com/2010/08/removedeactivate-a-missing-feature-for-a-cleaner-upgrade/
If you’re running across this blog it’s possible you’re missing a feature or working on upgrade.
There are multiple ways to detect missing features including the WssAnalyzeFeatures tool from MSDN and PreUpgradeCheck. Check out Gilham’s blog on removing missing features for more detail and tools.
Stsadm –o Preupgradecheck (Installed with SharePoint 2007 SP2)
In Features you’ll find the ID (GUID) and the word “missing”
Snippet from preupgrade check .htm report:
Name = [Unknown], Feature id = [bbe9def7-2fe9-a0b1-d712-aa128c837ebe], Reference count = [1], Scope = [Web], Status = [Missing]
If the site is still working as it should and you just want to clean things up you can remove the feature.
First you can uninstall the feature (it has to be there to uninstall it, we’ll see that in a second.)
C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/BIN>stsadm -help uninstallfeature
stsadm.exe -o uninstallfeature {-filename <relative path to Feature.xml> | -name <feature folder> | -id <feature Id>} [-force]
C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/BIN>stsadm -o uninstallfeature -id bbe9def7-2fe9-a0b1-d712-aa128c837ebe
Feature with Id 'bbe9def7-2fe9-a0b1-d712-aa128c837ebe' is not installed in this farm. The feature was not uninstalled. Looks like by doing a search, this feature is related to the community kit blog.
If the feature is not installed on the farm, and you want to force remove the feature you can run stsadm to deactivate the feature. More context to this error on William Wolfe’s blog.
C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/BIN>stsadm -help deactivatefeature
stsadm.exe -o deactivatefeature {-filename <relative path to Feature.xml> | -name <feature folder> | -id <feature Id>} [-url <url>] [-force]
C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/BIN>STSADM -o deactivatefeature -id bbe9def7-2fe9-a0b1-d712-aa128c837ebe
The feature with Id 'bbe9def7-2fe9-a0b1-d712-aa128c837ebe' is not currently installed. Use 'force' to deactivate it at this scope.
Let’s add the force parameter:
C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/BIN>STSADM -o deactivatefeature -id bbe9def7-2fe9-a0b1-d712-aa128c837ebe -force
Operation completed successfully.
Deactiviting this feature bbe9def7-2fe9-a0b1-d712-aa128c837ebe across all the web apps cleaned it up:
Now I’ll rerun preupgradecheck and see that features are now all installed. Our missing feature has been removed/deactivated (Dependency removed!).
FeatureInfo... Information Only – Now passed!
On an unrelated but related note, I’m seeing another missing feature of a different type… This one needs to be handled in a different way…
Re-running the upgrade I can still see it is missing a feature that’s not showing in preupgradecheck. The scope is on a specific web. I could pass in that web and try to deactivate it, so I’ll jump in the log to determine which database to look at.
[FeatureInfo] [DEBUG] [8/12/2010 1:31:07 PM]: Searching for features in content database wss_content_joel...[FeatureInfo] [DEBUG] [8/12/2010 1:31:07 PM]: Found 2 webs using feature definition 00bfea71-c796-4402-9f2f-0eb9a6e71b18 in content database wss_content_joel.[FeatureInfo] [DEBUG] [8/12/2010 1:31:07 PM]: Found 2 webs using feature definition 00bfea71-5932-4f9c-ad71-1557e5751100 in content database wss_content_joel.[FeatureInfo] [DEBUG] [8/12/2010 1:31:07 PM]: Found 2 webs using feature definition 00bfea71-a83e-497e-9ba0-7a5c597d0107 in content database wss_content_joel.[FeatureInfo] [DEBUG] [8/12/2010 1:31:07 PM]: Found 2 webs using feature definition 00bfea71-4ea5-48d4-a4ad-7ea5c011abe5 in content database wss_content_joel.[FeatureInfo] [DEBUG] [8/12/2010 1:31:08 PM]: Found 1 webs using feature definition fde5d850-671e-4143-950a-87b473922dc7 in content database wss_content_joel.[FeatureInfo] [DEBUG] [8/12/2010 1:31:08 PM]: Found 2 webs using feature definition 00bfea71-d1ce-42de-9c63-a44004ce0104 in content database wss_content_joel.[FeatureInfo] [DEBUG] [8/12/2010 1:31:08 PM]: Found 1 webs using missing feature definition bbe9def7-2fe9-a0b1-d712-aa128c837ebe in content database wss_content_joel.
Forcing the upgrade for SP2 still resulted in this error in the error log:
[SPManager] [ERROR] [8/12/2010 1:47:53 PM]: ReflexiveUpgrade [SPWebService Parent=SPFarm Name=SharePoint_Config] failed.[SPManager] [ERROR] [8/12/2010 1:47:53 PM]: Feature '20477d83-8bdb-414e-964b-080637f7d99b' is not installed in this farm, and can not be added to this scope.
This feature is a feature that should be on the farm and may have resulted from a WSS to MOSS conversion or db attach.
Total number of configuration settings run: 3Total number of successful configuration settings: 2Total number of unsuccessful configuration settings: 1Successfully stopped the configuration of SharePoint Products and Technologies.Configuration of SharePoint Products and Technologies failed. Configuration must be performed before you use SharePoint Products and Technologies. For further details, see the diagnostic log located at C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/LOGS/PSCDiagnostics_8_12_2010_13_56_13_669_1368454839.log and the application event log.
If you see this feature 20477d83-8bdb-414e-964b-080637f7d99b is missing and preventing your upgrade to SP2 or otherwise run the following:
First:
stsadm -o installfeature -name PublishingTimerJobs
Second:
stsadm.exe -o execadmsvcjobs
Finally:
psconfig -cmd upgrade -wait -inplace b2b
Total number of configuration settings run: 4Total number of successful configuration settings: 4Total number of unsuccessful configuration settings: 0Successfully stopped the configuration of SharePoint Products and Technologies.Configuration of the SharePoint Products and Technologies has succeeded.
And then I create Top site collection,the same error occured.
Activate the Office SharePoint Server Standard Web application features by click the Activate button in Central Administration > Application Management > Manage Web Application Features(SharePoint Web Application Management Section)
The problem is solved.
