VMware Cloud Community
MLAtW
Contributor
Contributor
Jump to solution

Clear error message on Replication / Recovery tab?

I have a message on the one of my VSphere Replication / Incoming Replications / Recovery Tab: "A generic error occurred in the vSphere Replication Managegment Server.  Exception details: java.Lang.NullPointerException'

How do I clear this message?

0 Kudos
1 Solution

Accepted Solutions
MLAtW
Contributor
Contributor
Jump to solution

I finally took a shot and stopped the replication, and re-created it to the same location.  That cleared the error, and the status is all OK now.

Hopefully, if I try to clone the VM again, I won't experience the same issue all over again.

View solution in original post

0 Kudos
5 Replies
Finikiez
Champion
Champion
Jump to solution

What type of client you use?

Can you post a full screenshot?

Thx.

0 Kudos
Finikiez
Champion
Champion
Jump to solution

does this error appear with only one VM or with all VMs?

Seems that something is wrong on vsphere replication management server side.

Have you tried restart it \ restart management agent on ESXi hosts where VM is running?

0 Kudos
MLAtW
Contributor
Contributor
Jump to solution

This is all in regards to a single VM on the ESXi 6.5 host.  All other VMs are ok.

I had attempted a recover operation, which had failed.  I then shutdown all VMs and rebooted the host.  I noticed this error message a day later (there was also a Replication 'failed' status, but that cleared up in another 24 hours).

I just rebooted the Replication Appliance VM, and the same message is still there.

0 Kudos
MLAtW
Contributor
Contributor
Jump to solution

Since rebooting both the ESXi host and the VM in question and the vSphere Replication Appliance has had no effect, what do you think about removing and re-creating the Replication of this VM to the same backup datastore?

I guess I would want to just stop the replication and configure a new replication?

0 Kudos
MLAtW
Contributor
Contributor
Jump to solution

I finally took a shot and stopped the replication, and re-created it to the same location.  That cleared the error, and the status is all OK now.

Hopefully, if I try to clone the VM again, I won't experience the same issue all over again.

0 Kudos