Skip to main content
Version: Omada Identity Cloud

Log overview

This page describes where to find the different logs in Omada Identity and lists Enterprise Server event IDs and their meanings.

Page activity log​

All user access to web pages that are a part of the Omada Identity are logged in to the dbo.tblActLog table in the database.

Writing logs to the dbo.tblActLog table can be managed by setting the EnableActivityLog customer setting to the desired value:

  • If this setting is enabled, logs are written to tblActLog table. This is the default value for on-premise customers.
  • If this setting is disabled, logs are not written to tblActLog table. This is the default value for Cloud customers.
  • If this setting is not defined, logs are written to tblActLog table.
note

Web request activity information is always written to the configured OIS logging targets, regardless of the EnableActivityLog customer setting.

Only Platform Administrators can change the value of the EnableActivityLog setting.

dbo.tblActLog

The dbo.tblActLog table to which the logs are written includes many different columns, such as:

  • ID - unique ID is assigned to each new page access.
  • UserId - the IDs for the user and customer accessing the page.
  • CreateTime - the time when the user first accessed the page.
  • PageName - he name of the page that the user accessed, for example, dataobjviewdlg.aspx.
  • PagePath - he complete path to the page, for example, /webservice/oim_systemonboarding.asmx.
  • QueryString - the query string is used to call the page, for example, op=pushconfiguration.
  • EndTime - the time when the user finished accessing the page.
  • IP - the IP address from which the access to the page came.

You can extract the data and paste it into a more reading-friendly format, for example, in a Microsoft Excel spreadsheet. You can also use the IIS page log for this type of information. To do this, follow these steps:

  1. Open IIS Manager on your computer.

  2. Locate the properties for the relevant view.

  3. Open the Logging feature.

    The Logging feature in IIS Manager
  4. In the Logging feature, select Enable in the Actions pane and specify the format for the log in the Format field.

    Enabling the Logging feature in IIS Manager
  5. To set up the log schedule, select from the available log schedules in the Log File Rollover section.

  6. To set the location of the log file directory, click Browse in the Log file section and select the specific location of the file. The path is displayed in the Directory field.

Performance counters​

Performance counters are instrumental in monitoring the health of the Omada Identity. Leveraging Windows functionality, this set of counters aids in ensuring system performance.

The installation of the performance counter category and instances occurs within the Enterprise Server MSI installer.

To initiate performance counters, you can access the Start performance counters master setting. For more information, refer to the Monitoring section in the Master settings document.

They include the following counters:

  • Web Pages – incremented for each WebPage request.
  • Web Service Calls – incremented for each WebService call.
  • Response Time – average response time.
  • DataObject Created – incremented for each data object created.
  • DataObject Updated – incremented for each data object updated.
  • DataObject Deleted – incremented for each data object deleted.
  • DataObject Purged – incremented for each data object purged.
  • Session Count – sample of number of interactive sessions.
  • Timer Heartbeat – incremented for each timer cycle.
  • RoleEngine Heartbeat – incremented for each role engine cycle.
  • RoleEngine Identity Calculated – incremented for each identity calculation.
  • Obsolete Property Value Count – sample of number of obsolete property value rows in the database.
  • Obsolete DataObject Version Count – sample of number of data object version rows in the database.
  • Deleted DataObject Count – sample of number of data object marked as deleted in the database.

You can find the counters on the application server under the Omada Enterprise category:

Counters on the Performance monitor.

Synthetic transactions​

PingDatabase.aspx

There are two functions in the Web Application for synthetic transactions. External monitoring tools can use the transactions to check the availability of the Omada Identity. PingDatabase.aspx is a webpage that shows the message OK when the application is up and running.

The Web Service's end-point is WebService/MasterWebService.asmx. It contains the web service called PingDatabase(), which returns the message OK when the application is up and running.

LoadBalancer.aspx (Health check endpoint for load balancers)

Omada Identity provides a dedicated unauthenticated endpoint that can be used by load balancers to verify node availability:

[BaseURL]/LoadBalancer.aspx

This endpoint returns one of the following:

  • 200 – Response.StatusCode, node is available.
  • 503 – Response.StatusCode, node is unavailable.
  • No response – the server cannot handle the load.

