Credits

Jeff Ingalls
Original Source: Jeff's blogpost on Technet > Forefront Identity Manager (FIM) Eventlogs, Events and Monitoring 


Downloads

XLS sheet with events from Jeff's blog:

  FIM2010-EventLogs.xlsx

Download the free FIM Management Pack (MP).


Event ID Groups

 

FIM Component EventLog Source Event ID Ranges*
Add-ins and Extensions Application Microsoft.ResourceManagement.OutlookClientHealthSource 1-65535
Add-ins and Extensions Application Microsoft.ResourceManagement.PasswordManagementHealthSource 1-65535
Add-ins and Extensions Application Microsoft.ResourceManagement.PasswordProxyHealthSource 1-65535
Certificate Management Application Enterprise Library Caching 1-65535
Certificate Management Application Enterprise Library Configuration 1-65535
Certificate Management Application Enterprise Library Manageability Extensions 1-65535
Certificate Management FIM Certificate Management FIM Certificate Management 1-65535
Certificate Management FIM Certificate Management FIM CM CA Modules 1-65535
Certificate Management Client Application FIM CM Update Client 0-520, 4097-4873, 5120-5632, 24576-28416, 51200-57345, 61440-61444
FIM Service Forefront Identity Manager Microsoft.ResourceManagement 1-65535
Password Change Notification Service Application PCNS Filter 1-5,2000-2002,4000-4001,6000-6023,7000
Password Change Notification Service Application PCNSSVC 1-5,2000-2005,2100-2305,4000-4301,6000-6039,7000
Synchronization Service Application FIMSynchronizationService 1-8, 100, 2000-2004, 4000, 6000-

 

Event IDs per FIM component

FIM Add-ins and Extensions

Eventlog: Application

Source Event ID Message
Microsoft.ResourceManagement.OutlookClientHealthSource 1-65535  
Microsoft.ResourceManagement.PasswordManagementHealthSource 1-65535  
Microsoft.ResourceManagement.PasswordProxyHealthSource 1-65535  

FIM Certificate Management

Eventlog: FIM Certificate Management

 

Source Event ID Message
FIM Certificate Management 1-65535  
FIM CM CA Modules  1-65535  

 
Eventlog: Application

 

Source Event ID Message
Enterprise Library Caching 1-65535  
Enterprise Library Configuration 1-65535  
Enterprise Library Manageability Extensions 1-65535  

FIM CM Client

Eventlog: Application

Source Event ID Message
FIM CM Update Client 0  
FIM CM Update Client 1 PKCS11 Error: Operation cancelled
FIM CM Update Client 2 PKCS11 Error: Insufficient memory to perform the requested function
FIM CM Update Client 3 PKCS11 Error: Invalid reader identifier
FIM CM Update Client 5 PKCS11 Error: General smart card error has occurred
FIM CM Update Client 6 PKCS11 Error: The requested function could not be performed
FIM CM Update Client 7 PKCS11 Error: Bad arguments
FIM CM Update Client 8 PKCS11 Error: No event
FIM CM Update Client 9 PKCS11 Error: Need to create threads
FIM CM Update Client 10 PKCS11 Error: Can't lock
FIM CM Update Client 16 PKCS11 Error: Attribute read only
FIM CM Update Client 17 PKCS11 Error: Attribute sensitive
FIM CM Update Client 18 PKCS11 Error: Invalid attribute type
FIM CM Update Client 19 PKCS11 Error: Invalid attribute value
FIM CM Update Client 32 PKCS11 Error: Invalid data
FIM CM Update Client 33 PKCS11 Error: Invalid data length range
FIM CM Update Client 48 PKCS11 Error: Device error
FIM CM Update Client 49 PKCS11 Error: Device memory error
FIM CM Update Client 50 PKCS11 Error: Device removed
FIM CM Update Client 64 PKCS11 Error: Invalid encrypted data
FIM CM Update Client 65 PKCS11 Error: Invalid encrypted data length range
FIM CM Update Client 80 PKCS11 Error: Function canceled
FIM CM Update Client 81 PKCS11 Error: Function not parallel
FIM CM Update Client 84 PKCS11 Error: Function not supported
FIM CM Update Client 96 PKCS11 Error: Invalid key handle
FIM CM Update Client 98 PKCS11 Error: Invalid key length range
FIM CM Update Client 99 PKCS11 Error: Inconsistent key type
FIM CM Update Client 100 PKCS11 Error: Key not required for this operation
FIM CM Update Client 101 PKCS11 Error: Key changed
FIM CM Update Client 102 PKCS11 Error: Key required for this operation
FIM CM Update Client 103 PKCS11 Error: Key indigestible
FIM CM Update Client 104 PKCS11 Error: Key function not permitted
FIM CM Update Client 105 PKCS11 Error: Key not wrappable
FIM CM Update Client 106 PKCS11 Error: Key not extractable
FIM CM Update Client 112 PKCS11 Error: Unsupported algorithm specified
FIM CM Update Client 113 PKCS11 Error: Invalid algorithm parameter
FIM CM Update Client 130 PKCS11 Error: Invalid object handle
FIM CM Update Client 144 PKCS11 Error: Operation active
FIM CM Update Client 145 PKCS11 Error: Operation not initialized
FIM CM Update Client 160 PKCS11 Error: Incorrect PIN
FIM CM Update Client 161 PKCS11 Error: Invalid PIN
FIM CM Update Client 162 PKCS11 Error: Invalid PIN length
FIM CM Update Client 163 PKCS11 Error: PIN expired
FIM CM Update Client 164 PKCS11 Error: PIN locked
FIM CM Update Client 176 PKCS11 Error: Session closed
FIM CM Update Client 177 PKCS11 Error: Too many sessions
FIM CM Update Client 179 PKCS11 Error: Invalid session handle
FIM CM Update Client 180 PKCS11 Error: Parallel sessions not supported
FIM CM Update Client 181 PKCS11 Error: Session is read only
FIM CM Update Client 182 PKCS11 Error: Session exists
FIM CM Update Client 183 PKCS11 Error: Read-only session exists
FIM CM Update Client 184 PKCS11 Error: Read-Write SO session exists
FIM CM Update Client 192 PKCS11 Error: Invalid digital signature
FIM CM Update Client 193 PKCS11 Error: Invalid digital signature length range
FIM CM Update Client 208 PKCS11 Error: Template incomplete
FIM CM Update Client 209 PKCS11 Error: Template inconsistent
FIM CM Update Client 224 PKCS11 Error: Unable to locate tokens. Please ensure a supported smart card is inserted
FIM CM Update Client 225 PKCS11 Error: Token is not recognized. Please ensure a supported smart card is inserted
FIM CM Update Client 226 PKCS11 Error: Token is write protected
FIM CM Update Client 240 PKCS11 Error: Invalid unwrapping key handle
FIM CM Update Client 241 PKCS11 Error: Invalid unwrapping key size
FIM CM Update Client 242 PKCS11 Error: Inconsistent unwrapping key type
FIM CM Update Client 256 PKCS11 Error: User already logged in
FIM CM Update Client 257 PKCS11 Error: User not logged in
FIM CM Update Client 258 PKCS11 Error: User PIN not initialized
FIM CM Update Client 259 PKCS11 Error: Invalid user type
FIM CM Update Client 260 PKCS11 Error: Another user already logged in
FIM CM Update Client 261 PKCS11 Error: Too many user types
FIM CM Update Client 272 PKCS11 Error: Invalid wrapped key
FIM CM Update Client 274 PKCS11 Error: Invalid wrapped key size
FIM CM Update Client 275 PKCS11 Error: Invalid wrapping key handle
FIM CM Update Client 276 PKCS11 Error: Invalid wrapping key size
FIM CM Update Client 277 PKCS11 Error: Inconsistent wrapping key type
FIM CM Update Client 288 PKCS11 Error: Random seed not supported
FIM CM Update Client 289 PKCS11 Error: Random RNG not supported
FIM CM Update Client 304 PKCS11 Error: Invalid domain parameters
FIM CM Update Client 336 PKCS11 Error: Buffer too small
FIM CM Update Client 352 PKCS11 Error: Invalid saved state
FIM CM Update Client 368 PKCS11 Error: Data is sensitive
FIM CM Update Client 384 PKCS11 Error: State unsaveable
FIM CM Update Client 400 PKCS11 Error: CRYPTOKI not initialized
FIM CM Update Client 401 PKCS11 Error: CRYPTOKI already initialized
FIM CM Update Client 512 PKCS11 Error: Failed to load PKCS11 module
FIM CM Update Client 513 PKCS11 Error: Failed to obtain PKCS11 API entries.
%1
FIM CM Update Client 514 PKCS11 Error: Required smart card not found
FIM CM Update Client 515 PKCS11 Error: Required attribute not found
FIM CM Update Client 516 PKCS11 Error: Unable to obtain Public Key from the card
FIM CM Update Client 517 PKCS11 Error: Unable to delete keys from the card
FIM CM Update Client 518 PKCS11 Error: Required key not found on the card
FIM CM Update Client 519 PKCS11 Error: PKCS11 module is not initialized
FIM CM Update Client 520 PKCS11 Error: Unable to synchronize server data. No valid PIN found
FIM CM Update Client 4097 Access denied. Property '%1' is read only
FIM CM Update Client 4100 Operation is not allowed: '%1'
FIM CM Update Client 4101 Property name '%1' is already registered
FIM CM Update Client 4102 Property not registered.
FIM CM Update Client 4105 Unable instantiate Plug-in component
FIM CM Update Client 4106 Interface not supported: %1
FIM CM Update Client 4107 Object provides read-only properties
FIM CM Update Client 4108 Invalid license
FIM CM Update Client 4109 License has expired
FIM CM Update Client 4110 Invalid OID
FIM CM Update Client 4111 Unknown OID
FIM CM Update Client 4112 Unexpected file format
FIM CM Update Client 4113 Failed to load XML document.
Source: %1
Reason: %2
FIM CM Update Client 4113 Unable to load module %1
FIM CM Update Client 4114 Failed to load XML document.
< %1> node expected
FIM CM Update Client 4114 Object initialization failed
FIM CM Update Client 4115 Node <%1> must have attribute '%2'
FIM CM Update Client 4115 AD Attribute Name is not configured for the application
FIM CM Update Client 4116 Unsupported value: %1
FIM CM Update Client 4117 Unable to create profile '%1'
FIM CM Update Client 4118 Node <%1> must have inner value
FIM CM Update Client 4119 Unsupported version of XML data.
%1
FIM CM Update Client 4120 Failed to load XML document.
< %1> node unexpected
FIM CM Update Client 4121 Failed to load XML document.
< %1> node has invalid value
FIM CM Update Client 4353 Unknown configuration type
FIM CM Update Client 4354 Invalid configuration parameter: '%1'
FIM CM Update Client 4355 File '%1' is already opened
FIM CM Update Client 4356 Invalid property value: '%1'
FIM CM Update Client 4357 Section not found or invalid requested type : '%1'
FIM CM Update Client 4358 Device type not supported
FIM CM Update Client 4359 Unexpected operation. Object has not been initialized.
FIM CM Update Client 4362 Unknown provider: %1
FIM CM Update Client 4865 Response does not correspond to Request
FIM CM Update Client 4866 Unable to load configuration for '%1':

