After 2016 update VMM module not working

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 8 years and 1 month old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
  • Print view
    • User avatar
    Kristian Terkelsen
    Posts: 2
    Last visit: Thu Jan 11, 2024 2:13 am

    After 2016 update VMM module not working

    Post by Kristian Terkelsen »

    Product, version and build: PowerShell Studio 2016 5.2.116.0
    32 or 64 bit version of product: 64
    Operating system: Win10
    32 or 64 bit OS: 64

    After 2016 update and latest updates, Import-Module VirtualMachineManager is not working any more.

    >> Running (Get-Module.ps1) Script Selection...
    >> Platform: V2 64Bit (STA)
    ERROR: Import-Module : The 'C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin\psModules\VirtualMachineManager\VirtualMachineManager.psd1' m
    ERROR: odule cannot be imported because its manifest contains one or more members that are not valid. The valid manifest members are ('ModuleToProcess', 'NestedModule
    ERROR: s', 'GUID', 'Author', 'CompanyName', 'Copyright', 'ModuleVersion', 'Description', 'PowerShellVersion', 'PowerShellHostName', 'PowerShellHostVersion', 'CLRVersi
    ERROR: on', 'DotNetFrameworkVersion', 'ProcessorArchitecture', 'RequiredModules', 'TypesToProcess', 'FormatsToProcess', 'ScriptsToProcess', 'PrivateData', 'RequiredAs
    ERROR: semblies', 'ModuleList', 'FileList', 'FunctionsToExport', 'VariablesToExport', 'AliasesToExport', 'CmdletsToExport'). Remove the members that are not valid ('H
    ERROR: elpInfoURI'), then try to import the module again.
    ERROR:
    Get-Module.ps1 (3, 14): ERROR: At Line: 3 char: 14
    ERROR: + Import-Module <<<< VirtualMachineManager
    ERROR: + CategoryInfo : InvalidData: (C:\Program File...ineManager.psd1:String) [Import-Module], InvalidOperationException
    ERROR: + FullyQualifiedErrorId : Modules_InvalidManifestMember,Microsoft.PowerShell.Commands.ImportModuleCommand
    ERROR:

    >> Execution time: 00:00:01
    >> Script Ended

    When done in ISE it's working fine. Please advise :-)

    Regards,
    Kristian Terkelsen
    EG A/S
    Top
    User avatar
    davidc
    Posts: 5913
    Last visit: Mon Jul 08, 2019 8:55 am
    Been upvoted: 2 times

    Re: After 2016 update VMM module not working

    Post by davidc »

    According to the output you are trying to run the script in V2 mode. It seems the module is not backwards compatible with PowerShell V2.

    David
    David
    SAPIEN Technologies, Inc.
    Top
    User avatar
    Kristian Terkelsen
    Posts: 2
    Last visit: Thu Jan 11, 2024 2:13 am

    Re: After 2016 update VMM module not working

    Post by Kristian Terkelsen »

    Doh :lol: you are correct changed to v5 and it's works. Thx for you help :P

    /Kristian T.
    Top
    This topic is 8 years and 1 month old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
  • Print view

    • Return to “PowerShell Studio”