Laserfiche WebLink
• <br />• <br />• <br />24SEVEN <br />3. ERROR <br />Version 2.6 <br />CompuDyne Proprietary <br />CAD Services — Overview <br />Before we catch an error in our multi - tiered catching system, we attempt to send it as far along in the <br />Message Receiving Process as possible (see Figure 1 page 3), just before it runs into the point of failure. <br />Most errors are logged in the Windows Event Viewer, but if possible, the message is saved to a MSMQ <br />(Microsoft Message Queue Server) recovery queue to be re -sent later with the CADM. That helps us get <br />messages easily back into the system, and speeds up debugging of errors. <br />3.1 TYPES OF ERRORS <br />3.1.1 BAD DATA ERROR <br />Bad Data Error — This is when the Message makes it completely through the process but has bad data. <br />If it is missing required fields, it will be inserted into our CAD messages tables in the 24SEVEN <br />database, but not into the tables that are accessed by the application. With this type of Error, an Error <br />code will be written into the table. Our current Message Reject codes are: <br />Message Reject Codes <br />Code Description <br />Code Number <br />No Incident Data Field <br />No Incident Number Field <br />p <br />No Incident Data or Number Field <br />g <br />Unknown Data Error <br />q <br />2. Database Error — This level of error catching occurs if the process cannot access the database due to <br />bad configuration or network issues. The messages are then placed into a different MSMQ, called our <br />CAD 24SEVEN Recovery Queue. The QPAdmin application allows viewing and resending of <br />messages back into the process. <br />3. Unknown Error — Unknown Error — If a message cannot be placed into a MSMQ or a Recovery <br />Queue, the error is unknown, and logged into the Windows Event Viewer. There is no storage option <br />for the message, if the error occurs at this level and the message is lost, the Administrator is alerted <br />inside of the Windows Event Viewer <br />CompuDyne <br />CompuDyne Proprietary <br />December 28, 2005 <br />Page 7 <br />