I was lazy and decided to uninstall my Beta SharePoint, delete all of the databases, then re-install SharePoint 2010 RTM on my server.  Everything ran perfectly through the install until I ran the SharePoint Products Configuration Wizard and received the error shown below.

Task configdb has failed with an unknown exception
07/14/2010 10:39:47 8 ERR Exception: System.InvalidCastException: Unable to cast object of type ‘Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection’ to type ‘Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection’.
at Microsoft.SharePoint.Administration.SPIisWebServiceSettings.ProvisionWebSiteSettings()
at Microsoft.SharePoint.Administration.SPIisWebServiceInstance.Provision()
at Microsoft.SharePoint.Administration.SPFarm.Join()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Per the following technet post, there’s an issue with the version of the .NET 3.5 Geneva not properly updating. I believe this is due to the fact that my Windows 2008 R2 is actually 8 months old (from my SharePoint 2010):  http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/b123b76a-5c16-4611-879e-0cb14b1a638c

Open the web.config file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root and change the identityModel Version from 1.0.0.0 to 3.5.0.0

Delete your databases and then re-run the SharePoint products configuration wizard and it should now complete successfully.

Popularity: 1% [?]

Problem

SharePoint health analyzer states that the state service is  missing its databse.

Solution

Create the state server database by following the steps  below

1) Login to SharePoint farm member server under the credentials of a farm administrator

2) Open “SharePoint 2010 Management Shell (don’t just open PowerShell)

NOTE: If you receive the “The Local Farm is Not Accessible” error see the following article: http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredependencyid-are-not-registered/ 

3) Run the following command
PS C:\New-SPStateServiceDatabase

4) Verify that the problem has been resolved by clicking the “ReAnalyze Now” button

If the problem persists verify that the Secure Store Service has been started

Popularity: 1% [?]

Problem

You have a shiny new SharePoint 2010 environment and it’s running beautifully but you can’t create workflows.  Actually, some workflows that don’t have an InfoPath association screen do work, however, others, such as the 3 State Workflow don’t work. 

Figure 1 below shows the 2nd screen of the 3 state workflow which is actually an InfoPath form, if you get an error on this screen then follow the steps in the solution below.

Figure 1: InfoPath based 3 state approval workflow association screen

Solution

Firstly, before making any changes make test test test.  Do not make these changes in a production environment without testing first in staging or development.

If you can not configure forms services from central admin (General Application Settings) then follow the steps below to configure InfoPath forms services: (or see the following blog post: http://www.sharepointassist.com/2010/06/15/wheres-infopath-forms-services-in-sharepoint-2010/)

1) Login to a SharePoint farm member server as a user who is a farm admin

2) Open a command prompt

3) Run the following command
c:\program files\common files\Microsoft Shared\Web Server Extensions\14\bin\stsadm -o installfeature -name IPFSAdminWeb

* NOTE: There is no need to “activate” the feature, it’s scoped to activate in Central Admin as soon as you install. If you receive a message that the feature is already installed but you do not see the feature on the “General Application Settings” page in central admin, activate the feature on central administration using the following command.
c:\program files\common files\Microsoft Shared\Web Server Extensions\14\bin\stsadm -o activatefeature -name IPFSAdminWeb -url http://sharepoint:8080 (where 8080 is the central admin port)

Popularity: 1% [?]

Problem

I have noted that in both my lab and some client machines that InfoPath forms services is not available under general application settings in central admin.

It’s also not visible under "Manage Service Applications"

Solution

Manually activate the feature using stsadm:

1. Login to host with admin rights
2. Open command prompt (run as administrator)
3. Run the following command
   c:\program files\common files\Microsoft Shared\Web Server Extensions\14\bin\stsadm -o installfeature -name IPFSAdminWeb

1. No need to "activate" the feature, it’s scoped to activate in Central Admin as soon as you install. If you receive a message that the feature is already installed but you do not see the feature on the "General Application Settings" page in central admin, activate the feature on central administration using the following command.
   c:\program files\common files\Microsoft Shared\Web Server Extensions\14\bin\stsadm -o activatefeature -name IPFSAdminWeb -url http://sharepoint:8080

1. Login to Central Administration and click on General Application Settings and you will see InfoPath Forms Services

Notes

This is counterintuitive but the feature already exists on the server (look in the \TEMPLATE\Features\ directory, you’ll see it). For some reason Microsoft has made it hard to find, or possibly my clients have simple been installing the bits improperly.

Popularity: 1% [?]

This article is part 3 in a 4 part series that shows how I build my SharePoint 2010 development environment from the ground up.  In the previous series I built a Windows 2008 R2, configured the Active Directory Domain Services role, provisioned SharePoint service accounts, configured the IIS role, installed and configured SQL 2008, updated SQL, and configured a SQL Server alias.

Now that you’ve diligently followed all of the steps in Part 1 and Part 2 of this series, and taken snapshots along the way, you’re ready to install SharePoint 2010!

The first step is to download the latest SharePoint 2010 media from Microsoft (note that the link might change)
http://www.microsoft.com/downloads/details.aspx?FamilyID=77C30C6C-47FC-416D-88E7-8122534B3F37&displaylang=en

Warning- If you click on "Install SharePoint Server" before installing the prerequisites you will receive an warning similar to the one below, mainly requiring "Geneva" which is required for SharePoint 2010 "Claims Based Authentication".

Our warning also asked us to install "Geneva" and IIS which we can do using the "Install software prerequisites " button

If the installation fails make sure that your server has an internet connection because the installation of Geneva requires that the server download content

Restart the installation after provisioning an internet connection and the installation should succeed

You should have received the keys in an email from Microsoft (if you are installing a trial)

Always choose Server Farm!!!

You almost always always always always will want to run a “Complete” install.  If you are wondering why your computer has multiple SQL Server instances as well as SQL Express then most likely you ran a stand-alone installation in the past.

I like to configure my Central Administration port as 8080. 

Login to Central Admin as the user you were logged in as when you first ran the SharePoint Products and Technologies Wizard (this is contrary to what you might think as we would assume that we would login as the application pool account)

I always like to configure alternate access mappings immediately

Next we want to create our top level web application that will host our top level site collection

No search, failover, or service application have been created so we’ll leave the defaults for now

Now create a site collection

If you get repeated login attempts that fail and you’ve tried your admin and application pool accounts, you might be unable to browse SharePoint locally related with Kerberos and host headers, see my article Unable to Brows SharePoint Locally Or Search Fails To Index Content to resolve the problem.

In the next part of this series we install Visual Studio 2010 and build run a few sample development tasks.

Popularity: 16% [?]