Service Desk Practitioners Forum
cancel

SD NNM integration Issue

Highlighted
harsh_3
New Member.

SD NNM integration Issue

We have SD 4.5 on windows in our environment along with NNM 7.5 on windows. I have integrated NNM with SD for automatically logging incidents in SD from NNM.

It was working fine till i upgraded the NNM to 7.51 with latest consolidate patch. After upgradation of NNM incidents are not being logged in SD. In ovactiond log file gives an error :"returned standard output data:
Error occurred, check: sd_event_error.log"

sd_event.log has the error : "SERVER_RESPONSE=ERROR: This instance of incident can not be processed, because not all primary keys values have been provided."

When i try logging the incident from command prompt it logs the incident in SD.

Has anyone faced this issue / or has any solution to this.
Will be generous with points if anyone can help.
1 REPLY
Ondra Ernyei
Honored Contributor.

Re: SD NNM integration Issue

Hello Harsh,

it seems NNM doesn't fill in all the necessary parameters, assuming from your description that the incident registration by hand works.
To find the root cause of this, instead of calling sd_event try to redirect the command call to an log file to see what NNM does.
Some parameter has to be missing.

I hope this helps,

Ondra