To prevent excessive polling, this endpoint caches the previous response for 5 seconds. Querying it more frequently provides no additional value.

The endpoint behavior is controlled by the LoadBalancerNodeEnabled key in web.config:

  • empty or true - endpoint returns data (200 or 503).
  • false - endpoint always returns 503.

This endpoint does not require authentication and is intended for load balancer health checks only.

Code method log​

You can use code methods to modify many configurations, for example, data objects, forms, processes, and users. Code methods are included in the basic setup, but users can also create and modify more code methods to suit their particular configuration. Code methods are linked to events, such as creating or modifying objects or the transition of a process.

Whenever someone uses a code method, the use is logged in the Code Method Log. You can find this log in the System Management menu. The code method log can assist you with monitoring the use of code methods and if the code methods are successful.

Find the Code method log view by going to Setup > Logs> Code Method Log. The main view displays a list of code methods that the system has run, as shown in the following image:

The Code method log view.

The complete list view includes the following information:

  • Class path and method - shows the name of the class path and code method.
  • Code assembly - show the code assembly that the code method used.
  • Call time - shows the time when the code method was called.
  • Success - shows if the code method ran successfully. This can be Yes or No.
  • Action object - shows the target of the code method’s action.

When you click a code method in the list, a page opens to display the complete details of the code method that has run.

The Code method log details view.

The details on the page include:

  • Assembly - shows the code assembly used by the code method.
  • Executed on - shows the time and date on which the code method ran.
  • Execution time - shows how long time it took to run the code method.
  • Executed by - shows the User ID of the user who called the code method.
  • Call parameters
  • Result parameters
  • Success - shows if the code method ran successfully. This can be Yes or No.
  • Action object - shows the object on which the code method action took place.

The Code Method Execution Details page can help you troubleshoot a code method if it has not worked successfully. You can also find details about the code methods in the SQL Server database table dbo.tblCodeMethodLog.

Enterprise Server logs​

Event IDs and their meanings are stable across releases. New event IDs may be added in later releases. Changes to existing event IDs are announced in advance and versioned.

The Omada Logging Framework sends entries, including all event IDs listed here, to the configured log targets. You can view them on the Event Log page. This applies to all deployments. In Omada Identity Cloud, only Omada can change the log configuration. For details, see Event Logging configuration.

tip

For a list of Omada Logging Framework event types and their event IDs, see Omada Logging Framework event types.

By default, on-premises installations record Enterprise Server errors, warnings, and information messages in the Windows event log under Application. You can view these entries in Event Viewer.

General and database events​

Event IDNameDescription
10000OtherUncategorized error.
10001LogErrorError in the log configuration.
10002ServerConfigurationServer configuration error.
10003LicenseErrorLicensing error.
10100ObjectNotFoundObject not found.
10200SqlCommonUncategorized SQL error. This can be a syntax error.
10201SqlTimeOutSQL error caused by a locked resource or a long-running statement.
10202SqlNetworkErrorCannot access the SQL Server. Can be caused by a connection string with errors.
10203SqlLoginFailedAccess to the SQL Server is denied. The username or password may not be correct.
10204SqlTransientErrorSQL transient error.
10205SqlUniquenessErrorSQL uniqueness error.
10206SqlRollbackFailureSQL rollback error.
10300CacheLockTimeoutA cache refresh failed because of a locked resource.

Authentication events​

Event IDNameDescription
10400LogonFailureA user has failed to log in to the application.
10401SamlResponseFailedSAML response failed.
10402OpenIDResponseFailedOpenID response failed.
10403UserAuthFailed to set user password.
10404LogonUserIsInactiveUser is inactive.
10405TooManyLogonAttemptsToo many logon attempts.
10406PasswordExpiredPassword has expired.
10407SamlConfigurationSAML configuration error.
10408LogConfigurationLog configuration errors and changes. Always logged, regardless of EnableSystemEventLogging.
10409LogonSuccessfulLogon successful.
10410LogoffInitiatedLog off initiated.
10411LogInitializedLog in initialized.

Code method and access modifier events​

