BostonTechGuy
Enthusiast
Enthusiast

Error Message when starting PowerCLI 5.5

Jump to solution

Afternoon,

On a new project with a company that is using ESXi 5.5.  So I have installed Powershell 3.0 and PowerCLI 5.5 onto my laptop.  I am getting series of errors when PowerCLI 5.5 launches.  I dont recongize the error and searching has not come up with answers to remove them.  I am hoping this is a simple fix that I am just missing.

Everything listed below loads in RED before I get the usual PowerCLI prompt.

ERRORS:

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 48

                        at <ScriptBlock>, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 60

                        at <ScriptBlock>, <No file>: line 1

PipelineIterationInfo : {0, 1}

PSMessageDetails      :

writeErrorStream      : True

Exception             : System.Management.Automation.Runspaces.PSSnapInExceptio

                        n: Windows PowerShell Snap-In

                        "VMware.DeployAutomation" is loaded with the following

                        warnings: There were errors in loading the format data

                        file:

                        VMware.VimAutomation.Vds, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml cannot

                        be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

                        VMware.DeployAutomation, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml cannot

                        be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

TargetObject          : VMware.DeployAutomation

CategoryInfo          : InvalidData: (VMware.DeployAutomation:String)

                        [Add-PSSnapin], PSSnapInException

FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnap

                        inCommand

ErrorDetails          :

InvocationInfo        : System.Management.Automation.InvocationInfo

ScriptStackTrace      : at LoadSnapins, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 48

                        at <ScriptBlock>, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 60

                        at <ScriptBlock>, <No file>: line 1

PipelineIterationInfo : {0, 1}

PSMessageDetails      :

writeErrorStream      : True

