Tuesday, November 24, 2009

Deploy Office Web apps on SharePoint 2010

Office Web Apps is the online companion to Word, Excel, PowerPoint and OneNote applications that allows users to access documents from virtually anywhere. Users can view, share, and work on documents with others online across personal computers, mobile phones, and the Web. Office Web Apps is available to users through Windows Live and to business customers with Microsoft Office 2010 volume licensing and document management solutions based on Microsoft SharePoint Server 2010.

To install Office Web Apps on your SharePoint Server 2010, read the following document for steps on how to deploy it. After deploying it to your SharePoint Server, users accessing your sites will be able to view, edit, and share documents from the web without the need to the Office client.


Other resources:

Integrated Windows Authentication with Claims Based Authentication in SharePoint 2010 error (IE)

Hi

In case you have a problem "signing as a different user" in SharePoint 2010 Web Application that uses "Claims Based Authentication" you will need to turn off the "Integrated Windows Authentication" option in Internet Explorer (As shown below). Without doing this, you wont be able to sign is as a different user.

This does not apply to other browsers and it is an IE issue.

Sunday, November 22, 2009

SharePoint Server 2010 Beta Key

In case you can’t find it on download page after registration page:

SharePoint Server 2010 Beta(Enterprise Client Access License features) product key:

PKXTJ-DCM9D-6MM3V-G86P8-MJ8CY

BV7VC-RMR6B-26P6Y-BTQDG-DX2KQ

Both keys can be used. Feel free to post it elsewhere!

Friday, November 20, 2009

Enabling Taxonomy features on a Site Collection created using "Blank Site" template

When you create a new site collection in SharePoint 2010 using the "Blank Site" or "STS#1" site template, the Taxonomy feature (and possibly other features) will not be activated by default. It appears that Microsoft does not staple any features in the farm with the blank site template. This means, there is no way to activate the Taxonomy features in a blank site using the SharePoint UI because the Taxonomy features are hidden.

To activate the features, run the following stsadm command from the command prompt to enable the feature

stsadm -o activatefeature -id "73EF14B1-13A9-416b-A9B5-ECECA2B0604C" -URL "http://siteurl/sitecollection"

This will enable the "TaxonomyFieldAdded" feature on the team site which should bring the "Term Store Management" link in the site administration section of a site. This will also enable you to add the Managed Metada column to your lists and content types.

On a side note, the following features are related to the taxonomy in SharePoint
TaxonomyFeatureStapler
TaxonomyFieldAdded
TaxonomyTenantAdminStapler
TaxonomyTenantAdmin
TaxonomyTimerJobs

All the above features are "hidden" which means that you can't enable them from the SharePoint UI

Wednesday, November 18, 2009

FileNotFoundException error when installing SharePoint 2010 Beta





On a Windows Server 2008 R2 installation which passed all the prerequisites, you might get the following error :


11/17/2009 16:39:32 9 ERR Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at Microsoft.SharePoint.Administration.SPFarm.CurrentUserIsAdministrator(Boolean allowContentApplicationAccess)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.DoesCurrentUserHaveWritePermission(SPPersistedObject persistedObject)
at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()
at Microsoft.SharePoint.Administration.SPFarm.Update()
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.RegisterDefaultDatabaseServices(SqlConnectionStringBuilder connectionString)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Provision(SqlConnectionStringBuilder connectionString)
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()WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


To resolve the problem you will need to download the following Geneva Framework version that had the required DLL.





Installing SharePoint 2010 Beta

Since SharePoint 2010 has been made available for MSDN/TechNet subscriber now, here’re some steps you would like to follow to get a successful installation. But keep in mind: This beta is not supported and you CANNOT upgrade the installation to RTM when it’s released. This Beta should only be used for evaluation purpose.


Follow these steps to install SharePoint Foundation 2010 and SharePoint Server 2010 Beta products. The process is split in two parts. The first part will install SharePoint Foundation 2010 Beta, and the second part will install SharePoint Server 2010 Beta. You can either install SharePoint Foundation 2010 or Start by installing SharePoint Server 2010.

before you start the installation, you will need the following pre-requisites

  • .Net Framework 3.5 with SP1 installed
  • Geneva Framework (Windows Identity Foundation) (download here)\
  • SQL Server 2005 SP3 and CU3 OR Server 2008 SP1 and CU2
  • Install WCF FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (Windows Server 2008, Windows Server 2008 R2 – link not activated yet) . Please note the 2008 fix also applies to Vista, while the 2008 R2 fix also applies to Windows 7.
    If you don't have this fix installed, you will get "Unrecognized attribute 'allowInsecureTransport'" error in ULS log. And most of the service applications will not run properly
  • Create a special AD account that will be used as the SharePoint Managed Account in your farm. Refer to step 3 of the following post for how to create this account.
After you have applied the fixes and updates
  • Run the pre-requisite tool for SharePoint foundation 2010
  • After installing the binaries, run the configuration wizard. Setup the farm using complete farm installation. Use standalone installation only on Windows 7/Vista for dev purposes.
  • Go to Central Administration and run the "Configuration Wizards" to setup the service applications. Use a special user for the SharePoint Managed Account for services and web applications in the farm
  • Enable Developer Dashboard and turn to OnDemand for troubleshooting page performance issues. It can be done by STSADM or SharePoint 2010 Management Shell (Windows PowerShell).
    STSADM: stsadm -o setproperty -pn developer-dashboard -pv OnDemand
    Windows PowerShell:
    $svc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService
    $ddsetting=$svc.DeveloperDashboardSettings
    $ddsetting.DisplayLevel=[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
    $ddsetting.Update()

After installing this, you will have SharePoint Foundation 2010/SharePoint Server 2010 installed.

External Links