Event IDNameDescription
10500CodeMethodExceptionA code method has failed.
10501CodeMethodFriendlyExceptionA code method has thrown a non-fatal exception.
10502CodeMethodMalConfigurationA code method has been configured which contains errors.
10503CodeMethodValidationCode method validation error.
10504AccessModifierValidationAccess modifier validation error.
10506ReferencedObjectDeletedReferenced object deleted.
10550XmlSchemaFileUpdateErrorError in the XML schema file update.

Database update events​

Event IDNameDescription
10600DatabasePatchAppliedA database patch has been installed.
10601DatabaseScriptExecuteDatabase script executed.
10602AppStringsImportedApp strings imported.
10603UpdateActionAssemblyErrorError in the assembly update action.
10604UpdateActionExpectedErrorError in the action expected update.

Mail events​

Event IDNameDescription
10700MailTooManyReceiversA function was prevented from sending notifications because it would send out too many emails, resulting in spam.
10701MailNoValidEmailAddressAn email notification could not be sent because no valid email address was found.
10702MailCannotSendMailAn error occurred while sending an email notification. This may be because of an email relay problem.
10703MailCannotBeQueuedMail cannot be queued.
10704MailCannotDecryptVarUnable to decrypt mail variable.
10705MailCannotRemoveMailFromQueueCannot remove mail from queue.
10706MailCannotAddMailLogCannot save mail to the log.
10707MailSentMail sent.
10708MailConnectionMail connection error.
10709MailAuthenticationMail authentication error.

Execution and integration events​

Event IDNameDescription
10800EventDefTooManyObjectsAn event definition did not trigger on all filtered objects because the threshold number of objects was exceeded.
11000TraceInformationTrace information from a code method or another function.
11001WebRequestWeb request failed.
12003SimulationHubRunSimulation service failed.
12100RunArchiveBatchArchiving cycle failed.
13000WebserviceErrorWeb service request failed.

Password reset events​

Event IDNameDescription
13200PasswordResetSuccededPassword reset success.
13201PasswordResetFailedPassword reset failure.
13202PasswordResetOneTimeCodePassword reset one-time code.
13203PasswordResetBruteForceDetectedPassword reset brute-force attempt detected.
13204PasswordResetMissingDelegateMethodPassword reset is missing the delegate method.
13205PasswordResetNotificationFailedPassword reset notification was not sent.
13206PasswordResetVerifyPasswordFailedPassword reset password verification failed.
13207PasswordResetAccountLookupFailedPassword reset account lookup failed.
13208PasswordResetSystemLookupFailedPassword reset system lookup failed.
13209PasswordFilterFailedPassword filter failure.
13210PasswordChangedPassword changed.
13211PasswordResetClientLoadFailureFailure to load the password reset client.

Access request and policy check events​

Event IDNameDescription
13300AccessRequestStatusConfigErrorError in the configuration of the access request status.
13350PolicyCheckConfigurationErrorError in the policy check configuration.
13351PolicyCheckExecutionErrorError during policy check execution.

API events​

Event IDNameDescription
13400ODataErrorOData error.
13500GraphQLErrorGraphQL error.

User interface and survey events​

Event IDNameDescription
14000AjaxGridErrorAjax grid error.
14001AjaxGridPossibleSqlInjectionPreventedPossible SQL injection in the Ajax grid has been prevented.
15000SurveyFeatureInfoSurvey feature information.
15001SurveyOwnershipNotAcceptedOwnership of a survey has been rejected.

Data and reporting events​

Event IDNameDescription
16000ComplexDataSetBuilderErrorComplex data set builder error.
16001CrossDatabaseQueryDetectedCross-database query detected.
17000KPIEvaluationErrorKPI evaluation error.

Other application events​

Event IDNameDescription
18000VirtualPropertyResolverErrorVirtual property resolver error.
19000AssigneeExpressionPathResolutionInfoInformation message about assignee expression path resolution.
19001AssigneeExpressionPathResolutionWarningWarning message about assignee expression path resolution.
20000OPEJobNotificationOPE job notification.
21000TimeZoneAlignmentTime zone alignment.
21001CustomerSettingRangeErrorCustomer setting range error.

Configuration import and upgrade events​

Event IDNameDescription
22001ConfigurationChangeImportConfiguration change import.
22100UpgradeSyncOfflineSystemsUpgrade sync offline systems.

