
5. Click "Change settings that are currently unavailable" option from the left (if it appears).

$farm = Get-SPFarm
$farm.BuildVersion
"SharePoint 2010 offers a suite of new and enhanced capabilities, which if utilised effectively in select business scenarios can bring enormous value to organisations. Document Management is one area where SharePoint 2010 offers many new features and benefits. This session covers two new document management capabilities: The Content Type Hub and Managed Metadata. Douglas will walk through the anatomy of Content Type Hubs and Managed Metadata, recommended approaches, constraints and how to best work around these constraints. A number of typical document management scenarios will be used throughout the session to demonstrate the concepts and keep it real. If time permits, he will also share some C# code snippets which support the scenarios described."For more information:
Failed to create the configuration database.Matching Error in the installation logs was:
An exception of type System.Collections.Generic.KeyNotFoundException was thrown. Additional exception information: The given key was not present in the dictionary.
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
04/14/2011 10:51:06 9 ERR Task configdb has failed with an unknown exception
04/14/2011 10:51:06 9 ERR Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException() at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Microsoft.SharePoint.Utilities.SPUtility.GetUserPropertyFromAD(SPWebApplication webApplicaiton, String loginName, String propertyName)
at Microsoft.SharePoint.Administration.SPManagedAccount.GetUserAccountControl(String username) at Microsoft.SharePoint.Administration.SPManagedAccount.Update() at Microsoft.SharePoint.Administration.SPProcessIdentity.Update() at Microsoft.SharePoint.Administration.SPApplicationPool.Update() at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, SPProcessAccount processAccount, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures) at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, IdentityType identityType, String applicationPoolUsername, SecureString applicationPoolPassword, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures) at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance(SqlConnectionStringBuilder administrationContentDatabase, SPWebService adminService, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.CreateAdministrationWebService(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.CreateBasicServices(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword, SecureString masterPassphrase) at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, String farmUser, SecureString farmPassword, SecureString masterPassphrase) at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
I’m running Windows 7 on a Dell Latitude E4300 4GB RAM with SharePoint Server 2010 installed for development and demo purposes. In the beginning SharePoint was running with an acceptable performance, but sometimes there would be a little wait here and there.
A few days ago Microsoft released an update for SharePoint Foundations 2010, which it claimed would improve stability and performance.
Guess what? After it was installed, I browsed my SharePoint sites using Chrome – man, it was lightning fast! Was it Chrome? Don’t think so. Same quick response in Internet Explorer 8! The performance is noticeably MUCH quicker. Great job guys!
This is the patch I installed:
Update for Office SharePoint Foundations 2010 (KB2032588)
“Microsoft has released an update for Office SharePoint Foundation 2010, 64-bit Edition. This update provides the latest fixes to Microsoft WSS 2010, 64-bit Edition. Additionally, this update contains stability and performance improvements.”
I was installing SharePoint 2010 – wait, what about the pre-requisites?
- SQL 2005 SP3 with Cumulative update package 3
- OR SQL 2008 SP1 with Cumulative update package 2
So what version have we got? Here’s the tip of the day (for me and to you to share), run this SQL Query to find out:
SELECT serverproperty('productversion'),
serverproperty('productlevel'),
serverproperty('edition')
This should give you information to determine the version number, the release level (RTM or Service Pack), and the edition (Express, Standard or Enterprise).
For convenience, I’ve added the version numbers required for SharePoint 2010:
- SQL 2005 SP3 - 2005.90.4035
- SQL 2008 SP1 – 2007.100.2531.0
For more version numbers go to http://support.microsoft.com/kb/321185.
Referenced from this Microsoft KB http://support.microsoft.com/kb/321185
For a few years now, I’ve been coding on .NET, SharePoint, and the like. I went to University and learnt about Object Orientation. I hardly noticed nor appreciated the many OOP concepts that I’ve unconsciously applied to my coding/solution design. Dare I say it, I think this may describe many developers with around 2-4 years of coding experience up their belts.
I recently started reading a few articles online and came to realisation of the extent to the level of OOP concepts that have actually been applied. It made more sense why some of solutions worked better than others (of which include both .NET and SharePoint solutions).
Like many others, I’ve just had the time to understand and learn how to use API’s and/or how to ‘structure’ code to get the job done in the least amount of time with the best quality (least amount of bugs), but never to understand some software architecture concepts. Take my tip, re-learn the concepts that reflect what you already know – a design pattern.
Here are the links I have referred to:
I just read an official note that there will be new four SharePoint 2010 certifications – and they are not specific to either SharePoint Foundation 4 or SharePoint Server 2010.
These exams are:
According to this blog post, the exams are expected to be available in June/July timeframe. More details here.
The Problem
I recently had to develop an Event Receiver that would require reading off the SPUser object of the item. What I found is that, at times when the exact name of the user is entered (and you click OK on the NewForm.aspx page without clicking the check name button), the SPFieldUserValue will return
–1;#domain\username
rather than
This is a problem when you try to access the SPFieldUserValue.User (SPUser type) property and it returns null.
The Solution
The solution was to get the SPFieldUserValue as a string, and then use the username to then try and resolve for the SPUser object. My rough cut out code is attached – quickly modified for this example. (*Use at your own risk. Is also why I don’t usually post code on my blog!)