Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
ZacE
Lurker
Posts: 1 Liked: never
Joined: Sep 08, 2020 7:42 pm
Full Name: zac
Contact:
Post
by ZacE » Sep 08, 2020 9:45 pm
this post
Hello, i have Veeam agent running on server 2012r2. It has been a great backup solution up until now. I am getting errors and cannot complete a backup job. This is a production server for a public school district. We have been evaluating Veeam as a backup solution with hopes of moving to a paid version. Any help you can provide would be greatly appreciated.
Here is my case number: 04377219
Here are some of the errors I have received, any help would be greatly appreciated.
I have uninstalled and reinstalled with a reboot in between.
Code: Select all
__________________________________________
9/8/2020 1:59:34 PM :: Error: startIndex cannot be larger than length of string. Parameter name: startIndex
__________________________________________________
9/8/2020 2:14:27 PM :: Error: Timeout to start agent
____________________________________
Faulting application name: Veeam.EndPoint.Manager.exe, version: 4.0.1.2169, time stamp: 0x5f0daaae
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19678, time stamp: 0x5e82c88a
Exception code: 0xc0000142
Fault offset: 0x00000000000ecf40
Faulting process id: 0x1dbc
Faulting application start time: 0x01d68625f2116da4
Faulting application path: C:Program FilesVeeamEndpoint BackupVeeam.EndPoint.Manager.exe
Faulting module path: KERNELBASE.dll
Report Id: 2fc05aab-f219-11ea-8116-9457a555943f
Faulting package full name:
Faulting package-relative application ID:
Andreas Neufert
VP, Product Management
Posts: 6747 Liked: 1408 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:
Post
by Andreas Neufert » Sep 09, 2020 7:58 am
this post
I think this is something only our support (this is not a support forum) can track down.
Maybe check if you have the latest version of Veeam:
https://www.veeam.com/kb3228
If it was a known issue then it should have been fixed there.
Users browsing this forum: Google [Bot] and 30 guests