The DEMS events and errors are logged in the DEMS log file DEMSLog.txt and in Windows events log.
To view the description of the events, open Windows Event Viewer, and click Unisys Data Exchange under Applications and Services Logs.
You can view the possible Error IDs and their descriptions in the following table:
Table 3. Error IDs and Descriptions
| Error Id | Error Description |
|---|---|
| 0 | Event completed successfully |
| 1 | Unknown error |
| 10000 | Environment already exists |
| 10001 | User role already exists |
| 10002 | Login user already exists |
| 10003 | Security profile already exists |
| 10004 | Internal object already exists |
| 10005 | Environment not found |
| 10006 | User role not found |
| 10007 | Login user not found |
| 10008 | Security profile not found |
| 10009 | Not allowed to delete the built-in environment |
| 10010 | Not allowed to delete the built-in user role |
| 10011 | Not allowed to delete the built-in login user |
| 10012 | Not allowed to delete the built-in security profile |
| 10013 | The environment name is invalid |
| 10014 | The user role name is invalid |
| 10015 | The login user name is invalid |
| 10016 | The security profile name is invalid |
| 10017 | The description is invalid |
| 10018 | The domain name is invalid |
| 20001 | Not allowed to delete the last DEMS admin user |
| 20002 | The principal server is down |
| 20003 | Cannot find the principal |
| 20004 | Local user group on a remote machine name is not allowed |
| 20005 | Invalid machine name |
| 20006 | The default security profile cannot be deleted |
| 20007 | Invalid security profile operation |
| 20008 | Invalid internal model state |
| 20009 | Not allowed to revoke the last DEMS admin user. |
| 30001 | The user is not authorized to open the DEMS site |
| 40001 | Failed to connect to DEMS |
| 40002 | The version of the DE component is higher than the DEMS |
| 40003 | The version of the DE component is no longer supported |
| 40004 | The request to DEMS failed |
The event data always contains 8 parameters. Some of the values may be empty if it is not applicable, but an empty data item still remains there.
An Event data is formatted as:
<EventData> <Data>The event description.</Data> <Data>The result of the event.</Data> <Data>A before image of the DEMS item being changed.</Data> <Data>An after image of the DEMS item being changed.</Data> <Data>The 5 digit error ID.</Data> <Data>A component effected, such as DEMS, DDW or Admin.</Data> <Data>The user id who performed the operation.</Data> <Data>Diagnostic information for the error.</Data> </EventData>
You can view the possible Event Ids their descriptions in the following table:
Table 4. Event ID and Description
| Event ID | Description |
|---|---|
| 1000 | User signed in |
| 2000 | Client query information in DEMS |
| 3000 | Environment created |
| 3001 | User role created |
| 3002 | Login created |
| 3003 | Security profile created |
| 3004 | Duplicate user role created |
| 4000 | Environment updated |
| 4001 | User role updated |
| 4002 | Login updated |
| 4003 | Security profile updated |
| 5000 | Environment deleted |
| 5001 | User role deleted |
| 5002 | Login deleted |
| 5003 | Login deleted |
| 5004 | Security profile deleted |
| 6000 | Data Exchange Development Workbench user authentication |
| 6001 | Admin Site user authentication |
| 6002 | Admin Service user authentication |
| 6003 | Runtime Service user authentication |
| 6004 | DE SQL Server Service user authentication |
| 6005 | Installation user authentication |
| 6100 | Data Exchange Development Workbench fetched application configuration |
| 6101 | Admin Site fetched application configuration |
| 6102 | Admin Service fetched application configuration |
| 6103 | Runtime Service fetched application configuration |
| 6104 | DE SQL Server Service fetched application configuration |
| 6105 | Installation fetched application configuration |