This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I've created an on-prem SP 2019 installation. Everything seems to be working except the User Profile Synchronization. I know there's a valid connection, because when I set up the Synchronization Connection, the 'Populate Containers' box pulls in the accounts and I see the names of all my users. But I run the full import and nothing seems to happen. Profiles are not imported. I get an error in the ULS log, 'Object reference not set to an instance of an object.'
Here's the strange part - Using a normal user account, I open the SharePoint site, and click my name (upper right-hand corner), then 'About me'. SharePoint creates my OneDrive/MySite. THEN my account appears in the Profile! It even has the info from the AD. But running the Profile Sync does nothing.
Trying to solve the problem, I have -
• Re-created the UP Service app from scratch several times.
• Re-created the AD connection.
• Ensured that the account used has Replicating Directory permissions.
• Ensured that the App Pool is running.
• Done the IISRESET at every step of the way.
What am I missing?
Probably best if you enabled Verbose logging (Set-SPLogLevel -TraceSeverity Verbose), reproduced the issue, ran Clear-SPLogLevel, then captured the logs surrounding the attempted UPSA import. This should give you better error details.
When providing a stack trace error, provide the full stack trace.
Okay, help me out here. I understand about the Verbose setting, which will provide maximum detail on what's happening. But what does the Clear-SPLogLevel do?
And Full stack trace is.... what, ALL messages from the job run beginning through all the errors?
StartImport :: Starting profile full import.
Write trace failed for type Microsoft.SharePoint.Administration.SPTaskUsageEntry with errorCode 8
SPPersistedObjectCollectionCache.RefreshDirtyCollections(): detected intervening update to collection cache file, dirtying all in-memory collection caches.
ERROR: Failed to OpenThreadToken, LastError=1008
Write trace failed for type Microsoft.SharePoint.Administration.SPTaskUsageEntry with errorCode 8
.
.
.
UserProfileApplication.DumpSynchronizationStatusToFile: Unexpected exception: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.Administration.UserProfileApplication.DumpSynchronizationStatusToFile().
What is the value of 'InstallPath' at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0?
The problem has been solved.
After writing the last message about the Timer Job, I started poking around IIS. I investigated all the Service jobs that might be involved with the User Profile sync. All seemed to be in order, but for good measure, I stopped, then restarted, all of those.
And suddenly, the import ran, pulling in all the Profiles.
I think it might have been the User Profile Service itself, but could have been any, or a combination.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 80%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
Hello Keith,
I also facing similar issue … Can yo let me know which timer jobs have you restarted.
Hi @Keith Vollero ,
Whether the profiles not imported means that "Number of User Profiles" is not correct?
Per my research, please try as following:
1)Select all objects again by clicking in the parent's OU checkbox and saved the changes.
2)Try to select another sync option 'Enable External Identity Manager' and saved. Then came back and select 'Use SharePoint Active Directory Import' setting and save.
This step cleans up the UPS databases from old data that could be causing trouble.
Remember to disable the Mysite cleanup timer job before working on this.
More information:
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Julie,
Thanks for the quick response. Unfortunately, still No Joy on the Profile Sync. The job just does not run.
Odd thing - The 'Select All' functionality seems off. I check the 'Select All' button when populating the containers, and the boxes all check. Save and close, but when I go back, the boxes are unchecked. I had to select each branch individually to select all the containers.
In any case, as I said, No Joy. The job doesn't run, and the same "Object reference not set to an instance of an object." error appears.
When looking through the logs, I noticed a different error (below). Clue?
12/14/2020 09:24:06.48 w3wp (0x13E4) 0x2398 SharePoint Foundation Upgrade SPDelegateManager awbky INFO Ignoring upgrade sequence: Microsoft.Office.Server.Upgrade.ProfileDatabaseExtensionSprocsSequence because related content database extension Microsoft.Office.Server.UserProfiles.ProfileDatabaseExtension is not enabled. 00000000-0000-0000-0000-000000000000
Hi @Keith Vollero ,
The "Select all" button will show as initially each time after selected it , it's the normal behavior.
From your description, whether the timer job "User Profile Service Application - User Profile ActiveDirectory Import Job " doesn't run?
If it is true, please refer to this article:
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Thank you for the confirmation on 'Select All'. It seemed quirky.
As to the other question, it isn't the Timer Job that's the problem. The Profile Import won't run even when I try to start it from Central Admin, using the Service Application interface
:
Hi @Keith Vollero ,
When you start incremental synchronization or full synchronization, User Profile service application - User Profile Active Directory import timer job works in the background to import objects from Active Directory to the Profile database.
Please refresh the Manage Profile Service page to check whether the profile synchronization status is Idle.
We could also check the timer job last run time to check whether the sync is complete.
This is one thing that puzzles me - The 'User Profile ActiveDirectory Import Job' timer job is set up to run every 5 minutes. It's Enabled. But it never runs. It doesn't fail, it just doesn't run. It doesn't error out, it just doesn't run. When I edit the Timer job and click 'Run Now' to run it manually, Nothing Happens. It doesn't show up in the Job History, just nothing happens.
It's as though something is missing from the Command string that executes the job, and all I get is the "System.NullReferenceException: Object reference not set to an instance of an object. " error.
Any ideas?
Julie,
The Sync Status is idle, that's the problem, it STAYS idle, even when I run the Sync job. Either one, Full or Incremental, the job just doesn't run. Checking the Timer job shows that the job hasn't run. When I click 'Run' from the Timer job, it still does not run.
In the ULS log, I see this:
StartImport :: Starting profile full import.
UserProfileApplication.DumpSynchronizationStatusToFile: Unexpected exception: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.Administration.UserProfileApplication.DumpSynchronizationStatusToFile().
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 28.000000000000004%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Hi Did you ever fix this ?