User profile synchronization service shows starting for long time

User profile synchronization service shows starting for long time

There could be many reasons for the service is in struck and shows starting only. .Why does it get stuck? Well, 15 provisioning runs will be attempted before it gives up. When we hit Start in Services in Server a series of tasks are run, which are to running the second stage of the Forefront Identity Manager setup. Those include things like setting up certificates, windows services, installing database schemas so on. If something is incorrect, it will try all tasks again, and more often than not, fail the service to start. That’s why it appears to be “stuck” when in fact its attempting each of the runs. Of course this can take a while, hence the appearance of being “stuck”. After around 20 to 45 minutes the status will return to Stopped, and you can attempt to start it again.

In some cases, the status will remain as “Starting” even after reboots. In this case something very bad has happened and you are best off throwing away the UPA service application and starting over.

You can however, manually start things back to the state before the starting of the UPS service instance. This can be necessary in some cases, but again, I strongly recommend you start clean by deleting and recreating the UPA. Before Re-creating the Service application ensure that all the below steps tried.

·        Ensure to restart the user profile service and synchronization service

·        Ensure to restart the FIM services

·        Ensure to do IISReset after the services starts

·        Ensure to reboot the server

·        Ensure to have the available space on DB server and SP server.

If all done but still issues not resolved, then try to Delete the Existing UPA service Application and create the new one and check the status.

To find the Error details,Please follow the below.

Browse to the location "C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell" and run miisclient.exe .it will show the actual error message which was causing the issue.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

SharePoint Roles

SharePoint Roles:

I am sharing this very simple Topic, because many of the Administrators want to know the difference and the responsibilities.

Owner:  Owner has a complete control over site, list, library and other content placed on site.

Designer: Users having designer role limited to certain activities. User can view, add, update, delete and approve content. Users can even customize the things, they have access to.

Editor: Editor role users are not allowed to customize site design or content. Users can add, edit, update and delete content from the site.

Contributor: Very limited role. They can delete content items which they have created but not by other.

Reader: Users are only allowed to view the content of site. Users are assigned to Reader roles can download and edit the content but cannot save it back on SharePoint site.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

We don’t have any refiners to show you

We don’t have any refiners to show you

                                      
 Issue: while we search for something in search centre, we can get the results but, it shows error” We don’t have any refiners to show you” or a “white space on left side of search centre”

Cause: This is due to the refinement web part is not added on search page or settings are not configured properly.There would be many other reasons this is one of those.

Solution: follow the below steps to add web part and configure settings.

1.   Open the search centre web page

2.   Go to site settings->edit page

        

3.   Click on Add web part         

                                 

4.   Go to search in categories and select Refinement and click ADD      

5.   The web part will be added                           

6.   Go to Edit web part and select Choose Refiners option.

                  

7.   Click on Choose refiners to select the Refiners.

              

8.   Click OK once selected and go back to Search and check the output.             

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered

The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered            

Problem occurs when you start SharePoint 2010 Management Shell (Power shell) but don’t get access to the farm. You would be unable to run commands. 

 Solution 1:Run Power shell with another user who don’t see above message e.g. Farm Admin

 Solution  2: 

  

1.    Execute “Add-SPShellAdmin -Username domain\User”(required user that you want to get Access to Power shell)

2.    Successful execution will ensure that desired user is Shell Admin and can execute commands. 

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

Solution  3:

As you can see it is Power Shell Version 3.0 which doesn’t support SharePoint 2010

http://blogs.msdn.com/b/ronalg/archive/2013/07/29/10382902.aspx?CommentPosted=true#commentmessage

to resolve the issue, change Power Shell start menu short cut path and added –version 2.0 switch parameter, below is the complete path with –version 2.0 switch.

C:\Windows\SYSTEM32\WINDOWSPOWERSHELL\V1.0\PowerShell.exe -version 2.0 -NoExit " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1' "

Add –version 2.0 switch;

By doing this  could run Power Shell 2.0 which support SharePoint 2010 commands

http://social.technet.microsoft.com/wiki/contents/articles/23151.sharepoint-2010-cmdlets-with-featuredependencyid-are-not-registered.aspx

  

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

The term is not recognized as the name of a CMDLET

The term is not recognized as the name of a CMDLET

     

The issue occurs some times while we run the CMDLETS on windows power shell or SharePoint management shell. Its due to the path issue, we can’t simply type the name of a script file in order to run it. Even with the execution policy configured to permit scripts, must precede the script filename with a path. you’ll see the” .\ “path in use, which refers to the current directory. You could also provide any other absolute or relative path in order to run a script—but you must provide a path of some kind. 

 Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!