Replication Jobs "Error in the application"

[Supraman]

Hello Guys,

I am not sure if anyone has come across this issue or not but just over the weekend over 80% of our replication jobs just started having the "Error in the Application" without any other messages as show below. From what I can tell some jobs did finish successfully without any issues and as far as I can tell nothing has recently changed. I have check the Vms and ruled out that the host was not the problem and ensure all of our proxies are in order working which they were. Re-running the job cause the same issue so I am not sure what cause this issue.

I have looked at the forum and there was only one other user reporting this same error and his was related to his Hosts or Poxies.

Currently I have a work around this issue, but it is not ideal.

9/13/2021 11:06:39 AM :: Processing XXXXX Error: Error in the application.
9/13/2021 11:06:44 AM :: Processing XXXXX: Error in the application.
9/13/2021 11:06:44 AM :: Processing XXXXX Error: Error in the application.
9/13/2021 11:06:44 AM :: Processing XXXXX: Error in the application.
9/13/2021 11:06:45 AM :: Processing XXXXX Error: Error in the application.
9/13/2021 11:06:45 AM :: Processing XXXXX Error: Error in the application.

[Mildur]

Please open a support case as requested when you create the topic.
Veeam Support can help you to solve this with the debug logs.

[Supraman]

Hello Mildur,

My case # 05020703 and so far I guess the support engineer is reviewing the logs.

[toddatomic]

Did you ever figure this out? I'm getting the same message on some of my replication jobs. "Error: Error in the application."

[Gostev]

Usually the cause for this error is DNS issue, but can be due to a bunch of other reasons too.
11a should log a proper error instead of this generic one, so if you can please install it.

[andrie]

Had this issue too in the last few days, the problem was a communication issue between the backup server and the proxy on port 2500. Check the task log for details.

[Supraman]

Hello Todd and Andrie,

For my issue I had to manually deleted the "Working snapshot" of the actually Replica VM from within Vcenter. I had to do this on like 50 VM once I had deleted it I re-ran the replication Job and it worked so in my particular case it was not an issue with the VBR server communicating with the Proxy.