Hyper-V replication problem

I have several 2012 R2 Hyper-V servers that replicate to another server and have done this for years. One server in particular I'm having trouble.
Noticed it yesterday that the replication health was critical and started to investigate. It showed that an avhdx file was on the hosted server and the hard drive in the settings had a long name in the drive settings. Normally when you shut down the server the avhdx  will merge with its parent. This time it did not and I had  to manually merge the file, delete the VM and recreate another one and reset up the replication. Everything went fine yesterday afternoon and replication was normal. This morning I came in and again it was back in the critical state. What can I do to fix this?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
What do the replica logs say as far as the reason for the critical state?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cyberservicesAuthor Commented:
Fix the problem and try again. not much here. I did create a brand new virtual machine with the same discs.
R@f@r P@NC3RVirtualization SpecialistCommented:

ok, let's wait until tomorrow to see if the problem does not arise again.

I remain attentive to your comments.

cyberservicesAuthor Commented:
I found on the Internet a solution that I tried. I shutdown the VM went to the folder where the VM is located and watched the merge and the avhdx file disappear. Then I restarted the VM again and noticed it did not create another avhdx. What was happening I was starting the VM to soon and not waiting until the VM to finish merging. Lesson learned.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.