%2
FIM CM Update Client 4867 Acceptance criteria failed: %1
FIM CM Update Client 4868 Could not start service.
Please analyze the event log
FIM CM Update Client 4869 Could not decode response
FIM CM Update Client 4870 Could not decode request
FIM CM Update Client 4871 Bad BASE64 format. Decoding failed
FIM CM Update Client 4872 Unable to convert UNICODE characters to ANSI codepage
FIM CM Update Client 4873 Invalid session key
FIM CM Update Client 5120 Unable to open certificate store
FIM CM Update Client 5121 Invalid size of DES key
FIM CM Update Client 5122 Provided key can not be used for importing/exporting other keys
FIM CM Update Client 5123 Certificate not found
FIM CM Update Client 5124 Invalid file format or corrupt PFX data.
FIM CM Update Client 5125 Provided smart card is not blank and can not be personalized
FIM CM Update Client 5126 Provided key is too large
FIM CM Update Client 5127 Invalid response size
FIM CM Update Client 5128 Invalid smart card PIN
FIM CM Update Client 5129 Unable to delete container '%1' from '%2'
FIM CM Update Client 5130 Unable to delete file '%1\\%2'
FIM CM Update Client 5131 File corrupt or unsupported format for crypto operation
FIM CM Update Client 5132 Specified key algorithm not supported
FIM CM Update Client 5133 Specified hash algorithm not supported
FIM CM Update Client 5134 Specified key usage does not allow for key archival
FIM CM Update Client 5135 Transport key not found. Unable to unwrap data
FIM CM Update Client 5136 Unable to validate certificate chain.
FIM CM Update Client 5137 Certificate chain validation failed.
%1
FIM CM Update Client 5376 The smart card is not connected
FIM CM Update Client 5377 'InitializeUpdate' call required for this operation
FIM CM Update Client 5378 Required key '%1' not found for secure channel
FIM CM Update Client 5379 Unsupported keyset type for secure channel
FIM CM Update Client 5380 Failed authenticating card cryptogram
FIM CM Update Client 5381 Failed authenticating host cryptogram
FIM CM Update Client 5382 Invalid state for this operation
FIM CM Update Client 5383 Data too large to transmit to the smart card
FIM CM Update Client 5384 Unsupported security level for secure channel
FIM CM Update Client 5385 Card must not be in transacted state for this operation
FIM CM Update Client 5386 Smart card PIN required for this operation
FIM CM Update Client 5387 Card communication error. SCardTransmit returned too few bytes
FIM CM Update Client 5388 Card communication error. SCardTransmit returned too many bytes
FIM CM Update Client 5632 The current settings of Base CSP provider do not allow for private key import.
FIM CM Update Client 24576 Authentication failed: %1
%2 attempts remaining
FIM CM Update Client 24577 Authentication failed: %1
FIM CM Update Client 25217 Read operation failed
FIM CM Update Client 25218 End of file reached
FIM CM Update Client 25219 Invalid context
FIM CM Update Client 25344 Input key error
FIM CM Update Client 25985 Memory problem
FIM CM Update Client 26368 Wrong length
FIM CM Update Client 27009 Missing key or key slot error
FIM CM Update Client 27010 Invalid or no key presented
FIM CM Update Client 27011 Blocked or missing key
FIM CM Update Client 27013 AC failure or missing key
FIM CM Update Client 27014 Inappropriate context
FIM CM Update Client 27264 Inappropriate context
FIM CM Update Client 27266 Missing FID or file
FIM CM Update Client 27267 Insufficient space or out of range
FIM CM Update Client 27268 Insufficient space
FIM CM Update Client 27270 EMV P1/P2 error
FIM CM Update Client 27904 Command instruction error
FIM CM Update Client 28160 Command class error
FIM CM Update Client 28416 Unspecified problem
FIM CM Update Client 51200 MetaData has not been initialized yet
FIM CM Update Client 51201 The specified data not found in the MetaData
FIM CM Update Client 51202 The version specified in MetaData storage was not recognized
FIM CM Update Client 51203 The specified MetaData path was not found
FIM CM Update Client 51204 The specified name was not found in the MetaData schema.
FIM CM Update Client 51225 Unable to read the MetaData file
FIM CM Update Client 51232 The MetaData has been already loaded
FIM CM Update Client 51233 The MetaData has been protected by unsupported method
FIM CM Update Client 51234 Unable to load a schema from the MetaData
FIM CM Update Client 51235 The MetaData schema is not correct for this product version
FIM CM Update Client 51236 Invalid type
FIM CM Update Client 57345 The method '%1' is called by user '%2'
FIM CM Update Client 61440 Added object : Section [%1] ; Data [%2]
FIM CM Update Client 61441 Deleted data : Section [%1] ; Data [%2]
FIM CM Update Client 61442 Deleted object : [%1]
FIM CM Update Client 61443 Renamed object : [%1]
FIM CM Update Client 61444 Set data : Section [%1] ; Data [%2]

