Push installation of Backup Exec Remote Agent fails with the error "Access Denied. Please edit the remote credentials and retry the validation."
Article ID: 100000625
Updated On:
Description
Error Message
ERROR: Exception: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Push installation of Backup Exec Remote Agent fails with the error "Access Denied. Please edit the remote credentials and retry the validation". SGMon log on the Media Server shows the error while connecting to the remote WMI, when run in the background while push installation is being attempted:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_SETUP: [03-02-10 10:20:11] [0000] 23:(03-02-10 10:20:11)->ERROR connecting to remote wmi: root\cimv2, server name, domain name\user name
_SETUP: [03-02-10 10:20:11] [0000] 23:(03-02-10 10:20:11)->ERROR: Win32: 5
_SETUP: [03-02-10 10:20:11] [0000] 23:(03-02-10 10:20:11)->ERROR: Exception: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementScope.Connect()
at Symantec.IFrameSDK.NetPush.WMIMethods.a(ManagementScope& A_0, String A_1, String A_2, String A_3, String A_4)
_SETUP: [03-02-10 10:20:11] [0000] 23:(03-02-10 10:20:11)->Cleaning up push install...
_SETUP: [03-02-10 10:20:11] [0000] 23:(03-02-10 10:20:11)->ERROR connecting to remote wmi: root\cimv2, server name, domain name\user name
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Resolution
The WMI (Windows Management Instrumentation) Diagnosis Utility can be used to find out errors related to WMI. To download WMI diagnosis utility click on the link below.
WMI Troubleshooting - Win32 apps | Microsoft Learn
WMIDiag.exe) is no longer supported, starting with Windows 8 and Windows Server 2012.Follow the steps below to run the utility on the remote server for which the Backup Exec Remote Agent Push install fails:
1. Log on to the remote server with the same account as Backup Exec Service Account
2. Copy the "WMIDiag.vbs" file to root of the C drive
3. Open Command prompt and execute the script from C:\>WMIDiag.vbs
Error occurs in a Windows XP Professional or above machine connected in WORKGROUP.
- Open My computer menu bar click Tools >> Folder Options
- In View tab under Advance Setting scroll to the very bottom and uncheck Use Simple File Sharing ( Recommended ) and click ok .
- Make sure the user account has sufficient Administrator privilege.
- Now add the remote system and under domain enter WORKGROUP name.
- Install the remote agent.
Solution 3:
Make sure Distributed COM is enabled on the media server and any remote computers experiencing this issue:
1. Launch the "Component Services" console by going to Start > Run. Type DCOMCNFG and then click OK
2. Under "Console Root", expand "Component Services" and then expand "Computers". Right click on "My Computer" and select Properties .
3. On the "Default Properties" tab, confirm that there is a check mark in the box next to Enable Distributed COM on this computer. If this is not selected already, put a check mark in the box and click "Apply"
4. On the "COM Security tab", under the "Access Permissions" section click on Edit Limits.
5. Add both the SYSTEM account and the administrator account that will be used to remotely manage the machine in BESR or SSR. Allow the accounts both Local Access and Remote Access.
6. On the "COM Security" tab, under the "Access Permissions" section click on Edit Default.
7. Add the SYSTEM account and administrator account from step 5. Allow the accounts both Local Access and Remote Access.
8. On the "COM Security" tab, under the "Launch and Activation Permissions" section add the SYSTEM account and administrator account from step 5 to both the Edit Limits and Edit Default fields. When adding the accounts in the "Launch Permissions" window, make sure that both the SYSTEM and administrator account have all permissions set to Allow
9. Click OK and exit out of the "Component Services" console.
Issue/Introduction