Employment events​

Event IDNameDescription
23001SystemEventCat_Employments_IdentityDisabledIdentity has been disabled.
23002SystemEventCat_Employments_IdentityLockedIdentity has been locked.
23003SystemEventCat_Employments_IdentityReEnabledIdentity has been re-enabled.

Access request events​

Event IDNameDescription
23101SystemEventCat_AccessRequests_RequestSubmittedAccess request submitted.
23102SystemEventCat_AccessRequests_RequestApprovedAccess request approved.
23103SystemEventCat_AccessRequests_RequestRejectedAccess request rejected.
23104SystemEventCat_AccessRequests_RequestCancelledAccess request cancelled.

Configuration events​

Configuration events record changes to configuration objects. They use the Configuration category.

Configuration event metadata can include these keys:

  • Actor: The user ID of the user who made the change.
  • EventType: The type of change, such as Created, Modified, or Deleted. For the changeset import event (23226), the value is Imported.
  • ObjectType: The type of the changed object, for example, Timer or UserGroup.
  • ObjectInformation: Object details such as Id, UId, and Name. For data objects such as Data Connections, it can also include TypeId and TypeName.
  • PropertyValues: Values for selected fields. The fields included depend on the object type. For example, Mail Template subjects and message content are not included.

The time is recorded as the log entry's DateTime; it is not a metadata key.

Individual entries for configuration changes applied during a changeset import include ChangeUId at the top level of MetaData. This GUID identifies the individual configuration change being applied and is always present on these entries. ChangeSetId is included only when its value is greater than 0; it is not written for file imports. The import event and these per-change entries can be correlated by time.

tip

Most configuration events depend on EnableSystemEventLogging.

  • For on-premises, this setting is disabled by default and can be configured by a platform administrator.
  • In Omada Identity Cloud, it is enabled by default and managed by Omada; Cloud customers cannot change or disable it.

The following events are always logged, regardless of this setting:

  • 10408 – LogConfiguration: Changes to the log configuration.
  • 23224 – SystemEventCat_Configuration_SystemEventLoggingChanged: Changes to EnableSystemEventLogging.
  • 23225 – SystemEventCat_Configuration_MasterSettingChanged: Master Setting changes.

To find these events, open the Event Log page and filter by the Configuration category.

Event text uses modified when the object itself is updated, for example, “Identity modified”, and changed when a reference is updated, for example, “System owner(s) changed.”

PropertyValues contains only the new values, not the previous ones.

Events triggered by UI requests may also include request context metadata: UserAgent, UserHostAddress, HttpMethod, QueryString, UserDateTime, and AuthenticationType. These keys are absent from changeset import entries and system actions.

For example, a Timer change may appear as follows:

Event ID: 23214
Message: Timer ('Timer 1000009') was modified by DWO@OMADA.NET.
MetaData: {"Actor":1021254,"EventType":"Modified","ObjectType":"Timer","ObjectInformation":{"Name":"Timer 1000009","UId":"456cd9e2-eaf5-45a0-a244-d49a7567c61b"},"PropertyValues":{"Timer_RepeatPattern":3}}

A UI change to EnableSystemEventLogging may appear as follows:

