SRM service crash during upgrade

Log location: c:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\vmware-dr.log

 

crash backtrace:

2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96860’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96942’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96962’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96963’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] PVM State Tracker: Initializing.
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] PVM State Tracker: Will NOT initialize VM Info.
2018-01-08T23:02:58.770-07:00 [03132 verbose ‘DatastoreGroupManager’ opID=640e1e2d] Found 9 devices on host ‘host-757’
2018-01-08T23:02:58.770-07:00 [03132 verbose ‘DatastoreGroupManager’ opID=640e1e2d] Found 9 VMFS volumes on host ‘host-757’
2018-01-08T23:02:58.770-07:00 [03132 verbose ‘DatastoreGroupManager’ opID=640e1e2d] Dr::Storage::Match::`anonymous-namespace’::DeviceFetcher::FetchDevices: Fetched devices for host host-757
2018-01-08T23:02:58.786-07:00 [01952 panic ‘Default’ ctxID=5c5b5384 opID=76706664]
–>
–> Panic: FAILURE: “Deserialize failed for data item (persistence id: ##global##_pvmi.protected-vm-106049): std::exception ‘class boost::archive::archive_exception’ “input stream error”” @ d:/build/ob/bora-4535903/srm/src/jobs/jobs.cpp:304
–> Backtrace:
–>
–> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 6.1.1, build: build-4535903, tag: –
–> backtrace[00] vmacore.dll[0x001BF51A]
–> backtrace[01] vmacore.dll[0x0005D88F]
–> backtrace[02] vmacore.dll[0x0005E9DE]
–> backtrace[03] vmacore.dll[0x001D7A55]
–> backtrace[04] vmacore.dll[0x001D7B4D]
–> backtrace[05] vmacore.dll[0x0004DEFC]
–> backtrace[06] dr-jobs.dll[0x00035DB7]
–> backtrace[07] MSVCR90.dll[0x00074830]
–> backtrace[08] MSVCR90.dll[0x00043B3C]
–> backtrace[09] ntdll.dll[0x0004B681]
–> backtrace[10] dr-jobs.dll[0x0000390C]
–> backtrace[11] dr-jobs.dll[0x00005408]
–> backtrace[12] dr-recovery.dll[0x0016F153]
–> backtrace[13] dr-recovery.dll[0x0016AC81]
–> backtrace[14] dr-recovery.dll[0x002B0488]
–> backtrace[15] dr-recovery.dll[0x002AEF33]
–> backtrace[16] dr-recovery.dll[0x002B4011]
–> backtrace[17] dr-recovery.dll[0x00031A19]
–> backtrace[18] functional.dll[0x00028089]
–> backtrace[19] vmacore.dll[0x00153B8E]
–> backtrace[20] vmacore.dll[0x0015749F]
–> backtrace[21] vmacore.dll[0x001589F1]
–> backtrace[22] vmacore.dll[0x0015A725]
–> backtrace[23] vmacore.dll[0x00066C4B]
–> backtrace[24] vmacore.dll[0x00155DC0]
–> backtrace[25] vmacore.dll[0x001D302B]
–> backtrace[26] MSVCR90.dll[0x00002FDF]
–> backtrace[27] MSVCR90.dll[0x00003080]
–> backtrace[28] kernel32.dll[0x000159CD]
–> backtrace[29] ntdll.dll[0x0002A561]
–> [backtrace end]
–>

 

Resolution:  Take a backup of the SRM DB and delete the contents of the table: pdj_dataitem and resume the installer.

 

Delete from pdj_dataitem;