Skip to main content
Answer

File Backup job failure possibly related to latest windows update

  • January 18, 2022
  • 3 comments
  • 8034 views

Forum|alt.badge.img

Hey all,

 A file backup job started failing when it attempted to run on Saturday the 15th. When the job ran on Friday evening, everything was fine, but it decided to start failing on Saturday. On Friday night, the recent Microsoft patch (kb5009557 2022-01 Cumulative Update for Windows Server 2019 (1809)) was installed after the Veeam job ran so I am thinking that the failure might be due to the update? Currently using Veeam Backup and Replication Build 11.0.0.837 installed on a Windows Server 2019 Hyper-V machine. When looking in Event Viewer, I looked under the Applications and Services Logs tree and the failed job is given an Event ID of 190 with this message, “Job details: Error: Agent: Failed to process method {NasMaster.CreateIfNotExistsJobBackup}: You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.” I have looked at the network and authentication settings of my NAS and everything there looks okay. Has anyone else experienced this after the latest Microsoft update?

Thanks

Best answer by Inder

@Amroth : Can you check if this helps 

https://forums.veeam.com/file-shares-f57/error-agent-failed-to-process-method-nasmaster-executebackupprocessor-cannot-find-object-in-corrupted-objects-t64859.html 

https://forums.veeam.com/file-shares-f57/backup-fails-with-error-failed-to-process-method-nasmaster-savesourcebackupmeta-t66899.html

3 comments

Forum|alt.badge.img+3
  • Experienced User
  • Answer
  • January 18, 2022

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • January 18, 2022

marcofabbri
Forum|alt.badge.img+12
  • On the path to Greatness
  • January 21, 2022

I know this is OT from solution, but for all related issue with lastest Windows updates, Microsoft stated that released fix inside this week update

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-21h2#2778msgdesc