Aller au contenu principal

I cannot install Acronis 12.5.1.7970

Thread needs solution

Having attempted to work with Acronis support and failed I figured I might post here and find someone with a similar situation.  I cannot even install Acronis 12.5 on a freshly installed Server 2016 bare metal box.  I am not applying any GPO's to this server at all- this is a clean Windows install.

During install I am specifying domain credentials for my Acronis Service Account and I am pointing Acronis at my MS SQL 2014 server.

I receive an error during install that I've attached a screenshot of.  "Failed to register the following components on the management server: Backup Agent & Storage Node.  For details, view the installation log." 

I have worked with Acronis support for weeks in September and they have been unable to provide me with an answer.  I installed 11.7 and started backing up my network.  Received an email about a week ago that v7970 has fixed my issues.  I wiped the server and now I'm stuck again with a non-working product.

I can't wait for my Commvault quote to get in, but for now, I have to have functioning backups.  Has anyone else faced this issue??  Where is the Acronis web interface hosted from?  I cannot sign on the interface after installation either.

Sidenote: I'm working in an air-gaped environment.

 

End of log file below.  The log is 10mb and too large to upload to this site.

 

1: [16:12:49:162]: (asn) RegisterAgentTool::Register: MsiProgressReporter::Update: ticks = 4194304, TicksRemain = 0 
1: [16:12:49:162]: (mms) RegisterAgentTool::Register: MsiProgressReporter::Update: ticks = 4194304, TicksRemain = 0 
1: [16:12:51:164]: (mms) RegisterAgentTool::Register: MsiProgressReporter::Update: ticks = 0, TicksRemain = 0 
1: [16:12:51:164]: (asn) RegisterAgentTool::Register: MsiProgressReporter::Update: ticks = 0, TicksRemain = 0 
1: [16:12:51:164]: Failed to register Backup Agent on AMS:
Error 0x1c90007: An error has occurred on the management server.
| line: 0x50a688b07baa8f65
| file: k:\13\enterprise\tools\register_agent\install\custom_action\lib\impl\register_agent_tool.cpp:192
| function: AmsRegistration::RegisterAgentTool::ThrowErrorIfFailed
| $module: custom_actions_ab_vsa64_s_7970 
1: [16:12:51:164]: Failed to register Storage Node on AMS:
Error 0x1c90007: An error has occurred on the management server.
| line: 0x50a688b07baa8f65
| file: k:\13\enterprise\tools\register_agent\install\custom_action\lib\impl\register_agent_tool.cpp:192
| function: AmsRegistration::RegisterAgentTool::ThrowErrorIfFailed
| $module: custom_actions_ab_vsa64_s_7970 
1: [16:12:51:165]: RegisterOnAMS: Register::Execute: CADataInputTraced::SetProperty: propertyName = Backup Agent_AlreadyRegistered, value = 0 
1: [16:12:51:165]: RegisterOnAMS: Register::Execute: CADataInputTraced::SetProperty: propertyName = Storage Node_AlreadyRegistered, value = 0 
1: [16:12:51:166]: RegisterOnAMS: Register::Execute: Registration results:
Backup Agent: failed.
Storage Node: failed.
 
1: MSIGEN:SendMessageToInstaller: started 
1: MSIGEN:SendMessageToInstaller: MsiCreateRecord succeeded 
1: MSIGEN:SendMessageToInstaller: MsiRecordSetStringW succeeded 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Doug,

The issue you refer to in a separate thread is likely caused by some different root reason. In your case from the MSI log I can see that registration of Acronis Storage Node component is the one that fails. However the failure occurs in a unique place which I couldn't find any similar reports for:

---------

1: [16:06:45:280]: (asn) RegisterAgentTool::Register: command = G:\Program Files\Acronis\RegisterAgentTool\register_agent.exe -s asn -o register -a PCLBACKUP03:9877 
1: [16:06:45:280]: RegisterOnAMS: Register::Execute: Catalog Service is not to be registered. Skipped. 
1: [16:06:45:809]: (mms) RegisterAgentTool::Register: result = 3 
1: [16:06:45:809]: (mms) RegisterAgentTool::Register: The command output:
Server error (404).

{
   "context" : 
   {
      "$module" : "mms_rest_api_vsa64_7970"
   },
   "domain" : "global",
   "origin" : 
   {
      "code" : 2,
      "fields" : 
      {
         "$module" : "mms_rest_api_vsa64_7970"
      },
      "lineTag" : "0x487816542fd366fc, k:\\13\\enterprise\\rest_api\\agent\\registration.cpp:353, AgentRestApi::`anonymous-namespace'::RegisterInOnPremise",
      "module" : 0,
      "suberror" : null,
      "text" : ""
   },
   "reason" : "internalError",
   "serCode" : "0x00000002"
}

---------

Such issues should be investigated with help from our support team and likely development involvement will be also required as part of the investigation, since it's unclear why registration process is unable to connect to the management server via RestAPI call.

I've contacted our support managers to review your submitted support tickets, analyze what went wrong, i.e. why it took such a long time and the problem is still not solved, and make corresponding actions to get things right.

Thank you.

Hi Vasily,

 

