-
- Novice
- Posts: 3
- Liked: never
- Joined: Feb 08, 2016 7:56 am
- Contact:
Error on first run
Hello,
Since I've updated Veeam Agent to the latest version, 3.0.1.1039, on a Windows Server 2012 R2, I always get the following error at the first run of the backup job:
Error: the username or password is incorrect: Failed to process [IsFileExists].
After the that, the retry is started and the jobs end successfully.
I'm having the same issue on another server, also with Veeam Agent 3.0.1039 and Windows Server 2012R2. In both cases the backup location is a shared folder on a NAS.
Things I've tried to solve the issue:
- reboot of the server
- change schedule of the backup job
- Reenter credentials.
Case id: 03616583
Since I've updated Veeam Agent to the latest version, 3.0.1.1039, on a Windows Server 2012 R2, I always get the following error at the first run of the backup job:
Error: the username or password is incorrect: Failed to process [IsFileExists].
After the that, the retry is started and the jobs end successfully.
I'm having the same issue on another server, also with Veeam Agent 3.0.1039 and Windows Server 2012R2. In both cases the backup location is a shared folder on a NAS.
Things I've tried to solve the issue:
- reboot of the server
- change schedule of the backup job
- Reenter credentials.
Case id: 03616583
-
- Veteran
- Posts: 3077
- Liked: 455 times
- Joined: Aug 07, 2018 3:11 pm
- Full Name: Fedor Maslov
- Contact:
Re: Error on first run
Hi Jv,
Welcome to Veeam Community Forums and thanks for posting!
The root cause could be different for this error. Please, keep working with the support team directly.
Thanks
Welcome to Veeam Community Forums and thanks for posting!
The root cause could be different for this error. Please, keep working with the support team directly.
Thanks
-
- Novice
- Posts: 3
- Liked: never
- Joined: Feb 08, 2016 7:56 am
- Contact:
Re: Error on first run
Hello,
I've received a message from the Support Team, that the ticket is closed due to high Support team load.
Can someone on the forum help me with this issue?
I've received a message from the Support Team, that the ticket is closed due to high Support team load.
Can someone on the forum help me with this issue?
-
- Veteran
- Posts: 3077
- Liked: 455 times
- Joined: Aug 07, 2018 3:11 pm
- Full Name: Fedor Maslov
- Contact:
Re: Error on first run
Hi,
We hope you understand that we cannot troubleshoot technical errors through the forums and this should be done on the support team end.
I'd suggest a complete reinstallation, but if no luck you'll need to investigate this difficulty with support engineers.
Thanks
We hope you understand that we cannot troubleshoot technical errors through the forums and this should be done on the support team end.
I'd suggest a complete reinstallation, but if no luck you'll need to investigate this difficulty with support engineers.
Thanks
-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Nov 01, 2017 10:11 pm
- Full Name: Jon
- Contact:
[MERGED] Failed to process [isFileExists] on Win10 (2004)
Every day, Veeam Agent for Windows fails the 1st backup, but then 2nd backup always successfully completes. This happens only on newest version of Windows 10 (2004). This does not happen on W10 (1909) or Windows 7. For the same VAFW build (4.0.1.2169).
Error is: "The user name or password is incorrect. Failed to process [isFileExists].
Backing up to shared folder on Synology DS916+ NAS.
My guess is on the 1st attempt there is some kind of expired token or credential being used from previous day causing the failure, then on 2nd attempt that token/credential is "refreshed" so it's accepted on 2nd try. Just a hunch.
Again, this error only happens on Win10 (2004), and it happens every day. No such error on Win10 (1909) or Win7 using same VAFW build 4.0.1.2169.
Error is: "The user name or password is incorrect. Failed to process [isFileExists].
Backing up to shared folder on Synology DS916+ NAS.
My guess is on the 1st attempt there is some kind of expired token or credential being used from previous day causing the failure, then on 2nd attempt that token/credential is "refreshed" so it's accepted on 2nd try. Just a hunch.
Again, this error only happens on Win10 (2004), and it happens every day. No such error on Win10 (1909) or Win7 using same VAFW build 4.0.1.2169.
-
- Product Manager
- Posts: 14836
- Liked: 3083 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Error on first run
Hello,
I merged it with a similar issue. Can you tell us please, what your support case number is?
Please remember, that the forums are not run by support and you need to post the case number for technical issues: veeam-backup-replication-f2/rules-of-po ... -t755.html
Best regards,
Hannes
I merged it with a similar issue. Can you tell us please, what your support case number is?
Please remember, that the forums are not run by support and you need to post the case number for technical issues: veeam-backup-replication-f2/rules-of-po ... -t755.html
Best regards,
Hannes
-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Nov 01, 2017 10:11 pm
- Full Name: Jon
- Contact:
Re: Error on first run
Hannes, the Support Case # 04339834
-
- Product Manager
- Posts: 14836
- Liked: 3083 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Error on first run
Hello,
as far as I see, you did not provide logs and did not answer to the support. No idea how we could guess the real reason, as it is not a "well known issue".
Best regard,
Hannes
as far as I see, you did not provide logs and did not answer to the support. No idea how we could guess the real reason, as it is not a "well known issue".
Best regard,
Hannes
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Mar 24, 2022 12:06 pm
- Full Name: Feras
- Contact:
Re: Error on first run
Hi,
did you find any solution ?
BR
Feras
did you find any solution ?
BR
Feras
-
- Veteran
- Posts: 3077
- Liked: 455 times
- Joined: Aug 07, 2018 3:11 pm
- Full Name: Fedor Maslov
- Contact:
Re: Error on first run
Hi Feras,
Based on what I see in the cases of the previous posters, no. I would recommend opening an independent one to investigate your particular situation.
Thanks
Based on what I see in the cases of the previous posters, no. I would recommend opening an independent one to investigate your particular situation.
Thanks
Who is online
Users browsing this forum: No registered users and 37 guests