Security Manager 5.00
Security Manager 5.1
Security Manager 4.X
The agent was unable to complete an I/O operation on file C:\Program Files\MCS OnePoint\OnePoint\Mission Critical Software\OnePoint\<configuration group name>\EvtCons.wkf
Event 21257 is logged in the Windows application log.
The central computer was scanned by another central computer and it now shows up in the managed computer list of the second central computer.
Event 21249 is logged showing that a central computer failed to contact another central computer.
This is caused by one of the following conditions:
- The account under which the OnePoint service runs does not have create\modify file permissions in the C:\Program Files\MCS OnePoint\OnePoint\Mission Critical Software\OnePoint\<configuration name> folder.
- The file is either corrupt or a remnant from a previous agent installation.
- The Onepoint process may not have actually stopped before another instance of the process started up.
- If an agent was installed on a central computer, this would cause the 21249 event
- On 5.0, a second Central Computer scanned this central computer and has marked it as an agent. Please contact NetIQ Technical Support for information about how to resolve this situation. This situation is caused when central computers are included in either manualmc.txt files or included in other CC's managed computer rules. To avoid this, do not list any central computers in the manualmc.txt files and make sure to have an exclude for every other Central Computer in the managed computer rules. For example, you have 2 central computers. On CC 1, you would have an include for CC 1 and an exclude for CC 2. On CC 2, you would have an include for CC 2, and an exclude for CC 1.
After stopping the OnePoint service\process on the problem computer, restart the service. If that does not work, reboot the box (and if necessary delete the file). If you suspect that another CC has scanned this CC, then please contact NetIQ Technical Support for information about how to resolve this problem.
This is a dynamically created cache file. Deleting it will result in the loss of queued events that have not yet been sent to the Consolidator.