How to re associate list workflows with lists after a migration in SharePoint 2010

Recently I had been exercised on migrating a sub site into a root web in a different site collection.One of the major issue, out of many, was none of the list work flows were working.

After further investigations, figured out that the issue was due to old list Id’s that were associated with the workflows from the source site which I exported.

Follow the steps below to re associate new list Id’s with the workflow using MS SharePoint Designer.

Step 1: Open the site in SPD

Step 2: Locate the workflow you want to re associate with new list Id's (See image below)

Step3: Change the 4 list Id’s numbered in below image with the new Id’s

• DocLibID
  • The list Id for the workflow definitions lists (This is a hidden list and you can use SharePoint manager to get the list id)-Refer the image below

• ListID
  • The list Id that needs to associate with the workflow
• TaskListID
  • "Workflow Tasks" list Id
• HistoryListId
  • "Workflow History" list Id

Configuring Forms Based Authentication (FBA) in SharePoint 2010

One of my favorite configuration tasks from SharePoint 2007 is to configure multiple authentication providers. So I wanted to do the same thing in SharePoint 2010 too. Here I will be using the MSSQL database as the membership store for the users.
Steps

1. Create MSSQL membership store
2. Create the new web application
3. Configure support for FBA
1. In Central Administration
2. In new web application
3. In STS web service (new in SharePoint 2010)
4. Adding user policies to the web application
5. Login to the site

Step 1: Create MSSQL membership store
This is where all the user details going to be store.

• Create the database
• Run the ASP.NET SQL Server Setup Wizard located at C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe and follows the instructions.

• Once completed create a separate database user and assign that user and add the “db_owner” role.
• Add users into the membership store
• Launch the Visual Studio and create a web site project
• Add a connection string pointing to the above created database
• Launch the “ASP.NET Configuration” wizard in “Website” menu item.
• Click on the “Security” link and select the “internet” option and add users in to the store.

Step 2: Create the new web application

• Go to Central Administration > Manage web applications and click on the “New” in the ribbon
• Set the settings in the dialog box as in the below images (Check the red boxes)

• Once the web application created, create the site collection as well.

Step 3: Configure FBA support

• Edit the web.config for the central administration in the virtual directories folder
• Add the following entry just above the </system.web> node

<membership defaultProvider="AspNetSqlMembershipProvider"> <providers> <remove name="AspNetSqlMembershipProvider" /> <add connectionStringName="AspNetSqlProvider" passwordAttemptWindow="10" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" description="Stores and retrieves membership data from the Microsoft SQL Server database" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </membership> <roleManager defaultProvider="AspNetWindowsTokenRoleProvider"> <providers> <clear /> <remove name="AspNetSqlRoleProvider" /> <add connectionStringName="AspNetSqlProvider" applicationName="/" description="Stores and retrieves roles data from the local Microsoft SQL Server database" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </roleManager>

• Add the below connectionString details just above the </configuration> node and put the corresponding values for the database,user id and password

<connectionStrings> <add connectionString="Data Source=eccolw7ira;Initial Catalog=<database>;User ID=<user id>;Password=<password>" name="AspNetSqlProvider" /> </connectionStrings>

• Edit the web.config for the corresponding site in the virtual directories folder
• Add the following entry just above the </system.web> node.
• Note : If the membership entry is already available , add only the missing entries (Highlighted in Yellow) from the bellow entry.

<membership defaultProvider="i"> <providers> <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlMembershipProvider" /> <add connectionStringName="AspNetSqlProvider" passwordAttemptWindow="10" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" description="Stores and retrieves membership data from the Microsoft SQL Server database" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </membership> <roleManager defaultProvider="c"> <providers> <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlRoleProvider" /> <add connectionStringName="AspNetSqlProvider" applicationName="/" description="Stores and retrieves roles data from the local Microsoft SQL Server database" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </roleManager>

• Add the below connectionString details just above the </configuration> node and put the corresponding values for the database,user id and password

<connectionStrings> <add connectionString="Data Source=eccolw7ira;Initial Catalog=<database>;User ID=<user id>;Password=<password>" name="AspNetSqlProvider" /> </connectionStrings>

• Edit the web.config located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken
• Add the following entry just above the </configuration> node

<system.web> <membership defaultProvider="AspNetSqlMembershipProvider"> <providers> <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlMembershipProvider" /> <add connectionStringName="AspNetSqlProvider" passwordAttemptWindow="10" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" description="Stores and retrieves membership data from the Microsoft SQL Server database" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </membership> <roleManager defaultProvider="AspNetSqlRoleProvider" enabled="true" cacheRolesInCookie="false"> <providers> <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlRoleProvider" /> <add connectionStringName="AspNetSqlProvider" applicationName="/" description="Stores and retrieves roles data from the local Microsoft SQL Server database" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </roleManager> </system.web> <connectionStrings> <add connectionString="Data Source=eccolw7ira;Initial Catalog=<database>;User ID=<user id>;Password=<password>" name="AspNetSqlProvider" /> </connectionStrings>

Step 4: Adding user policies into the web application

• Go to Central administration > Manage web applications and select the web application and click on the “User Ploicy” button in ribbon.
• Click on the “Add users” link and select the “Default” as the zone and click on “Next”.
• Type the user name in the “Users” text box and click on the People Picker icon.
• If everything configured correctly you should see the user name get underlined in the “users” box. OR
• Click on the “Browse” button under the users text box and type the user name in the search text box and click on the search button.
• And you should see the user name in the search result.

Step 5: Login to the site

• Open the site in browser and select the “Forms Authentication” from the drop down

• Provide the user credentials and you should be redirected to the home page

Arctic SharePoint Challenge 2011

The team Puzzlepart is sponsoring one of the most intriguing event you would ever going to experience during this winter.
Are you ready to take on the challenge ?
Visit http://arcticsharepointchallenge.com/ for more info and feel free to follow @SPChallenge (Dexter the Lynx challenge mascot) on twitter.

SharePoint 2010 : First custom connector implementation for BCS

Today, I managed to read on BCS a bit and wanted to try out some custom connector implementation for the external systems.
Found out this code snippet from MSDN for a connector to the file system.
Managed to complete this exercise and created an external list with the External Content Type and I did see the files from the file system in the list.See bellow images.
Folder contents in file system :

External list in SP context :

I am really impressed by this and it has already inspired me to go deep into this and hoping to create some more custom connectors for other external systems as well.
Found out lot of issues/problems while I am doing this and I just list down possible erroneous  scenarios.

1. Business Data Connectivity Services issues
2. Assembly deployment to the GAC
3. Assembly information
4. Configure Business Data Connectivity access rights

Keep those things in mind if you also get into trouble.  

Error accessing Business Data Connectivity Services in Windows 7

While I was doing some research on BCS , wanted to import a BDC model from Central Administration > Manage service applications > Business Data Connectivity Services.

As I hit the link,  following error message prompted.

 

As usual did a search on the Google and found out the following entries.

http://sensoft2000-sharepoint.blogspot.com/2010/08/error-access-services-is-unable-to.html

https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=23806

Downloaded the above fix and installed.

problem solved. :)

More references on the issue :

http://blogs.technet.com/b/dahnesh/archive/2010/06/16/error-while-accessing-business-data-connectivity-services-on-windows-7.aspx

http://support.microsoft.com/kb/976462

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=976462&kbln=en-us

 

Sharepoint foundation 2010 on windows 7 x64

Today,I installed Sharepoint Foundation 2010 on my laptop successfully according to this article.Downloaded the Sharepoint Foundation 2010 from here and started following the installation steps mentioned in this article.

The second step under “To set up a developer workstation” failed successfully because of this command “c:\SharePointFiles\SharePoint /extract:c:\SharePointFiles”
Here it referred to a file called “SharePoint” but the name of the downloaded application was “SharePointFoundation.exe”. So in order to pass this step I had to change the name from “SharePoint” to “SharePointFoundation” in the above command.

After that I continued with the installation steps and managed to launch the setup.exe after completing the installation of prerequisites mentioned.
In the 3rd step under the  “Step 3: Install SharePoint 2010” I select the “Server Farm” option and in the next step I selected the standalone option.I had no clue what so ever why I selected that option, but it happened for some reason and it worked.

Then I had to wait for a quite a longer time to complete the installation and prompted to run the sharepoint configuration wizard.
And finally after the configuration wizard completed, it prompted the newly created sharepoint team site.(See image at top)

Now sharepoint foundation 2010 at my finger tips so that I can start playing with it.

The 12 factors to turn ASP.NET developers to SharePoint 2010

Found this article on Share point dev wiki.
http://www.sharepointdevwiki.com/display/sp2010/2009/11/04/The+12+factors+to+turn+ASP.NET+developers+to+SharePoint+2010

Share point 2010 Hands-on Labs in C# and VB

Developer hands on labs can be found at http://www.microsoft.com/downloads/details.aspx?FamilyID=C010FC68-B47F-4DB6-B8A8-AD4BA33A35C5&displaylang=en#filelist

Good luck !

SharePoint 2010 Sneak Peak

Are you wondering about how will SharePoint 2010 look like.Here we go click on SharePoint Sneak Peek.