03-07-2011 07:59 AM
Event ID: 1024
Description: (MDLAPI24) Node platform matching failed.; origHR=c1ff0018; wbemHR=8004101d; finalHR=80041001
Thanks in advance.
03-07-2011 08:15 AM
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.
03-07-2011 08:18 AM
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?
03-07-2011 08:49 AM
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.
06-30-2011 02:21 AM
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.
03-06-2012 07:38 AM
We are seeing this error message also. Were you able to find anything out from HP?
Say "Thanks" by clicking on Kudo's to the left :)
07-10-2012 11:17 AM
Has anyone successfully resolved this with HP? We had it for quite some time, we refreshed several servers and it went away. I assumed it was a node messed up in the database and that the node was removed. Now the error is back and I am not over joyed to go back to HP support to resolve. If they create an error in their system shouldn't they have documentation to what it relates to and some proper steps to resolve.
Do not mean to rant but have spent 3 months trying to resolve previously with no luck.
03-28-2013 09:42 AM
Anyone know how to solve this issue?
I received this same error message in Windows Event Log recently in OMW 9 (OMW_00150).