Summary
The following table lists events that you can monitor in your Moxie environment
|
ID Number
|
Sources
|
Message Type
|
Description
|
| 1000 |
Data Server Agent Client Logging Agent Log Server Sync Server Script Engine |
Information | The service started successfully |
| 1005 | Data Server | Information | DataPipe connection status information |
| 1006 | Data Server | Information | Primary DataPipe server is now connected |
| 1007 | Data Server | Information | Primary DataPipe server has disconnected |
| 1010 | Data Server | Information | This series of messages is for information on the Data Server |
| 1011 | Data Server | Warning | Incorrect Passphrase entered |
| 1020 | Data Server | Information | Indicates whether the Data Server has successfully connected to the SQL Server |
| 1021 | Data Server | Information | Indicates whether the Data Server has successfully accessed the file cache |
| 1030 | Data Server | Information | Indicates the status of the Data Server license |
| 1051 |
Log Server Client Logging Agent Data Server Player |
Information | Indicates whether there is sufficient disk space for log files |
| 1100 |
Data Server Agent Client Logging Agent Log Server Sync Server Script Engine |
Information | The service has stopped |
| 1200 | Player | Information | Indicates the content logging status |
| 1250 | Player | Warning | A potential problem has been detected logging Player content |
| 1300 | Sync Service | Information | This series of messages is for information on the Sync Service |
| 1350 | Sync Service | Warning | A potential problem has been detected with the Sync Service |
| 1400 | Script Engine | Information | This series of messages is for information on the Script Engine |
| 1450 | Script Engine | Warning | A potential problem has been detected with the Script Engine |
| 1500 | Agent | Information | This series of messages is for information on actions executed by the Moxie Agent |
| 1600 | Log Server | Information | The Log Server has received or processed log data |
| 1700 | Log Server | Information | This series of messages is for information on the Log Server |
| 2000 | Data Server | Error | An error occurred with Data Server communications |
| 2005 | Data Server | Error | DataPipe connection status error |
| 2010 | Data Server | Error | An error occurred with the Data Server |
| 2020 | Data Server | Error | An error occurred with the Data Server SQL Connection |
| 2021 | Data Server | Error | An error occurred with the Data Server file cache access |
| 2022 | Data Server | Error | Incorrect Data Server impersonation credentials |
| 2030 | Data Server | Error | An error occurred with the Data Server license |
| 2040 | Data Server | Error | A SQL error occurred on the Data Server |
| 2050 | Sync Service | Error | An error occurred with the File Watcher |
| 2051 |
Log Server Client Logging Agent Data Server Player |
Error | Insufficient disk space for log files |
| 2060 | Data Server | Error | An error exporting a workspace |
| 2070 | Data Server | Error | An error importing a workspace or file |
| 2080 | Log Server | Error | An error importing or exporting data from the Log Server |
| 2090 | Data Server | Error | An error sending content files from the Data Server |
| 2100 | Agent | Error | An error occurred during a remote upgrade |
| 2110 | Agent | Error | An error occurred with the Agent communications channel |
| 2200 |
Log Server Client Logging Agent |
Error | An error occurred logging content |
| 2300 | Sync Service | Error | An error occurred on the Sync Service |
| 2400 | Script Engine | Error | An error occurred on the Script Engine |
| 2700 | Log Server | Error | An error occurred on the Log Server |
| 2710 | Log Server | Error | An error occurred when attempting to compress a log package |
| 2720 | Log Server | Error | An error occurred opening a log package |
| 2721 | Log Server | Error | An error occurred with the permissions to write to the Log Server SQL database |
| 2722 | Log Server | Error | An error occurred with the Log Server SQL database |
| 2723 | Log Server | Error | An error occurred when attempting to decompress a log package |
| 2724 | Log Server | Error | An error occurred when attempting to unpackage the log data zip file |
| 2725 | Log Server | Error | The log data zip file is corrupt |
| 2726 | Log Server | Error | An error occurred when attempting to remove old data from the log data folder |
| 2730 | Log Server | Error | The log uploader failed to start |
| 2731 | Log Server | Error | The log uploader failed to stop |
| 2732 | Log Server | Error | A critical error occurred uploading data to the log database |
| 2733 | Log Server | Error | The log uploader task failed while waiting to upload files to the log database |
| 2734 | Log Server | Error | The log uploader task failed to stop |
| 2740 | Log Server | Error | The Log Server is not configured |
| 2750 | Log Server | Error | An error occurred when attempting to connect to the log status repository |
| 2751 | Log Server | Error | The Log Server encountered a critical error when attempting to write to the log status file |
| 2752 | Log Server | Error | The request to read log status file failed |
| 2760 | Log Server | Error | An unexpected log file name was encountered |
| 2761 | Log Server | Error | The reconciliation log file name was not relative |
| 2770 | Log Server | Error | An error occurred while attempting to write the Log Server status to the database |
| 2771 | Log Server | Error | The Log Server status file is corrupt |
| 2772 | Log Server | Error | Log Server status file batch fail |
| 3000 | Agent | Information | This series of messages is for information on remote deployments |
