2 issues with ABR11

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

Hi all, I seem to be having these 2 issues ever since updating to v1737

The first is extremely annoying and would like it sorted out very soon.

1- Every 5-6 hours the Managementserver.exe crashes in the background and causes the console to be stuck on "Waiting for reconnection" for about 40 min before I can use it again. Event logs show the following. THIS IS A CLEAN INSTALL of 1737 on a fresh VM

Faulting application name: ManagementServer.exe, version: 11.0.0.17437, time stamp: 0x4f627cab
Faulting module name: ManagementServer.exe, version: 11.0.0.17437, time stamp: 0x4f627cab
Exception code: 0xc00000fd
Fault offset: 0x0019cfcb
Faulting process id: 0x1998
Faulting application start time: 0x01cd18eb8f30a895
Faulting application path: C:\Program Files (x86)\Acronis\AMS\ManagementServer.exe
Faulting module path: C:\Program Files (x86)\Acronis\AMS\ManagementServer.exe

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ManagementServer.exe
P2: 11.0.0.17437
P3: 4f627cab
P4: ManagementServer.exe
P5: 11.0.0.17437
P6: 4f627cab
P7: c00000fd
P8: 0019cfcb
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ManagementServer_17a794ff36f6f8a97db4b79328c98db6d2e88f7_071752f9

Analysis symbol:
Rechecking for solution: 0
Report Id: 53cc0039-84ef-11e1-8bb0-005056ae00ea
Report Status: 4

*******************************************************************************
2- Every couple of days random agents/computers randomly change their next deployment state to "[Manual Start]" even though they are set to perform a full backup every morning at 2 or 4am in the morning. The only way around this is if I go into the affected computers and restart all acronis services (I have done clean installs of agent core and agent too without any help) then change the next start time to 1 second later and then change it back to deploy to the computer to start correctly. I do notice that affected computers sometimes show their mms.exe in task manager as 20-50MB instead of the usual 130MB usage.

I have attached event logs and the windows log too

Attachment Size
report.zip 84.75 KB
Thu, 04/12/2012 - 23:36
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 27
Comments: 1940

1) a crash dump (.dmp) of ManagementServer.exe is needed.
2) Do they stop performing backup too or just display the time incorrectly?

Fri, 04/13/2012 - 03:49
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

1- When should I create the .dmp file? Directly after is crashes?

2- Yes, it won't create the backups at all.

Fri, 04/13/2012 - 04:47
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

It just happened again, here is the dmp file *directly* after is happens. The process doesn't close off it just goes from over 1.2GB down to 60-90MB and take at least another 30 min to start working again.

*edit* see below

Mon, 04/16/2012 - 22:53
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 27
Comments: 1940

1) You need to get a dump of crash itself, e.g. with procdump (http://technet.microsoft.com/en-us/sysinternals/dd996900)
with a command procdump -e -mp ManagementServer.exe
Restart the service, issue this command in a cmd prompt and wait until it crashes again.

Fri, 04/13/2012 - 17:52