Thursday, June 12, 2014

The management agent MOSSAD-Connection with AD failed on run profile “DS_FULLIMPORT” because of connectivity issues



The management agent MOSSAD-Connection with AD failed on run profile “DS_FULLIMPORT” because of connectivity issues.

Issue: After configuring the User profile service application, when we start the full synchronization, we see the error” The management agent MOSSAD-Connection with AD failed on run profile”

Cause: As in my view and experiance, This error  is generally caused by the User running the task not having the right permissions set up on Active Directory. 
There could be many reasons, This is the most common.

Event ID:
·        Log Name:      Application
·        Source:        FIMSynchronizationService
·        Event ID:      6050
·        Task Category: Management Agent Run Profile
·        Level:         Error
·        Keywords:      Classic
·        User:          N/A
·        Computer:      SharePoint2013
·        Description:
·        The management agent “MOSSAD-Connection with AD” failed on run profile “DS_FULLIMPORT” because of connectivity issues.

Solution: please follow the below steps if you have the Access to AD. If not, please check the steps with AD team.

1.   Open the Active Directory Users and Computers snap-in.
2.   On the View menu, click Advanced Features.
3.   Right-click the domain object, i.e. for EX: “Sharepoint.com”, and then click Properties.
4.   On the Security tab, click Add. If for some reason the user account you are using to run this service is already on the list you can skip to step 7.
5.   In the Select Users, Computers, or Groups dialog box find the user account under which the profile sync service is running and then click Add.
6.   Click OK to return to the Properties dialog box.
7.   Select the recently added user account // user account under which the profile sync service will run under.
8.   Ensure to Select the “Replicating Directory Changes” check box from the list.
9.   Click Apply and then click OK.
10.     Now start a new full sync from your SharePoint Central Administration to verify the issue has been resolved!

I have Explained in very Detail about User profile in SharePoint 2013.Please check the POST Categories tab for User Profile on Blog.
 

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

Tuesday, June 10, 2014

Reporting Web service proxy Does not exist in the farm



Reporting Web service proxy Does not exist in the farm

Issue: After we configure Everything related to Reporting services for SharePoint 2013,when we try to create the reporting service application in CA, we encounter the issue “Reporting Web service proxy Does not exist in the farm”

                    

Cause: The issue is due to the reporting features are installed but not configured the reporting services and the proxy in CA. 

Solution: Ensure to run the below commands to get rid of the error.we must run the below two commands before creating the SSRS service application in CA.

Install-SPRSService
Install-SPRSServiceProxy

You can find the very detailed explanation in the below Article.

http://expertsharepoint.blogspot.de/2014/03/sql-reporting-services-installation.html
 

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

Monday, June 9, 2014

Timer service terminated with service-specific error or Timer service terminated unexpectedly in share point



Timer service terminated with service-specific error  or Timer service terminated unexpectedly in share point

This is an issue that face every SharePoint administrator many times in their experience. This could be of many reasons. In this article I am providing the reason that cause the issue as per my experience.

Due to the issue with the timer service we see the other parts like Alerts, Backups, Search and UPS also stops working

When I tried to retract a solution, but the status showing "Retracting" only for long time. After digging in events, I figure out that the issue is with the SharePoint Timer service on one of the servers crashed every couple of minutes. The event log showed the following errors.

Events:
Log Name: System
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [Server name]
Description:
The SharePoint 2010 Timer service terminated with service-specific error %%-2147467259.
and
Log Name: System
Source: Service Control Manager
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [Server name]
Description:
The SharePoint 2010 Timer service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.

Solution: Ensure to follow the below steps to resolve the issue

·         Open the Registry Editor
·         Browse to HKLM > SOFTWARE > Microsoft > Shared Tools > Web Server Extensions > 14.0 > Secure > ConfigDB(For SharePoint 2013,Its 15.0)
·         Copy the value in the property "Id" 

                     
·         Browse to folder C:\ProgramData\Microsoft\SharePoint\Config and create a folder with the name of the previously copied value 

                          

·         Restart the SharePoint Timer service
·         The folder should be populated with XML files after restart
 

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

ShareThis

X