Highlighted
Absent Member.. Absent Member..
Absent Member..
243 views

UCMDB-SM Data Push Issue

Jump to solution

Hi Experts,

 

I've integrated UCMDB-SM and there seems to be an issue with SM data push.

 

Error message that I get is following:

Validation Check Fails Error from SM, return code 71, the error message is "Validation failed"

 

Response message from SM

<cmn:messsage type="String">No link records exist for this format or file.</cmn:message>

<cmn:messsage type="String">Key #2 is empty. (se.base.method,add.record.radd)</cmn:message>

<cmn:messsage type="String">file:(device) key:(logical.name=xxx.xxx.xxx.xxx DEFAULTDOMAIN)(se.base.method,add.record.radd)</cmn:message>

<cmn:messsage type="String">The record being added contains a NULL key. (se.base.method,add.record.radd)</cmn:message>

<cmn:messsage type="String">file:(joincomputer) key:(file.device,local.name=xxx.xxx.xxx.xxx DEFAULTDOMAIN)(se.base.method,add.record.radd)</cmn:message>

<cmn:messsage type="String">The record being added contains a NULL key. (se.base.method,add.record.radd)</cmn:message>

<cmn:messsage type="String">This record contains an invalid null key.</cmn:message>

 

Is this indicating the issue is with SM side or UCMDB side?

 

Can anyone help me what exactly the issue is in here? How can I resolve this?

 

I've also attached print screen for reference.

 

Thanks,

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: UCMDB-SM Data Push Issue

Jump to solution

Hello,

 

This issue is mentioned in the Troubleshooting section of UCMDB-SM Integration guide, page 233  :

http://support.openview.hp.com/selfsolve/document/KM00642838

 

Pasting the Solution section below for your quick reference :

 

Solution

Find the key number in the <messages> section to see which No Nulls key has a NULL value. For
example, if you find a message “Key #1 is empty”, check the first key definition of the device table
to see which field(s) this key is for, and then make sure that a non-NULL value has been mapped to
the field(s) in the XSLT file.

For instructions on how to configure an attribute mapping, see "How to Map the CI Attribute to a
Web Service Field" on page 144.

 

 

Regards,

Unni

 

“Micro Focus Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”

Click the KUDOS star to say 'Thanks'

View solution in original post

0 Likes
2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: UCMDB-SM Data Push Issue

Jump to solution

Hello,

 

This issue is mentioned in the Troubleshooting section of UCMDB-SM Integration guide, page 233  :

http://support.openview.hp.com/selfsolve/document/KM00642838

 

Pasting the Solution section below for your quick reference :

 

Solution

Find the key number in the <messages> section to see which No Nulls key has a NULL value. For
example, if you find a message “Key #1 is empty”, check the first key definition of the device table
to see which field(s) this key is for, and then make sure that a non-NULL value has been mapped to
the field(s) in the XSLT file.

For instructions on how to configure an attribute mapping, see "How to Map the CI Attribute to a
Web Service Field" on page 144.

 

 

Regards,

Unni

 

“Micro Focus Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”

Click the KUDOS star to say 'Thanks'

View solution in original post

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: UCMDB-SM Data Push Issue

Jump to solution

Thanks Unni for suggestion.

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.