Unable to connect to the Synchronization Service.

Error:

----------------------------------
Synchronization Service Manager
-----------------------------------
Unable to connect to the Synchronization Service.

Some possible reasons are:
1) The service is not started.
2) Your account is not a member of a required security group.

See the Synchronization Service documentation for details.

Reason:
The Forefront synchronization service user does not have access rights in the required permission groups.

Solution:
1. Open the "Server Manager"
2. Go to the Groups Folder
3. Select the "FIMSyncBrowse" group  and double click on it.
4. Add the respective user and Click "OK" button.
5. Do the same steps to add the same user for "FIMSyncJoiners", "FIMSyncOperators", "FIMSyncPasswordSet" groups.
6. Logoff your server and Login again.
7. Now you can see that if you click on miiclient.exe file, it will be displayed without showing error.

For More information, see the below screenshot:

That's it...

Issue: User profiles Sync DB doesn't have Tables or Stored Procedures

Issue:

While you are trying to import the user profiles in SharePoint 2010, you will get lots of errors. Particularly, we will face some of the issues like below:

1. Forefront Identity Manager Service may not be started.

2. Forefront Identity Manager Synchronization service may not be started.

3. If you see the "eventvwr", you will get some of the errors like below:

   

Error 1:

The Forefront Identity Manager Service cannot connect to the SQL Database Server.

The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.

Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.

Error 2:

 .Net SqlClient Data Provider: System.Data.SqlClient.SqlException: Could not find stored procedure 'RegisterService'.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at Microsoft.ResourceManagement.Data.DataAccess.RegisterService(String hostName)

Error 3:

The Forefront Identity Manager Service was not able to initialize a timer necessary for supporting the execution of workflows.The Forefront Identity Manager Service could not bind to its endpoints. This failure prevents clients from communicating with the Web services.

Error 4:

 A most likely cause for the failure is another service, possibly another instance of Forefront Identity Manager Service, has already bound to the endpoint. Another, less likely cause, is that the account under which the service runs does not have permission to bind to endpoints.

Ensure that no other processes have bound to that endpoint and that the service account has permission to bind endpoints. Further, check the application configuration file to ensure the Forefront Identity Manager Service is binding to the correct endpoints.

Solution:

I have spent lots of time to fix this issue. Hmmmm...  The solution is in SQL server side. In SQL Server database, you cannot find any "tables" or "Stored Procedures" in "Sync DB"

I have given the solution in single screenshot.  In the below screenshot, set the "db_owner" schema for "dbo".

Close

If you set the "dbo" as "db_owner", you can able to start the "Forefront Identity Manager Service". so that you will be able to start the profile import process.

Update: 
The same permission should be assigned to all user profile service databases like "Profile DB", "Social DB".


Also you need to restart the below services
1. Forefront Identity Manager service 
2. Forefront Identity Manager Synchronization Service
3. IIS 

Thats it...

Error: Your Personal site cannot be created because Self-Service Site Creation is not enabled. Contact your site administrator for more information.

Error:

Your Personal site cannot be created because Self-Service Site Creation is not enabled. Contact your site administrator for more information.

Reason:

As mentioned in the error message, the "Self-Service Site creation" is not enabled in your central admin.

Solution:

To enable the "Self-Service Site creation" option, just follow the steps given below:

1. Go to the Central admin.

2. Go to the "Application Management" & Select the specific web application.

3. Now, you can see the "Self-Service Site Creation" option in the Ribbon Menu.

4. Click on that Menu item and Select the "On" option in the pop-up window.

5. Click "OK" and now click the "My Content" link from your "My Site" site. You can see the "Processing" screen which means that your steps are correct.

6. Now you can see the newly created personal site. Here, you can create your own blogs, documents, etc... 

Thats it...

Error: Your personal site cannot be created because the managed path "personal" has not been created for this site. Contact your site administrator for more information.

Error:

Your personal site cannot be created because the managed path "personal" has not been created for this site. Contact your site administrator for more information.

Reason:

You haven't added the "Managed Path" for the the "My Site".

Solution:

Just follow the below steps to add "Personal" path as "Managed Path".

1. Go to "Central admin"

2. Select "Application Management" and select the specific "Web Application".

3. Type the 'MySite Host' URL as I mentioned in the above image. (I have created new site collection for MySite. So, I have added 'sites/mysite/personal' in the above screenshot).

4. Click OK.

Thats it...