Why does the server record the ID 16640 Error at the same time in Event Viewer?
A. The “system logging facility” on Windows is the Event Logger. The Windows interface to the Event Logger requires you to specify an Event ID. Smarts defines the Event ID EVLOG_GENERIC (which has value of 16640). An Event ID has a string containing descriptive text and places to substitute arguments in it. EVLOG specifies that there will be a single argument which will substitute for the entire message. What Smarts substitutes is the entire, formatted text of the message, just as it would appear in the log file. 16640 events from Smarts in Windows are general. Basically, any error logged by DFM which is of high severity will also be logged to the Windows event viewer with code 16640. The error message is about an inconsistency in the topology being corrected during auto discovery. While processing, a call was made to “oczcb110” which at that time was not in the topology (resulting in “call on a NULL repository object”). Furthermore, the same object was being managed by 2 separate DFM
Related Questions
- Every time when the server shuts down I get error reports that F-Secure SMTP and Real-Time Scanners cannot connect to the server. What is the problem?
- After Webcasting for a short time using the Push mode, I get a Server Disconnected error. What’s wrong?
- If a non-exempt employee works an evening event with no HCC access, how will they record their time?
