Acronis 12.5 7970 Windows XP

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 33
Comments: 51

Hi

we are having trouble to manage a Windows XP machine.

We've performed unattended installation, confirming that the agent gets correctly installed and the services are running under the correct service account, but when we try to add the machine to the AMS we get:

Error code: 18
Module: 627
LineInfo: 0x90324F34A77128F7
Fields: {"ResourceAddress":"WORKSTATION","ResourceType":"windows_remote_install","$module":"access_manager_vsa64_7970"}
Message: Failed to check credentials for specified account.
------------------------
Error code: 5
Module: 69
LineInfo: 0x279DD1D7639F7576
Fields: {"$module":"remote_installation_addon_vsa64_7970"}
Message: Connection to 'WORKSTATION' is broken.
------------------------
Error code: 65520
Module: 0
LineInfo: 0xBD28FDBD64EDB8F1
Fields: {"code":"2147942453","$module":"remote_installation_addon_vsa64_7970"}
Message: The network path was not found

I can ping from the server to the name and to the IP. I get the same message if I try to add the machine with the IP.

We decided to uninstall the agent and install it again using the installer because you can add the machine automatically to the AMS specifying the AMS in the installation. After specifying the server and the credentials, the dialog to select the TENANT where the machine is going to be added appears and allowed us to select the desired TENANT. After doing so, again, confirming that the machine has the agent installed and that the services are running, the machine does not appear in the AMS...

Any feedback is much appreciated.

Thanks in advance.

 

Fri, 11/10/2017 - 15:34
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

There are no known issues related to installation of backup agent onto Windows XP (assuming that SP3 is required so the problem should be investigated with help from our support team by collecting logs from both agent side (via C:\Program Files\Common Files\Acronis\AdvReport\systeminfo.exe utility) and from management server side (via web console GUI Overview->Activities).

The first log to check should be C:\ProgramData\Acronis\BackupAndRecovery\MMS\mms.0.log on the agent side which would contain information about registration attempts and related errors.

Thank you.

Fri, 11/10/2017 - 16:25
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 33
Comments: 51

Hi Vasily, thanks for the answer.

Generated the systeminfo log in the server using the utility. Anyway, after rebooting the server a W7 machine that had had its agent installed at the same time as the Windows XP appeared and also the Windows XP machine appeared. I was able to backup both machines after rebooting the server.

Since then (yesterday) the server did nothing, and today when I checked the status I realized that the machines where in the correct tenant but appeared as OFFLINE... Even at ORGANIZATION level where the server's agent appears, the server agent appeared OFFLINE... Nonsense... [Basics done, I can ping the machines from the servers, the machines ping the server, all the agents are up and running etc]

Stopped all the acronis services in the server and started again. I've noticed that one of the services starts but stops after 10 seconds AMSS service...

Here, the log from Application log:

Log Name:      Application
Source:        Acronis Backup and Recovery
Date:          11.11.2017 13:40:41
Event ID:      10
Task Category: (185)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      AcronisServer
Description:
Error 0xb9000a: Failed to initialize server.
| trace level: error
| line: 0xb957662f70a232d
| file: k:\13\enterprise\service\impl\server.cpp:420
| function: Core::ServerImpl::Start
| $module: management_server_vsa64_7970
|
| error 0xb9000a: Failed to initialize server.
| line: 0xb957662f70a24bb
| file: k:\13\enterprise\service\impl\server.cpp:818
| function: Core::ServerImpl::Initialize
| $module: management_server_vsa64_7970
|
| error 0xb90001: Registration in ApiGateway failed
| line: 0x1d47a965b08ae0ec
| file: k:\13\enterprise\service\impl\api_gateway_registration.cpp:43
| function: ApiGateway::RegisterService
| $module: management_server_vsa64_7970
|
| error 0x2b10008: Failed to register in ApiGateway
| line: 0x4e3de39696b1a5bb
| file: k:\13\enterprise\common\interprocess\api_gateway.cpp:190
| function: ApiGateway::Register
| $module: management_server_vsa64_7970
|
| error 0x2b10001
| line: 0x6eeba09873cef73b
| file: k:\13\enterprise\common\interprocess\pipe_win.cpp:47
| function: Interprocess::ConnectToPipe
| $module: management_server_vsa64_7970
|
| error 0xfff0: The system cannot find the file specified
| line: 0xbd28fdbd64edb8f1
| file: k:\13\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| code: 0x80070002
| $module: management_server_vsa64_7970
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Acronis Backup and Recovery" />
    <EventID Qualifiers="0">10</EventID>
    <Level>2</Level>
    <Task>185</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-11T12:40:41.000000000Z" />
    <EventRecordID>18922</EventRecordID>
    <Channel>Application</Channel>
    <Computer>AcronisServer</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Error 0xb9000a: Failed to initialize server.
| trace level: error
| line: 0xb957662f70a232d
| file: k:\13\enterprise\service\impl\server.cpp:420
| function: Core::ServerImpl::Start
| $module: management_server_vsa64_7970
|
| error 0xb9000a: Failed to initialize server.
| line: 0xb957662f70a24bb
| file: k:\13\enterprise\service\impl\server.cpp:818
| function: Core::ServerImpl::Initialize
| $module: management_server_vsa64_7970
|
| error 0xb90001: Registration in ApiGateway failed
| line: 0x1d47a965b08ae0ec
| file: k:\13\enterprise\service\impl\api_gateway_registration.cpp:43
| function: ApiGateway::RegisterService
| $module: management_server_vsa64_7970
|
| error 0x2b10008: Failed to register in ApiGateway
| line: 0x4e3de39696b1a5bb
| file: k:\13\enterprise\common\interprocess\api_gateway.cpp:190
| function: ApiGateway::Register
| $module: management_server_vsa64_7970
|
| error 0x2b10001
| line: 0x6eeba09873cef73b
| file: k:\13\enterprise\common\interprocess\pipe_win.cpp:47
| function: Interprocess::ConnectToPipe
| $module: management_server_vsa64_7970
|
| error 0xfff0: The system cannot find the file specified
| line: 0xbd28fdbd64edb8f1
| file: k:\13\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| code: 0x80070002
| $module: management_server_vsa64_7970</Data>
  </EventData>
</Event>

Of course I'm not able to open the web server because the service is down... So I reboot the server again. And everything is back to normal... The machines now appear online...

I'm able to correctly remove a Windows 7 machine and add it again to the server without having to remotely install the agent, it adds to the server without installing (because the agent is already installed in the machine).

The case of the Windows XP machine is the same, cannot add it from the server because the provious post error and I cant also add it using the register_agent tool (I have a log of the error I get from this tool, sending you via PM).

Using the forum because I've found several solutions posted here so I hope this can solve others problems :)

Thanks in advance.

Sat, 11/11/2017 - 13:45