Skip to main content

The Acronis Remote Agent service failed to start due to the following error: The system cannot find the file specified.

Thread needs solution

Trying to install ABR10 agent on Windows 2003 R2 64bit server. I get the following in the event log of the remote server...

The Acronis Remote Agent service failed to start due to the following error:
The system cannot find the file specified.

Attached is log file from my ABR10 server.

I also tried to copy the entire contents of the RemoteInstall directory to the remote server and install from there and I receive the same error.

Also, I have installed the agent on other Windows 2003 R2 64bit servers.

Any help would be appreciated!

Thanks.

0 Users found this helpful

Hello Eric!

Welcome to Acronis Forum and thank you for finding time to report about the issue! I'm familiar with this type of issues and will be glad to provide you with assistance.

According to the log you have kindly specified the issue was caused by problems with registering VSS and services. So I would apppreciate if you could kindly do the following: 

  1. To solve the issue, install the Acronis Agent (Build 11345 or higher) ignoring the Cscript error by issuing the following command:

    msiexec.exe /i [PATH]AcronisAgentWindows.msi IGNORE_VSS_REGISTRATION_ERRORS=1

    where [PATH] is the path to where you have the AcronisAgentWindows.msi file.

    For example,

    msiexec.exe /i C:\AcronisAgentWindows.msi IGNORE_VSS_REGISTRATION_ERRORS=1

  2. Please also check the services. The following services should be started: Volume Shadow Copy, COM+ System Application, Distributed Transaction Coordinator (Control Panel -> Administrative Tools -> Services).

Should the issue persist, please kindly regather the MSI log and Acronis Info. After that please submit a support request and tell me the case number - I'd like to make sure that it's handled in a proper way.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

I have this problem as well, but since I cannot compare my log file with the one Eric Retherford appears to have sent separately, I herewith send my log, that almost every (incremental) backup session produces:

1 Informatie 19-12-2012 16:00:01 Stage-beschrijving
2 Informatie 19-12-2012 16:00:02 Bewerking Documenten is via planning gestart.
3 Informatie 19-12-2012 16:00:18 Bezig met analyseren van partitie '0-0'...
4 Informatie 19-12-2012 16:00:19 Bezig met analyseren van partitie 'C:'...
5 Informatie 19-12-2012 16:00:19 Bezig met analyseren van partitie '0-0'...
6 Informatie 19-12-2012 16:00:20 Bezig met analyseren van partitie 'E:'...
7 Informatie 19-12-2012 16:00:20 Bezig met analyseren van partitie '0-0'...
8 Informatie 19-12-2012 16:00:20 Bezig met analyseren van partitie 'F:'...
9 Informatie 19-12-2012 16:00:20 Bezig met analyseren van partitie 'L:'...
10 Informatie 19-12-2012 16:00:20 Bezig met analyseren van partitie '0-0'...
11 Informatie 19-12-2012 16:00:21 Bezig met analyseren van partitie 'K:'...
12 Informatie 19-12-2012 16:00:21 Stage-beschrijving
13 Informatie 19-12-2012 16:00:21 Prioriteit gewijzigd in Laag.
14 Informatie 19-12-2012 16:00:21 Back-updatabase bijwerken:
Verificatievereisten voor databasetoegang instellen.
15 Informatie 19-12-2012 16:00:22 Bezig met vergrendelen van partitie C:...
16 Informatie 19-12-2012 16:00:27 Incrementele back-up maken Van:
C:\Users\John\Documents\ Naar bestand:
"K:\Mijn back-ups\Documenten.tib" Compressie:
Normaal Uitsluiten: Systeembestanden
17 Informatie 19-12-2012 16:30:25 De volgende back-ups zijn gemaakt:
"K:\Mijn back-ups\Documenten(2)3.tib"
18 Informatie 19-12-2012 16:30:25 Back-updatabase bijwerken:
Nieuwe back-upversie met record-id 0 invoegen in de back-up met id 6224369287158703809.
19 Informatie 19-12-2012 16:30:25 Back-updatabase bijwerken:
Back-upversie met record-id 250 verwijderen.
20 Informatie 19-12-2012 16:30:28 Back-updatabase bijwerken:
Nieuwe volumes invoegen in back-upversie met record-id 0
van de back-up met id 6224369287158703809 die zich in de back-upgroep met id 0 bevindt.
21 Informatie 19-12-2012 16:30:44 Back-updatabase bijwerken:
Nieuwe back-upopties instellen voor back-upgroep met id 419.
22 Informatie 19-12-2012 16:30:44 Back-updatabase bijwerken:
Verificatievereisten voor databasetoegang verwijderen.
23 Informatie 19-12-2012 16:31:09 Back-uparchief consolideren Locatie:
"K:\Mijn back-ups\Documenten(2)3.tib" Doel:
"K:\Mijn back-ups\Documenten(2)3_E6EF2217-5F32-4F18-BAE6-60F0A8A68435.tib"
24 Informatie 19-12-2012 16:31:09 Back-uparchief consolideren Locatie:
"K:\Mijn back-ups\Documenten(2)3.tib" Doel:
"K:\Mijn back-ups\Documenten(2)3_E6EF2217-5F32-4F18-BAE6-60F0A8A68435.tib"
25 Acronis True Image Home 19-12-2012 16:31:09 Kan gegevensstroom niet openen.
26 Acronis True Image Home 19-12-2012 16:31:09 Het opgegeven bestand bestaat niet.
27 Acronis True Image Home 19-12-2012 16:31:09 Het opgegeven bestand bestaat niet.
28 Acronis True Image Home 19-12-2012 16:31:09 Het systeem kan het opgegeven bestand niet vinden
29 Informatie 19-12-2012 16:31:10 Back-updatabase bijwerken:
Informatie over maken van nieuwe back-upversie
invoegen in de back-up met id 6224369287158703809.
30 Acronis True Image Home 19-12-2012 16:31:29 De bewerking is voltooid met fouten.

I hope someone can help me with this error, and I hope that the Dutch text makes sense. Sorry!

P.S. I cut several lines at convenient places to make it more readable and to avoid too long sentnces.

P.S. 2 My OS is Vista, my ATI version is 12, up to date: 15.0.0.7133

We just had this same problem using Snap Deploy. Fixed with the help of Level 2 support. This is what we did. Same steps might work for other products using remote agent service.

In our case, we found when the Snap Deploy Console opened it won't connect to the Snap Deploy's OS Deploy Server. We noticed, the Remote Agent service wasn't running.

Look in C:\ProgramData\Acronis\DeployServer\Database for the Database file. In our case it was size 0. It shouldn't be. Something was preventing it from being populated. The following fixed it for us.

  • Snap Deploy console must be closed
  • Disable your firewall and antivirus (You may want to do it out of hours.)
  • Start the Remote Agent service manually. Refresh a few times to make sure it's still running and didn't stop again
  • Now open the console (or your equivalent app)  The console connects to OS Deploy Server successfully. In our case, the Database file was now 144K.
  • We re-enabled firewall and antivirus

We verified the service continues to start OK by manually stopping and starting it a few times. NOTE: Console must be closed when you stop the service. Trying to stop the service while Console was opened causes things to hang.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

LookinAround thank you so much for taking the time to share your solution with other users!