Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

SQL processing fails with "Logon failure: the user has not been granted the requested logon type at this computer" error after upgrade to Update 3a

$
0
0

Challenge

Just after upgrade Veeam B&R to Update 3a you may notice failures on following operations:
  • truncate SQL transaction logs;
  • collect SQL instances for Veeam Explorer for SQL (VESQL);
  • back up database transaction logs;
While the error message varies depending on actual operation there is a common error "Logon failure: the user has not been granted the requested logon type at this computer. Code: 1385" thrown in the job sessions.

Cause

The issue is caused due to additional permission and roles required for Update 3a:
  1. Account used for application-aware processing should have the following security policies applied:
    • Logon as a batch job granted.
    • Deny logon as a batch job not set.
  2. In case you need to provide minimum permissions for the account to perform backup operations additionally db_datawriter role should be applied on system database msdb


 

Solution

Please adjust account's security rights and roles on msdb according to the updated system requirements.
Alternatively you may install private fix with following workflow:

1. After failing to logon as a batch job, the job will immediately retry using interactive logon (pre-U3a way) before failing completely.

2. Warning about backupset update failure was changed to info event which additionally explains the issue in better details:
Transaction logs backup will not be possible due to insufficient permissions to update backupset for SQL instance: %SQLInstance%


Here is instruction how to install private fix:

1. Stop Veeam jobs and Veeam services;

2. Take a backup of the following backup files on Veeam B&R server and VSS proxies:
  • C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Core.dll
  • C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.VssProvider.dll
  • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\sql\VeeamLogShipper_X64.exe
  • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\sql\VeeamLogShipper_X86.exe
  • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2008R2_X64.dll
  • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X64.dll
  • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X86.dll
  • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupportXP_X86.dll
3. Replace the file with one from the fix;

4. Start Veeam services.

Viewing all articles
Browse latest Browse all 4362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>