View service event log
The Adaxes Windows event log contains technical error, warning, and information messages generated by the Adaxes service and several other Adaxes components.
Unlike the general log which records user activity, automation workflows, and other operations performed via Adaxes, the event log records events related to internal Adaxes mechanisms and background processes. Monitoring the event log can help diagnose issues with your Adaxes deployment before they affect your environment.
To view the log:
-
On the computer where Adaxes service is installed, open Windows Start menu.
-
Type Event Viewer and press Enter.
-
Expand Applications and Services Logs and select Adaxes.
Event ID tables
Every event logged by Adaxes has a unique identifier. Event IDs are grouped into categories. For example, events numbered 1600 through 1612 are related to approval requests, 2800 through 2813 – to licensing, and so on. Most of the events are logged by the Adaxes service, but there is a small set of events that are logged by the ADSI provider, the backup/restore tool, and the Adaxes web server.
Directory
Events related to interaction between Adaxes service and your directory – managed domains, Exchange servers, and Microsoft 365.
Common
Events that can be logged regardless of the directory type.
-
ID
-
Level
-
Details
-
1000
-
Error
-
An error has occurred while initializing services for a managed domain.
-
1001
-
Warning
-
Failed to get the list of global and universal groups where a specific user is a member.
-
1002
-
Error
-
Failed to update the members of a specific rule-based group.
-
1003
-
Information
-
A scheduled task configured to run once was deleted successfully.
-
1004
-
Warning
-
One or more scheduled tasks were interrupted unexpectedly.
-
1005
-
Error
-
Failed to execute a scheduled task for a specific object. Error details are available in the event description.
-
1006
-
Error
-
Failed to recover the execution status of a scheduled task after it was interrupted.
-
1007
-
Error
-
Failed to recover the execution status of a rule-based group membership update after it was interrupted.
-
1008
-
Error
-
Failed to protect an object from accidental deletion.
-
1009
-
Information
-
More than one extending object was found for the object with the specified GUID. All extending objects were successfully merged.
-
1010
-
Warning
-
More than one extending object was found for the object with the specified GUID, but the merge has failed. Details about conflicting objects can be found in the event description.
-
1011
-
Error
-
Incorrect minimum or maximum length is specified for password generation. The default settings will be used.
-
1012
-
Error
-
Failed to update the global schema cache.
-
1013
-
Error
-
Failed to update the cache of managed domains.
-
1014
-
Error
-
Failed to update the cache of directory partitions.
-
1015
-
Error
-
Failed to fetch Adaxes virtual attributes.
Active Directory
Events related to managed Active Directory domains.
-
ID
-
Level
-
Details
-
1100
-
Error
-
Failed to validate the service account used for managing a specific Active Directory domain.
-
1101
-
Error
-
Failed to create or update an Adaxes service connection point in a managed domain.
Troubleshooting
- Verify that the Adaxes service account has sufficient permissions: How do I grant permissions to publish Adaxes service.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
1102
-
Error
-
Failed to delete an Adaxes service connection point from a managed domain.
Troubleshooting
- Verify that the Adaxes service account has sufficient permissions: How do I grant permissions to publish Adaxes service.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
1103
-
Error
-
Failed to create or update an Adaxes service connection point on the computer where Adaxes service is installed.
Troubleshooting
- Verify that the Adaxes service account has sufficient permissions: How do I grant permissions to publish Adaxes service.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
1104
-
Error
-
Failed to delete an Adaxes service connection point from the computer where Adaxes service is installed.
Troubleshooting
- Verify that the Adaxes service account has sufficient permissions: How do I grant permissions to publish Adaxes service.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
1105
-
Error
-
Failed to publish settings for the Adaxes self-service client via a service connection point.
-
1106
-
Error
-
Failed to check whether a network share with a specific name exists.
-
1107
-
Warning
-
Failed to access the home directory of a specific user. Adaxes service account has insufficient permissions.
-
1108
-
Error
-
Failed to create a home directory for a user because a required property is not specified.
-
1109
-
Error
-
Failed to move a home directory of a user because a required property is not specified.
-
1110
-
Error
-
Failed to move a specific file when moving a user's home directory.
-
1111
-
Error
-
Failed to move more than one file when moving a user's home directory.
-
1112
-
Error
-
Failed to delete a user's home directory.
-
1113
-
Error
-
Failed to calculate the password expiration date for a specific account.
-
1114
-
Error
-
Failed to get the effective password policy for a specific user.
-
1115
-
Error
-
Failed to get the default domain password policy for a specific user.
-
1116
-
Error
-
Failed to determine whether Recycle Bin is enabled for a specific managed domain.
-
1117
-
Error
-
Failed to retrieve forest trust information for a specific Active Directory domain.
-
1118
-
Error
-
Failed to update the attribute of an object that contains the object's domain. Most likely, the object was moved to another domain or deleted, and can no longer be located.
-
1119
-
Warning
-
A number of warnings were encountered when building the service schema. Warning details are available in the event description.
-
1120
-
Error
-
Failed to update the directory schema for a specific domain.
-
1121
-
Error
-
Failed to update the directory servers information cache.
-
1122
-
Error
-
Failed to update the cache of the LDAP connection pool.
-
1123
-
Warning
-
NTDS query policy values were not found on a domain controller. Default values will be used instead.
-
1124
-
Warning
-
Failed to track configuration changes using VLV search. Plain search will be performed to complete the task.
Entra ID
Events related to managed Microsoft Entra ID domains.
-
ID
-
Level
-
Details
-
1200
-
Error
-
Failed to create a synchronized account in Microsoft Entra ID.
-
1201
-
Error
-
Failed to create a synchronized group in Microsoft Entra ID.
-
1202
-
Error
-
Failed to delete the synchronized on-premises account after deleting an account in Microsoft Entra ID.
-
1203
-
Error
-
Failed to delete the synchronized on-premises group after deleting a group in Microsoft Entra ID.
-
1204
-
Warning
-
Object cache of a specific Microsoft Entra domain hasn't been updated for a long time.
Troubleshooting
- Verify that the Adaxes service on the host responsible for cache maintenance is running. For details, see Configure cache maintenance for Microsoft Entra domains.
- Verify that nothing is blocking the connection between this Adaxes service and Microsoft Entra. For details, see Adaxes network usage.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
1205
-
Error
-
Object cache of a specific Microsoft Entra domain was updated with errors. Error details are available in the event description.
-
1206
-
Error
-
Failed to update the object cache of a specific Microsoft Entra domain.
Troubleshooting
- Verify that the Adaxes service on the host responsible for cache maintenance is running. For details, see Configure cache maintenance for Microsoft Entra domains.
- Verify that nothing is blocking the connection between this Adaxes service and Microsoft Entra. For details, see Adaxes network usage.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
1207
-
Warning
-
The cache for a specific Microsoft Entra domain could not be fully updated. The Adaxes service instance responsible for cache maintenance is running an older version which does not support some Entra ID object properties. Consider upgrading all services to the same version to avoid such compatibility issues.
-
1208
-
Warning
-
The cache for a specific Microsoft Entra domain could not be fully updated. This Adaxes service instance is responsible for cache maintenance but is running an older version, which does not support some Entra ID object properties. Consider upgrading all services to the same version to avoid such compatibility issues.
-
1209
-
Error
-
One or more errors were encountered while cleaning up permanently deleted Entra objects from the Entra cache. Error details are available in the event description.
-
1210
-
Error
-
Failed to synchronize the capacity of a specific Entra resource mailbox to the Adaxes backend.
-
1211
-
Error
-
The synchronization of Entra object properties stored in external resources was terminated because too many errors were encountered. Error details are available in the event description.
-
1212
-
Error
-
Failed to back up the configuration of a specific Entra domain.
-
1213
-
Error
-
Failed to restore the configuration of a specific Entra domain.
-
1214
-
Error
-
Failed to delete the configuration data of a specific Entra domain.
Exchange and Microsoft 365
Events related to on-premises Exchange servers, Exchange Online, and Microsoft 365.
-
ID
-
Level
-
Details
-
1300
-
Error
-
Failed to retrieve Exchange and Microsoft 365 configuration details for a domain.
-
1301
-
Error
-
Failed to update the basic information about a Microsoft 365 tenant.
-
1302
-
Error
-
Failed to update Microsoft 365 tenant data.
-
1303
-
Error
-
Failed to refresh the cache of Microsoft 365 tenants.
-
1304
-
Error
-
Failed to reset the credential cache for a Microsoft 365 tenant after adding new credentials.
-
1305
-
Error
-
Failed to reset the credential cache for a Microsoft 365 tenant after updating stored credentials.
-
1306
-
Error
-
Failed to reset the credential cache for a Microsoft 365 tenant after deleting stored credentials.
-
1307
-
Error
-
Failed to save the Immutable ID into the source anchor attribute for a specific object.
-
1308
-
Error
-
Failed to determine whether Microsoft Exchange is installed in a specific domain.
-
1309
-
Error
-
Failed to determine whether a specific Exchange Organization is in a hybrid configuration.
-
1310
-
Error
-
Failed to sort Exchange servers from a specific domain by their availability.
-
1311
-
Error
-
Failed to execute an Exchange operation. Error details are available in the event description.
-
1312
-
Error
-
Failed to synchronize Send As permissions of a specific mail-enabled group to Exchange Online.
-
1313
-
Error
-
Failed to update the corresponding Active Directory properties of a synchronized mailbox after updating the mailbox in Exchange Online.
-
1314
-
Error
-
Failed to initialize the Exchange configuration cache.
-
1315
-
Error
-
Failed to reload the Exchange configuration cache.
-
1316
-
Error
-
Failed to install the Exchange Online PowerShell V3 module, which Adaxes requires to manage Exchange Online.
-
1317
-
Error
-
Failed to establish a remote PowerShell session to a specific on-premises Exchange server.
-
1318
-
Error
-
Failed to find the administrative group of a specific Exchange server.
-
1319
-
Error
-
Failed to get the Legacy Exchange DN of a specific Exchange administrative group.
-
1320
-
Error
-
Failed to get an unused Legacy Exchange DN.
Password self-service
Events related to the password self-service system.
-
ID
-
Level
-
Details
-
1400
-
Warning
-
Failed to send the enrollment invitation to specific users because they don't have an email address.
-
1401
-
Error
-
Failed to send a password reset notification to a specific recipient. Error details are available in the event description.
-
1402
-
Warning
-
Value references in an enrollment invitation email resolved with warnings.
-
1403
-
Warning
-
Value references in a password reset notification email resolved with warnings.
-
1404
-
Warning
-
An SMS verification code was sent with warnings.
-
1405
-
Warning
-
An email verification code was sent with warnings.
-
1406
-
Information
-
Password self-service settings synchronization for a specific Entra domain has completed.
-
1407
-
Error
-
Failed to add a user to a password self-service report. Error details are available in the event description.
Access control
Events related to authentication as well as permissions to view objects and perform operations in Adaxes.
-
ID
-
Level
-
Details
-
1500
-
Warning
-
Membership in specific local groups will not be included in the access token of a specific user because Adaxes was unable to establish a connection to the domain where those groups reside.
-
1501
-
Error
-
Failed to authenticate a user due to an invalid ID token.
-
1502
-
Error
-
Failed to invalidate an authentication ticket for a specific user account. The ticket will remain valid until expired.
-
1505
-
Error
-
Failed to update the cache of REST API access tokens.
-
1506
-
Error
-
Failed to delete expired REST API access tokens.
-
1507
-
Error
-
Failed to refresh the cache of security roles, permissions, and assignments.
-
1508
-
Error
-
Failed to create a client context for a specific user.
-
1509
-
Error
-
Failed to update the activity scope cache of security roles. Recently added or revoked permissions might not yet be effective.
-
1510
-
Error
-
Failed to get the ID of the custom command that is being deleted. Permissions for command execution will not be deleted.
-
1511
-
Error
-
Failed to delete the permissions for the execution of a recently deleted custom command.
Approval requests
Events related to approval requests and approval request notifications.
-
ID
-
Level
-
Details
-
1600
-
Error
-
Failed to process an approval request. Error details are available in the event description.
-
1601
-
Warning
-
The number of pending approval requests has exceeded the configured threshold. For information on how to configure the threshold, see Change configuration parameters.
Troubleshooting
This is typically caused by one of the following:
- Approvers are unaware that pending requests exist.
- Approvers are not responding to pending requests.
- Approval workflows are misconfigured and generating excessive requests.
To resolve this:
- Review the approval workflows for misconfiguration.
- Verify that approval email notifications are delivered, or approvers are notified in any other way.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
1602
-
Error
-
Failed to check the number of pending approval requests against the configured threshold.
-
1603
-
Error
-
Failed to send an email notification about an approval request.
-
1604
-
Warning
-
Failed to send an email notification about an approval request to an approver. The user has no email address.
-
1605
-
Error
-
Failed to send an email notification about a processed approval request.
-
1606
-
Warning
-
Failed to send an email notification about a processed approval request to the operation initiator. The user has no email address.
-
1607
-
Error
-
Failed to send an email notification about an approved operation that subsequently failed.
-
1608
-
Warning
-
Failed to send an email notification to an operation initiator about an approved operation that subsequently failed. The user has no email address.
-
1609
-
Error
-
Failed to send an invitation to process an approval request to a user.
-
1610
-
Warning
-
Some value references resolved with warnings while sending an approval request notification. Warning details are available in the event description.
-
1611
-
Error
-
Failed to update the description of an operation that requires approval.
-
1612
-
Information
-
Approval request notification settings were successfully reset to defaults.
Logging
Events related to log records, interaction with external logging databases, and logging notifications.
-
ID
-
Level
-
Details
-
1700
-
Error
-
Failed to save log records to the external MS SQL database.
-
1701
-
Error
-
Failed to record an operation to the logging database.
-
1702
-
Error
-
Failed to prepare data for logging last operations into the database.
-
1703
-
Error
-
Failed to insert log records into the database.
-
1704
-
Warning
-
The execution log of an operation exceeds the size limit. The operation was logged without it.
-
1705
-
Error
-
Failed to ensure that structure of the logging database is correct.
-
1706
-
Error
-
Failed to update information about the replication group the logging database belongs to.
-
1707
-
Error
-
An exception has occurred while disposing the connection to the logging database.
-
1708
-
Error
-
Failed to send the external database connection error report. Error details are available in the event description.
-
1709
-
Error
-
Failed to send log records to the Syslog server on the specified host.
-
1710
-
Error
-
Failed to update the language and regional format settings for the general log.
-
1711
-
Error
-
Failed to refresh the cached logging settings.
-
1712
-
Error
-
Failed to remove outdated log records from the local SQLite database. For details on how to configure the log record retention period, see Change retention period for log records.
Messaging
Events related to SMS messages.
-
ID
-
Level
-
Details
-
1800
-
Error
-
Failed to send an SMS to a specific mobile number.
-
1801
-
Warning
-
An SMS message was sent with warnings. Warning details are available in the event description.
-
1802
-
Information
-
A response to an SMS message was received.
-
1803
-
Error
-
Failed to parse the response to an SMS message sent to a specific mobile number.
Reports
Events related to reports and report categories.
-
ID
-
Level
-
Details
-
1900
-
Error
-
A scheduled report failed to generate. Details about the report and its recipient are available in the event description.
-
1901
-
Error
-
Failed to load a pinned report.
-
1902
-
Error
-
Failed to resolve the identifier of the report category being deleted. Permissions for this category will not be removed from existing security roles.
-
1903
-
Error
-
Failed to remove permissions related to the deleted report category from security roles.
Built-in configuration
Events related to the creation of built-in configuration objects when installing Adaxes or restoring such objects to their initial state.
-
ID
-
Level
-
Details
-
2000
-
Error
-
Failed to create a built-in security role.
-
2001
-
Error
-
Failed to create a built-in property pattern.
-
2002
-
Error
-
Failed to create a built-in business rule.
-
2003
-
Error
-
Failed to create a built-in custom command.
-
2004
-
Error
-
Failed to create a built-in scheduled task.
-
2005
-
Error
-
Failed to create a built-in report.
-
2006
-
Error
-
Failed to create a built-in report category.
-
2007
-
Error
-
Failed to create a built-in report overview.
-
2008
-
Error
-
Failed to create the container for the built-in security roles.
-
2009
-
Error
-
Failed to create the container for the built-in property patterns.
-
2010
-
Error
-
Failed to create the container for the built-in business rules.
-
2011
-
Error
-
Failed to create the container for the built-in custom commands.
-
2012
-
Error
-
Failed to create the container for the built-in scheduled tasks.
-
2013
-
Error
-
Failed to create a built-in report container.
-
2014
-
Error
-
Failed to create the root container for report schedules.
-
2015
-
Error
-
Failed to create a built-in container.
-
2016
-
Error
-
Failed to create a built-in web interface configuration.
-
2017
-
Error
-
Failed to delete an intermediate object that was created when restoring a built-in configuration object.
Command queue
Events related to the command queue – a queue of operations that will be executed by the Adaxes service.
General
-
ID
-
Level
-
Details
-
2100
-
Error
-
An operation threw an exception while being executed.
-
2101
-
Information
-
An asynchronous operation has been completed. Operation details are available in the event description.
-
2102
-
Warning
-
An error has occurred when checking a condition in a business rule, custom command, scheduled task, or report.
-
2103
-
Error
-
Cannot execute an operation added to a command queue by a business rule. Error details are available in the event description.
-
2104
-
Error
-
Cannot execute an operation added to a command queue by a custom command. Error details are available in the event description.
-
2105
-
Error
-
Cannot execute an operation added to a command queue by a scheduled task. Error details are available in the event description.
-
2106
-
Error
-
Execution of a specific operation was halted midway. It will not proceed further, and any operations waiting for it will not be executed.
-
2107
-
Error
-
An unhandled exception has occurred while processing an operation in the pipeline. Further execution will be canceled.
-
2108
-
Error
-
An unhandled exception has occurred while processing an enqueued operation. Further processing will be cancelled.
-
2109
-
Information
-
Execution of an external program in a Run a program or PowerShell script action has completed. Program output is available in the event description.
-
2110
-
Information
-
Execution of an external program in a Run a program or PowerShell script action has completed and produced no output.
-
2111
-
Information
-
Execution of a PowerShell script in an asynchronous Run a program or PowerShell script action or If PowerShell script return true condition has completed. Script output is available in the event description.
-
2112
-
Information
-
Execution of a PowerShell script in a Run a program or PowerShell script action or If PowerShell script return true has exceeded the timeout and was terminated.
Troubleshooting
- Review the action or condition where the script is used and optimize the script, if possible.
- Increase the timeout for script execution. For details, see this help article. It is not recommended to significantly increase the timeout unless absolutely necessary. Adjusting the script of the workflow should always be your primary course of action.
- Contact support@adaxes.com and ask for assistance. Attach your script in a TXT format and describe all the details about the issue you are facing and the desired outcome.
-
2113
-
Error
-
Failed to recover pending operations from the command queue after an unexpected service shutdown.
-
2114
-
Error
-
Failed to execute recovered operations after an unexpected service shutdown.
-
2115
-
Information
-
Pending operations were restored to the command queue successfully.
-
2116
-
Information
-
Pending operations in the command queue were backed up successfully.
-
2117
-
Error
-
Failed to back up pending operations. Do not uninstall the Adaxes service until they have been backed up successfully, otherwise, they will be lost.
-
2118
-
Error
-
Failed to deserialize a command from its XML representation.
-
2119
-
Error
-
Failed to deserialize a delayed operation. The operation will not be executed.
-
2120
-
Warning
-
A command processor has set an incorrect state to an operation in the queue. The state was changed.
-
2121
-
Warning
-
A command processor has set an incorrect execution state to an operation in the queue. The execution state was changed.
-
2122
-
Error
-
A command processor threw an exception when processing an operation. Error details are available in the event description.
-
2123
-
Error
-
Failed to restore postponed operations preserved on the file system before uninstalling the Adaxes service
Value references
Events related to the processing of value references in operations.
-
ID
-
Level
-
Details
-
2200
-
Warning
-
A business rule generated a warning while processing value references.
-
2201
-
Error
-
A business rule generated an error while processing value references in a specific action. It is recommended to review the configuration of this action in the rule.
-
2202
-
Error
-
A business rule generated an error while processing value references in a specific condition. It is recommended to review the configuration of this condition in the rule.
-
2203
-
Warning
-
A custom command generated a warning while processing value references.
-
2204
-
Error
-
A custom command generated an error while processing value references in a specific action. It is recommended to review the configuration of this action in the command.
-
2205
-
Error
-
A custom command generated an error while processing value references in a specific condition. It is recommended to review the configuration of this condition in the command.
-
2206
-
Warning
-
A scheduled task generated a warning while processing value references.
-
2207
-
Error
-
A scheduled task generated an error while processing value references in a specific action. It is recommended to review the configuration of this action in the task.
-
2208
-
Error
-
A scheduled task generated an error while processing value references in a specific condition. It is recommended to review the configuration of this condition in the task.
-
2209
-
Error
-
Failed to process value references in a specific action.
-
2210
-
Warning
-
An invalid value reference was detected in the default value of a specific property in a property pattern. This value reference will be ignored.
-
2211
-
Warning
-
Several invalid value references were detected in the default value of a specific property in a property pattern. These value references will be ignored.
-
2212
-
Warning
-
A recursive value reference was detected in the default value of a specific property in a property pattern. This value reference will be ignored.
-
2213
-
Warning
-
Several recursive value references were detected in the default value of a specific property in a property pattern. These value references will be ignored.
Backend
Events related to the Adaxes backend.
Initialization
Events related to AD LDS health, Adaxes service startup, installation, upgrade to newer versions, and uninstallation.
-
ID
-
Level
-
Details
-
2300
-
Error
-
Failed to create REST API configuration.
-
2301
-
Error
-
Failed to create administration console settings.
-
2302
-
Information
-
The container for the service settings was created successfully.
-
2303
-
Information
-
The container for configuration set settings was created successfully.
-
2304
-
Information
-
A configuration container was created successfully.
-
2305
-
Information
-
A configuration container was deleted successfully.
-
2306
-
Error
-
Failed to register the domain where the Adaxes service account is located.
-
2307
-
Error
-
Failed to register the specified web interface for a service during initialization.
-
2308
-
Error
-
Failed to verify Adaxes service version equality within the configuration set.
-
2309
-
Error
-
Failed to update the maximum version of Adaxes services in the configuration set.
-
2310
-
Warning
-
The Adaxes service on the specified host shares configuration with another service of a different version. Consider upgrading all services to the same version to avoid potential compatibility issues.
-
2311
-
Error
-
Failed to restore local configuration. Local configuration, like domain controller restrictions and Exchange PowerShell settings, is not replicated between services. It is restored from backups which are automatically created when a service instance is stopped.
-
2312
-
Error
-
Failed to back up local configuration. Local configuration, like domain controller restrictions and Exchange PowerShell settings, is not replicated between services. A local configuration backup is needed to preserve these settings if an Adaxes service is reinstalled. Restart the Adaxes service to make another attempt.
-
2313
-
Information
-
The backend server schema is out of date and will be reloaded.
-
2314
-
Information
-
The domain directory schema is out of date and will be reloaded.
-
2315
-
Information
-
Tombstone lifetime for the AD LDS backend server has been changed.
-
2316
-
Error
-
Failed to change the tombstone lifetime for the backend server.
-
2317
-
Error
-
An error occurred while adding the Adaxes service account to the list of AD LDS configuration set administrators.
-
2318
-
Information
-
A local partition in AD LDS was created successfully.
-
2319
-
Warning
-
Failed to create a local AD LDS partition. Naming Master Role server is not available. The container for local service data storage will be created in the replicated partition, which will cause additional network traffic.
-
2320
-
Warning
-
Failed to create a local AD LDS partition. Naming Master Role server belongs to a domain that doesn't have any trust relationships with this domain. The container for local service data storage will be created in the replicated partition, which will cause additional network traffic.
-
2321
-
Warning
-
Failed to create a local AD LDS partition. The container for local service data storage will be created in the replicated partition, which will cause additional network traffic.
-
2322
-
Information
-
The local AD LDS partition was deleted successfully.
-
2323
-
Error
-
Failed to delete the local AD LDS partition.
-
2324
-
Information
-
The AD LDS instance was removed from the configuration set.
-
2325
-
Error
-
Failed to remove an AD LDS instance from the configuration set. Error details are available in the event description.
-
2326
-
Warning
-
An AD LDS instance cannot be removed from the configuration set because all other instances are unavailable.
-
2327
-
Error
-
Failed to verify the availability of the server that holds the specified FSMO role.
-
2328
-
Information
-
A server that had a specific FSMO role in AD LDS may have been removed from the configuration set incorrectly. The role will be seized by another available server.
-
2329
-
Information
-
An FSMO role was seized by another server from the configuration set.
-
2330
-
Error
-
An attempt to seize an FSMO role was made, but failed.
Secure storage
Events related to the secure storage in AD LDS.
-
ID
-
Level
-
Details
-
2400
-
Error
-
Failed to encrypt the secure storage master key for a specific Adaxes service instance. If you are seeing this event often and it causes issues with credential replication to other services, consider resetting secure storage.
-
2401
-
Error
-
Failed to publish the master key in AD LDS for an Adaxes service instance that does not have it.
-
2402
-
Error
-
Failed to obtain the master key for the secure storage. There are no Adaxes services in the configuration set to authorize the request.
-
2403
-
Error
-
An error has occurred while renewing the secure storage master key.
-
2404
-
Error
-
An error occurred while searching for unused master keys for the secure storage.
-
2405
-
Error
-
Failed to delete the secure storage master key for a specific Adaxes service instance.
-
2406
-
Error
-
Failed to decrypt the secure storage master key on a specific Adaxes service instance. Key recovery will be requested from another service instance.
-
2407
-
Error
-
Failed to decrypt the secure storage master key, so a new master key was created. All data in secure storage encrypted with the previous key will be lost.
-
2408
-
Warning
-
The secure storage master key hasn't been updated for a long time. Make sure the Adaxes service responsible for updating the master key is up and running.
-
2409
-
Warning
-
The secure storage master key hasn't been updated for a long time. Make sure at least one of the Adaxes services responsible for updating the master key is up and running.
-
2410
-
Error
-
Failed to get a specific data entry from the secure storage.
-
2411
-
Error
-
Failed to encrypt a specific secure storage data entry using the new master key.
-
2412
-
Information
-
The request to reset the secure storage has completed successfully. The stored data was erased and the keys were reset.
Internal
Events related to the internal operation of the Adaxes service.
General
-
ID
-
Level
-
Details
-
2500
-
Error
-
An error occurred during the service initialization. The service will be stopped.
Troubleshooting
The recommended troubleshooting order is:
- Verify that all Adaxes services sharing configuration are of the same version and there are no stale services in the set. For information on how to view current services in your environment, see this article.
- Verify that the account that runs Softerra Adaxes Service Windows service is the same account that you specified when you installed Adaxes. The service account cannot be change without reinstalling the Adaxes service.
- Verify that the credentials specified in the Softerra Adaxes Service Windows service settings are valid. If you changed the service account password, you also need to manually update it in the Windows service settings.
- Verify that the Adaxes service account has sufficient permissions. For details, see Permissions required by Adaxes.
- Verify that all the ports used by Adaxes are open. For details, see Adaxes network usage.
- If the issue persists, contact support at support@adaxes.com for assistance.
-
2501
-
Error
-
Adaxes service has terminated with an error. Error details are available in the event description.
-
2502
-
Error
-
The URL of the web interface used for object links is either not configured or not accessible from the computer hosting the Adaxes service. For information on how to check or change this URL, see Specify web interface to use in object links.
-
2503
-
Error
-
Failed to retrieve information about the web interface configured to work with the current Adaxes service.
-
2504
-
Error
-
Failed to update the cache of service administrator SIDs.
-
2505
-
Error
-
Failed to fetch the list of unmanaged user accounts.
-
2506
-
Error
-
Failed to reload the cache of unmanaged accounts.
-
2507
-
Error
-
Failed to reload the internal cache of configuration parameter values.
-
2508
-
Error
-
Failed to parse the value of a specific configuration parameter. The default value will be used.
Troubleshooting
Refer to the corresponding section of the article about changing configuration parameters, and set the parameter value in the correct format.
-
2509
-
Error
-
Failed to open the file specified as the output file for the PowerShell trace. Specify a different file or fix the file access rights for the Adaxes service account.
-
2510
-
Error
-
A parameter occurs in the Softerra.Adaxes.Service.ini initialization file more than once. The first encountered value will be used.
-
2511
-
Error
-
The initialization culture specified in Softerra.Adaxes.Service.ini is incorrect. The default culture will be used.
-
2512
-
Error
-
Failed to read monitoring data published by an Adaxes service.
-
2513
-
Error
-
Failed to publish the data necessary for monitoring the Adaxes service state.
-
2514
-
Error
-
An error has occurred while migrating property patterns from earlier versions.
Maintenance tasks
Events related to routine maintenance tasks that Adaxes performs. For example, Entra domain cache maintenance.
-
ID
-
Level
-
Details
-
2600
-
Information
-
The task that deletes outdated approval requests has started. For details, see How to change retention period for approval requests.
-
2601
-
Information
-
The task that deletes outdated approval requests has completed successfully.
-
2602
-
Information
-
The task that removes operations with deleted approval requests from the command queue has completed successfully.
-
2603
-
Error
-
The task that removes operations with deleted approval requests from the command queue has failed.
-
2604
-
Error
-
The task that updates the approval request metadata has completed with errors. For information on how to change the update interval, see Change configuration parameters.
-
2605
-
Warning
-
The task that updates the approval request metadata has completed with warnings.
-
2606
-
Information
-
The tasks that synchronizes the extending object properties of synced objects in a hybrid environment has completed successfully.
-
2607
-
Error
-
The tasks that synchronizes the extending object properties of synced objects in a hybrid environment has failed.
-
2608
-
Error
-
The task that checks the client secret expiration status of an Entra application used by Adaxes has failed.
-
2609
-
Error
-
Cannot check the client secret expiration status of an Entra application because of insufficient permissions. Error details are available in the event description.
-
2610
-
Information
-
The task that revokes unused authenticator apps has started.
-
2611
-
Information
-
The task that revokes unused authenticator apps has completed successfully.
-
2612
-
Information
-
The task that stamps Exchange Online properties has started.
-
2613
-
Information
-
The task that stamps Exchange Online properties has completed successfully.
-
2614
-
Information
-
The task that stamps Exchange Online properties was aborted.
-
2615
-
Error
-
Failed to stamp Exchange Online properties for a specific object.
-
2616
-
Error
-
A Microsoft 365 tenant was deleted while the task that stamps Exchange properties was running for that tenant. This error can be safely ignored.
-
2617
-
Error
-
The task that cleans up the pool of SMTP clients has failed.
-
2618
-
Error
-
Failed to execute certain maintenance tasks.
-
2619
-
Error
-
An error has occurred during the execution of a specific maintenance task.
Licensing
Events related to the licensing status, license violations, and license notifications.
-
ID
-
Level
-
Details
-
2800
-
Warning
-
The total number of enabled, non-expired user accounts in all domains managed by Adaxes exceeds the allowed limit. This event is logged once when the violation is first detected.
-
2801
-
Warning
-
The total number of enabled, non-expired user accounts across all managed domains exceeds the allowed license limit. This event is logged daily until the license violation is resolved. If the violation is not resolved within 30 days, the Adaxes service will stop working.
-
2802
-
Information
-
The license key is missing.
-
2803
-
Error
-
Failed to check whether a new license key was activated.
-
2804
-
Error
-
The activated license key is not compatible with the current product version. Your license may entitle you to a compatible key. To check and obtain one, contact your account manager at sales@softerra.com.
-
2805
-
Error
-
The activated license key is invalid. Contact your account manager at sales@softerra.com to obtain a valid key.
-
2806
-
Error
-
The content of the activated license file is invalid or corrupted. Contact your account manager at sales@softerra.com for a replacement key.
-
2807
-
Error
-
The activated license key cannot be verified.
-
2808
-
Warning
-
The temporary license key expires soon. Contact sales@softerra.com if you would like to extend your temporary license.
-
2809
-
Error
-
The temporary license key has expired. Contact sales@softerra.com if you would like to get a new key.
-
2810
-
Error
-
Failed to apply the license key. Error details are available in the event description.
-
2811
-
Error
-
Failed to send an email notification to the license owner about an issue with the current licensing status. Error details are available in the event description.
-
2812
-
Warning
-
The evaluation period expires soon. Make sure that you have activated your license key.
-
2813
-
Error
-
The evaluation period has expired. Adaxes service will be stopped.
ADSI
Events generated by the ADSI provider.
-
ID
-
Level
-
Details
-
1
-
Information
-
The configuration settings were successfully loaded from the Softerra.Adaxes.Adsi.dll.config file.
-
2
-
Information
-
The Adaxes service was started successfully.
-
3
-
Information
-
The Adaxes service was stopped.
-
100
-
Warning
-
Failed to locate an Adaxes service instance in this domain.
-
101
-
Warning
-
Failed to establish a secure connection because the current user cannot be authenticated on the remote computer.
-
102
-
Warning
-
Client remoting channels do not match server channels.
-
103
-
Warning
-
Failed to unregister a service connection point.
-
104
-
Error
-
Failed to parse the data from a specific service connection point.
-
105
-
Error
-
Failed to save the schema cache file. The schema cache will not be used, which may cause performance problems.
-
106
-
Error
-
Failed to remove the schema cache file. The schema cache will not be used, which may cause performance problems.
-
107
-
Error
-
The current user is not allowed to save schema cache to the selected location. The schema cache will not be used, which may cause performance problems.
-
108
-
Error
-
The current user is not allowed to remove the schema cache file. Schema cache will not be used, which may cause performance problems.
-
109
-
Error
-
Failed to initialize the PowerShell environment cache.
Backup restore
Events generated by the Softerra.Adaxes.BackupRestore tool.
-
ID
-
Level
-
Details
-
30002
-
Information
-
Adaxes initiated a request to stop one of its Windows services.
-
30003
-
Information
-
One of Windows services that belong to Adaxes was stopped.
-
30004
-
Information
-
Adaxes initiated a request to start one of its Windows services.
-
30005
-
Information
-
One of Windows services that belong to Adaxes was started.
-
30006
-
Information
-
Adaxes has started backing up a configuration object category. For example, property patterns. This event is logged once per category when a configuration backup is made.
-
30007
-
Information
-
Service configuration file was backed up.
-
30008
-
Information
-
Logging database file was backed up.
-
30009
-
Information
-
A file was added to the configuration backup.
-
30010
-
Information
-
Service configuration file was restored.
-
30011
-
Information
-
Logging database file was restored.
-
30012
-
Information
-
A file was restored successfully.
-
30013
-
Information
-
Properties of the Approval Requests container were restored.
-
30014
-
Warning
-
Approval requests will not be restored because the Adaxes service shares its configuration with other Adaxes services.
-
30015
-
Warning
-
Failed to restore configuration data. Error details are available in the event description.
-
30016
-
Error
-
Failed to correct configuration object GUIDs.
-
30017
-
Error
-
Failed to update the GUID for a specific configuration object. Error details are available in the event description.
-
30018
-
Information
-
Started rolling back the configuration restore process.
-
30019
-
Information
-
Finished rolling back the configuration restore process.
-
30020
-
Error
-
Failed to delete the temporary rollback container after restoring the configuration.
-
30021
-
Error
-
Failed to delete the temporary directory created during configuration backup/restore.
Web server
Events generated by Adaxes web interface or web interface configurator.
-
ID
-
Level
-
Details
-
10000
-
Error
-
Failed to get the web interface configuration. Error details are available in the event description.
-
10001
-
Error
-
Failed to get password self-service information for a specific user.
-
10002
-
Error
-
Failed to use a specific domain as a default during sign in. This domain is not managed by the Adaxes service.
-
10003
-
Error
-
Failed to determine whether the a specific web interface configuration is allowed on the current web server. The configuration will be ignored.
-
10004
-
Error
-
Failed to determine whether the configuration is available for the current user. The configuration will be ignored.
-
10005
-
Warning
-
More than one custom command with the same ID was found.
-
10006
-
Error
-
Failed to read data from a file.
-
10007
-
Error
-
Failed to write data to a file.
-
10008
-
Error
-
Failed to delete obsolete files.
-
10009
-
Error
-
Failed to create a folder for temporary storage.
-
10010
-
Error
-
Failed to delete obsolete blob storage files.
-
10011
-
Error
-
Failed to clean up temporary objects.
-
10012
-
Error
-
Failed to parse the value of an HTTP header.
-
10013
-
Error
-
Failed to update favorites for a user.
-
10014
-
Error
-
Failed to update the cache of Adaxes services.