Upgrade to 5.5 with strange Replication issues to follow

[brianbroyles]

We just upgraded our environment to 5.5 and the first thing that we done was to pause our server in replication.  But while vacating one of the host the vm errored out and shutdown.  From logs it appeared that there was a lock on the vm somewhere in esx so we decided to shutdown the VRA server and that allowed the vm to migrate.  But after finishing the upgrade and the dust settled I was able to resume all servers except for the one that received the error.  Now I get an error when trying to resume this vm.

[mmarinov]

Is this standalone vsphere replication or it is as part of SRM?

I can't say much with no logs, but it turns out that the source VM has corrupted info within the vCenter Server or/and the host. Thus working with the corresponding APIs for computing permissions regarding replication operations are not possible. You should file an SR and provide the logs we can deeply analyze the problem.

One workaround would be re-configure replication but that means that you will lose all you data on the target site and need to initiate the inital full sync from the scratch.

Regards,

--Martin