[Resolved] 11 upgrade - storage node not working correctly

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 4

Storage node problem on upgrade to Acronis 11 advanced server with universal restore.

Case #: 01496366

Synopsis: Acronis 10 Management Server worked. After upgrade to Acronis 11 Management Server, it has not been able to deploy backup plan to agent on
server. It did deploy to agents on client machines. If I connect directly to agent on server, I can build and run backup plan. I constantly receive the following alert every few minutes: Operation Failed: Synchronizing with Agent.

Platform:
Windows Server 2003
Roles:
File server
Print server
Application server (IIS, ASP.NET)
Terminal server
Domain Controller (Active Directory)
DNS server
DHCP server

Acronis versions:
ABR11A_17217_en-US.exe, ABR11A_17218_en-US.exe, and ABR11A_17375_en- US.exe:
Acronis Backup & Recovery 11 Agent Core
Acronis Backup & Recovery 11 Agent for ESX(i) VirtualAppliance
Acronis Backup & Recovery 11 Management Server
Acronis Backup & Recovery 11 Storage Node
Acronis Backup & Recovery 11 Tray Monitor
Acronis Backup & Recovery 11 Agent
Acronis Backup & Recovery 11 Bootable Media Builder
Acronis Backup & Recovery 11 Universal Restore
Acronis Wake-on-LAN Proxy
Acronis PXE Server

I have done the following:
• Deleted, recreated, redeployed all backup plans
• Upgraded from 17217 to 17218 to 17375
• Installed all Microsoft updates except optional: KB925876, KB2632503, KB968930, KB943729, and KB2617986
• Removed storage node and tried to re-add unsuccessfully (see errors below)
• Deleted all backup plans again
• Ran repair on all installed Acronis products
• Still unable to re-add storage node

Microsoft Errors:

The application has requested the runtime to terminate in an unusual way

StorageServer.exe - Application Error
The exception unknown software exception (0x40000015) occurred in the application at location 0x4a923a5b

Acronis Errors:

Command 'Backing up' has failed.
Additional info:
--------------------
Error code: 3
Module: 309
LineInfo: 4a8728dc8a1c94f8
Fields:
Message: Command 'Backing up' has failed.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields:
Message: Backup has failed.
--------------------

Operation with partition '0-0' was terminated.
Details:
Failed to create volume snapshot.

Error code: 0x70021
$module = "C:\Program Files\Acronis\BackupAndRecovery\DiskBundle.dll"
Tag: 0xA5695862AAF8E674
Failed to start creating the volume snapshot.

Error code: 0x10C442
Tag: 0x14181C22EF45B077
The device is not ready

Error code: 0xFFF0
code = 2,147,942,421 (0x80070015)
Tag: 0xBD28FDBD64EDB8BC
Additional info:
--------------------
Error code: 502
Module: 1
LineInfo: a164035b3ff39287
Fields: $module : C:\Program Files\Acronis\BackupAndRecovery\DiskBundle.dll
Message: Operation with partition '0-0' was terminated.
Details:
Failed to create volume snapshot.

Error code: 0x70021
$module = "C:\Program Files\Acronis\BackupAndRecovery\DiskBundle.dll"
Tag: 0xA5695862AAF8E674
Failed to start creating the volume snapshot.

Error code: 0x10C442
Tag: 0x14181C22EF45B077
The device is not ready

Error code: 0xFFF0
code = 2,147,942,421 (0x80070015)
Tag: 0xBD28FDBD64EDB8BC
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e674
Fields:
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b077
Fields:
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8bc
Fields: code : 2147942421
Message: The device is not ready
--------------------

Error: Routine failed to serialize result.
Additional info:
--------------------
Error code: 16
Module: 173
LineInfo: c93597b64f4e1c38
Fields: $module : C:\Program Files\Acronis\StorageNode\StorageServer.exe
Message: Error: Routine failed to serialize result.
--------------------
Error code: 2
Module: 0
LineInfo: c93597b64f4e1c39
Fields:
Message: Not enough memory.
--------------------

Failed to add the storage node
Details:
Code: 11,337,744(0xAD0010)
LineInfo: 0xc93597B64F4E1C38;

Module: C:\Program Files\Acronis\StorageNode\StorageServer.exe
Message: Error: Routine failed to serialize result.

Code: 2(0x2)
KLineInfor: 0xC93597B64F4E1C39

Message: Not enough memory.

Wed, 03/14/2012 - 17:47
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 4

It appears that I have fixed the problem. Unfortunately, I do not know what exactly caused the issue, nor do I know if one task or a combination of tasks created the positive outcome. To solve it, I did the following:

1. Deleted Symantec 10.2 and all related components
2. Deleted everything related to Acronis from Add\Remove Programs
3. Deleted all remaining Acronis files from Program Files
• I did not delete registry entries nor did I delete SQL databases
• After deleting Acronis and restarting the computer, I received the Microsoft message: Found new hardware, Windows needs to install software. No hardware or peripherals were added, nor have any been added just before or after the onset of this issue. In addition, before I deleted Acronis, this computer had been restarted numerous times without receiving this message.
4. During installation of Acronis, I was prompted the use existing SQL data or overwrite. I chose to overwrite.
5. While creating a new Storage Node, I used the server’s ip address instead of name. Reference Acronis article 11080: Acronis Backup & Recovery 10: Policy Deployment Fails with "Failed to proccess synchronization data." I do not have any problems with DNS, but I figured why take a chance.
6. I attached and re-indexed managed vaults
7. I first created, deployed, and ran a backup plan on the management console for the server
8. I then created, deployed, and ran a backup plan on the management console for a group of computers

Currently, everything appears to be working correctly.

Sat, 03/17/2012 - 01:47