AMS on WS Core
Hey guys,
I'm currently setting up a new server infrastructure and am trying to install the Acronis management Server on a fresh Windows Server 2019 Standard without GUI (Core).
Unfortunately, I'm receiving the error message "Registration failed: Failed to register the following components on the management server: Backup Agent: 'Management server error: 'Registration of agent in AMS failed. Body: '.'" during installation or repair.
So before digging in log files, I'd like to know whether installing AMS on WS Core is supported at all?!
Thanks in advance!
PS: According to the documentation it should be supported: https://www.acronis.com/en-us/support/documentation/AcronisBackup_12.5/index.html#36985.html 🤔
I attached the logfiles for review.
Bhanu Prakash Reddy wrote:It seems Acronis Management service is not started. Can please check Acronis management server service is started.
Hello Bhanu Prakash Reddy,
thank you for your reply!
Indeed, AcrMngSrv wasn't running, thus I just started it manually.
However, as soon as I try to access the AMS web interface (after successfully logging in), it seems to crash. 🙁
In the event viewer, these are the according logs:
Scheduler kann den Task nicht ausführen"" mit GUID '2A4082E8-1C2B-11E1-87BA-D5724824019B'} wegen Fehler 1060 (Es gibt einen Versuch, einen Dienst anzufordern, der nicht existiert.)
Fehler 0xb9000a: Initialisieren des Servers fehlgeschlagen.
| Ablaufverfolgungsebene: Fehler
| Zeile: 0xb957662f70a235b
| Datei: e:\497\enterprise\service\impl\server.cpp:466
| Funktion: Core::ServerImpl::Start
| $module: management_server_vsa64_14330
|
| Fehler 0xb9000a: Initialisieren des Servers fehlgeschlagen.
| Zeile: 0xb957662f70a2535
| Datei: e:\497\enterprise\service\impl\server.cpp:940
| Funktion: Core::ServerImpl::Initialize
| $module: management_server_vsa64_14330
|
| Fehler 0xb9000f: Initialisierung der Komponente 'MSP Machine Registry component' fehlgeschlagen.
| Zeile: 0x27fbb047d6ce058a
| Datei: e:\497\enterprise\service\impl\component_manager_impl.cpp:101
| Funktion: Core::ComponentManager::Record::Initialize
| $module: management_server_vsa64_14330
|
| Fehler 0xf90004: ASYNC: Unidentified job.
| Zeile: 0xd9612b4aaebb8e3f
| Datei: e:\528\enterprise\common\async\base_job.cpp:40
| Funktion: Async::BaseJob::Describe
| $module: abr_ams_vsa64_14330
|
| Fehler 0x2470001: HTTP transfer error
| Zeile: 0xcbd0886296318956
| Datei: e:\528\enterprise\common\http\curl_transport.cpp:417
| Funktion: Http::Curl::CurlDetails::RequestScope::MakeError
| requestType: GET
| uri: 127.0.0.1/api/resource_manager/v1/agents?type=agent
| host: 127.0.0.1
| port: 0x77dd
| curlResult: 0x7
| $module: abr_ams_vsa64_14330
|
| Fehler 0x2260007: Failed to connect to 127.0.0.1 port 30685: Connection refused
| Zeile: 0xcbd0886296318955
| Datei: e:\528\enterprise\common\http\curl_transport.cpp:416
| Funktion: Http::Curl::CurlDetails::RequestScope::MakeError
| $module: abr_ams_vsa64_14330
Hello Sicom,
thank you for posting this issue on Acronis forums and sharing your logs!
We are sorry to know that you've encountered this issue. It is a known problem (Alert manager can't start without opengl32 library, ABR-227879) which will be fixed in a soon U5 update.
In order to workaround this issue, please copy the opengl32.dll, glu32.dll and ddraw.dll files from C:\Windows\system32 folder from Windows 2019 Server with GUI to C:\Program Files\Acronis\AlertManager folder
Then restart Acronis Service Manager and Acronis Management Server Services (Start -> Run -> services.msc and restart both services).
Maria Belinskaya wrote:In order to workaround this issue, please copy the opengl32.dll, glu32.dll and ddraw.dll files from C:\Windows\system32 folder from Windows 2019 Server with GUI to C:\Program Files\Acronis\AlertManager folder
Then restart Acronis Service Manager and Acronis Management Server Services (Start -> Run -> services.msc and restart both services).
Hello Maria,
thank you for you suggestion!
I tried that, followed up with a reboot and a repair installation, then copied the files and rebooted once again but the problem seems to persist. 😔
Meanwhile a colleague of yours also confirmed that this problem is related to a known issue that will be fixed in an update "very soon".
I guess I'll just have to wait it out...
Hello Sicom.
Thanks for sharing the results. Sorry to know about the failure.
I tried that, followed up with a reboot and a repair installation, then copied the files and rebooted once again but the problem seems to persist. 😔
Have you tried to manually restart Acronis services at the final step?
Then restart Acronis Service Manager and Acronis Management Server Services (Start -> Run -> services.msc and restart both services).
Hello Maria,
yes, I did but was still unable to register any clients or access the data of the web interface.
However, in one last attempt, I copied the dll-files directly into system32, completely uninstalled and reinstalled the full Acronis-suite and after that I worked!
As this is just a workaround and the installation of the storage node on a second core server failed too, I decided to wait for the update.
Hopefully that one will also bundle OpenJDK instead of Java SE.
Thank you for your help! 😀
I encountered the same thing, and ignored the error during installation. When I opened the browser and login, it redirected me back to the login page. I looked at the error logs and it said something about socket issue / timeout. As soon as I got rid of the proxy setting in my browser and connected directly to the internet I was able to login. So somehow the Acronis application required to get to the internet over proxy but that didn't work. I was upgrading from 11.7 to 12.5, but not sure why it was not preserving the clients I had registered in 11.7. I'll go and re-do the upgrade again.
Hello Adrian,
thank you for posting in this forum thread!
Could you please share an activity log with this error? In the Management Console GUI please follow Overview -> Activities, select an activity with this socket error, click on Show details -> Download log.