dbc_RemoteWriteFile: ERR – could not write progress status message to the NAME socket

In continuation with my old post where I troubleshoot the Symantec NetBackup Error (31073), today faced similar error on another server where UAC was enabled earlier but disabled later.

On investigation found Error (31073) again but this time even after implementing all solutions from my last post link, faced a new error as below,
Error:
In GUI console,

ERR – Error in CreateEx: 0x80070005.
CONTINUATION: – Unknown VDI error code
In dbclient,

06:24:13.321 [1628.6700] <2> vnet_pbxConnect: pbxConnectEx Succeeded
06:24:13.321 [1628.6700] <2> logconnections: BPRD CONNECT FROM 162.53.54.114.63473 TO 10.62.208.4.1556 fd = 888
06:24:13.839 [1628.6700] <16> writeToServer: ERR – send() to server on socket failed:
06:24:13.839 [1628.6700] <16> dbc_RemoteWriteFile: ERR – could not write progress status message to the NAME socket
06:24:13.839 [1628.6700] <4> Dbbackrec::Perform: INF – OPERATION #1 of batch c:\lclbin\tsv\bin\log_trans_trunc_pr309.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 5(5) seconds.

Troubleshooting Steps:

1. As UAC was enabled previously, which now disabled, hence tried to give permissions wherever possible like folder where backup scripts are present, to registry, to Veritas folder under Program Files, etc.

2. Removed “Run as Administrator” checkbox from dbbackup.exe and dbbackex.exe as below,

3. Still error was there, tried running batch with right click > Run as admin privileges and backup were successful, it means I still missing something which restricted normal privileges to write on socket

4. Went to group policy editor at Run>gpedit.msc> at,

5. Analyzed following policies,

6. Found issues with following two policies,

1. User Account Control: Use Admin Approval Mode for the built-in Administrator account

This policy setting controls the behavior of Admin Approval Mode for the built-in Administrator account.

The options are:

• Enabled: The built-in Administrator account uses Admin Approval Mode. By default, any operation that requires elevation of privilege will prompt the user to approve the operation.

• Disabled: (Default) The built-in Administrator account runs all applications with full administrative privilege.

Current Settings:

 

2. User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode

This policy setting controls the behavior of the elevation prompt for administrators.

The options are:

• Elevate without prompting: Allows privileged accounts to perform an operation that requires elevation without requiring consent or credentials. Note: Use this option only in the most constrained environments.

• Prompt for credentials on the secure desktop: When an operation requires elevation of privilege, the user is prompted on the secure desktop to enter a privileged user name and password. If the user enters valid credentials, the operation continues with the user’s highest available privilege.

• Prompt for consent on the secure desktop: When an operation requires elevation of privilege, the user is prompted on the secure desktop to select either Permit or Deny. If the user selects Permit, the operation continues with the user’s highest available privilege.

• Prompt for credentials: When an operation requires elevation of privilege, the user is prompted to enter an administrative user name and password. If the user enters valid credentials, the operation continues with the applicable privilege.

• Prompt for consent: When an operation requires elevation of privilege, the user is prompted to select either Permit or Deny. If the user selects Permit, the operation continues with the user’s highest available privilege.

• Prompt for consent for non-Windows binaries: (Default) When an operation for a non-Microsoft application requires elevation of privilege, the user is prompted on the secure desktop to select either Permit or Deny. If the user selects Permit, the operation continues with the user’s highest available privilege.

Current Settings:

After changing these policies, issue was found fixed.

 

Useful references:

http://blogs.lostincreativity.com/sqldba/symantec-veritas-netbackup-issue-error-31073/

http://tcc.technion.ac.il/backup/VNBCodes.html –
Veritas Status Codes and Messages