Storage Node service stopped

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 7
Commenti: 1

Hi all,
almost every day the storage node service has been stopped. In the Windows event log I found the following error:
Protokollname: Application
Quelle: Application Error
Datum: 13.11.2013 04:46:30
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: ACRONIS-SERVER.gpunkt.magdeburg.de
Beschreibung:
Name der fehlerhaften Anwendung: StorageServer.exe, Version: 11.5.0.32266, Zeitstempel: 0x50618569
Name des fehlerhaften Moduls: StorageServer.exe, Version: 11.5.0.32266, Zeitstempel: 0x50618569
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000048a928
ID des fehlerhaften Prozesses: 0x125c
Startzeit der fehlerhaften Anwendung: 0x01cee017148eedf7
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Acronis\StorageNode\StorageServer.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Acronis\StorageNode\StorageServer.exe
Berichtskennung: 2dd1accc-4c16-11e3-9f30-005056b6001a
Ereignis-XML:

1000
2
100
0x80000000000000

33816
Application
ACRONIS-SERVER.gpunkt.magdeburg.de

StorageServer.exe
11.5.0.32266
50618569
StorageServer.exe
11.5.0.32266
50618569
c0000005
000000000048a928
125c
01cee017148eedf7
C:\Program Files (x86)\Acronis\StorageNode\StorageServer.exe
C:\Program Files (x86)\Acronis\StorageNode\StorageServer.exe
2dd1accc-4c16-11e3-9f30-005056b6001a

Is there any explanation why the service is stopped. The machine acronis storage node runs on is a Windows 2008 Server 64bit with 8GB RAM.

Regards
anko

Mer, 11/13/2013 - 06:27
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Messaggi: 0
Commenti: 1379

It stopped because it crashed (maybe several times) and then system did not restart the service any more. It's impossible to tell the reason without the crash dump, and it's better to update to the latest build (37975) because the crash reason it may be already fixed there. If it doesn't help you will need to contact support, so that the dump could be analyzed be developers.

Mer, 11/13/2013 - 06:58