Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
3262 views

HPOV-STO error in eventlog

What does this error really mean? How do I fix it?

Source: HPOV-STO
Category: None
Type: Error
Event ID: 1024
Description: (MDLAPI24) Node platform matching failed.; origHR=c1ff0018; wbemHR=8004101d; finalHR=80041001

Thanks in advance.

Adam
Labels (1)
0 Likes
18 Replies
Cadet 1st Class
Cadet 1st Class

Hello

Are you seeing this error for node with OM 8.60.501 agent or previous version?

Regards
Ram
0 Likes
Cadet 1st Class
Cadet 1st Class

Hello

Also what operation on the OMW server triggers this error?

Regards
Ram
0 Likes
Absent Member.
Absent Member.

i have a mix of agent versions. 8.6 -> 8.6.501

i have no idea what is causing this. that is why i posted.

this is just showing up on my mgmt server in the event log. no idea what or where it is coming from.
0 Likes
Cadet 1st Class
Cadet 1st Class

Hello

How frequently do you see the error? I wonder if it is coming from the nightly agent-server synchronization (which means you will see the error once a day around 3:00 AM)

What is the OMW server patch level?
Regards
Ram
0 Likes
Absent Member.
Absent Member.

patch 90.

This happens thoughout the day. No set interval.

Last 2 times were
10:47 and 11:02 but has not occurred since 11:02.

0 Likes
Cadet 1st Class
Cadet 1st Class

Hello

Setup tracing for OvStoreProv and see if it shows you anything useful.

If you do have HP Support contract then get in touch with them for this issue.

Hope this helps.
Regards
Ram
0 Likes
Absent Member.
Absent Member.

Hi Adam,
Have you succeeded in solving of this problem?

Kind regards,
Evzen
0 Likes
Absent Member.
Absent Member.

No luck. I am disappointed with HP Support once again.
0 Likes
Absent Member.. Absent Member..
Absent Member..

Same situation as you Adam - been having those errors for quite some time on multiple management servers. Recent upgrades to the latest Windows agent on the management server have not solved it. Nor has the latest management server patches - though we've yet to try OMW_000117 that was released this week. Interested. My theory on it was there was a managed node on the server where OMW couldn't determine the OS type, or at least it didn't match any OS type definition that it had. This used to happen for us with W2k8 R2 nodes for example, but I thought that the latest patches had introduced that OS type to the mgmt server.

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

Could be this microsoft issue

 

http://support.microsoft.com/kb/889405

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

Hi Adam,

 

We are seeing this error message also.  Were you able to find anything out from HP?

 

Thanks,

Brandy

http://www.linkedin.com/in/brandyreid
Say "Thanks" by clicking on Kudo's to the left 🙂
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.