DE · EN
Call us
+41 44 508 80 00 Ueberlandstrasse 1, 8600 Dübendorf
build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | format run

$ soultec get post/redfishlib-cpp264-in-executeredfishcall -o yaml$ soultec get post/redfishlib-cpp264-in-executeredfishcall -o json$ soultec get post/redfishlib-cpp264-in-executeredfishcall -o toml$ soultec get post/redfishlib-cpp264-in-executeredfishcall -o xml$ python3 redfishlib-cpp264-in-executeredfishcall.pyPS> ./redfishlib-cpp264-in-executeredfishcall.ps1$ go run redfishlib-cpp264-in-executeredfishcall.go$ node redfishlib-cpp264-in-executeredfishcall.js

apiVersion: soultec.ch/v1kind: Postmetadata: name: redfishlib-cpp264-in-executeredfishcall locale: en labels: author: dario-doerflinger series: lessons-learned capability/virtualization: 1.42 vendor/vmware: 0.98 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: 315 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, score: 1.00} search: /en/search.json
{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "redfishlib-cpp264-in-executeredfishcall", "locale": "en", "labels": { "author": "dario-doerflinger", "series": "lessons-learned", "capability/virtualization": 1.42, "vendor/vmware": 0.98 }, "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": 315, "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", "score": "1.00" } ], "search": "/en/search.json" }}
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.42"vendor/vmware" = 0.98[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[[spec.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."[[spec.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'''[[spec.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.'''[[spec.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 = 315search = "/en/search.json"[[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"score = "1.00"
<?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.42</entry> <entry key="vendor/vmware">0.98</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> <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> </spec> <status> <corpus>315</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</ref> <score>1.00</score> </item> </alsoLike> <search>/en/search.json</search> </status></manifest>
# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "redfishlib-cpp264-in-executeredfishcall", "locale": "en", "labels": { "author": "dario-doerflinger", "series": "lessons-learned", "capability/virtualization": 1.42, "vendor/vmware": 0.98, }, "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" "\n" "We found them in /var/log/sut.log.\n" "\n" "### Troubleshooting steps\n" "\n" "None 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" "\n" "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:\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" "\n" "Removing 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": 315, "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", "score": "1.00", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))
# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Post' metadata = [ordered]@{ name = 'redfishlib-cpp264-in-executeredfishcall' locale = 'en' labels = [ordered]@{ author = 'dario-doerflinger' series = 'lessons-learned' 'capability/virtualization' = 1.42 'vendor/vmware' = 0.98 } annotations = [ordered]@{ 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 = [ordered]@{ 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 = @( [ordered]@{ 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.' } [ordered]@{ 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'@ } [ordered]@{ 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.'@ } [ordered]@{ 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 = [ordered]@{ corpus = 315 alsoLike = @( [ordered]@{ ref = 'posts/announcing-end-of-support-life-for-vsphere-7-0' score = '1.00' } [ordered]@{ ref = 'posts/hpe-vm-essentials-part-2' score = '1.00' } [ordered]@{ ref = 'solutions/vmware/vsphere' score = '1.00' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32
// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": map[string]any{ "name": "redfishlib-cpp264-in-executeredfishcall", "locale": "en", "labels": map[string]any{ "author": "dario-doerflinger", "series": "lessons-learned", "capability/virtualization": 1.42, "vendor/vmware": 0.98, }, "annotations": map[string]any{ "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": map[string]any{ "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": []any{"virtualization"}, "vendors": []any{"vmware"}, "series": "lessons-learned", "hero": "/blog-assets/redfishlib-cpp264-in-executeredfishcall/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false, "sections": []any{ map[string]any{ "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.", }, map[string]any{ "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", }, map[string]any{ "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" + "\n" + "We found them in /var/log/sut.log.\n" + "\n" + "### Troubleshooting steps\n" + "\n" + "None 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" + "\n" + "The log messages stayed exactly the same and the host would not take the new firmware.", }, map[string]any{ "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" + "\n" + "Removing 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": map[string]any{ "corpus": 315, "alsoLike": []any{ map[string]any{ "ref": "posts/announcing-end-of-support-life-for-vsphere-7-0", "score": "1.00", }, map[string]any{ "ref": "posts/hpe-vm-essentials-part-2", "score": "1.00", }, map[string]any{ "ref": "solutions/vmware/vsphere", "score": "1.00", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}
// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Post", metadata: { name: "redfishlib-cpp264-in-executeredfishcall", locale: "en", labels: { author: "dario-doerflinger", series: "lessons-learned", "capability/virtualization": 1.42, "vendor/vmware": 0.98, }, 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" + "\n" + "We found them in /var/log/sut.log.\n" + "\n" + "### Troubleshooting steps\n" + "\n" + "None 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" + "\n" + "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:\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" + "\n" + "Removing 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: 315, 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", score: "1.00", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 86 lines · YAML · validated at build# 73 lines · JSON · validated at build# 106 lines · TOML · validated at build# 116 lines · XML · validated at build# 118 lines · Python · read back at build, equals the JSON record# 115 lines · PowerShell · read back at build, equals the JSON record# 124 lines · Go · read back at build, equals the JSON record# 109 lines · JavaScript · read back at build, equals the JSON record · served at /en/insights/redfishlib-cpp264-in-executeredfishcall.md

Lessons learned · 2024-01-31

redfishlib.cpp:264 :: In executeRedfishCall()

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.

2024-01-31Date
Dario DörflingerAuthor
1Min read
Topics Virtualization 1.42
Vendors VMware 0.98

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.

Prerequisites

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

The problem

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.

Solution

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.

You might also like

Post 1.00

vSphere 7 retires: end of support in October 2025
Post 1.00

HPE VM Essentials – Part 2
VMware 1.00

vSphere

Cookies and external services

We want to know how our pages are used. For that we rely on Google Analytics, on Google Ads and HubSpot for marketing, and on Google Maps for directions. None of it loads before you agree, and you can change your choice at any time under “Privacy settings” in the footer.

Controller: soulTec AG, Ueberlandstrasse 1, 8600 Dübendorf. Privacy policy