Event ID: 23224
Message: The 'EnableSystemEventLogging' customer setting was disabled.
MetaData: {"Actor":1021254,"EventType":"Modified","ObjectType":"CustomerSetting","ObjectInformation":{"Name":"EnableSystemEventLogging"},"PropertyValues":{"EnableSystemEventLogging":false},"UserAgent":"<user agent>","UserHostAddress":"<client address>","HttpMethod":"POST","QueryString":"","UserDateTime":"2026-10-30T15:42:53.6019329Z","AuthenticationType":"OpenID"}
Event IDNameMeaning and actionsAdditional metadata
23201SystemEventCat_Configuration_MembersAddedUser Group members added.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23202SystemEventCat_Configuration_MembersRemovedUser Group members removed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23203SystemEventCat_Configuration_ResourceChangedResource configuration changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23204SystemEventCat_Configuration_ApprovalConfigurationChangedApproval configuration changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23205SystemEventCat_Configuration_AssignmentPolicyChangedAssignment policy changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23206SystemEventCat_Configuration_ConstraintChangedConstraint changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23207SystemEventCat_Configuration_PrioritizationPolicyChangedPrioritization policy changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23208SystemEventCat_Configuration_AuthRoleChangedAuthorization Role created, modified, or deleted.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23209SystemEventCat_Configuration_AuthRoleElementPermissionChangedAuthorization Role element permission added, revoked, or changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23210SystemEventCat_Configuration_UserChangedUser data object changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23211SystemEventCat_Configuration_UserGroupChangedUser Group created, modified, or deleted. Reference changes, such as role assignment changes, appear as changed in the event text.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23214SystemEventCat_Configuration_TimerChangedTimer created, modified, or deleted.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23215SystemEventCat_Configuration_EventDefinitionChangedEvent Definition created, modified, or deleted.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23216SystemEventCat_Configuration_CopyRuleChangedCopy Rule created, modified, or deleted.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23217SystemEventCat_Configuration_MailTemplateChangedMail Template created, modified, or deleted.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23218SystemEventCat_Configuration_ProcessTemplateChangedProcess Template created, modified, or deleted.Actor, EventType, ObjectType, ObjectInformation (object Name and UId), PropertyValues (empty: {}).
23220SystemEventCat_Configuration_DataObjectTypeChangedData Object Type created, modified, or deleted. Changes to its properties, views, and filters are not logged when made separately from the Data Object Type.Actor, EventType, ObjectType, ObjectInformation (object Name and UId), PropertyValues (empty: {}).
23221SystemEventCat_Configuration_CodeMethodConfigurationChangedCode Method Configuration created, modified, or deleted.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23222SystemEventCat_Configuration_DataConnectionChangedData Connection created, modified, or deleted. A Data Connection stores connection details, such as a connection string.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23223SystemEventCat_Configuration_CustomerSettingChangedCustomer Setting modified.Actor, EventType, ObjectType, ObjectInformation, PropertyValues
23224SystemEventCat_Configuration_SystemEventLoggingChangedEnableSystemEventLogging changed.Actor, EventType, ObjectType, ObjectInformation, PropertyValues. Always logged.
23225SystemEventCat_Configuration_MasterSettingChangedMaster Setting modified.Actor, EventType, ObjectType, ObjectInformation, PropertyValues. Always logged.
23226SystemEventCat_Configuration_ChangeSetImportedA changeset was imported. The event is written once per import and identifies who imported it and when. It does not include a changeset identifier.Actor, EventType (Imported), ObjectType (ChangeSet), ObjectInformation (empty), and PropertyValues (empty). Logged when EnableSystemEventLogging is enabled.
23229SystemEventCat_Configuration_DataExchangeConfigurationChangedData Exchange Configuration created, modified, or deleted. It defines a data exchange operation, including its object type and import type.Actor, EventType, ObjectType, ObjectInformation, PropertyValues

Governance events​

Event IDNameDescription
23301SystemEventCat_Governance_SurveyStartedSurvey started.
23302SystemEventCat_Governance_SurveyCompletedSurvey completed.
23303SystemEventCat_Governance_SystemOwnersChangedSystem owners changed.
23304SystemEventCat_Governance_SystemClassificationChangedSystem classification changed.
23305SystemEventCat_Governance_IdentityCreatedIdentity created.
23306SystemEventCat_Governance_IdentityModifiedIdentity modified.
23307SystemEventCat_Governance_IdentityManagersChangedManagers of the identity have been changed.
23308SystemEventCat_Governance_OrgUnitManagersChangedManagers of the organizational unit have been changed.

System operation events​

Event IDNameDescription
23401SystemEventCat_SystemOperation_NewSystemOnboardedNew system onboarded.
23402SystemEventCat_SystemOperation_TechnicalIdentityRequestedTechnical identity has been requested.
23403SystemEventCat_SystemOperation_WarehouseImportSucceededSuccessful Data Warehouse import.
23404SystemEventCat_SystemOperation_WarehouseImportPartiallySucceededPartially successful Data Warehouse import.
23405SystemEventCat_SystemOperation_WarehouseImportFailedFailure of the Data Warehouse import.

Email log​

The Omada Identity’s system administrator can view a log of all emails that the system has generated.

