ProLiant Servers (ML,DL,SL)
1820548 Members
4788 Online
109626 Solutions
New Discussion

Re: Agentless Management Service fails to initialize on Windows Server 2022

 
SOLVED
Go to solution
CraigNZ
Occasional Advisor

Agentless Management Service fails to initialize on Windows Server 2022

Hey People,.

I recently managed to get Windows Server 2022 installed on my Proliant Microserver Gen8.

I've got most things/drivers going OK, except the Agentless Management Service fails to initialize (that's the error in the Windows Event Logs).

I'm using AMS v10.60.0.0.

The gen8 has the System ROM: J06 04/04/2019
iLO firmware: 2.82 Feb 06 2023

Anyone got any ideas?  There's no additional information in the Windows Event Logs and I can't see any logs from AMS.
Where can I find more info on why it's failing?

Thanks
Craig

15 REPLIES 15
support_s
System Recommended

Query: Agentless Management Service fails to initialize on Windows Server 2022 - Prolaint server - Microserver Gen8

System recommended content:

1. HPE Integrated Lights-Out 4 (iLO 4) - UI Displays "Agentless Management service not available" Message on Software UI Page After VMWare ESXi Upgrade

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

CraigNZ
Occasional Advisor

Re: Query: Agentless Management Service fails to initialize on Windows Server 2022 - Prola

Sorry automated response.  This doesn't involve VMWare/ESXi.

However that article did lead me down a path the reminded me/pointed out that the Microserver Gen 8 doesn't officially support Windows Server 2022 - it stops as Server 2016.

But so far, everything else seems to work OK, so it would be a shame to have to rebuild with Server 2016, which is already out of mainstream support.

TVVJ
HPE Pro

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hello,

You may download and install "Agentless Management Service for Microsoft Windows x64" and see if it helps.

Regards,



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.
[All opinions expressed here are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
CraigNZ
Occasional Advisor

Re: Agentless Management Service fails to initialize on Windows Server 2022

That version of AMS isn't compatible with something in my server:

Installer error messageInstaller error message
Tam92
HPE Pro

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hello,

The message is expected as it is an unsupported configuration.

We would request you to install the supported OS version and then you shall be able to install the required AMS.

This AMS installation requires the iLO Channel interface driver to be installed prior to this. If there is a mismatch between iLO chif driver and AMS file,the installation will not take place.

Prerequisites:

The Channel Interface Driver for Windows X64 must be installed prior to this component.

Microsoft SNMP Service must be enabled, if SMA (System Management Assistant) is enabled.



Thanks,
TAM



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]
Accept or Kudo
CraigNZ
Occasional Advisor

Re: Agentless Management Service fails to initialize on Windows Server 2022

Thanks for that.

I'm trying to avoid installing Server 2016, as that's no longer supported by Microsoft.

So I've got Server 2022.

I went back and re-installed the Microserver Gen 8 specific versions of iLO Management Controller Drivers (v.3.30), Channel Interface Driver (v3.31) and the Agentless Management Service (v10.60).

Still have the same problem, where the AMS wont successfully start.  I am seeing the following in the event log now, so it looks like a VC++ library issue?

Faulting application name: hpqams.exe, version: 10.60.0.0, time stamp: 0x57d96be7
Faulting module name: msvcrt.dll, version: 7.0.20348.1, time stamp: 0x68e1e0af
Exception code: 0x40000015
Fault offset: 0x000000000000b0ac
Faulting process id: 0x27b0
Faulting application start time: 0x01da48f71a668edc
Faulting application path: C:\Program Files\Hewlett-Packard\AMS\service\hpqams.exe
Faulting module path: C:\WINDOWS\System32\msvcrt.dll
Report Id: 12676537-1054-4cff-be19-9ed81d0c75f4
Faulting package full name:
Faulting package-relative application ID:

 

I have Microsoft Visual C++ 2012 Redistributable (x64), v 11.0.61030.0 and Visual C++ 9.0 SP1 + KB971092 Runtime DLLs (x64) v9.0.30729.4148 installed.
Not sure if those are the appropriate/latest versions of those.

