NetBackup ERR – Error in VxBSADeterminePolicy: 26 and ERR – Error in CryptAcquireContext : 2148073508

Kind of unique issue faced today, SQL Server backup job was continuously failing (with ERROR(-1) and exit status 2) to take database backups on Symantec NetBackup Utility. In GUI console following error was logged in,

 

USER – Verify that an active SQL Server policy exists for this client.

ERR – Error in VxBSADeterminePolicy: 26.

CONTINUATION: – There is no copy of the requested object.

 

This is not first time we were running backup, it started failing suddenly one day; with same error we verified on NetBackup end and there too policy was defined, hence to troubleshoot further we enabled dbclient logs by creating dbclient folder at c:\Program Files\Veritas\NetBackup\logs\ location

 

When job ran again then it logged following error message,

11:40:24.492 [4732.7996] <4> getServerName: Read server name from nb_master_config: nbxxxx01

11:40:24.492 [4732.7996] <4> CDBIniParms::CDBIniParms: INF – NT User is useradmin

11:40:24.501 [4732.7996] <16> DB_CryptAcquireContext: ERR – Error in CryptAcquireContext : 2148073508.

11:40:24.507 [4732.7996] <1> DB_CryptAcquireContext: CONTINUATION: – The profile for the user is a temporary profile.

11:40:24.509 [4732.7996] <16> DB_CryptAcquireContext: ERR – Error in CryptAcquireContext : 2148073508.

11:40:24.509 [4732.7996] <1> DB_CryptAcquireContext: CONTINUATION: – The profile for the user is a temporary profile.

11:40:24.509 [4732.7996] <8> CSQLDBMSOptions::CSQLDBMSOptions: WARN – Error encountered looking up your default SQL userid and password from file.

11:40:26.855 [4732.7996] <4> SQLEnumerator: INF – Enumerated SQL hosts: S

 

So from this point, it seemed that the account under which job is running is not able to create its user profile properly and when we checked the user profile folders, we found the issue as if anyone newly logs in to server then it creates TEMP profile instead of actual profile of user (for e.g. useradmin),

 

 

So we understood that the account is unable to load SQL Server policy due to this sudden change is profile creation method, so we checked the backup script and found that policy was not defined in script, hence we added the policy name in script and after same the backups started running fine.

 

OPERATION BACKUP

DATABASE $ALL

SQLHOST “SQLServerName”

SQLINSTANCE “SQLInstanceName”

NBSERVER “MASTER”

MAXTRANSFERSIZE 6

BLOCKSIZE 7

POLICY SQLBackupPolicyNAme

NUMBUFS 2

ENDOPER TRUE

 

 

Although the change of user profile creation method is still not understood but backup issue is fixed by adding policy details in script itself. Hope it helps!

 

Other Useful references which I read to fix similar type of issues

http://www.symantec.com/business/support/index?page=content&id=TECH48716 – ERROR (-1)–ERR – Error in VxBSADeterminePolicy: 26 –There is no copy of requested object

http://www.symantec.com/connect/forums/none-requested-files-were-backed-ms-sql – ERR – Error in VxBSADeterminePolicy: 26.

http://www.symantec.com/business/support/index?page=content&id=TECH33205 – Error starting a process

http://www.symantec.com/business/support/index?page=content&id=TECH24492 – Exit Status Code 2 – You provided an illegal keyword

http://www.symantec.com/business/support/index?page=content&id=TECH154335 – ERR – Error in CryptAcquireContext –Keyset does not Exist

http://www.symantec.com/business/support/index?page=content&id=TECH90862 – ERR – Error in CryptAcquireContext –Object Already Exists