Acronis Storage Node Service stops after start
Hi,
I just updated to the most recent product version 11.0.17437, starting with the server, updating the installed components (Management Server, Management Console, Storage Node, Command-Line Tool, License Server, PXE Server and Components for Remote Installation).
After a reboot I started the Management Console and checked the central depots. There I see "connection to storage node failed" (in german). I checked the windows service "Acronis Storage Node Servce", which was stopped. It is set to Auto Start, an I started it manually again. It run for about 15sec, then stopped again. I changed the service account to Local System, tried again - nothing better. So I changed back to previous domain account we used before the update.
All components have been updated, also the management console used for administration (local on the same server).
The event log shows an entry about the service now running, then 19 secs later "stopped". No error messages in between. Event ID is 7036 (nothing special).
Right now I cannot use the software at all.
Any ideas?
Regards
Uli
Update:
I tried repairing the installation of Storage Node Service, and even uninstalled and reinstalled it. No progress with this.

- Se connecter pour poster des commentaires

change the account the service uses to login.
- Se connecter pour poster des commentaires

As you see in my first post i already tried this. Do you propose any special account / rights for this?
What about support? This seems to be a critical bug making use of the software impossible.
- Se connecter pour poster des commentaires

you could try running a clean installation:
* uninstall storage node (and all acronis stuff)
* move everything from /programdata/acronis away to a safe location
* reinstall acronis software
-- you should now have an empty storage node
* reattach you vault. as you moved away the catalog, the storage node will now be busy for a while, rescanning all the backups.
* hopefully it doesn't crash any more.
- Se connecter pour poster des commentaires

Sure I could try this. But would you recommend this for productive scenarios?
- Se connecter pour poster des commentaires

I'm not recommending B&R 11 for productive scenarios yet. I'm still testing the recent build.
you should definitely open a support case. Support seems to have become a lot quicker in the recent weeks...
- Se connecter pour poster des commentaires

Hi Ulrich
I've had the same issue following the recent upgrade.
Got it working again by doing the following:
*Renamed C:\ProgramData\Acronis\BackupAndRecovery\ASN to ASN.old
*Started the service again. The ASN folder was recreated.
*Attached all vaults again
All data seems to be here, however a number of archives are registered as Untitled archive(#) - there is still a reference to the machine that was backed up though.
Regards
Mikkel Kristensen
- Se connecter pour poster des commentaires

Hi Mikkel,
this works so far, that i can start the service again, and it keeps running. Therefore I now have the problem, that there is a problem obtaining the statistics for depot 'arl:/...'
The other functions (validate, disconnect) throw errors, so i can't disconnect and reconnect the depots. I also can not reconnect without disconnecting, because the depot already exists.
"Delete" is not what I want.
I can create a NEW depot, that works.
The problem seems to be (as i can see while editing the "old" depots), that it can't resolve the depot administrators and users. It shows an error like this:
Code: 10.027.025(0x990011)
LineInfo: 0xB1CA5C15FD9846FD;
Modul: management_server_vs
Nachricht: Abrufen der Depot-Benutzer für das verwaltete Depot 'arl:/958D9430-A37A-4568-9717-658697A12551/A6CFBE6E-AEF4-40D8-A0A3-D8A43DDCCAEF' fehlgeschlagen.
Code: 2.555.910(0x270006)
LineInfo: 0xFC4666E88268D83C;
Modul: storage_server_vsa64
Nachricht: Unbekanntes Depot 'A6CFBE6E-AEF4-40D8-A0A3-D8A43DDCCAEF'.
- Se connecter pour poster des commentaires

Hi Ulrich,
Sorry cannot help there. I didn't have any problems attaching the Vaults again.
Regards
Mikkel Kristensen
- Se connecter pour poster des commentaires

Hi Mikkel,
seems to work now. I rebootet the server, removed the storage node, created it new and reattached the depots.
Backups are running again.
Thank you!
Regards
Ulrich
- Se connecter pour poster des commentaires