Thanks
Craig

Tam92
HPE Pro

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hello,

I understand your situation, but this is how it is. This is an unsupported configuration, and not tested by HPE.


Thanks,
TAM



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]
Accept or Kudo
CraigNZ
Occasional Advisor

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hey Tam,

no doubt.  Though to be pedantic - the installers seem to think it's supported - they install successfully.  Whereas when I try to install the iLO5 or the Gen9/10 specific installers (or older Server 2008 installers), they point out it's not supported and wont install.

 

Such a shame really.

Thanks
Craig

Tam92
HPE Pro

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hello,

Gen8 servers have iLO 4. ILO 5 drives will not install on these servers.

This is the last supported AMS version for Microserver Gen8 with Windows 2016.

https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_1338aab98aa04b0391e73c3976&tab=Installation+Instructions

Thanks,
TAM



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]
Accept or Kudo
CraigNZ
Occasional Advisor
Solution

Re: Agentless Management Service fails to initialize on Windows Server 2022

Interestingly enough, I was able to install 10.75.0.0 (https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_9185dac09990444b8a7973890e&tab=Installation+Instructions) and it started working - even though that's supposed to be for Gen 9.

Note: 10.70.0.0 wouldn't install - unsupported server version.

I was then able to upgrade to 10.100.1.0 (https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_b5fbeb03dd1e465c870f85adf1&tab=Installation+Instructions) and it's seems to be continuing to work OK.

The iLO console is reporting that Agent Management Service is OK!

Yay!

 

Tam92
HPE Pro

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hello Craig,

Glad to hear that it is working   Being a part of HPE I would never recommend going for the unsupported configuration. Hope you understand.

Have a lovely day ahead

Thanks,
TAM



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]
Accept or Kudo
CraigNZ
Occasional Advisor

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hey Tam,

Totally understand.  At least now there's a reference here for anyone else that goes down the same path as me.

FYI I picked up the Microserver Gen 8 (XEON E3-1230 V2, 16 Gig) second hand, really cheap.  The previous owner had bought it new, but never set it up (I suspect he had fund getting an OS installed on it, without putting the OS on the RAID drives. So it's basically unused and should have plenty of hours of life in it.

With Windows Server 2022 installed, I've got it running a DLNA (Serviio) server running, Hyper-V (for a HomeBridge VM) and slowly configuring it up as a remote desktop gateway - all to replace my old Server 2019 with Essentials "hacks".  I wish Microsoft would just bring back Essentials (aka the old Homeserver SKU) back for non OEMs.

Thanks
Craig

GustavoE
New Member

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hi Craig,

I hope it’s not too late to comment, as I had exatly the same problem, but I hadn’t noticed it until my server was monitored by ZABBIX and then I detected the same failure that you reported. However, after a short search, I found what could possibly be the definitive solution.

From here https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_8d51c1775a8b4043b933549262 I downloaded version 10.100.1.0 from January 30, 2023, of the ‘HPE ProLiant Agentless Management Service for HPE Apollo, ProLiant and Synergy Gen9 servers’ which, as strange as it may seem, allowed me to install it on my server despite it being GEN8 and not GEN9 as the title indicates.

It simply updated the version I already had which was failing (10.60.0.0 Oct 24, 2016) and now the service runs without problems, my ZABBIX no longer detects the failure, and the event viewer does not indicate problems.

I hope this helps you.

Regards.

Gustavo Echavarría

(ALIADO IT Engineer)

 

 

 

 

CraigNZ
Occasional Advisor

Re: Agentless Management Service fails to initialize on Windows Server 2022

Hey @GustavoE ,

Yeah, that's close to what I ended up doing, though I found I couldn't install 10.100.x directly, I had to install 10.70.x first.

 

Thanks for mentioning Zabbix - looks cool, will have to check it out.

Thanks
Craig

Thompson79
Member

Re: Agentless Management Service fails to initialize on Windows Server 2022

Thanks for posting the fix. Ran into the same issue.