Archive for November, 2009

Failover Database Support in SharePoint 2010

November 30th, 2009 Comments off

In SharePoint 2010 there are some high availability improvements. One of the major option is proper database mirroring support.
 There is now an option for a Failover Database Server. You can define a database name for every content database. This effectively allows SharePoint 2010 will automatically be aware of database mirroring. If the primary SQL server dies, SharePoint will automatically re-connect to the failover database.
For example you have content database SQLDB1 and failover database SQLDB2. By default SharePoint will communicate with SQLDB1. But in case SQLDB1 dies or SharePoint unable to communicate with SQLDB1 it will automatically retry connection to failover database and start communication with SQLDB2. SQLDB2 is a mirror to the SQLDB1. The default timeout to connect to failover database is 15 seconds. It will retry automatically, so you have no need to worry about any manual process to change the database.
Here is the image, that how you define failover database when creating new web application.
Failover Database


Have fun.

SharePoint 2010 – allowInsecureTransport error

November 27th, 2009 Comments off

Today, when I have installed SharePoint 2010 on my other machine with windows server 2008 R2. It gave me a new error for ‘Unrecognized attribute ‘allowInsecureTrasnport’. The exception was the same as UserProfileException. It was really frustrated. But when I start looking for the solution, I found that people who using Windows 7 and Windows Server 2008 R2 are getting the same error. The error screen would be like this.

allowInsecureTransport Error

I dig down a little bit and found the error location. It was coming from the same clinet.config file. There are different suggestions for solution. Some people remove the ‘allowInsecureTrasnport’ attribute from the client.config file. But this created some other problems for some guys, like people are saying that after these changes configuration wizard run successful but now search is not returning anything. So it’s better to not to change the client.config file in this case.


Now Microsoft has launched a hotfix for it, you can download it from this link (Download). There are options for 64 bit operation system as well. I downloaded the 64 bit file and install it. And the problem was solved.


Claims based authentication in SharePoint 2010

November 25th, 2009 1 comment

SharePoint Server 2010 is a claims aware application. It incorporates a new, more powerful and flexible authentication model that works with any corporate identity system, including Active Directory directory services, LDAP-based directories, application-specific databases, and new user-centric identity models such as LiveID. This model uses claims-based authentication and a new product, code-named “Geneva”.

Claim based authentication is very simple and make application development simple, because application based on claim based authentication do not need to verify all the credentials. Someone who determines your company’s security policy can make those rules and buy or build the issuer. Your application simply receives the equivalent of a boarding pass. No matter what authentication protocol was used, Kerberos, SSL, forms authentication, or something more exotic, the application gets a signed set of claims that has information it needs about the user. This information is in a simple format that the application can use right away.

The purpose is to make SharePoint authentication simple for all the users. You can still use windows authentication but this is something extra. Microsoft wants to make SharePoint useful to its customers, not spend a lot of time integrating with each and every identity system one-by-one, or worse not do it. It will make simpler user experience and fewer passwords.

Here are some of the resources, I found useful.

Claim Based Authentication – MSDN
A Guide to Claim-based Identity
Exploring Claims-Based Identity

Run Configuration Wizard – SharePoint 2010 Beta 2

November 19th, 2009 Comments off

When you completed your installations for SharePoint 2010, you can run start configuration wizard straight away or later from the Start -> All Programs -> Microsoft SharePoint 2010 Products -> SharePoint 2010 Products Configuration Wizard.

Step 1


Click Next and choose yes for below popup.

Step 1 Confirmation Popup


SharePoint Configuration Steps


After this screen if you see any error like this “Microsoft.Office.Server.UserProfiles.UserProfileException: The request channel timed out while waiting for a reply after 00:00:19.9340000. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. —> System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:19.9340000. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding..  Just do check my this post for solution. Click here

Here is the success screen you will see if all goes well.

Configuration Wizard Success Message


Have fun :)

SharePoint 2010 – UserProfile Channel timed out error

November 19th, 2009 8 comments

Recently when I have installed SharePoint 2010 Beta 2 and run the configuration wizard, it ended with an error message. It was definitely very irritating message. There was exception in Microsoft.Office.Server.UserProfiles.UserProfileException for the request channel timed out.

Channel time out exception


After doing some research on it finally I found the solution for it. It was giving exception for timeout in UserProfiles service. For this you need to increase the timeout for UserProfile service. Open this file “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config”. One thing to remember is that now 12 hive is gone, now it’s 14 hive. You will see the file like this.



Here you can see that timeout is set to 20 sec only for ProfileServiceHttpsBinding. I just changed it to 50 seconds and rerun the configuration wizard.

client.config timeout changed


It was successful after that.


Install SharePoint 2010 Beta 2

November 18th, 2009 2 comments

SharePoint 2010 is on it’s way and it’s making the people crazy about it. Success of SharePoint 2007 has changed the whole concept of early SharePoint idea and now it is the most demanding technology for web.

