Kaseya Community

Backup Exec Module

This question is not answered

We have been running the Backup Exec Module for some time without issue but now I have a server that the module will not collect the data anymore.

The server is running BE2012 SP1a

The procedures say they run but now data shows up in the job history.

Any Suggestion?

All Replies
  • Thanks for this suggestion, The BE command line opens just fine but now the error has changed:

    Could not load BEMCLI module.

    System.Management.Automation.PSSecurityException: AuthorizationManager check failed.

      at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)

      at Microsoft.PowerShell.Commands.ModuleCmdletBase.GetScriptInfoForFile(String fileName, String& scriptName)

      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModule(String fileName, String moduleBase, String prefix, SessionState ss, Boolean& found)

      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadUsingExtensions(String moduleName, String fileBaseName, String extension, String moduleBase, String prefix, SessionState ss, Boolean& found)

      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleNamedInManifest(String moduleName, String moduleBase, Boolean searchModulePath, String prefix, SessionState ss, Boolean loadTypesFiles, Boolean loadFormatFiles, Boolean& found)

      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(ExternalScriptInfo scriptInfo, ManifestProcessingFlags manifestProcessingFlags, Version version)

      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModule(String fileName, String moduleBase, String prefix, SessionState ss, Boolean& found)

      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadUsingExtensions(String moduleName, String fileBaseName, String extension, String moduleBase, String prefix, SessionState ss, Boolean& found)

      at Microsoft.PowerShell.Commands.ImportModuleCommand.ProcessRecord()

      at System.Management.Automation.CommandProcessor.ProcessRecord()

  • Hi,

    Looks like authorization (to run a powershell script) fails. It could also happen if PowerShell's execution policy is somehow set to "Restricted" on the BE 2012 machine. Try the following steps:

    1. Please run the the powershell cmdlet "Get-ExecutionPolicy" from the PowerShell's command-prompt. If the output reads as Undefined or Restricted, please run the the powershell cmdlet "Set-ExecutionPolicy AllSigned". Ensure it is correctly updated by running "Get-ExecutionPolicy" cmdlet once again. Now try running the BE's agent procedure from Kaseya console and also check for any errors in Kaseya console.

    2. If the issue still persists, could you PM the log file from the corresponding BE 2012 SP3 media server? Typically the default location of the log file would be "C:\Program Files (x86)\Kaseya\<some-ID>\BEMPKDataCollector\Logs".

    Regards,

    Ramesh Bupathy  |  Symantec



    Removed a step which is not required.
    [edited by: Ramesh Bupathy (Symantec) at 1:14 AM (GMT -8) on Jan 20, 2014]