Omada Identity does not log emails that include sensitive material to the email log, for example, emails that include passwords. Find the log by going to Setup > Administration > System Management > Email Log. The initial view shows an overview of generated emails.

The email log shows:

  • The To and From names.
  • The Subject of the email.
  • The Date and Time sent.

View the details of a sent email by clicking the Subject in the list view. The details for the email are shown in the Sent Email dialog box.

The details of a sent email.

You can also find details about sent emails in the SQL Server's database table dbo.tblMailLog.

Data Exchange log​

Whenever you have run a data exchange, a log entry of the data exchange is added to the data exchange log. To find the log for data exchange, go to Setup > Administration > Connectivity > Data Exchange.

In the initial view, right-click the data exchange you want to view and select History. The Data Exchange Log dialog box opens and shows all the data exchanges that have taken place on your system.

Click any of the listed data exchanges to see the Data exchange log details for this data exchange. The Data exchange log details include the date and length of the time when the exchange ran, the status of exchange, the number of objects created or updated, and more.

Data exchange log details.

Timer execution log​

The timer log list displays a list of all timer runs times. To see this log, go to Setup > Administration > Data management > Timers, click the ellipsis (...) menu for a given timer, and select History. The Timer Execution Log will be displayed.

Timer Execution Log.

The Timer Execution Log lists the history of whenever a timer ran:

  • The name of the timer.
  • When the timer ran.
  • The name of the triggering server.

You can also find these details in the Enterprise Server's database. The timer log is stored in a table called dbo.tblTimerLog.

Omada Role and Policy Engine log​

The Role and Policy Engine creates a log for the Event Viewer with the application name Omada Role and Policy Engine with many events to log.

Info messages

IDNameDescription
100GeneralInfoThe 100-series are information messages.
101CycleRunStartedRoPE has started a calculation cycle.
102CycleRunCompletedRoPE has completed a calculation cycle.
104RequeuedPreviousFailuresRoPE has automatically queued identities that previously failed calculation again.
105QueuedIdentitiesWithRecent
ActivationsOrExpirations
The engine has automatically queued identities that either have:

An assignment that was pre-valid at the time of calculation, but has meanwhile entered its validity period

Or:

An assignment that is enabled but with a date in the Valid To setting that is in the past.
106DeletedHistoricCalculationsThe engine has completed the periodic deletion of historic calculations for all identities.
107TraceOutputInfo written for problem tracing purposes.
108PausedRoPE paused.
110CycleRunCleanupCyclerun cleanup error.
111CalculationInfoCalculation message.
112ResumedRoPE resumed.
113GetActualStateEventsLoading actual state events.
114GetActualStateLoading actual state.
115QueuingTasksRoPE service running hourly tasks.
116DailyTasksRoPE service running daily tasks.
117SchemaUpdateSchema updates.
118PublishingOdsMessagesRoPE service publishing Operational Data Store messages.
119DeletingOldOdsMessagesRoPE service deleting old Operational Data Store messages.
120DeleteOldRecordsDelete old cycle runs and related data.

Warning messages

IDNameDescription
200GeneralWarningThe 200-series are warning messages.
201MasterDataIssueA non-fatal issue exists in the engine's master data configuration.
202GetActualStateAssignmentIgnoredAn assignment returned from actual store was ignored.

Error messages

IDNameDescription
300GeneralErrorThe 300-series are error messages.
301LockAndLoadQueued
IdentitiesError
Error occurred while attempting to lock and load queued identities for calculation processing.
302GeneralExecutionErrorGeneral execution error.
303IdentityCalculationErrorError calculating identity.
304BatchProcessingErrorBatch processing error.
305ServiceExecutionErrorService execution error.
306ODWBusinessKeyResolution
Error
Could not resolve an Omada Identity Data Warehouse composed business key to a data object in ES.
307ResourcePoolWithMissing
ODWBusinessKeyError
One or more systems/resource pools detected that has a system category and thus is expected to be present in the Omada Identity Data Warehouse but does not have a business key in the ES.
308SimulationErrorSimulation failed.
309RemoteAPIAuthentication
Failed
Authentication of the RemoteAPI client failed.
310ConfigurationErrorRequired configuration is missing or invalid.
311RollbackFailureRollback failure.
312GetActualStateErrorError occurred loading data.
313GetActualStateErrorGraphQLError occurred loading data - GraphQL Error.
314IdentityCalculationTransientErrorIdentity calculation failed with transient error - retrying.

