- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Servers - General
- >
- Ilo Cmdlets broke
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2023 02:55 AM - last edited on тАО03-29-2023 12:09 AM by support_s
тАО03-20-2023 02:55 AM - last edited on тАО03-29-2023 12:09 AM by support_s
I'm trying to do some updates on HPE ILO5 with powershell. The script previously worked but it seems that something is broke. I get the following error.. Anyone seen it and have a solution?
Tested with cmlets ver 2.2.0.0 and 3.3.0.0. ILO5 Version 2.72 nad 2.78.
Get-HPEiLOTPMStatus : [192.168.104.12]: Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'HPE.iLO.Com
munication.Redfish.DataEntity.OData' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize cor
rectly.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2023 03:30 AM
тАО03-27-2023 03:30 AM
Re: Ilo Cmdlets broke
The error message suggests that there might be an issue with the JSON response that the cmdlet is receiving from the iLO5 server. ,
One possible reason for this error could be a change in the iLO5 API response format between the versions you tested.
Here are a few things you can try to resolve this issue:
Verify that the iLO5 server is working correctly and responding to requests.
Check if there is a firmware update available for your iLO5 server that might resolve any known issues with the API response.
Try downgrading the iLO5 firmware to a lower version, and test if the cmdlets work correctly with that version.
Check if there are any new versions of the iLO cmdlets available and try updating to the latest version.
Check the PowerShell version and make sure it is compatible with the iLO cmdlets.
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2023 12:07 AM
тАО03-29-2023 12:07 AM
Re: Ilo Cmdlets broke
Please advise if you need any further advise on what has already been shred by @Vinky_99 .
Thank you.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2023 12:51 AM
тАО03-29-2023 12:51 AM
SolutionHello, thanks for reaching out.
I found the issue. I thought I was using the latest ILO cmdlets but seems I didn't Updating to 4.0.0.0 solved the issue.
@ShruthiSK Note: The signer of the cmd lets for 4.0.0.0 is diffrent from 3.3.0.0 so that produced a warning/error.
Thanks for the assistance.
BR
Henke