Question regarding .TMP files
I have the connector working and sending XML alerts to my remote system. My question is, if I update an alert in the SCOM console before the XML file is processed, a TMP file gets created with the updated value. Is the connector working properly? I've even found that if I delete the XML file then update the alert within SCOM, a new XML file is created with the original values but the updated values come across in TMP file.

Thanks in advance,

  • Moved by Robert_Hearn Tuesday, March 09, 2010 6:19 PM migrated (From:Interop - Universal Connector)
November 10th, 2009 4:32pm

Hi Scott,

Any updatesfrom OpsMgr sideend up with xml files in the "FromOpsMgr" subfolder. A tmp file is created while the Interop provider is processing the received update and then renamed to xml right after it completes the processing.

If you delete an xml file in "FromOpsMgr" folder and you don't do the necessary "Ack" (create an "Ack" xml in the folder with your management group name), the Interop connector will treat the forwarding as a failure and it will try to resend the same update. (By default, it will retry for 5 times). This is probably the reason that you see the XML file with the original values.

For UNV integration detail, please refer the "SCOM2007R2_UniversalConnector_DevelopingAnIntegration.doc" in the release package.

Douglas [MSFT]

  • Marked as answer by Robert_Hearn Monday, January 04, 2010 6:22 PM
Free Windows Admin Tool Kit Click here and download it now
November 10th, 2009 5:26pm


From the white paper titled - SCOM2007R2_UniversalConnector_DevelopingAnIntegration.doc included with the connector download.

Create the acknowledgement file to let Operations Manager know the alert was received

Things to consider:

-          If you do not send an acknowledgement back to Operations Manager, Operations Manager will forward the alert again until it receives an acknowledgement or it exceeds the maximum number of retries. 

          The acknowledgement file must be created in a directory with the same name as the management group from which it came.  This enables the Universal Connector to handle multiple management groups.  The directory where the acknowledgement file should be created is:

  • %ProviderInstallDirectory%\UnvEvents\%ManagementGroup%

-          The %ManagementGroup% directory is not created by default, so the integration logic must check for its existence and create it if it doesnt exist.

-          The acknowledgement file must contain the following attributes at a minimum:

  • AlertId
  • EventId
  • EventType=2
  • ManagementGroupName

-          Notice the EventType value for an acknowledgement is 2.

-          The value of EventId will be placed in the TicketId property in the Operations Manager alert.

  • Proposed as answer by Monday, June 17, 2013 9:15 AM
June 13th, 2013 12:01pm

Then try to send ack:

AlertID = lslkkldfkldf
EventType = 2
EventID = MyTicketNumber
ManagementGroupName = MyGroup

I got in Ticked ID on SCOM side: ERROR: received ack with no TicketId

how to know that is wrong there? 

  • Edited by Wednesday, June 26, 2013 1:14 PM edited
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2013 12:43pm

solved - it was my mistake in .std file I describe Ticked Id as EventID but not EventId, so in tag in file was not properly understand by OpsMgr. 
  • Proposed as answer by Thursday, June 27, 2013 11:43 AM
June 27th, 2013 11:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics