redfishlib.cpp:264 :: In executeRedfishCall()

apiVersion: soultec.ch/v1kind: Postmetadata: name: redfishlib-cpp264-in-executeredfishcall locale: en labels: author: dario-doerflinger series: lessons-learned capability/virtualization: 1.37 vendor/vmware: 0.88 annotations: source: blog-content/posts/en/redfishlib-cpp264-in-executeredfishcall.md route: /en/insights/redfishlib-cpp264-in-executeredfishcall/ schema: /nerd/schema/posts.json markdown: /en/insights/redfishlib-cpp264-in-executeredfishcall.mdspec: title: "redfishlib.cpp:264 :: In executeRedfishCall()" date: 2024-01-31 author: dario-doerflinger locale: en summary: >- On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter, so a cluster image can carry the firmware as well. capabilities: [virtualization] vendors: [vmware] series: lessons-learned hero: /blog-assets/redfishlib-cpp264-in-executeredfishcall/hero.webp migrated: 2026-08-24 translationReviewed: false draft: false sections: - body: | On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter. Those components let us define a cluster image that includes the firmware. - heading:

Prerequisites

body: | A few things have to be in place for these features: - HPE OneView is installed - The HPE SPP is registered in HPE OneView - The server hardware is recorded in HPE OneView - HPE OneView for vCenter is installed and configured - The SPP is registered in vCenter - The cluster image is configured, firmware components included - The servers already have the vendor add-on installed (that is what brings the SUT tool) - The servers have SUT configured in AutoDeploy mode - heading:

The problem

