Event ID 8247 — UNIX to Windows Password Synchronization Service -- Run-time Issues
Applies To: Windows Server 2008 R2
UNIX to Windows Password Synchronization Service -- Run-time Issues indicates the functionality of UNIX to Windows password synchronization operations.
When Password Synchronization is configured for UNIX to Windows synchronization, and UNIX to Windows synchronization is functioning normally, passwords that are changed on UNIX hosts are synchronized on Windows-based computers and domains. The Password Synchronization pluggable authentication module (PAM) makes this possible by intercepting the password change request on the UNIX host, encrypting the password, and then sending the password change request to the Password Synchronization service running on the Windows-based computers with which it is configured to be synchronized.
|Product:||Windows Identity Management for UNIX|
|Message:||Error occurred in acquiring handle to Cryptographic Service Provider. Error=%1|
Fix possible failures for Win32 API
Password Synchronization is unable to update a user password because it experienced a failure attempting to call a Windows API.
Read the full text of the error message in Event Viewer to obtain the exact Windows error code.
To correct the error, try the following steps in order, moving on to the next step only if the current action failed to clear the error condition:
- Free virtual memory by closing unused applications.
- Restart the Password Synchronization service.
- Restart the computer on which the error was generated.
To verify the functional state of UNIX to Windows password synchronization, retry UNIX to Windows password synchronization. UNIX to Windows password synchronization is fully operational when the password synchronization succeeds, and functioning with warning conditions present if password synchronization fails for some passwords but succeeds for others.
If password synchronization succeeds for some passwords but fails for others, the UNIX to Windows Password Synchronization Service is likely fully operational, but there might be account- or computer-specific configuration problems preventing password changes from being synchronized on UNIX-based hosts.