FIM Password Change Notification Service

Eventlog: Application

 

Source Event ID Message
PCNS Filter 1 Normal
PCNS Filter 2 Warning
PCNS Filter 3 Unexpected Error
PCNS Filter 4 Error
PCNS Filter 5 Success
PCNS Filter 2000 Unused
PCNS Filter 2001 The Password Change Notification Filter DLL has been registered with the system. It will be loaded on the next reboot.
PCNS Filter 2002 The Password Change Notification Filter DLL has been unregistered from the system. It will remain loaded until the next reboot.
PCNS Filter 4000 Unused
PCNS Filter 4001 The Password Change Notification Service is not started. The password change notification for %1 will not be sent.
PCNS Filter 6000 The request for notifications is invalid at this time. Password notifications will not be sent.
%n%1%2
PCNS Filter 6002 The Password Change Notification Filter DLL is not loaded in the LSASS process. Password notifications will not be sent.
PCNS Filter 6003 The Password Change Notification service executable "%1" is not digitally signed. The service will not be started and password notifications will not be sent.
PCNS Filter 6004 The Password Change Notification service executable "%3" failed while verifying the file signature. The service will not be started and password notifications will not be sent.
%n%1%2
PCNS Filter 6005 The Password Change Notification filter received an error while looking up account name %3. The notification will not be sent.%n
%n%1%2
PCNS Filter 6006 Error opening registry key %3
%n%1%2
PCNS Filter 6007 Error reading a value from the registry.
%nKey: %3
%nValue: %4
%nError: %1%2
PCNS Filter 6008 Error writing a value to the registry.
%nKey: %3
%nValue: %4
%nError: %1%2
PCNS Filter 6009 Error initializing the security descriptor.
%n%1%2
PCNS Filter 6010 Error initializing the LPC server.
%n%1%2
PCNS Filter 6011 Error stopping the LPC server.
%n%1%2
PCNS Filter 6013 The password filter failed to deliver the password to the Password Change Notification Service.
%n%n%1%2
%n%nThe password change notification for %3 will not be sent.
PCNS Filter 6014 Error importing the session key.
%n%1%2
PCNS Filter 6015 Error initializing the RPC binding to the service.
%n%1%2
PCNS Filter 6016 Error creating a thread to start the service.
%n%1%2
PCNS Filter 6017 Error accessing the Service Control Manager.
%n%1%2
PCNS Filter 6018 Error returned from the CryptoAPI.
%n%1%2
PCNS Filter 6019 Error allocating memory.
%n%1%2
PCNS Filter 6020 Error retrieving the path to the service executable.
%n%1%2
PCNS Filter 6021 The filter waited for the service to stop for %1 seconds, but service is still running. This request will be cancelled.
PCNS Filter 6023 Error copying string value.
%n%1%2
PCNS Filter 7000 An unexpected error occurred.
%n%1%2
PCNSSVC 1 Normal
PCNSSVC 2 Warning
PCNSSVC 3 Unexpected Error
PCNSSVC 4 Error
PCNSSVC 5 Success
PCNSSVC 2000 Unused
PCNSSVC 2001 The Password Change Notification Service started.
PCNSSVC 2002 The Password Change Notification Service stopped.
PCNSSVC 2003 A new notification queue has been created.
PCNSSVC 2004 An existing notification queue was found.
%n
%n%1 notifications read from disk
%n%2 notifications expired
%n%3 notifications have no targets
%n
%n%4 notifications queued for delivery
PCNSSVC 2005 The queue size for target '%1' has decreased below the configured warning level.
There are %2 notifications queued for this target.
The configured queue size warning level for this target is %3.
PCNSSVC 2100 The password notification has been delivered to all targets.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nTargets: %4
PCNSSVC 2101 Target '%1' is disabled. Password changes will not be queued for this target.
PCNSSVC 2102 Target '%1' is enabled. Password changes will be queued for this target.
PCNSSVC 2103 The configuration for Target '%1' has been deleted. %2 pending notifications have been updated to remove this target from the list.
PCNSSVC 2104 The Password Change Notification Service is stopping.
PCNSSVC 2105 The Password Change Notification Service is starting.
PCNSSVC 2106 The service configuration has changed. The new configuration is listed below.
%n
%nMaximum Queue Length: %1
%nMaximum Queue Age: %2 seconds
%nMaximum Notification Retries: %3
%nRetry Interval: %4 seconds
PCNSSVC 2107 The connection information for target '%1' has changed. The new connection information is listed below.
%n
%nServer: %2
%nService Principal Name: %3
%nAuthentication Service: %4
PCNSSVC 2108 The filter for target '%1' has changed. The new filter criteria is listed below.
%n
%nInclusion Group: %2
%nExclusion Group: %3
PCNSSVC 2109 The name translation object failed while translating %1 into a valid user name.
%n
%nThe object is being re-created to recover from this condition. No data has been lost.
PCNSSVC 2201 The password notification was received from the filter.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nTargets: %4
PCNSSVC 2202 The target '%1' requested a delay in notifications of %2 seconds. All notifications to this target will be delayed until %3.
PCNSSVC 2300 A thread has been started to send notifications to target '%2'
%n
%nThread ID: %1
PCNSSVC 2301 The thread for target '%2' has stopped.
%n
%nThread ID: %1
PCNSSVC 2302 The following notification has been sent.
%n
%nThread ID: %1
%nTracking ID: %2
%nUser GUID: %3
%nUser: %4
%nTarget: %5
%nDelivery Attempts: %6
PCNSSVC 2303 The password notification security filter has blocked the following notification.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nTarget: %4
PCNSSVC 2304 A samaccount name that mapped to mutliple objects was found and handled.
%n
%nSamaccount: %1
%nSID: %2
PCNSSVC 2305 Object guid was successfully retrieved using DsCrackName.
%n
%nSamaccount: %1
%nSID: %2
PCNSSVC 4000 Unused
PCNSSVC 4001 The configuration was loaded. There are no active targets configured. No passwords will be queued.
PCNSSVC 4002 The configuration was refreshed. There are no active targets configured. No passwords will be queued.
PCNSSVC 4003 The target server has not responded to a password notification.
The target server may be busy or not responding.
The Password Change Notification Service will continue to wait for a response.
%n
%nThread ID: %1
%nTracking ID: %2
%nUser GUID: %3
%nUser: %4
%nTarget: %5
%nDelivery Attempts: %6
PCNSSVC 4004 The target server has not responded to a status query.
The target server may be busy or not responding.
The Password Change Notification Service will continue to wait for a response.
%n
%nThread ID: %1
%nTarget: %2
PCNSSVC 4005 The queue size for target '%1' has reached or exceeded the configured warning level.
There are %2 notifications queued for this target.
The configured queue size warning level for this target is %3.
PCNSSVC 4100 The password notification could not be delivered to all targets.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nSuccessful Targets: %4
%nFailed Targets: %5
PCNSSVC 4101 The Active Directory object for account '%1' could not be found. This can happen if the account was deleted after the password was set, but before this password notification was received by this service. This can also happen if an object is created, which generates a new password notification, and then is immediately deleted.
%n
%nThis password notification will be discarded.
PCNSSVC 4200 This password notification has exceeded the retry limit for the target.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nTarget: %4
PCNSSVC 4201 There are no active targets configured. The following password notification will not be queued for delivery.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
PCNSSVC 4202 While loading the queue file from disk, all targets scheduled for the following password
notification have been disabled or deleted from the configuration. This notification is being
discarded.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
PCNSSVC 4203 While refreshing the server configuration, all targets scheduled for the following password
notification have been disabled or deleted from the configuration. This notification is being
discarded.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
PCNSSVC 4204 While refreshing the server configuration, the following password
notification has expired or exceeds the configured maximum queue length.
This notification is being discarded.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nCompleted Targets: %4
%nIncomplete Targets: %5
PCNSSVC 4205 While loading the queue file from disk, the following password notification has expired.
This notification is being discarded.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nCompleted Targets: %4
%nIncomplete Targets: %5
PCNSSVC 4206 The target '%1' requested an invalid delay in notifications of %2 seconds. The delay has been adjusted to %3 seconds. All notifications to this target will be delayed until %4.
PCNSSVC 4207 The target '%1' requested a negative delay in notifications of %2 seconds. This will be ignored and notifications will continue at the current retry or keep-alive interval.
PCNSSVC 4208 The following password notification has expired or exceeds the configured maximum queue length.
This notification is being discarded.
%n
%nTracking ID: %1
%nUser GUID: %2
%nUser: %3
%nCompleted Targets: %4
%nIncomplete Targets: %5
PCNSSVC 4301 A negative acknowledgement was received for the following notification:
%n
%nThread ID: %1
%nTracking ID: %2
%nUser GUID: %3
%nUser: %4
%nTarget: %5
%nDelivery Attempts: %6
PCNSSVC 6000 The configuration information does not exist in Active Directory. The service will stop.
PCNSSVC 6001 An existing notification queue was found.
%n
%n%1 notifications read from disk
%n%2 notifications expired
%n%3 notifications have no targets
%n
%n%4 notifications queued for delivery
%n
%nThe remainder of the queue was corrupt. The file has been saved as %5. A new queue has been created.
PCNSSVC 6002 The handshake between the password filter and the service failed. The service will stop.
%n
%n%1%2
PCNSSVC 6004 An error occurred translating %3 into a valid user name.
%n
%n%1%2
PCNSSVC 6005 An error occurred decrypting the password for object %3.
%n
%n%1%2
PCNSSVC 6006 Error opening registry key %3
%n
%n%1%2
PCNSSVC 6007 Error reading a value from the registry.
%nKey: %3
%nValue: %4
%nError: %1%2
PCNSSVC 6008 Error writing a value to the registry.
%nKey: %1
%nValue: %2
%nError: %3
PCNSSVC 6009 The signature in the notification header is invalid. This notification is being discarded with an Access Denied error.
%n%1%2
PCNSSVC 6010 The SID in the notification structure is invalid. This notification is being discarded with an Access Denied error.
%n%1%2
PCNSSVC 6011 The number of bytes requested from the queue file did not match the number of bytes read.
%n
%nBytes Requested: %1
%nBytes Read: %2
PCNSSVC 6012 An error occurred seeking to offset %3 in the queue file.
%n%1%2
PCNSSVC 6013 An error occurred while reading the queue file.
%n%1%2
PCNSSVC 6014 The signature in the queue file header is invalid.
The queue file will be renamed and a new one will be created.
PCNSSVC 6015 The queue file is invalid. The hash length in the queue file header does not match the hash length returned by the CSP.
The queue file will be renamed and a new one will be created.
PCNSSVC 6016 The queue file header is invalid. The queue file will be renamed and a new one will be created.
PCNSSVC 6017 The queue file entry at offset %1 is invalid. The queue file will be renamed and a new one will be created.
PCNSSVC 6018 An error occurred while writing the queue file.
%n%1%2
PCNSSVC 6022 Error returned from the CryptoAPI.
%n%1%2
PCNSSVC 6023 Error copying string value.
%n%1%2
PCNSSVC 6024 The data is very large and cannot be processed. The notification will be discarded.
%n%1
%nAccount: %2
PCNSSVC 6025 Password Change Notification Service received an RPC exception attempting to deliver a notification.
%11
%nThread ID: %1
%nTracking ID: %2
%nUser GUID: %3
%nUser: %4
%nTarget: %5
%nDelivery Attempts: %6
%nQueued Notifications: %7
%n%8 - %9
%n%n%10
PCNSSVC 6026 This machine is not a domain controller. The Password Change Notification Service will stop.
PCNSSVC 6027 The service failed to create an RPC binding for target '%4'. The target is being disabled. Password changes will not be queued for this target.
%n
%nThread ID: %3
%n%1%2
PCNSSVC 6028 A target thread terminated unexpectedly. The service will shutdown.
PCNSSVC 6029 There are more than %1 targets configured in Active Directory, which exceeds the maximum supported by the service. Target %2 was not loaded, and passwords will not be queued for that target.
PCNSSVC 6030 The configuration container has been deleted from Active Directory. The service will stop.
PCNSSVC 6031 The service was unable to open the queue for target '%2'. The thread will stop.
%n
%nThread ID: %1
PCNSSVC 6032 The filter configuration for target '%1' is invalid. This will result in ALL notifications
being filtered for this target. Verify that the target object has correct values for the
Inclusion and Exclusion Security Identifiers (SID's).
PCNSSVC 6033 The RPC listener thread exited unexpectedly. The service will stop.
%n%1%2
PCNSSVC 6034 The hash length calculated for this entry does not match the hash length in the queue file header. The entry will be discarded.
PCNSSVC 6035 The registry value '%1' is not defined as type %2. This value will be ignored and the default value %3 will be used.
PCNSSVC 6036 Password Change Notification Service received an RPC exception querying the status of the target.
%6
%nThread ID: %1
%nTarget: %2
%n%3 - %4
%n%n%5
PCNSSVC 6037 An error occurred processing a password change notification received from Active Directory.
The notification was discarded by the Password Change Notification Service.
%n
%nUser: %3
%n%1%2
PCNSSVC 6038 An error occurred converting an object SID into an object GUID.
%n
%nSID: %3
%n%1%2
PCNSSVC 6039 An error occurred calling ADSI to retrieve the object.
%n
%nAdsPath: %3
%n%1%2
PCNSSVC 7000 An unexpected error occurred.
%n%1%2

FIM Service

 

FIM Synchronization Service

 

Source Event ID Message
FIMSynchronizationService 1 Management Agent Run Profile
FIMSynchronizationService 2 Database
FIMSynchronizationService 3 Server
FIMSynchronizationService 4 Web Service
FIMSynchronizationService 5 Security
FIMSynchronizationService 6 Server
FIMSynchronizationService 7 MA Extension
FIMSynchronizationService 8 Password Synchronization
FIMSynchronizationService 100 Success
FIMSynchronizationService 2000 Unused
FIMSynchronizationService 2001 The service was started successfully.
FIMSynchronizationService 2002 The service was stopped successfully.
FIMSynchronizationService 2003 Number of retry passes needed to complete run:%n
Connector Space : "%1"%n
Metaverse : "%2"%n
FIMSynchronizationService 2004 The %1 failed to update the timestamp. Verify that SQL Server is running.%n
Error Code: %2%n
Error Message: %3%n
FIMSynchronizationService 4000 Unused
FIMSynchronizationService 6000 The management agent "%1" failed to run because the credentials were invalid.%n
%n
User Action%n
Verify the credentials and configuration for the management agent.
FIMSynchronizationService 6001 The management agent "%1" failed on run profile "%2" because
a connection could not be established to the server.
FIMSynchronizationService 6002 The management agent "%1" failed on run profile "%2" because
the target file "%3" is already open.
FIMSynchronizationService 6003 The evaluation period for this copy of %1 has ended. To continue using this version of %1, please purchase and install the complete product.
FIMSynchronizationService 6004 The management agent "%1" failed on run profile "%2" because
of an unspecified server error.%n
Additional Information%n
%n
%3
FIMSynchronizationService 6005 The management agent "%1" failed on run profile "%2" because
of an unspecified management agent error.%n
Additional Information%n
%n
%3
FIMSynchronizationService 6006 The management agent "%1" failed on run profile "%2" because
the step type specified is a delta import and a full import is required.
FIMSynchronizationService 6007 The management agent "%1" failed on run profile "%2" because
the domain controller could not be contacted.
FIMSynchronizationService 6008 The management agent "%1" failed on run profile "%2" because
the specified code page does not match the code page of the file.%n
%n
User Action%n
Verify the code page configuration for the management agent.
FIMSynchronizationService 6009 The management agent "%1" failed on run profile "%2" because
the management agent configuration is invalid.
FIMSynchronizationService 6010 The management agent "%1" failed on run profile "%2" because
the step type of the file being resumed from does not match the step type
of the run.%n
The file name is "%3".%n
%n
User Action%n
Verify the log file configuration for this run profile step is correct.
FIMSynchronizationService 6011 The management agent "%1" failed on run profile "%2" because
the management agent has detected a partition rename.%n
%n
User Action%n
Refresh and verify the partition configuration for the management agent.
FIMSynchronizationService 6012 The management agent "%1" failed on run profile "%2" because
the management agent did not import any objects during the run step.
FIMSynchronizationService 6013 The management agent "%1" failed on run profile "%2" because
the management agent did not import any objects during the run step.%n
The input file name is "%3".
FIMSynchronizationService 6014 The management agent "%1" failed on run profile "%2" because
the management agent is not configured for a step type of delta import.
FIMSynchronizationService 6015 The management agent "%1" failed on run profile "%2" because
the management agent has detected that a partition has been deleted.%n
%n
User Action%n
Refresh and verify the partition configuration for the management agent.
FIMSynchronizationService 6016 The management agent "%1" failed on run profile "%2" because
the management agent has detected that the database schema has changed.%n
%n
User Action%n
Refresh and verify the schema for the management agent.
FIMSynchronizationService 6017 The management agent "%1" failed on run profile "%2" because
the management agent has detected that a partition has not been configured
for the operation.%n
%n
User Action%n
Refresh and verify the partition configuration for the management agent.
FIMSynchronizationService 6018 The management agent "%1" failed on run profile "%2" because
the management agent was unable to connect to the source database
due to insufficient permissions.
%n
User Action%n
Verify that the account used to access the database has sufficient permissions.
FIMSynchronizationService 6019 The management agent "%1" failed on run profile "%2" because
the management agent was unable to open the database table.
%n
User Action%n
Verify the permissions for the database table.
FIMSynchronizationService 6020 The management agent "%1" failed on run profile "%2" because a
partition specified in the configuration could not be located.%n
%n
User Action%n
Refresh and verify the partition configuration for the management agent
and the target partition.
FIMSynchronizationService 6021 The management agent "%1" failed to run profile "%2" because it is configured
for import operations only.
FIMSynchronizationService 6050 The management agent "%1" failed on run profile "%2" because
of connectivity issues.%n
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6051 The management agent "%1" failed on run profile "%2" because the
user terminated the operation.%n
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6052 The management agent "%1" failed on run profile "%2" because
the service was shutdown.
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6053 The management agent "%1" run profile "%2" exceeded the object limit
on a step.
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6054 The management agent "%1" failed on run profile "%2" because
there were errors reading objects from the connected data source.%n
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6055 The management agent "%1" failed on run profile "%2" because the
export operation encountered write errors.
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6056 The management agent "%1" failed on run profile "%2" because
the server encountered errors.
FIMSynchronizationService 6057 The management agent "%1" failed on run profile "%2" because
the management agent encountered errors.
FIMSynchronizationService 6058 The management agent "%1" failed on run profile "%2" because
the input file could not be found.
The input file name is "%3".%n
%n
User Action%n
Verify that the input file is in the management agent's working directory.
FIMSynchronizationService 6059 The management agent "%1" failed on run profile "%2" because
the management agent was unable to read or write to the file.%n
%n
User Action%n
Verify the available space on the drive partition and that the file
is not corrupted.
FIMSynchronizationService 6060 The management agent "%1" run profile "%2" completed a step with errors.%n
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6061 The management agent "%1" failed on run profile "%2" because
the run step error limit of 5000 was exceeded.
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6062 The management agent "%1" failed on run profile "%2" because the
disk containing the MaData working directory is full.
FIMSynchronizationService 6063 The management agent "%1" failed on run profile "%2" because
the management agent was unable to access the file due to insufficient
permissions.%n
The file name is "%3".
FIMSynchronizationService 6064 The management agent "%1" failed on run profile "%2" because
the file could not be opened.%n
The file name is "%3".
FIMSynchronizationService 6065 The management agent "%1" failed on run profile "%2" because
parsing errors were detected at the following location:%n
%3
FIMSynchronizationService 6066 The management agent "%1" failed on run profile "%2" because
the management agent was unable to convert data to or from the
specified codepage at the following location:%n
%3
FIMSynchronizationService 6067 The management agent "%1" failed on run profile "%2" because
the changelog is not enabled on the data source server.
FIMSynchronizationService 6068 The management agent "%1" failed on run profile "%2" because
the extension "%3" explicitly ended the run.%n
%n
The stack trace is: %n
%4
FIMSynchronizationService 6069 The management agent "%1" failed on run profile "%2" because
the management agent configuration is invalid.
FIMSynchronizationService 6070 The management agent "%1" failed on run profile "%2" because
null characters were embedded in the input file.%n
%n
User Action%n
Verify the input file and the code page configuration for the management agent.
FIMSynchronizationService 6071 The management agent "%1" failed on run profile "%2" because
of a database deadlock.
FIMSynchronizationService 6072 The management agent "%1" failed on run profile "%2" because
the system is out of memory.
FIMSynchronizationService 6073 The management agent "%1" failed on run profile "%2" because
the database or database log file is full.%n
%n
User Action%n
Verify the available space on the partition hosting the database or
increase the database log file size.
FIMSynchronizationService 6074 The management agent "%1" failed on run profile "%2" because
a changelog with an invalid order was detected on the data source server.
%n
User Action%n
Run the management agent with a step type of full import.
FIMSynchronizationService 6075 The management agent "%1" failed on run profile "%2" because
the connection to the server database was lost.%n
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
Verify that SQL Server is running.
FIMSynchronizationService 6076 The management agent "%1" run profile "%2" exceeded the deletion limit
on a step.
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6077 The management agent "%1" failed on run profile "%2" because the extension
timed out.
FIMSynchronizationService 6078 The management agent "%1" failed on run profile "%2" because
the header row in the file and the configured header row differed
at the following location:%n
%3
FIMSynchronizationService 6100 The management agent "%1" step execution completed on run profile "%2"
with errors.%n
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6105 The management agent "%1" step execution completed on run profile "%2" but
some objects had exported changes that were not confirmed on import.%n
%n
Additional Information%n
Discovery Errors : "%3"%n
Synchronization Errors : "%4"%n
Metaverse Retry Errors : "%5"%n
Export Errors : "%6"%n
Warnings : "%7"%n
%n
User Action%n
View the management agent run history for details.
FIMSynchronizationService 6125 The management agent "%1" completed run profile "%2" with a delta import
step type before completing a full import.%n
%n
User Action%n
Run the management agent with a step type of full import.
FIMSynchronizationService 6126 The management agent "%1" completed run profile "%2" with a delta import or
delta synchronization step type. The rules configuration has changed since
the last full import or full synchronization.%n
%n
User Action%n
To ensure the updated rules are applied to all objects, a run with step type
of full import and full synchronization should be completed.
FIMSynchronizationService 6127 The management agent "%1" completed run profile "%2" with a delta import or
delta synchronization step type. The rules configuration has changed since
the last full synchronization.%n
%n
User Action%n
To ensure the updated rules are applied to all objects, a run with step type of
full synchronization should be completed.
FIMSynchronizationService 6150 The management agent "%1" failed on run profile "%2". The run step stopped
because the metaverse rules extension was not configured.%n
%n
User Action%n
Verify the configuration for the metaverse rules extension.
FIMSynchronizationService 6151 The management agent "%1" failed on run profile "%2". The run step stopped
because the management agent rules extension was not configured.%n
%n
User Action%n
Verify the configuration for the management agent rules extension in the
Management Agent Designer.
FIMSynchronizationService 6152 The management agent "%1" failed on run profile "%2". The run step stopped
because a required rules extension "%3" could not be loaded.%n
%n
User Action%n
Verify that the rules extension is located in the Extensions directory.
FIMSynchronizationService 6154 The management agent "%1" failed on run profile "%2". The run step stopped because
there are duplicate extension object implementations in the specified .NET
assembly ("%3").
FIMSynchronizationService 6155 The management agent "%1" failed on run profile "%2". The run step stopped because
the extension object in the assembly "%3" could not be instantiated and
the stack trace is: %n
%n
%4
FIMSynchronizationService 6156 The management agent "%1" failed on run profile "%2". The run step stopped because
access was denied to the extension dll "%3".
FIMSynchronizationService 6157 The management agent "%1" failed on run profile "%2". The run step stopped because
the extension dll "%3" is not a valid assembly and could not be loaded.
FIMSynchronizationService 6158 The management agent "%1" failed on run profile "%2". The run step stopped because
the extension dll "%3" could not be found.%n
%n
User Action%n
Verify that the rules extension specified is located in the Extensions
directory.
FIMSynchronizationService 6159 The management agent "%1" failed on run profile "%2" because of a problem
with the initialize method on the extension object. The extension dll is
"%3" and the stack trace is: %n
%n
%4
FIMSynchronizationService 6160 The management agent "%1" failed on run profile "%2" because
the extension "%3" could not be loaded. A required dependency was missing.
FIMSynchronizationService 6161 The management agent "%1" failed on run profile "%2" because the extension "%3"
does not contain a class implementing the required (IMVSynchronization or
IMASynchronization) interface in the assembly.
FIMSynchronizationService 6162 The management agent "%1" failed on run profile "%2" because
the rules extension has been updated while a run was in progress.%n
%n
User Action%n
To ensure the updated rules are applied to all objects, a run with step type of
full synchronization should be completed.
FIMSynchronizationService 6163 The management agent "%1" failed on run profile "%2" because
the extension "%3" does not implement a required entry point.%n
%n
User Action%
Verify all rules configured as rules extensions are implemented in this rules
extension.
FIMSynchronizationService 6164 The management agent "%1" failed on run profile "%2". The run step stopped because a
configured extension dll for this management agent was not found.%n
%n
User Action%n
Verify that the extension is located in the Extensions directory.
FIMSynchronizationService 6165 The management agent "%1" failed on run profile "%2". The run step stopped because
a configured extension dll for this management agent is not a valid assembly
and could not be loaded.
FIMSynchronizationService 6166 The management agent "%1" failed on run profile "%2". The run step stopped
because a configured extension for this management agent could not be loaded.%n
%n
User Action%n
Verify that the extension is located in the Extensions directory.
FIMSynchronizationService 6167 The management agent "%1" failed on run profile "%2" because a configured
extension for this management agent does not contain a class implementing
the required interface.
FIMSynchronizationService 6168 The management agent "%1" failed on run profile "%2". The run step stopped because
there are duplicate extension object implementations in a configured assembly
for this management agent.
FIMSynchronizationService 6169 The management agent "%1" failed on run profile "%2". The run step stopped because
the extension object for the management agent could not be instantiated.
FIMSynchronizationService 6170 The management agent "%1" failed on run profile "%2" because
a configured extension for this management agent could not be loaded.
A required dependency was missing.
FIMSynchronizationService 6172 The management agent "%1" failed on run profile "%2". The run step stopped because
access was denied to a configured extension for this management agent.
FIMSynchronizationService 6173 The management agent "%1" failed on run profile "%2" because
a configured extension for this management agent does not implement a
required entry point.
FIMSynchronizationService 6174 The management agent "%1" failed on run profile "%2" because
a configured extension for this management agent explicitly ended the run.
FIMSynchronizationService 6201 The server encryption keys have been successfully created.%n
%n
User Action%n
Store a backup of the encryption keys in a secure location.
This will be required for server restore operations.
FIMSynchronizationService 6202 The server encryption keys could not be created.%n
%n
User Action%n
Verify that the service account has permissions to the following registry key:%n
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service
FIMSynchronizationService 6203 The service encryption keys could not be loaded.%n
%n
User Action%n
Verify that the service account has permissions to the following registry key:%n
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service
FIMSynchronizationService 6204 The server encountered an unexpected error when loading the database.
FIMSynchronizationService 6205 The server encountered an error when performing a move for the object "%1".
FIMSynchronizationService 6206 The service encryption keys could not be found.%n
%n
User Action%n
Verify that the service account has permissions to the following registry key:%n
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service%n
%n
If the problem persists, run setup and restore the encryption keys
from backup.
FIMSynchronizationService 6207 The service encryption keys are corrupt.%n
%n
User Action%n
Run setup and restore the encryption keys from backup.
FIMSynchronizationService 6208 The server encryption keys could not be accessed.%n
%n
User Action%n
Verify that the service account has permissions to the following registry key:%n
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service%n
%n
If the problem persists, run setup and restore the encryption keys
from backup.
FIMSynchronizationService 6209 The service was unable to start because it failed to authenticate to
the database.%n
%n
User Action%n
Verify that SQL Server is running, that the service account has
permissions to access the database and the SQL Server service account
password is correct.
FIMSynchronizationService 6210 The service is stopping because it is unable to authenticate to the database.%n
%n
User Action%n
Verify that SQL Server is running, that the service account has
permissions to access the database and the SQL Server service account
password is correct.
FIMSynchronizationService 6211 The service was unable to start because the version of the database does not
match the version of the product.
FIMSynchronizationService 6212 The service is stopping because the version of the database does not match
the version of the product.
FIMSynchronizationService 6213 The service was unable to start because it was unable to access the database.%n
%n
User Action%n
Verify that the service account has permissions to access the database.
FIMSynchronizationService 6214 The service is stopping because it is unable to access the database.%n
%n
User Action%n
Verify that SQL Server is running and that the service account has
permissions to access the database.
FIMSynchronizationService 6215 The service was unable to start because it failed to open the database.%n
%n
User Action%n
Verify that SQL Server is running, that the service account has permissions
to access the database and that the %1
database is located on the server.
FIMSynchronizationService 6216 The service is stopping because it failed to open the database.%n
%n
User Action%n
Verify that SQL Server is running, that the service account has permissions
to access the database and that the %1
database is located on the server.
FIMSynchronizationService 6217 The service was unable to start because the service account does not
have database owner permissions.%n
%n
User Action%n
Verify that the service account has database owner permissions for the
%1 database.
FIMSynchronizationService 6218 The service is stopping because the service account does not have database
owner permissions.%n
%n
User Action%n
Verify that the service account has database owner permissions for the
%1 database.
FIMSynchronizationService 6219 The service was unable to start because a connection to the SQL Server
could not be established.%n
%n
Additional Details%n
The following error information was returned by the provider:%n
%n
%1
FIMSynchronizationService 6220 The service was unable to start because a connection to the SQL Server
could not be reestablished.%n
%n
Additional Details%n
The following error information was returned by the provider:%n
%n
%1
FIMSynchronizationService 6221 The service was unable to start because it failed to connect to the database.%n
%n
User Action%n
Verify that SQL Server is running and that the service account has
permissions to access the database.
FIMSynchronizationService 6222 The service is stopping because it failed to connect to the database.%n
%n
User Action%n
Verify that SQL Server is running and that the service account has
permissions to access the database.
FIMSynchronizationService 6223 The server encryption keys do not match the database instance or keyset id.
The encryption keys should be restored from a backup copy by running setup.
FIMSynchronizationService 6224 The service was unable to start because the version of the database is
newer than the version of the binaries installed. In order to enable the
server to function normally, install the latest update.
FIMSynchronizationService 6300 The server encountered an unexpected error:%n
%n
"%1"
FIMSynchronizationService 6301 The server encountered an unexpected error in the synchronization engine:%n
%n
"%1"
FIMSynchronizationService 6302 The server encountered an unexpected error in the management agent
controller when starting a run.%n
%n
"%1"
FIMSynchronizationService 6304 The server encountered an unexpected memory allocation error.%n
%n
"%1"
FIMSynchronizationService 6305 The server encountered an unexpected error searching for connector space
objects.%n
%n
"%1"
FIMSynchronizationService 6306 The server encountered an unexpected error while performing an operation for
the client.%n
%n
"%1"
FIMSynchronizationService 6307 The server encountered an unexpected error searching for metaverse objects.%n
%n
"%1"
FIMSynchronizationService 6308 The server encountered an unexpected error enumerating management agents.%n
%n
"%1"
FIMSynchronizationService 6309 The server encountered an unexpected error while performing an operation for
a management agent.%n
%n
"%1"
FIMSynchronizationService 6310 The server encountered an unexpected error while performing an operation
for the joiner.%n
%n
"%1"
FIMSynchronizationService 6311 The server encountered an unexpected error while performing a callback
operation.%n
%n
"%1"
FIMSynchronizationService 6312 The server encountered an unexpected error while performing an operation for
a rules extension.%n
%n
"%1"
FIMSynchronizationService 6313 The server encountered an unexpected error creating performance counters for
management agent "%1".%n
Performance counters will not be available for this management agent.
FIMSynchronizationService 6314 The server encountered an unexpected error renaming performance counters for
management agent "%1".%n
The performance counters could not be renamed.
FIMSynchronizationService 6315 The server was unable to backup all modified files in the extensions directory.
%n
%1
FIMSynchronizationService 6316 The server encountered an unexpected error restoring rules extension:%n
"%1"
FIMSynchronizationService 6317 The computer name in the database does not match the computer name.%n
%n
User Action:%n
Run miisactivate.exe to update the server configuration to match the new
computer name.
FIMSynchronizationService 6318 The server encountered an unexpected error loading the configuration for
management agent "%1".
FIMSynchronizationService 6319 The server encountered an unexpected error loading the configuration for the
metaverse.
FIMSynchronizationService 6320 The management agent "%1" encountered an error. The Terminate method for
rules extension "%2" threw an exception.%n
The stack trace is:%n
%n
"%3"
FIMSynchronizationService 6321 The server encountered an error. The Terminate method for
metaverse rules extension "%1" threw an exception.%n
The stack trace is:%n
%n
"%2"
FIMSynchronizationService 6322 The server encountered an error because the connection to SQL Server failed.
FIMSynchronizationService 6323 The server encountered an error because SQL Server is out of disk space.%n
%n
User Action%n
Verify the available space on the partition hosting the database.
FIMSynchronizationService 6324 The server encountered an unexpected error and stopped.%n
%n
"%1"
FIMSynchronizationService 6325 The server encountered a problem while clearing the export error state
for objects that are no longer in error. These entries will be reprocessed
the next time an export run step is performed for management agent "%1".
FIMSynchronizationService 6326 The server encountered a problem while removing placeholder objects that
are no longer referenced. These objects will be reprocessed the next time
the connector space for the management agent "%1" is updated.
FIMSynchronizationService 6327 The server encountered a problem while processing data. A locking error was
encountered and the operation will require a retry at a subsequent time
to fix the problem.%n
%n
"%1"
FIMSynchronizationService 6328 The server encountered an error while attempting to perform a set/change
password operation.%n
%n
"%1"
FIMSynchronizationService 6329 An unexpected error has occurred during a password set operation.
%n
"%1"
FIMSynchronizationService 6330 An error occured while calling EndConnectionToServer for a password operation.
This has no effect on whether the password operation completed successfully or
not.
%n
%nErrorCode: %1
%nErrorString: %2
FIMSynchronizationService 6331 A update on the configuration of a MA or MV failed to replicate to a target connector directory that is capable
of storing MA/MV configurations. As a result, the MA/MV configuration data in this connector directory is not up to date.
Please correct the condition that causes the error, and triggers a resync by updating the password information of the target MA.
%n
%nAdditional information:
%nError Code: %1
%nError Message: %2
%nOperation: %3
%nName of the MA to replicate: %4
%nGuid of the MA to replicate: %5
%nName of the target MA: %6
%nGuid of the target MA: %7
FIMSynchronizationService 6401 The management agent controller encountered an unexpected error.%n
%n
"%1"
FIMSynchronizationService 6500 %1
FIMSynchronizationService 6600 A user was denied access for an operation.%n
%n
Additional Details%n
User: "%2"
Operation attempted:"%1"
FIMSynchronizationService 6800 The password management extension encountered an error.%n
The stack trace is:%n
%n
"%1"
FIMSynchronizationService 6801 The extensible extension returned an unsupported error.%n
The stack trace is:%n
%n
"%1"
FIMSynchronizationService 6802 The extensible management agent encountered an error while deleting the run step file:%n
%n
"%1"
FIMSynchronizationService 6803 The management agent "%1" failed on run profile "%2" because
the server encountered errors.
FIMSynchronizationService 6804 Unable to delete temporary shadow cache directory:
%n
"%1"
FIMSynchronizationService 6900 The server encountered an unexpected error while processing a password change
notification:%n
%n
"%1"
FIMSynchronizationService 6901 A password synchronization set operation has failed in a target connected data
source.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
%nErrorCode: %7
%nErrorString: %8
FIMSynchronizationService 6902 A password synchronization set operation was successful in a target connected
data source.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
FIMSynchronizationService 6903 A password notification was received from a Password Change Notification
Service.
%n
%nAdditional information:
%nReference ID: %1
%nPassword Last Change Time: %2
%nSource Object GUID: %3
%nDelivery Attempt: %4
%nSource User Name: %5
%nServer: %6
FIMSynchronizationService 6904 A password notification was received but could not be processed because a
corresponding connector space object could not be located.
%n
%nAdditional information:
%nReference ID: %1
%nSource Object GUID: %2
%nSource User Name: %3
FIMSynchronizationService 6905 A password notification was received but could not be processed because the
corresponding object is a disconnector.
%n
%nAdditional information:
%nReference ID: %1
%nSource Object GUID: %2
%nSource DN: %3
%nSource MA Name: %4
FIMSynchronizationService 6906 A password notification was received but could not be processed because the
corresponding object is not linked to any connector space objects in target
management agents.
%n
%nAdditional information:
%nReference ID: %1
%nSource Object GUID: %2
%nSource DN: %3
%nSource MA Name: %4
FIMSynchronizationService 6907 A password notification was successfully staged for synchronization.
%n
%nAdditional information:
%nReference ID: %1
%nTarget Object GUID: %2
%nTarget MA Name: %3
%nTarget DN: %4
FIMSynchronizationService 6908 The password synchronization set operation has exceeded the maximum retry limit
for this target connected data source.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
FIMSynchronizationService 6909 A heartbeat has been received from the Password Change Notification Service on
the following Active Directory domain controller:
%nServer: %1
FIMSynchronizationService 6910 Password synchronization has been enabled.
FIMSynchronizationService 6911 Password synchronization has been disabled.
FIMSynchronizationService 6912 Password notification was received for account (%6) but was not processed
because it is the %1 account.
%n
%nAdditional information:
%nReference ID: %2
%nPassword Last Change Time: %3
%nSource Object GUID: %4
%nDelivery Attempt: %5
%nSource User Name: %6
FIMSynchronizationService 6913 The password notification caller has successfully authenticated to be a Domain
Controller of the following domain:
%nDomain: %1
%nServer: %2
FIMSynchronizationService 6914 The connection from a password notification source failed because it is not a
Domain Controller service account.
%nDomain: %1
%nServer: %2
FIMSynchronizationService 6915 An error has occurred during authentication to the password notification
source.
%n
"%1"
FIMSynchronizationService 6916 %1 has detected that the database has been restored
from backup. Password synchronization is disabled.
%n
%nUser Action
%nIf password synchronization was enabled before the database was restored, in
order to avoid duplicate password synchronization set events, verify the
password synchronization queue and clear any redundant password events before
enabling password synchronization.
FIMSynchronizationService 6917 A password notification was received but was not processed because the maximum
number of changes for this connector space object in a 24-hour period has been
reached.
%n
%nAdditional information:
%nReference ID: %1
%nSource Object GUID: %2
%nSource DN: %3
%nSource MA Name: %4
%nMaximum changes: %5
%nCurrent change: %6
FIMSynchronizationService 6918 A password notification was received but was not processed because the
timestamp was out of date. This could be caused by the Domain Controller
sending password changes out of order.
%n
%nAdditional information:
%nLast password timestamp: %1
%nCurrent password timestamp: %2
%nReference ID: %3
%nSource Object GUID: %4
%nSource DN: %5
%nSource MA Name: %6
FIMSynchronizationService 6919 A password synchronization set operation was not performed because the timestamp
was out of date. A timestamp could become out of date if
Server has already received a newer password synchronization event, or the
password has been set via WMI at a more recent time.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
FIMSynchronizationService 6920 An unexpected error has occurred on a password synchronization thread and
caused it to exit.
%n
"%1"
FIMSynchronizationService 6921 The password synchronization set operation was not processed because password
management was not enabled on the target management agent.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
%n
%nUser Action
%nVerify the password synchronization settings for the source and target
management agents are correct.
FIMSynchronizationService 6922 The password synchronization set operation was not processed because password
management is not configured on the target management agent.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
%n
%nUser Action
%nVerify the password synchronization settings for the source and target
management agents are correct.
FIMSynchronizationService 6923 The password synchronization set operation was not processed because the target
connector space object could not be found in the connected directory.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
FIMSynchronizationService 6924 The password synchronization history clear operation was completed
successfully.
%n%1 entries were cleared from the source and target history table.
%nUser: %2
FIMSynchronizationService 6925 The password queue clear operation was completed successfully.
%n%1 entries were cleared from the password synchronization queue.
%nUser: %2
FIMSynchronizationService 6926 A password notification was received but could not be processed because the
corresponding management agent is not enabled as a password synchronization
source or has no target management agents configured.
%n
%nAdditional information:
%nReference ID: %1
%nSource Object GUID: %2
%nSource DN: %3
%nSource MA Name: %4
%n
%nUser Action
%nTo synchronize passwords for objects in this partition, ensure that password
synchronization is enabled the partition and one or more target management
agents are selected.
FIMSynchronizationService 6927 The password synchronization set operation failed because the password does not
satisfy the password policy of the target system.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
%n
%nUser Action
%nEnsure the password policy of the target system is compatible with the password
policy of the source system.
FIMSynchronizationService 6928 The password synchronization set operation failed because the target
management agent's password extension is not configured to support password set
operations.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
%n
%nUser Action
%nVerify the password extension for the target management agent supports
password set operations and enable this option in the management agent
configuration.
FIMSynchronizationService 6929 The password synchronization set operation was not processed because the
management agent of the target connector space object was deleted.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget MA ID: %4
%nRetry Count: %5
FIMSynchronizationService 6930 The password synchronization set operation was not processed because the
password was found to be invalid.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget MA Name: %4
%nRetry Count: %5
%n
%nUser Action
%nVerify that the SQL database has not been tampered with.
FIMSynchronizationService 6931 A new MA was added to the list of targets for password sync for objects in a partition.
%n
%nAdditional information:
%nSource MA Name: %1
%nSource Partition Name: %2
%nTarget MA Name: %3
FIMSynchronizationService 6932 The password synchronization set operation was not processed because the target
connector space object could not be found in the connected directory or it was
provisioned to the connected directory but has not been confirmed by an import run.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
FIMSynchronizationService 6933 The password synchronization set operation was not processed because the target
entry was found to be corrupted.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget MA ID: %4
%nCorrupted Data: %5
FIMSynchronizationService 6934 The password synchronization set operation was not processed because the target
connector space object has not yet been exported to the connected directory.
%n
%nAdditional information:
%nTracking ID: %1
%nReference ID: %2
%nTarget Object GUID: %3
%nTarget DN: %4
%nTarget MA Name: %5
%nRetry Count: %6
FIMSynchronizationService 6935 A password notification was received and matched to a connector space object
that is a placeholder. Placeholder objects are not real and cannot be the target
of a password change notification. The server will continue searching for other
objects that may match the password notification.
%n
%nAdditional information:
%nReference ID: %1
%nSource Object GUID: %2
%nSource MA Object GUID: %3
%nSource DN: %4
%nSource MA Name: %5

 


 

See also