none
Get-Help not work

    Question

  • Hi All,

    I installed new Win 2016 + Exch 2016 CU4 (DAG) and on both server I have problem with Get-Help for Exch cmdlets.

    Can you help me?

    [PS] C:\>Get-Help New-Mailbox
    Get-Help : Exception calling "Open" with "0" argument(s): "The following error occurred while loading the extended type data file: Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_P
    hysicalMemoryArray": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_PhysicalMemoryArray": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LogicalMemoryConfiguration": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LogicalMemoryConfiguration": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\WIN32_CACHEMEMORY": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\WIN32_CACHEMEMORY": The member PSConfiguration is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\WIN32_CACHEMEMORY": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\WIN32_CACHEMEMORY": The member ERROR is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LogonSession": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LogonSession": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LogicalDisk": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LogicalDisk": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LoadOrderGroup": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_LoadOrderGroup": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_ScheduledJob": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_ScheduledJob": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_IRQResource": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_IRQResource": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_IDEController": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_IDEController": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_Group": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_Group": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_Directory": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_Directory": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_Environment": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_Environment": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_DMAChannel": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_DMAChannel": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_DiskQuota": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_DiskQuota": The member PSStatus is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_DiskDrive": The member DefaultDisplayPropertySet is already present.
    Error in TypeData "System.Management.ManagementObject#root\cimv2\Win32_DiskDrive": The member PSConfiguration is already present.


    Friday, December 16, 2016 3:45 PM

Answers

  • Error doesn't happen if you start normal Powershell - and then "add-pssnapin -name Microsoft.Exchange.Management.PowerShell.SnapIn.

    Just for information - I know that using the PSSnapin isn't really supported.


    fgc

    • Proposed as answer by Richard McDaniel Friday, August 11, 2017 8:08 PM
    • Marked as answer by Jan Řežab Thursday, August 24, 2017 10:17 AM
    Saturday, February 18, 2017 9:55 AM

All replies

  • Hi,

    I post here to let you know that we are working on this issue.

    If you connect exchange via Window PowerShell, will this issue occur? Is your Window Server 2016 is RTM version?

    https://technet.microsoft.com/en-us/library/dd335083(v=exchg.160).aspx


    Best Regards,

    Lynn-Li
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 19, 2016 2:27 AM
    Moderator
  • Hi,

    Yes, if I'm connected remotely get-help don't work to.

    Windows version:

    [PS] C:\>[System.Environment]::OSVersion.Version
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    10     0      14393  0
    
    
    [PS] C:\>


    [srv01.xxx.lcl]: PS>get-help get-mailbox
    
    
    writeErrorStream              : True
    Exception                     : System.Management.Automation.RemoteException: Exception calling "Open" with "0" argumen
                                    t(s): "The following error occurred while loading the extended type data file: Error in
                                     TypeData "Microsoft.Management.Infrastructure.CimInstance#root/cimv2/Win32_PortResourc
                                    e": The member DefaultDisplayPropertySet is already present.
                                    Error in TypeData "Microsoft.Management.Infrastructure.CimInstance#root/cimv2/Win32_Por
                                    tResource": The member PSStatus is already present.
                                    Error in TypeData "Microsoft.Management.Infrastructure.CimInstance#root/cimv2/Win32_Dis
                                    kPartition": The member DefaultDisplayPropertySet is already present.
                                    Error in TypeData "Microsoft.Management.Infrastructure.CimInstance#root/cimv2/Win32_Dis
                                    kPartition": The member PSStatus is already present.
    ......................
    
    ......................
                                    Error in TypeData "Microsoft.Exchange.Migration.MigrationBatch": The member Serializati
                                    onDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Mapi.MailboxStatistics": The member Serializ
                                    ationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.SystemConfiguration.ConfigurationS
                                    ettings.ExchangeSettings": The member SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Storage.Management.MigrationStatus": The mem
                                    ber SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Storage.Management.MigrationBatch": The memb
                                    er SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Storage.Management.MigrationUser": The membe
                                    r SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.MailboxReplicationService.ReportEntry": The membe
                                    r SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.MailboxReplicationService.RequestStatisticsBase":
                                     The member SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Common.LocalizedString": The member Property
                                    SerializationSet is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Common.LocalizedString": The member Serializ
                                    ationMethod is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.GroupMailboxMembersSync
                                    Status": The member SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.SyncConfig": The member
                                     SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.SyncDynamicDistribution
                                    Group": The member SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.SyncDistributionGroup":
                                     The member SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.SyncMailContact": The m
                                    ember SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.SyncMailUser": The memb
                                    er SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Management.StoreTasks.MailboxFolderUserId": The m
                                    ember SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.PublicFolderInformation": The member Seriali
                                    zationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Storage.Management.PublicFolderMailboxMonito
                                    ringInfo": The member SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.SyncMailbox": The membe
                                    r SerializationDepth is already present.
                                    Error in TypeData "Microsoft.Exchange.Management.ValidateConnectors.ValidationTaskResul
                                    t": The member SerializationDepth is already present.
                                    Error in TypeData "Deserialized.Microsoft.Exchange.Management.SystemConfigurationTasks.
                                    ExchangeCertificate": The member TargetTypeForDeserialization is already present.
                                    Error in TypeData "Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeCerti
                                    ficate": The TypeConverter was ignored because it already occurs.
                                    Error in TypeData "Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeCerti
                                    ficate": The member PropertySerializationSet is already present.
                                    Error in TypeData "Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeCerti
                                    ficate": The member SerializationMethod is already present.
                                    Error in TypeData "Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeCerti
                                    ficate": The member SerializationData is already present.
                                    Error in TypeData "Microsoft.Exchange.Management.ClassificationDefinitions.Fingerprint"
                                    : The TypeConverter was ignored because it already occurs.
                                    Error in TypeData "Microsoft.Exchange.Management.ClassificationDefinitions.Fingerprint"
                                    : The member SerializationData is already present.
                                    Error in TypeData "Deserialized.Microsoft.Exchange.Management.ClassificationDefinitions
                                    .Fingerprint": The member TargetTypeForDeserialization is already present.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.RunspaceServerSettingsP
                                    resentationObject": The TypeConverter was ignored because it already occurs.
                                    Error in TypeData "Microsoft.Exchange.Data.Directory.Management.RunspaceServerSettingsP
                                    resentationObject": The member SerializationData is already present.
                                    Error in TypeData "Deserialized.Microsoft.Exchange.Data.Directory.Management.RunspaceSe
                                    rverSettingsPresentationObject": The member TargetTypeForDeserialization is already pre
                                    sent.
                                    "
                                       v System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
                                       v System.Management.Automation.PowerShell.CoreInvokeRemoteHelper[TInput,TOutput](PSD
                                    ataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
                                       v System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollectio
                                    n`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
                                       v System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSett
                                    ings settings)
                                       v System.Management.Automation.RemotePipeline.Invoke(IEnumerable input)
                                       v Microsoft.PowerShell.Executor.ExecuteCommandHelper(Pipeline tempPipeline, Exceptio
                                    n& exceptionThrown, ExecutionOptions options)
    TargetObject                  :
    FullyQualifiedErrorId         : RuntimeException
    InvocationInfo                :
    ErrorCategory_Category        : 0
    ErrorCategory_Activity        :
    ErrorCategory_Reason          : MethodInvocationException
    ErrorCategory_TargetName      :
    ErrorCategory_TargetType      :
    ErrorCategory_Message         : NotSpecified: (:) [], MethodInvocationException
    SerializeExtendedInfo         : False
    ErrorDetails_ScriptStackTrace : at <ScriptBlock><Begin>, <No file>: line 60
    
    
    [srv01.xxx.lcl]: PS>



    • Edited by Jan Řežab Monday, December 19, 2016 8:56 AM
    Monday, December 19, 2016 8:53 AM
  • Hi,

    I built Exchange Server 2016 on Window Server 2016 yesterday and reproduced this issue on this new server.

    So I contact Exchange product Team, they said that they are investigating on this issue. And welcome to Exchange Team Blog, generally they will have an update on blog when new products/features are released or some problems are fixed.


    Best Regards,

    Lynn-Li
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, December 20, 2016 9:01 AM
    Moderator
  • I also am experiencing this issue.

    Server 2016 + Exch 2016 CU 4

    Tuesday, December 20, 2016 7:17 PM
  • Hi,

    Thanks for info.


    Tuesday, December 20, 2016 8:11 PM
  • Same issue here w/ fresh install of Ex2016 CU4 on Server 2016. 
    Friday, December 23, 2016 7:30 PM
  • Same issue here.
    Friday, January 27, 2017 8:37 AM
  • Same issue here, fresh install 2016 on 2016 with CU4
    Sunday, January 29, 2017 5:20 PM
  • Same issue here. Ran the latest Windows Updates yesterday. Rebooted and hit the following:

    "[PS] C:\Windows\system32>get-help new-mailbox
    get-help : Exception calling "Open" with "0" argument(s): "The following error occurred while loading the extended
    type data file: Error in TypeData "System.Management.Automation.PSModuleInfo": The member DefaultDisplayPropertySet is
    already present.
    Error in TypeData "System.Collections.DictionaryEntry": The member Name is already present.
    Error in TypeData "System.Diagnostics.ProcessModule": The member Product is already present.
    Error in TypeData "System.Diagnostics.ProcessModule": The member Description is already present.
    Error in TypeData "System.Diagnostics.ProcessModule": The member ProductVersion is already present.
    Error in TypeData "System.Diagnostics.ProcessModule": The member FileVersion is already present.
    Error in TypeData "System.Diagnostics.ProcessModule": The member Company is already present.
    Error in TypeData "System.Diagnostics.ProcessModule": The member Size is already present.
    Error in TypeData "Deserialized.System.Net.IPAddress": The member TargetTypeForDeserialization is already present.
    Error in TypeData "System.Net.IPAddress": The member SerializationDepth is already present.
    Error in TypeData "System.Net.IPAddress": The member DefaultDisplayProperty is already present.
    Error in TypeData "System.Net.IPAddress": The member IPAddressToString is already present.
    Error in TypeData "System.DateTime": The member DateTime is already present.
    Error in TypeData "System.Management.Automation.ApplicationInfo": The member FileVersionInfo is already present.
    Error in TypeData "System.Drawing.Printing.PrintDocument": The member Duplex is already present.
    Error in TypeData "System.Drawing.Printing.PrintDocument": The member Color is already present.
    Error in TypeData "System.Drawing.Printing.PrintDocument": The member Name is already present.

    ........."

    Wednesday, February 01, 2017 1:59 AM
  • Same error happes to me with Win2016+Exchange2016+CU4+ all latest windows+microsoft updates

    Please note: this issue

    • only occurs when using exchange command shell
    • does NOT occur with standard powershell shell

    Both powershell sessions are started locally at the exchange server machine (not from a remote server)

    Thursday, February 09, 2017 12:52 PM
  • Error doesn't happen if you start normal Powershell - and then "add-pssnapin -name Microsoft.Exchange.Management.PowerShell.SnapIn.

    Just for information - I know that using the PSSnapin isn't really supported.


    fgc

    • Proposed as answer by Richard McDaniel Friday, August 11, 2017 8:08 PM
    • Marked as answer by Jan Řežab Thursday, August 24, 2017 10:17 AM
    Saturday, February 18, 2017 9:55 AM
  • I also have the same problem...

    Monday, March 13, 2017 2:28 PM
  • Hi!

    CU 5 was installed, the problem remained

    Monday, March 27, 2017 11:38 AM
  • Correct. Just tested that and the problem still exists.

    Cheers

    Monday, March 27, 2017 2:20 PM
  • Error doesn't happen if you start normal Powershell - and then "add-pssnapin -name Microsoft.Exchange.Management.PowerShell.SnapIn.

    Just for information - I know that using the PSSnapin isn't really supported.


    fgc

    Agreed, but if I use remote Powershell (New-PSSession to http://<SERVER>/powershell/) the problem is the same.

    Haven't tried a real remote PowerShell Session and then load the Snapin.

    Cheers

    Monday, March 27, 2017 2:22 PM
  • I am experiencing the same issue. Have to use Google instead of get-help for my answers.
    Friday, May 19, 2017 1:51 PM
  • Noticed this issue doesn't exist on an Ex2016 EDGE serveron Server 2016. The 'Exchange Management Shell' shortcut Target on the EDGE server is different than the one on the Mailbox server. The EDGE command works on the Mailbox server and eliminates the problem with Get-Help.

    Mailbox:

    C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command ". 'C:\Program Files\Microsoft\Exchange Server\V15\bin\RemoteExchange.ps1'; Connect-ExchangeServer -auto -ClientApplication:ManagementShell "

    EDGE:

    C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files\Microsoft\Exchange Server\V15\bin\exshell.psc1" -noexit -command ". 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Exchange.ps1'"

    NOTE: We have only on-premise Exchange. There may be a loss of functionality for a Hybrid install.



    • Edited by MirthMage Tuesday, May 23, 2017 8:02 PM Formatting
    • Proposed as answer by Richard McDaniel Friday, August 11, 2017 8:08 PM
    Tuesday, May 23, 2017 8:01 PM
  • Same issue. Fully patched on-premises Exchange 2016 on Server 2016 Standard.

    As FGC stated, this does work when used with add-pssnapin, but that's only a workaround. After 6 months there should be a fix.

    Friday, June 02, 2017 8:05 PM
  • Same Issue with Server 2016 and Exchange 2016 CU5 (Clean Install)

    On Server 2012 R2 and Exchange 2016 CU4 and CU5 the help works fine

    MT

    Wednesday, June 28, 2017 2:53 PM
  • More than 6 months later, two CUs later this problem still exists (Exchange 2016 CU6(!) on Server 2016.

    WTF? Is there anyone looking into this?

    Peter

    Wednesday, July 12, 2017 1:16 PM
  • Any updates about this issue?


    -=C U=-

    Monday, July 17, 2017 7:07 AM
  • Howdy,

    I can confirm that this problem still exists with a clean install of Exchange Server 2016 CU6 on Windows Server 2016.

    Pretty poor that the Exchange Server dev team can't even document this as a known reproducible problem.

    Sunday, July 23, 2017 5:32 AM
  • This thread documents three things:

    -Microsoft doesn't care about technet forum threads unless they have a serious number of upvotes (this one has "2" after all these months... I will add a third one now)

    -people don't understand that upvoting matters

    -Microsoft's own mail admins either don't use exchange 2016 or they are so omnipotent that they don't use get-help at all ;-)

    ->Please acknowledge the workaround that has been shared: open powershell and run

    add-pssnapin -name Microsoft.Exchange.Management.PowerShell.SnapIn
    There, you can use get-help.


    Friday, July 28, 2017 1:13 PM
  • Oh bouy! There is still no solution for this problem? I am experiencing the same issues.
    Saturday, August 05, 2017 6:50 PM
  • I am experiencing the same issue,
    Saturday, August 05, 2017 6:52 PM
  •  Ex16 CU6 - still same issue on Windows 2016 Server


    Bueschu

    Thursday, August 10, 2017 6:05 AM
  • Hi,

    I built Exchange Server 2016 on Window Server 2016 yesterday and reproduced this issue on this new server.

    So I contact Exchange product Team, they said that they are investigating on this issue. And welcome to Exchange Team Blog, generally they will have an update on blog when new products/features are released or some problems are fixed.

    No offense, but why is this marked as the answer when it doesn't provide a fix for the problem in either the text or the linked content?  As of 8/11/2017 the latest update for Exchange Server 2016 (CU6) still has not addressed this problem.  If there is a workaround posted on the Exchange Team Blog I haven't found it.  Perhaps a permalink to the blog article would be more helpful than a generic link to the blog, if indeed a blog article has addressed this issue.
    Friday, August 11, 2017 8:17 PM
  • MS as a Managed Service Provider could you please address this. You deploy a new Exchange environment for a customer they then believe we have not implemented the solution correctly. Running CU6 and noted in all Exchange 2016 instances for the 4 Environments I manage.
    • Proposed as answer by MasterJames Friday, August 25, 2017 4:11 PM
    Wednesday, August 16, 2017 12:04 PM
  • Still Broken :-(

    Exchange Team....we need this fixed please. Where do I vote?

    Friday, August 25, 2017 4:10 PM
  • Same as eight months ago, Exchange 2016 on Windows 2016 Server.
    Tuesday, August 29, 2017 7:42 PM
  • any update?  Still a problem?
    Wednesday, September 06, 2017 4:43 PM
  • Happening here, also.

    Fresh install of Exchange Server 2016, latest CU as of today, under Windows Server 2016.

    Cheers!

    Thursday, September 07, 2017 1:53 PM
  • It may work for some, but it does not work for me on two different installs of CU6. Use Google, Ii guess, as another writer suggested...
    Sunday, October 08, 2017 3:01 PM
  • Just astonishing.  2 CUs and over 8 months with this basic problem on the books.  Doesn't anybody there keep a bug list, and don't they have somebody scanning these forums for issues to add to it?  I'm getting really tired of debugging vendors' software for them...
    Tuesday, October 10, 2017 6:13 PM
  • CU 7 and the problem is still not solved.
    Saturday, November 04, 2017 4:34 PM
  • This issue still exists (Issue: Get-Help errors out when Exchange Server 2016 in installed on Windows Server 2016). What I have been informed: The fix is on the Windows side and that the Windows Team has been notified. No estimated time of resolution.

    Craig - MSFT PFE

    Wednesday, December 06, 2017 8:46 PM