By the way...

http://technet.microsoft.com/en-us/library/ee890108.aspx

Developer dashboard is not only for Developers, the administrators can also take good advantage of it. They can do quantitative analysis if their site is slow then how much slow and when the users started raising complaints. There are three in which this DD can remain: 1. OFF (which is by default) 2. ON - which turns it on all the time. It is generally not a good option as it causes performance overhead and turning it on would make all the Site Collection Admins to see it. 3. On Demand – It appears like a small button and site collection admins can turn it on any time they want. This is most feasible option. To set it to OnDemand, execute following powershell cmdlets: $dd = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings $dd.DisplayLevel = ‘OnDemand’ $dd.TraceEnabled = $true $dd.Update() This is enabled on the whole farm so you can go and look the the Right-Top of the site where a white colored button should appear. Upon clicking

  While configuring the SharePoint 2010 for Forms Based Authentication, I encountered above error. To get the problem, I had to change “IncludeExceptionDetailInFaults” to true somewhere. But WHERE? Here is what solved my problem: Go to following path: 1. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken 2. Open Web.config there. 3. Add following in the “behaviors > serviceBehaviors > behavior” node. <serviceDebug includeExceptionDetailInFaults="true"/> Now try to login and see what error it gives, off to a next error

Perhaps I posted this before, but if not, I am posting again for my reference. Use this tool to view SharePoint 2010 Error Logs: http://code.msdn.microsoft.com/ULSViewer/Release/ProjectReleases.aspx?ReleaseId=3308 SharePoint 2010 Log files are usually located here, sort by date and open the latest one in the ULS Viewer: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS Create a “Filter” and select “Message” and enter “Error” in value. This should give you all error entries in the file and you can find out what is wrong.

Before uninstalling the Filestream provider, make sure that you have content migrated back in the content database. To ensure this, just open “AllDocStreams” in the SharePoint Content database and look at the “Content” and “Rbsid” columns. the “Rbsid” columns should be NULL and “Content” column should be filled with data. If you uninstall the RBS provider before migrating the data back in the content database, all the data will become unavailable/ inaccessible. Use following command to Migrate content back and forth from and to DB to Blob Store: $rbss.SetActiveProviderName(“”) $rbss.Migrate()

The scenario was, I installed the RBS with Filestream and uninstalled the RBS and realized that all the blobs are still out there on file system due to which the uninstall process failed. Now I tried to call $rbss.Migrate() in PS but it failed because the RBS was no longer installed! I tried to call $rbss.Enable() but it failed with an error saying “SQL Remote Blob Storage should be installed on the web front end and content database before your can enable it” something like that. I re-installed RBS and filestream provider but it didn’t let me enable it and kept giving error. RESOLUTION and Lesson Learnt: To resolve the error, I re-booted the server and it worked. It is important to note that after installing RBS, it is required to restart the windows if are failing to “Enable” it on the content database.

To provision a Remote Blob Storage with FILESTREAM Provider provided by Microsoft, you have to follow instructions in this article: http://technet.microsoft.com/en-us/library/ee663474.aspx Things to NOTE: 1. For me, the tables with prefix mssqlrbs in the content database somehow didn’t appear by running the following command so I had to use wizard to create those tables in the content database instead of following command: msiexec /qn /lvx* rbs_install_log.txt /i RBS_X64.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME=" <ContentDbName> " DBINSTANCE=" <DBInstanceName> " FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1 Where: <ContentDbName> is the database name. <DBInstanceName> is the SQL Server instance name. 2. To Migrate all the data from Database to newly provisioned Blob Store, just execute following cmdlets in SharePoint Powershell: $cdb = Get-SPContentDatabase -WebApplication < http://