This versatile collaborative tool can be used as a document management and storage system, but the product is highly configurable and usage varies substantially among organizations. However, software is software, and SharePoint has its own fair share of bugs and kinks. One good example is a bug users have been reporting where the Active Directory Import timer job does not run: Since SharePoint relies on organizational work, not being able to import new members can severely affect the program’s functionality. That is why we’ve decided to put together this list so that you can be guided in a step-by-step manner to a viable solution.
How do I fix the SharePoint user profile import error?
All the servers in the farm that are running the User Profile Service are also not allowed to run timer jobs of the Service Job type. In our case, importing a user profile is also a service job and it can only run on servers running the User Profile service. This means that there are no servers on the farm that are allowed to run the job.
Change your server’s properties
The PowerShell command written above will l check to make sure there is at least one User Profile Service instance in the farm. Additionally, this sets the AllowServiceJobs property to true for the timer instance on those servers. If modifying server properties seems too complicated, another solution would be starting the User Profile Service on a server where service jobs are allowed. By following these steps, you should no longer have any issues with import jobs using SharePoint’s Active Directory feature. If you’re aware of other ways to solve this problem, don’t hesitate to share them with us in the comments section below.
SPONSORED
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
