Fix: User profile AD import job not running in SharePoint

3 min. read

Updated onOctober 4, 2023

updated onOctober 4, 2023

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Key notes

In an attempt to incorporate as many apps within theMicrosoft Office Suite that are relevant to work environments,Microsoftdecided to also incorporateSharePoint.

This versatilecollaborative toolcan be used as a document management and storage system, but the product is highly configurable and usage varies substantially amongorganizations.

However, software is software, andSharePointhas its own fair share of bugs and kinks. One good example is a bug users have beenreportingwhere the Active Directory Import timer job does not run:

I created User Profile service application inSharePoint2016 and created synchronization connection to import users from AD. Then started full synchronization but it is not importing any user from AD. “Profile Synchronization Status” is always in Idle mode.

SinceSharePointrelies 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 totruefor 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 usingSharePoint‘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.

Fix: User profile AD import job not running in SharePoint#

How do I fix the SharePoint user profile import error?#

Change your server’s properties#

Fix: User profile AD import job not running in SharePoint

How do I fix the SharePoint user profile import error?

Change your server’s properties