body: | In one environment we could not stage or remediate a host. These errors kept showing up in the log: **\[INFO\] :: \[redfishlib.cpp:264\] :: In executeRedfishCall(), the operation is rawget the link is /redfish/v1/systems/1/hpserversettings/firmwaredriverbaselinesettings/** **\[ERROR\] :: \[redfishlib.cpp:352\] :: Error value from Transaction is : -12 and error name is HTTP server returned error status.** \[ERROR\] :: \[sutmetadatainterface.cpp:739\] :: Unable to sync OV to HP Tools in RIS We found them in /var/log/sut.log. ### Troubleshooting steps None of these solved it: - Reboot the ESXi host - Reboot HPE OneView - Reboot HPE OneView for vCenter - Reboot vCenter Server - Reset the HPE iLO The log messages stayed exactly the same and the host would not take the new firmware. - heading:

Solution

body: | The remaining options would have been: - Remove the HPE server from HPE OneView and add it again - Reinstall ESXi on the HPE server - Open an HPE support case Removing the host from HPE OneView and adding it back made the errors disappear. *Solution: re-register the HPE server in HPE OneView.*status: corpus: 267 alsoLike: - {ref: posts/announcing-end-of-support-life-for-vsphere-7-0, score: 1.00} - {ref: posts/hpe-vm-essentials-part-2, score: 1.00} - {ref: solutions/vmware/vsphere-foundation, score: 0.59}

{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "redfishlib-cpp264-in-executeredfishcall", "locale": "en", "labels": { "author": "dario-doerflinger", "series": "lessons-learned", "capability/virtualization": "1.37", "vendor/vmware": "0.88" }, "annotations": { "source": "blog-content/posts/en/redfishlib-cpp264-in-executeredfishcall.md", "route": "/en/insights/redfishlib-cpp264-in-executeredfishcall/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/redfishlib-cpp264-in-executeredfishcall.md" } }, "spec": { "title": "redfishlib.cpp:264 :: In executeRedfishCall()", "date": "2024-01-31", "author": "dario-doerflinger", "locale": "en", "summary": "On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter, so a cluster image can carry the firmware as well.", "capabilities": [ "virtualization" ], "vendors": [ "vmware" ], "series": "lessons-learned", "hero": "/blog-assets/redfishlib-cpp264-in-executeredfishcall/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false }, "sections": [ { "body": "On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter. Those components let us define a cluster image that includes the firmware." }, { "heading": "

Prerequisites

", "body": "A few things have to be in place for these features:\n\n- HPE OneView is installed\n- The HPE SPP is registered in HPE OneView\n- The server hardware is recorded in HPE OneView\n- HPE OneView for vCenter is installed and configured\n- The SPP is registered in vCenter\n- The cluster image is configured, firmware components included\n- The servers already have the vendor add-on installed (that is what brings the SUT tool)\n- The servers have SUT configured in AutoDeploy mode" }, { "heading": "

The problem

", "body": "In one environment we could not stage or remediate a host. These errors kept showing up in the log:\n\n**\\[INFO\\] :: \\[redfishlib.cpp:264\\] :: In executeRedfishCall(), the operation is rawget the link is /redfish/v1/systems/1/hpserversettings/firmwaredriverbaselinesettings/**\n\n**\\[ERROR\\] :: \\[redfishlib.cpp:352\\] :: Error value from Transaction is : -12 and error name is HTTP server returned error status.**\n\n\\[ERROR\\] :: \\[sutmetadatainterface.cpp:739\\] :: Unable to sync OV to HP Tools in RIS\n\nWe found them in /var/log/sut.log.\n\n### Troubleshooting steps\n\nNone of these solved it:\n\n- Reboot the ESXi host\n- Reboot HPE OneView\n- Reboot HPE OneView for vCenter\n- Reboot vCenter Server\n- Reset the HPE iLO\n\nThe log messages stayed exactly the same and the host would not take the new firmware." }, { "heading": "

Solution

", "body": "The remaining options would have been:\n\n- Remove the HPE server from HPE OneView and add it again\n- Reinstall ESXi on the HPE server\n- Open an HPE support case\n\nRemoving the host from HPE OneView and adding it back made the errors disappear.\n\n*Solution: re-register the HPE server in HPE OneView.*" } ], "status": { "corpus": 267, "alsoLike": [ { "ref": "posts/announcing-end-of-support-life-for-vsphere-7-0", "score": "1.00" }, { "ref": "posts/hpe-vm-essentials-part-2", "score": "1.00" }, { "ref": "solutions/vmware/vsphere-foundation", "score": "0.59" } ] }}

apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "redfishlib-cpp264-in-executeredfishcall"locale = "en"[metadata.labels]author = "dario-doerflinger"series = "lessons-learned""capability/virtualization" = "1.37""vendor/vmware" = "0.88"[metadata.annotations]source = "blog-content/posts/en/redfishlib-cpp264-in-executeredfishcall.md"route = "/en/insights/redfishlib-cpp264-in-executeredfishcall/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/redfishlib-cpp264-in-executeredfishcall.md"[spec]title = "redfishlib.cpp:264 :: In executeRedfishCall()"date = 2024-01-31author = "dario-doerflinger"locale = "en"summary = "On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter, so a cluster image can carry the firmware as well."capabilities = ["virtualization"]vendors = ["vmware"]series = "lessons-learned"hero = "/blog-assets/redfishlib-cpp264-in-executeredfishcall/hero.webp"migrated = 2026-08-24translationReviewed = falsedraft = false[[sections]]body = "On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter. Those components let us define a cluster image that includes the firmware."[[sections]]heading = "

Prerequisites

"body = '''A few things have to be in place for these features:- HPE OneView is installed- The HPE SPP is registered in HPE OneView- The server hardware is recorded in HPE OneView- HPE OneView for vCenter is installed and configured- The SPP is registered in vCenter- The cluster image is configured, firmware components included- The servers already have the vendor add-on installed (that is what brings the SUT tool)- The servers have SUT configured in AutoDeploy mode'''[[sections]]heading = "

The problem

"body = '''In one environment we could not stage or remediate a host. These errors kept showing up in the log:**\[INFO\] :: \[redfishlib.cpp:264\] :: In executeRedfishCall(), the operation is rawget the link is /redfish/v1/systems/1/hpserversettings/firmwaredriverbaselinesettings/****\[ERROR\] :: \[redfishlib.cpp:352\] :: Error value from Transaction is : -12 and error name is HTTP server returned error status.**\[ERROR\] :: \[sutmetadatainterface.cpp:739\] :: Unable to sync OV to HP Tools in RISWe found them in /var/log/sut.log.### Troubleshooting stepsNone of these solved it:- Reboot the ESXi host- Reboot HPE OneView- Reboot HPE OneView for vCenter- Reboot vCenter Server- Reset the HPE iLOThe log messages stayed exactly the same and the host would not take the new firmware.'''[[sections]]heading = "

Solution

"body = '''The remaining options would have been:- Remove the HPE server from HPE OneView and add it again- Reinstall ESXi on the HPE server- Open an HPE support caseRemoving the host from HPE OneView and adding it back made the errors disappear.*Solution: re-register the HPE server in HPE OneView.*'''[status]corpus = 267[[status.alsoLike]]ref = "posts/announcing-end-of-support-life-for-vsphere-7-0"score = "1.00"[[status.alsoLike]]ref = "posts/hpe-vm-essentials-part-2"score = "1.00"[[status.alsoLike]]ref = "solutions/vmware/vsphere-foundation"score = "0.59"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>redfishlib-cpp264-in-executeredfishcall</name> <locale>en</locale> <labels> <author>dario-doerflinger</author> <series>lessons-learned</series> <entry key="capability/virtualization">1.37</entry> <entry key="vendor/vmware">0.88</entry> </labels> <annotations> <source>blog-content/posts/en/redfishlib-cpp264-in-executeredfishcall.md</source> <route>/en/insights/redfishlib-cpp264-in-executeredfishcall/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/redfishlib-cpp264-in-executeredfishcall.md</markdown> </annotations> </metadata> <spec> <title>redfishlib.cpp:264 :: In executeRedfishCall()</title> <date>2024-01-31</date> <author>dario-doerflinger</author> <locale>en</locale> <summary>On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter, so a cluster image can carry the firmware as well.</summary> <capabilities> <item>virtualization</item> </capabilities> <vendors> <item>vmware</item> </vendors> <series>lessons-learned</series> <hero>/blog-assets/redfishlib-cpp264-in-executeredfishcall/hero.webp</hero> <migrated>2026-08-24</migrated> <translationReviewed>false</translationReviewed> <draft>false</draft> </spec> <sections> <section> <body>On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter. Those components let us define a cluster image that includes the firmware.</body> </section> <section> <heading>

Prerequisites

</heading> <body>A few things have to be in place for these features:- HPE OneView is installed- The HPE SPP is registered in HPE OneView- The server hardware is recorded in HPE OneView- HPE OneView for vCenter is installed and configured- The SPP is registered in vCenter- The cluster image is configured, firmware components included- The servers already have the vendor add-on installed (that is what brings the SUT tool)- The servers have SUT configured in AutoDeploy mode </body> </section> <section> <heading>

The problem

</heading> <body>In one environment we could not stage or remediate a host. These errors kept showing up in the log:**\[INFO\] :: \[redfishlib.cpp:264\] :: In executeRedfishCall(), the operation is rawget the link is /redfish/v1/systems/1/hpserversettings/firmwaredriverbaselinesettings/****\[ERROR\] :: \[redfishlib.cpp:352\] :: Error value from Transaction is : -12 and error name is HTTP server returned error status.**\[ERROR\] :: \[sutmetadatainterface.cpp:739\] :: Unable to sync OV to HP Tools in RISWe found them in /var/log/sut.log.### Troubleshooting stepsNone of these solved it:- Reboot the ESXi host- Reboot HPE OneView- Reboot HPE OneView for vCenter- Reboot vCenter Server- Reset the HPE iLOThe log messages stayed exactly the same and the host would not take the new firmware. </body> </section> <section> <heading>

Solution

</heading> <body>The remaining options would have been:- Remove the HPE server from HPE OneView and add it again- Reinstall ESXi on the HPE server- Open an HPE support caseRemoving the host from HPE OneView and adding it back made the errors disappear.*Solution: re-register the HPE server in HPE OneView.* </body> </section> </sections> <status> <corpus>267</corpus> <alsoLike> <item> <ref>posts/announcing-end-of-support-life-for-vsphere-7-0</ref> <score>1.00</score> </item> <item> <ref>posts/hpe-vm-essentials-part-2</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vsphere-foundation</ref> <score>0.59</score> </item> </alsoLike> </status></manifest>

Prerequisites

The problem

Solution

Prerequisites

The problem

Solution

Prerequisites

The problem

Solution

Prerequisites

The problem

Solution

redfishlib.cpp:264 :: In executeRedfishCall()

Prerequisites

The problem

Troubleshooting steps

Solution

You might also like

vSphere 7 retires: end of support in October 2025

HPE VM Essentials – Part 2

vSphere Foundation