This article has been archived. It is offered "as is" and will no longer be updated.
Rapid publishing disclaimer
Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.
OVO Node is not managed or missing.
These errors are telling you that the GUID the connector is trying toupdate in OVO does not exist.
This can happen when either the node isnot part of a 'Node Group' in OVO or there is a 'Template' catching the initial event from the node in question and discarding it.
You can find out what node is causing this error by putting theconnector in debug mode '1 - ALL' and looking for the 'Invalid ID'returned in the momprodconn.log. Above the error will list all theproperties the connector is passing to OVO and the node name/ip will be one of them.
Once you determine what node is causing the issue try running the'opcmsg' command from a command prompt on the OVO server and generate an event for the node in question and see if it displays in the OVO Message Browser. If it displays properly then you most likely have a template catching the alert coming from MOM and discarding it.
If it does not display the event in the OVO Message Browser verify thenode is part of a 'Node Group' or check your templates.
The connector works as follows:
New alert is generated in MOM.
Auto-forward rule in MOM sends alert to OVO.
OVO agent on OVO server accepts new alert from MOM and returns theGUID for the event in OVO to MOM and stores it in the 'Ticket ID' field of the MOM alert.
OVO agent forwards event up to OVO server.
OVO server checks the event against 'Node Groups' and 'Templates' to verify event should be accepted or rejected.
If the event is rejected, the next time the connector tries tomodify/acknowledge the event from MOM, OVO will return the error'Invalid ID' as it was not added to the OVO database.