Other messages

IDNameDescription
900OtherOther.

Omada Provisioning Service logs​

OPS creates a log for the Event Viewer with the application name Omada Provisioning Service with many events to log.

EventIdNameDescription
101FailedToLoadExtensionOPS failed to load extension method.
102UnexpectedDatabaseErrorUnexpected database error.
103EntityValidationErrorsErrors in the entity validation.
130UnhandledErrorUnhandled error.
151FailedParsingConnectionStringFailed parsing of the connection string.
152UpgradeFailedUpgrade failure.
201FailedToLoadSystemConfigurationFailed to load system configuration.
202UnexpectedErrorInSystemManagerUnexpected error in system manager.
203JobDeemedDuplicateDuplicate jobs error.
204ErrorSavingBatchOPS batch could not be saved.
205FailedToInitializeSystemConfigurationFailed to initialize the system configuration.
206FailedToNotifyQueuedFailed to notify queued.
207IntegrityCheckerIntegrity checker.
301TaskProcessingExceptionTask processing exception.
302TaskProcessingFailedTask processing failure.
303JobProcessingFailedJob processing failure.
304NoConnectorsAvailableInPoolNo connectors available in pool.
305ErrorDequeuingJobDequeuing job error.
401StatisticsRefreshedStatistics have been refreshed.
402ThresholdExceededThreshold has been exceeded.
403NotificationErrorNotification error.
501NotificationFailedNotification failed.
502NotificationQueueNotification queue.
601ErrorArchivingJobsJobs could not be archived.
602FailedToInitializeSystemConfigurationInitialization of the system configuration failed.
603UnexpectedErrorInSystemManagerUnexpected error in system manager.
701ErrorPurgingJobsError purging jobs.
702FailedToInitializeSystemConfigurationFailed to initialize system configuration.
703UnexpectedErrorInSystemManagerUnexpected error in system manager.
1001DequeueJobDequeuing of jobs.
1002LoadJobFromStoreJob loaded from store.
1003TaskProcessingConnectorTask processing connector.
1004ProcessingJobJob processed.
1005PersistBatchBatch persisting.
1006PersistBatchDetailsBatch persisting details.
1007PersistBatchDetailsTasksBatch persisting details tasks.

System log on-prem​

You can use the system log to collect specific data that your organization requires. The system log is stored in a table called dbo.tblSystemLog found in the SQL Server.

For example, you could configure code methods that monitor that a specific process is completed and record the details of when they take place. You can configure your code methods to use the .NET methods that are found in a particular Enterprise Server class to produce logs in a readable format for reports and audits.

The benefits of the system log are flexibility of planning and the ability to create code methods to customize the data to log.

Password reset log on-prem​

The Enterprise Server database contains a table tblPasswordResetLog which contains both successful and failed password reset attempts.

The log is only accessible via the SQL Server Management Studio.

The columns are:

ColumnsDescription
IdentityID_The integer ID of the Identity Data Object.
IdentityIdentThe username / IDENTITYID.
ActionTimeThe date and time of the attempt.
Actionsee values in the table below.
MessageDescription of the attempt.
IPthe IP address of the remote client / caller.
Originreference the provisioning service OriginId.

The values of the column Action are:

ValueDescription
Enrolled = 0User enrolled to password reset.
ResetSucceeded = 1Reset success.
ChallengeResponsFailed = 2User failed to answer challenge questions.
ResetFailed = 3Operation failed.
SoftLocked = 4Threshold for failed attempts exceeded (temporary lock).
HardLocked = 5Threshold for failed attempts exceeded (locked).
IdentityIdentFailed = 6The entered username was not recognized.
Submitted = 7The password change has been handed over to a provisioning service.
Throttling = 8Password reset web page is throttling because of many failed requests.
Unlocked = 9Identity was unlocked by an administrator.
PartialSuccess = 10The password reset action partially succeeded.
ConfigurationError = 11Wrong configuration of password reset handlers.