I've just tried to register my storage node to my console, but it failed with the following error, do you have any idea ?

Failed.
500

{
   "context" :
   {
      "$module" : "mms_rest_api_vsa64_10330"
   },
   "domain" : "global",
   "origin" :
   {
      "code" : 500,
      "fields" :
      {
         "$module" : "mms_rest_api_vsa64_10330"
      },
      "lineTag" : "0x487816542fd3685e, e:\\216\\enterprise\\rest_api\\agent\\reg
istration.cpp:707, AgentRestApi::`anonymous-namespace'::UnregisterAgent",
      "module" : 0,
      "suberror" : null,
      "text" : "Unregistration of agent in AMS failed. Body: {\"reason\":\"wcsIn
ternalError\",\"date\":\"2018-07-25T16:20:44.213469+00:00\",\"troubleshoot\":nul
l,\"effect\":null,\"cause\":\"Internal server error.\",\"stacktrace\":\"Tracebac
k (most recent call last):\\n  File \\\"c:\\\\program files\\\\acronis\\\\pyshel
l\\\\site-packages\\\\flask.zip\\\\flask\\\\app.py\\\", line 1486, in full_dispa
tch_request\\n    rv = self.dispatch_request()\\n  File \\\"c:\\\\program files\
\\\acronis\\\\pyshell\\\\site-packages\\\\flask.zip\\\\flask\\\\app.py\\\", line
 1472, in dispatch_request\\n    return self.view_functions[rule.endpoint](**req
.view_args)\\n  File \\\"C:\\\\Program Files\\\\Acronis\\\\WebServer\\\\wcs\\\\w
eb\\\\temp_ams_proxy.py\\\", line 108, in _route_the_request_to_ams\\n    header
s=_update_headers(request.headers))\\n  File \\\"C:\\\\Program Files\\\\Acronis\
\\\WebServer\\\\wcs\\\\web\\\\temp_ams_proxy.py\\\", line 67, in _make_request\\
n    raise exc\\n  File \\\"C:\\\\Program Files\\\\Acronis\\\\WebServer\\\\wcs\\
\\web\\\\temp_ams_proxy.py\\\", line 56, in _make_request\\n    return urllib.re
quest.urlopen(req, timeout=wcs.web.session.DEFAULT_REQUEST_TIMEOUT)\\n  File \\\
"C:\\\\Program Files\\\\Acronis\\\\PyShell\\\\stdlib.zip\\\\urllib\\\\request.py
\\\", line 163, in urlopen\\n    return opener.open(url, data, timeout)\\n  File
 \\\"C:\\\\Program Files\\\\Acronis\\\\PyShell\\\\stdlib.zip\\\\urllib\\\\reques
t.py\\\", line 466, in open\\n    response = self._open(req, data)\\n  File \\\"
C:\\\\Program Files\\\\Acronis\\\\PyShell\\\\stdlib.zip\\\\urllib\\\\request.py\
\\", line 484, in _open\\n    '_open', req)\\n  File \\\"C:\\\\Program Files\\\\
Acronis\\\\PyShell\\\\stdlib.zip\\\\urllib\\\\request.py\\\", line 444, in _call
_chain\\n    result = func(*args)\\n  File \\\"C:\\\\Program Files\\\\Acronis\\\
\PyShell\\\\stdlib.zip\\\\urllib\\\\request.py\\\", line 1282, in http_open\\n
  return self.do_open(http.client.HTTPConnection, req)\\n  File \\\"C:\\\\Progra
m Files\\\\Acronis\\\\PyShell\\\\stdlib.zip\\\\urllib\\\\request.py\\\", line 12
57, in do_open\\n    r = h.getresponse()\\n  File \\\"C:\\\\Program Files\\\\Acr
onis\\\\PyShell\\\\stdlib.zip\\\\http\\\\client.py\\\", line 1198, in getrespons
e\\n    response.begin()\\n  File \\\"C:\\\\Program Files\\\\Acronis\\\\PyShell\
\\\stdlib.zip\\\\http\\\\client.py\\\", line 297, in begin\\n    version, status
, reason = self._read_status()\\n  File \\\"C:\\\\Program Files\\\\Acronis\\\\Py
Shell\\\\stdlib.zip\\\\http\\\\client.py\\\", line 258, in _read_status\\n    li
ne = str(self.fp.readline(_MAXLINE + 1), \\\"iso-8859-1\\\")\\n  File \\\"C:\\\\
Program Files\\\\Acronis\\\\PyShell\\\\stdlib.zip\\\\socket.py\\\", line 576, in
 readinto\\n    return self._sock.recv_into(b)\\nsocket.timeout: timed out\\n\",
\"origin\":\"timed out\",\"context\":{\"_internal\":\"100011:-1:-1\"}}"
   },
   "reason" : "internalError",
   "serCode" : "0x000001f4"
}
 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Mathieu,

The context is not completely clear, e.g. which operation you try to perform - it definitely makes sense to investigate the issue with our support team involved since closer analysis of current Acronis Storage Node (ASN) setup will be required: for example, whether ASN was registered on some old management server and now is tried to re-register on newer one or something else could've happened.

Thank you.