Possible GPO errors and troubleshooting steps

  1. Remote directory creation failed
  2. Session state is broken / No valid session / PsSession failed
  3. Insufficient privilege
  4. Command not found
  5. GPO was not found
  6. Object reference not set to an instance of an object
  7. The system cannot open the specified device or file
  8. Error HRESULT E_FAIL has been returned from a call to a COM component
  9. The library, drive, or media pool is empty
  10. The specified directory service attribute or value does not exist
  11. The system cannot find the path specified
  12. The data is invalid
  13. Unknown errors
  1. Remote directory creation failed
  2. This error occurs when RecoveryManager Plus cannot access the ADMIN$ share of the configured DC.

    • Make sure that the account used to configure the DC in RecoveryManager Plus has enough permissions to access the ADMIN$ share of the configured DC.
  3. Session state is broken / No valid session / PsSession failed
  4. To fix this issue, reboot RecoveryManager Plus.

  5. Insufficient privilege
  6. This error occurs when the account used to configure RecoveryManager Plus does not have sufficient privileges.

    To fix this issue, perform the following steps in the configured DC.

    • Click Start menu and search for PowerShell.
    • Right-click PowerShell icon and select Run as Administrator.
    • Type Enable-PsRemoting -Force and press Enter.

    Check if the machine in which RecoveryManager Plus is installed and the configured DC are in the same domain network. If not, add the DC to the trusted hosts list of the machine. Perform the following steps in the machine in which RecoveryManager Plus is installed.

    • Click Start menu and search for PowerShell.
    • Right-click PowerShell icon and select Run as Administrator.
    • Type the following command
    • winrm s winrm/config/client '@{TrustedHosts="<dc1-name>,<dc2-name>"}'

  7. Command not found
  8. This issue occurs when the group policy module is not present in the DC. 

    Note: If you are using a Window Server 2008 DC, contact RecoveryManager Plus support to resolve your issue. For all other versions of DCs, follow the steps listed below. 

    Check if group policy module is installed in the DC. If not, install it by following the steps listed below.

    • Log in to the DC and launch Server Manager.
    • In Server Manager, select Features in the left pane and then click Add Features in the Features pane. This starts the Add Features Wizard.
    • On the Select Features page, select Group Policy Management, click Next and then click Install.
  9. GPO was not found
  10. This issue occurs when the GPO that is to be backed up is not  found in the environment. This might be due to orphaned GPOs being present in the environment.

    • Log in to the DC and open GPMC. Check if the particular GPO is available and try again.
  11. Object reference not set to an instance of an object
  12. This behavior occurs if a user or a group name that is referenced in a Group Policy Object corresponds to an abbreviation that is defined for a built-in group that is used by the Security Descriptor Definition Language (SDDL) format. For example, this behavior occurs if you name a user or a group "SA." The "SA" abbreviation corresponds to the SDDL security identifier (SID) string that represents the built-in Schema Admins group.

    If a user name or a group name matches an SDDL abbreviation that is defined for a built-in group, a function that is called by the Group Policy Management Console treats the user name or the group name as a SID. Therefore, the backup fails.

    To fix this issue, 

    • Use the Active Directory Users and Computers snap-in to change the name of the user or the group that corresponds to one of the abbreviations that is used by SDDL. For more information on this issue and for a list of well-known SIDs that are defined in DSSL, click here.
  13. The system cannot open the specified device or file
  14. This error occurs when the account used to configure RecoveryManager Plus does not have privileges to access the GPO containers.

    • Make sure that the account has sufficient privileges to access the GPO containers.
  15. Error HRESULT E_FAIL has been returned from a call to a COM component
  16. This error occurs when the specific GPO is corrupted or when it cannot be copied or imported to GPMC.

    Contact Microsoft support or delete and recreate the GPO.

  17. The library, drive, or media pool is empty
  18. This error occurs when a Folder Redirection Policy is set for a GPO. This issue occurs due to an SID change in machines running Windows Server 2003 or higher.

    These issues occur because the Folder_Redirection section of the .ini files is larger than 32,767 characters. However, the limit for the combined SID list for all folders is 32,767 characters. For more information on this issue, click here.

    To solve this issue,

    • Split the policy into smaller policies. Make sure that the total size of each policy file is smaller than the 32,767 character limit.
  19. The specified directory service attribute or value does not exist
  20. This error occurs when the account used to configure RecoveryManager Plus does not have enough privilege to read AD Users and Computer containers.

    • Make sure that the account used to configure RecoveryManager Plus has at least “read” right on AD Users and Computer containers.
  21. The system cannot find the path specified.
  22. This issue occurs when the GPO container is not present in the SYSVOL folder.

    To fix this issue, try either of the following steps.

    • If you have multiple DCs in your domain, you can restore the GPO container from another DC.
    • Re-build the missing GPO Policy folder structure.
  23. The data is invalid.
  24. %ALLUSERSPROFILE%\Application Data\Microsoft\Group Policy\History contains a copy of the preferences contained in GPOs. If the copy process failed, an invalid XML file may be left in one of the subdirectories, thus creating the error. 

    To fix this issue, create a clean copy of the GPO by following the steps listed below. 

    • Log in to the DC and open file explorer.
    • Navigate to %ALLUSERSPROFILE%\Application Data\Microsoft\Group Policy\History.
    • Delete all subdirectories.
    • Open command prompt and execute the command “gpupdate”.
    • Verify that subdirectories appear under %ALLUSERSPROFILE%\Application Data\Microsoft\Group Policy\History.
  25. Unknown errors.
  26. Contact support@recoverymanagerplus.com to resolve this issue.

Get download link