Azure AD Connect Error: System.ArgumentNullException

[vc_row][vc_column][vc_column_text]Recently a client was having issues with AD user accounts not synchronizing into Azure AD. When kicking off a sync through the Synchronization Service Manager things appeared to be operating normally.  However, when attempting to trigger a sync through PowerShell it threw a very obtuse message:


PS C:\> Import-Module adsync
PS C:\> Get-ADSyncScheduler
Get-ADSyncScheduler : System.ArgumentNullException: Value cannot be null. Parameter name: token
PS C:\> Start-ADSyncSyncCycle -PolicyType Initial
Start-ADSyncSyncCycle : System.Management.Automation.CmdletInvocationException: System.ArgumentNullException: Value cannot be null. Parameter name: token

After checking in the event log to see if I could find any helpful indicators of the failure, I found a 906 event in the ADFS logs:

Sure enough the password expired for the service account used by AD Connect.  The password was reset and the cmdlet to sync worked and user accounts showed up in AAD![/vc_column_text][/vc_column][/vc_row]

Share:

Facebook
Twitter
LinkedIn
Picture of Levi Stevens

Levi Stevens

Contact Us

=
On Key

More Posts

WME Cybersecurity Briefings No. 024
Cyber Security

WME Security Briefing 28 August 2024

GhostWrite Vulnerability in T-Head CPUs Exposes Devices to Unrestricted Access Overview A critical architectural flaw in T-Head’s XuanTie C910 and C920 RISC-V CPUs was uncovered by recent research from the CISPA Helmholtz Center for Information Security. Dubbed GhostWrite, the vulnerability

Click Here to Read Full Article »
Be assured of everything

Get WME Services

Stay ahead of the competition with our Professional IT offerings.

=