SharePoint 2010 Beta 2 is available now to download. I have tried my part to give others help in installing new SharePoitn 2010 on their machines.

For this installation I have created a new VM on my hyper-v and installed Windows Server 2008 SP1 on it. I still don’t trust SP2. But you can try on Windows Server 2008 SP2. Then I installed SQL Server 2008 and SQL Server 2008 SP1. After that I have also installed Microsoft Office 2010 Beta 2. But you can ignore it if not required.

You need to do two things before the installations as prerequisites, but not done by SharePoint prerequisites installer.

  • Remove PowerShell from Windows Server 2008 features (You can see my other blog for it, Click here
  • You need to install KB971831, (See this blog for it, Click here)

So now it’s the time for SharePoint 2010 Beta 2, which is much better and quicker than Beta 1. Here are the snapshots of step by step installation.

First step

 There are few links on first screen pointing to the installation guide and upgrade guide. Now click on the Install software prereuisites. So it will start instllation.

Step 3

On this screen it will show you the list of all the programs it’s going to install or configure as prerequisites for SharePoint 2010.

Step 4

Just click ‘Next’

Step 5

Displaying the installation status bar. 

Success message

After above steps, you will see this success message for installation completion for prerequisites.

Now click on the Install SharePoint Server. You will see this screen in start for key.

SharePoint 2010 Key

Here you will give your key fro the product. There are different editions for SharePoint 2010. For intranet scenario (Enterprise Client Access License and Standard Client Access License) and internet/extranet scenario (Standard and Enterprise). I have used the key for second option with enterprise editions.

SharePoint 2010 Installation


Just select accept and continue.

Choose configuration


I have selected standalone. It depends on your installation scenario.

SharePoint 2010 Installation


After this installation status bar screen, you will see the last screen.

SharePoint Installation Sucess Message


That’s all done. Your installation for SharePoint 2010 Beta 2 is done. You can start configuration wizard now or later from the Start -> All Programs -> Microsoft SharePoint 2010 Products -> SharePoint 2010 Products Configuration Wizard.

Categories: SharePoint 2010 Tags:

SharePoint 2010 Installation – PowerShell Error

November 18th, 2009 Comments off

While you are installaing SharePoint 2010 prerequisites and you see an error screen saying that cannot install PowerShell V2 (CTP3).

PowerShell Error Screen


It’s pretty common. Before installation you need to remove PowerShell feature from Windows Server 2008 features. Just open Server Manager and select Remove Features and select PowerShell. Thats all. Now you can start your installation.


SharePoint 2010 KB971831 error

November 18th, 2009 1 comment

While your installation for SharePoint 2010, you see this error screen about KB971831.

KB971831 Error Screen

There is nothing really to worry, actually it’s a prerequisites for SharePoint 2010. You can download this KB item from this Download link. And then choose the appropriate version for your operating system. There is option for 64 bit operating system as well. The one I used for my Windows Server 2008.

Use Custom CSS in MOSS RadEditor

November 17th, 2009 Comments off

Telerik’s MOSS RadEditor is a great editor, especially if you are concerned about accessible html outputs. If you are using MOSS RadEditor, you might notice that it doesn’t pick your custom styles at edit time. Reason is by default it uses this style file “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources\RadEditorSharePoint\\RadControls\Editor\Skins\Default2006\EditorContentArea.css”. You have two options one you can edit this file and add your style here.

Second option is that you can set the css file by using the property “CssFiles” in ConfigFile.xml or ListConfigFile.xml depends on your configuration. For example you are deploying your CSS files in below folder structure under layouts folder.


your entry in config files will be like this.

<property name=CssFiles><item>/_LAYOUTS/MyWebFiles/css/editor_style.css</item></property>


Categories: MOSS Tags: , , ,

SharePoint 2010 will be 64 bit only

November 4th, 2009 1 comment

Yes it’s true that SharePoint 2010 will be 64 bit only. With all the advancements in technology it’s not suitable to use such big server products on 32 bits machines. Considering the performance factor in future Microsoft is laucnhing SharePoint 2010 only for 64 bit.

These are the preliminary system requirements for SharePoint 2010.

  • SharePoint Server 2010 will be 64-bit only.
  • SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
  • SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
  • Microsft has already recommended use SharePoint 2007 on 64 bit machine as a best practice. Microsoft responded like this on choosing SQL Server 64 bit “This decision was based on our current test data for SharePoint Server 2010 and real world experience from customers running SharePoint Server 2007 with 32-bit SQL Server.  SharePoint performance and scalability can benefit significantly from 64-bit SQL Server and the throughput increases are significant enough for us to make the difficult decision to only support SharePoint Server 2010 on 64-bit SQL Server 2005 or 2008.  It has been our strong recommendation for some time that SharePoint Server 2007 customers take advantage of 64-bit SQL Server due to the inherent performance and scale benefits it can provide.”

    For more information SharePoint 2010 Team Blog