Exception             : System.Management.Automation.PSSecurityException: File

                        C:\Program Files (x86)\VMware\Infrastructure\vSphere Po

                        werCLI\Scripts\Initialize-VMware_DeployAutomation.ps1

                        cannot be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts\In

                        itialize-VMware_DeployAutomation.ps1 is not digitally

                        signed. The script will not execute on the system. For

                        more information, see about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170. --->

                        System.UnauthorizedAccessException: File C:\Program

                        Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Scri

                        pts\Initialize-VMware_DeployAutomation.ps1 cannot be

                        loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts\In

                        itialize-VMware_DeployAutomation.ps1 is not digitally

                        signed. The script will not execute on the system. For

                        more information, see about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170.

                           --- End of inner exception stack trace ---

                           at System.Management.Automation.AuthorizationManager

                        .ShouldRunInternal(CommandInfo commandInfo,

                        CommandOrigin origin, PSHost host)

                           at System.Management.Automation.CommandDiscovery.Sho

                        uldRun(ExecutionContext context, PSHost host,

                        CommandInfo commandInfo, CommandOrigin commandOrigin)

                           at System.Management.Automation.CommandDiscovery.Loo

                        kupCommandProcessor(CommandInfo commandInfo,

                        CommandOrigin commandOrigin, Nullable`1 useLocalScope,

                        SessionStateInternal sessionState)

                           at System.Management.Automation.CommandDiscovery.Loo

                        kupCommandProcessor(String commandName, CommandOrigin

                        commandOrigin, Nullable`1 useLocalScope)

                           at System.Management.Automation.ExecutionContext.Cre

                        ateCommand(String command, Boolean dotSource)

                           at System.Management.Automation.PipelineOps.AddComma

                        nd(PipelineProcessor pipe, CommandParameterInternal[]

                        commandElements, CommandBaseAst commandBaseAst,

                        CommandRedirection[] redirections, ExecutionContext

                        context)

                           at System.Management.Automation.PipelineOps.InvokePi

                        peline(Object input, Boolean ignoreInput,

                        CommandParameterInternal[][] pipeElements,

                        CommandBaseAst[] pipeElementAsts,

                        CommandRedirection[][] commandRedirections,

                        FunctionContext funcContext)

                           at System.Management.Automation.Interpreter.ActionCa

                        llInstruction`6.Run(InterpretedFrame frame)

                           at System.Management.Automation.Interpreter.EnterTry

                        CatchFinallyInstruction.Run(InterpretedFrame frame)

TargetObject          :

CategoryInfo          : SecurityError: (:) [], PSSecurityException

FullyQualifiedErrorId : UnauthorizedAccess

ErrorDetails          : File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts\In

                        itialize-VMware_DeployAutomation.ps1 cannot be loaded.

                        The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts\In

                        itialize-VMware_DeployAutomation.ps1 is not digitally

                        signed. The script will not execute on the system. For

                        more information, see about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170.

InvocationInfo        : System.Management.Automation.InvocationInfo

ScriptStackTrace      : at LoadSnapins, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 56

                        at <ScriptBlock>, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 60

                        at <ScriptBlock>, <No file>: line 1

PipelineIterationInfo : {}

PSMessageDetails      :

writeErrorStream      : True

Exception             : System.Management.Automation.Runspaces.PSSnapInExceptio

                        n: Windows PowerShell Snap-In "VMware.ImageBuilder" is

                        loaded with the following warnings: There were errors

                        in loading the format data file:

                        VMware.VimAutomation.Vds, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml cannot

                        be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

                        VMware.DeployAutomation, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml cannot

                        be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

                        VMware.ImageBuilder, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.ImageBuilder.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.ImageBuilder.Format.ps1xml cannot be

                        loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.ImageBuilder.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

TargetObject          : VMware.ImageBuilder

CategoryInfo          : InvalidData: (VMware.ImageBuilder:String)

                        [Add-PSSnapin], PSSnapInException

FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnap

                        inCommand

ErrorDetails          :

InvocationInfo        : System.Management.Automation.InvocationInfo

ScriptStackTrace      : at LoadSnapins, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 48

                        at <ScriptBlock>, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 60

                        at <ScriptBlock>, <No file>: line 1

PipelineIterationInfo : {0, 1}

PSMessageDetails      :

writeErrorStream      : True

Exception             : System.Management.Automation.Runspaces.PSSnapInExceptio

                        n: Windows PowerShell Snap-In

                        "VMware.VimAutomation.Cloud" is loaded with the

                        following warnings: There were errors in loading the

                        format data file:

                        VMware.VimAutomation.Vds, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml cannot

                        be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Vds.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

                        VMware.DeployAutomation, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml cannot

                        be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.DeployAutomation.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

                        VMware.ImageBuilder, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.ImageBuilder.Format.ps1xml : File

                        skipped because of the following validation exception:

                        File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.ImageBuilder.Format.ps1xml cannot be

                        loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.ImageBuilder.Format.ps1xml is not

                        digitally signed. The script will not execute on the

                        system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

                        VMware.VimAutomation.Cloud, , C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Cloud.Format.ps1xml :

                        File skipped because of the following validation

                        exception: File C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Cloud.Format.ps1xml

                        cannot be loaded. The file C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\VMware.VimAutomation.Cloud.Format.ps1xml is

                        not digitally signed. The script will not execute on

                        the system. For more information, see

                        about_Execution_Policies at

                        http://go.microsoft.com/fwlink/?LinkID=135170..

TargetObject          : VMware.VimAutomation.Cloud

CategoryInfo          : InvalidData: (VMware.VimAutomation.Cloud:String)

                        [Add-PSSnapin], PSSnapInException

FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnap

                        inCommand

ErrorDetails          :

InvocationInfo        : System.Management.Automation.InvocationInfo

ScriptStackTrace      : at LoadSnapins, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 48

                        at <ScriptBlock>, C:\Program Files

                        (x86)\VMware\Infrastructure\vSphere

                        PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:

                        line 60

                        at <ScriptBlock>, <No file>: line 1

PipelineIterationInfo : {0, 1}

PSMessageDetails      :

          Welcome to the VMware vSphere PowerCLI!

Thanks,

Boston Tech Guy

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
BostonTechGuy
Enthusiast
Enthusiast

My mistake.  It was sitting right in front of me.  The Set-ExecutionPolicy was not changed on my laptop.  You forget about these set and forget changes when you move to a new machine.

View solution in original post

0 Kudos
1 Reply
BostonTechGuy
Enthusiast
Enthusiast

My mistake.  It was sitting right in front of me.  The Set-ExecutionPolicy was not changed on my laptop.  You forget about these set and forget changes when you move to a new machine.

View solution in original post

0 Kudos