Highlighted
Acclaimed Contributor.
Acclaimed Contributor.
547 views

SM and OMI OOB integration is not working

Hello All

We have OMI 10.60 and SM 9,40 integrated and when we raise SM incident from OMI, we see following error in sm.log file,

24571( 24801) 07/25/2017 08:49:32  RTE D (0x99082F60)      DBACCESS - Cache Find   against file scmessage found 1 record (syslanguage="en" and class="scjs" and message.id="0")
 24571( 24801) 07/25/2017 08:49:32  RTE E Script failed: Error in executing script BDM_SM.processRequestError in executing script 'BDM_SM.processRequest'Error in executing script BDM_SM.processRequest: ValidationFailedException: Validation failed for probsummary - failed to add record
 24571( 24792) 07/25/2017 08:49:32 JRTE E Caught exception:
com.hp.ov.sm.common.core.DAOValidationFailedException: : Validation failed for probsummary - failed to add record

It does not show which field validation failed and all.

Is there any way we can find this information.

0 Likes
9 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

check the sm.log for HPSM.   If not there, then turn on tracing with debughttp:1 

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

Dear

We had done the tracing in SM end and from sm.log, I had shown the errors.

Without doing the tracing, there will be no errors in sm.log

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

I don't see any SOAP Requests or Responses.  Are you sure you traced with the parameter debughttp:1?

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

Hello Tom

Traced with debughttp:1

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

Can you attach the log here for review?

Also, can you look through your log for this thread:

24571( 24792)

That's the one that mentioned the failed validation on probsumarry.  Look very carefully to see if says the actual validation message received.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

Hi

I am not able to attach the log file here, since it accepts only image files. Can I send me an message with your email id, so I can send the log file.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

Message sent.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

Hello Powe

We further digged and found that AUTO assignment group is not assigne to OM integration user. And we disabled one validation ruleset im.fields.validation and then we see that it is creating SM incident.

How do we find that which field from OMI is causing the error in the validation ruleset im.fields.validation. We know we can disable one by one and check, but is there any other way which can tell us where the issue lies.

Please help

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: SM and OMI OOB integration is not working

I replied to your email. It looks like a validation on the probsummary format control. 

24571( 24810) 07/25/2017 08:50:49  RTE I Undisplayed message:Trippletdesc is required.  <-This is the validation you hit

24571( 24810) 07/25/2017 08:50:49  RTE I Undisplayed message:[BDM Mapping] Replace invalid category 'Infrastructure'

Here is where in the trace this all occurred…..

 

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    454 [ 0] format.cadd                         decide.vals               decision     CPU(    0      2 )

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    454 [ 0] format.cadd                         calculate.vals            userdefn     CPU(    0      2 )

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    454 [ 0] format.cval                         start                     decision     CPU(    0      2 )

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    454 [ 0] format.cval                         calc.validations          process      CPU(    0      2 )

24571( 24810) 07/25/2017 08:50:34  RTE D (0x98963900)      DBACCESS - Cache Find   against file ScriptLibrary found 1 record (name="DisplayName")

24571( 24810) 07/25/2017 08:50:34  RTE D SCRIPTTRACE: DisplayName.validateRefField entered, line 1171

24571( 24810) 07/25/2017 08:50:34  RTE D SCRIPTTRACE:Parameter type:RELATION value:probsummary={["IM3050356", "incident", '07/25/17 08:50:34', "OMSMIntegrUser", "3", "1", , "EN-DATA", , , , , , , , , , , , , , , , , , , , , , , , , , , , , , {"<none>"}, {}, {}, {}, {}, , , , , , "91445ECE-40BF-4443-B386-025FC8715AE1", , , , , , , , , , , , {"

 

 

24571( 24810) 07/25/2017 08:50:34  RTE D SCRIPTTRACE:Parameter type:STRING2 value:trippletdesc

24571( 24810) 07/25/2017 08:50:34  RTE D (0x98963900)      DBACCESS - Cache Find   against file ScriptLibrary found 1 record (name="DisplayName")

24571( 24810) 07/25/2017 08:50:34  RTE D (0x985CF990)      DBACCESS - Cache Find   against file scmessage found 1 record (syslanguage="en" and class="ruleset" and message.id="1")

24571( 24810) 07/25/2017 08:50:34  RTE D SCRIPTTRACE: DisplayName.validateRefField exited, elapsed: 1 ms

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    460 [ 0] format.cval                         test.result               decision     CPU(    0      2 )

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    460 [ 0] format.cval                         gen.message               process      CPU(    0      2 )

24571( 24810) 07/25/2017 08:50:34  RTE D (0x985CF990)      DBACCESS - Cache Find   against file scmessage found 1 record (syslanguage="en" and class="us" and message.id="1742")

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    460 [ 0] format.cval                         check.popup               decision     CPU(    0      2 )

24571( 24810) 07/25/2017 08:50:34  RTE D RADTRACE    460 [ 0] format.cval                         bad.validation.msg        userdefn     CPU(    0      2 )

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.