Exception calling "add" with "2" argument(s): The specified user or domain group was not found...

The following error will occur if we mentioned User account name incorrectly.

" Exception calling "add" with "2" argument(s): The specified user or domain group was not found."

when we were migrating classic mode to claims based. We did a small spell mistake.

Like Domain\user instead of this Domin\User

Sharepoint 2007 site to sharepoint 2010 migration

Database Changes: 

1. Take Backup of the current content database of site (2007 site) from SQL Server.
2. In SQL Management Studio (In 2010 site  SQL server), create new DB and restore the content database, need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).

Site Changes: 

1. Create a "New Web Application" in SP2010. 
2. Remove Content Database of newly Created site.
• c:\program files\common files\microsoft shared\web server extentions\14\bin.
• stsadm -o deletecontentdb -url http://*** -databasename -databaseserver .
3. Now restore the DB to the created Web Application from STSADM
• stsadm -o addcontentdb -url http://*** -databasename -databaseserver
                 
4. Delete old content database in SQL Management Studio (optional). 

Files:

 Copy Pate bin/UserControl folder to new site folder.

Cannot get Role Manager with name

 

Cannot get Role Manager with name . The role manager for this process was not properly configured. You must configure the role manager in the .config file for every SharePoint process

After you have configured the Claims based authentication and tried to login to the site using Windows Authentication then you will be able to login and see site without any issues. But, when you tried to login to the site using Forms authentication then you will see above message if and only if you haven't configured Role Manager correct. In my case I am using Sql Server Membership Provider. I have added web.config changes required for all the three web applications and in the "Authentication Providers" section of the web application I have given Member ship provider and Role Manager. But, I haven't configured Role Manager at all. This is the reason why the error message coming.

So, the solution will be either remove the Role Manager entry in the Authentication Providers section or configure Role Manager correctly. In my case I am not using any roles, so I removed the name from authentication providers and everything started working correct.

Ref : http://sharepoint-2010-world.blogspot.com/2011/03/cannot-get-role-manager-with-name.html

Form Authentication with Active Directory member role...

http://blogs.msdn.com/b/sridhara/archive/2010/01/07/setting-up-fba-claims-in-sharepoint-2010-with-active-directory-membership-provider.aspx

http://blogs.technet.com/b/speschka/archive/2009/11/05/configuring-forms-based-authentication-in-sharepoint-2010.aspx

http://technet.microsoft.com/en-us/library/ee806890.aspx#section2

We followed as per sridhara site. Everything worked fine.

After doing this, while login to site with form authentication we got error like below

The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

Followed this link and solved our problem...
http://sharepoint-2010-world.blogspot.com/2011/03/server-was-unable-to-process-request.html

Migrating the sharepoint site classic mode authentication to Claims based Authentication

Reference using the below links migrated site successfully.

 

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

http://weblogs.asp.net/sreejukg/archive/2011/03/25/change-sharepoint-authentication-from-classic-mode-to-claims-based.aspx

http://blog.henryong.com/2011/08/18/sharepoint-2010-converting-from-classic-to-claims-authentication-lessons-learned/#comment-6558

Error Message
Set-SPWebApplication: An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=SharePoint Sites was updated by domain\serviceAccount, in the OWSTIMER process, on machine SPServer. View the tracing log for more information about the conflict.
As per henry blog, I feel best to follow the steps 3 & 4 to avoid the above error message...

--------- ------------------------ -------------------

(After Migration we did not use Point No.7)

An unexpected Error has Occurred...

Cannot access User Profile Service Application after provisioning Synchronization Service...

The answer is nice and easy – just perform an IIS Reset.  For some reason if you have Central Administration on the same server, you will not be able to access the User Profile Service Application management area until you do an IISreset. 

Help

Sharepoint 2010 Interview Q & A

Question and Answers Link