I’m pleased to announce the second beta release of Exchange Analyzer.

This release contains the following fixes and improvements:

  • Added new test AD001: Active Directory domain functional level
  • Added new test AD002: Active Directory forest functional level
  • Fixed error being thrown by Get-DatabaseAvailabilityGroup when an Exchange 2010 DAG was present
  • Fixed errors when script was run from a path with spaces in it
  • Added an intro and summary to report
  • Added a summary of Client Access URLs to assist with identifying causes of CAS test failures
  • Changed database backup timestamp comparisons to UTC for accuracy
  • Various minor fixes for typos and clarity
  • Changed “More Info” links to standardised Wiki-based documentation

Several of those improvements are thanks to Exchange admins in the community who took the time to run the tool in their environments, and sent us bug reports and other feedback. This has helped us to improve the framework that Exchange Analyzer is built upon, which will assist us with the further development of new tests and features for the next releases.

For more information see the Exchange Analyzer page. You can download the latest version from the TechNet Script Gallery. If you are updating from the previous beta please ensure you copy the updated module to your PowerShell modules folder.

Comments and feedback are welcome below. If you have a question please check the Exchange Analyzer FAQ first.

To receive news and updates about Exchange Analyzer by email subscribe to the Exchange Analyzer mailing list.

About the Author

Paul Cunningham

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com.

Comments

  1. Sanjay

    Hi paul,

    I am trying to run exchange analyzer tool but getting below errors.

    WARNING: An error has occurred during basic data collection.
    WARNING: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.

  2. Shane

    [PS] C:\Scripts\ExchangeAnalyzer>.\Run-ExchangeAnalyzer.ps1 -verbose
    VERBOSE: Collecting data about the Exchange organization
    VERBOSE: 2 Exchange servers found.
    VERBOSE: 5 databases found.
    VERBOSE: 0 DAGs found.
    WARNING: An error has occurred during basic data collection.
    WARNING: Directory object not found
    [PS] C:\Scripts\ExchangeAnalyzer>

    1. pro pro

      I get the same error

      1. Kyle

        Same for me, but cant find any more info or outputs on what the object is from the script either

        1. Brett

          i also get the same and sent an email to the dev.
          It appears to get up to get-addomaincontroller which when run manually produces data so i figure its something after this point in the script.

          Anyone have any idea’s (Error management is not very helpful)

    2. Brett

      i also get the same and sent an email to the dev.
      It appears to get up to get-addomaincontroller which when run manually produces data so i figure its something after this point in the script.

      Anyone have any idea’s (Error management is not very helpful)

  3. Asem Mahmoud

    i get below error when i try to run exchange analyzer script on my exchange server 2013

    ” WARNING: An error has occurred during basic data collection.
    WARNING: The term ‘Get-OrganizationConfig’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a
    path was included, verify that the path is correct and try again.

      1. Ken Gulick

        Oh, how did I miss that. Working now.

    1. Matt D

      I received the split error with out Exchange 2013 servers, now when I run the updated version I get another error, but not the split error

      Get-TestResultObject : A parameter cannot be found that matches parameter name ‘WarningList’.
      At C:tempExchangeAnalyzer-Fix-Issue-62TestsEXSRV001.ps1:46 char:39
      + -WarningList $WarningList `
      + ~~~~~~~~~~~~
      + CategoryInfo : InvalidArgument: (:) [Get-TestResultObject], ParameterBindingException
      + FullyQualifiedErrorId : NamedParameterNotFound,Get-TestResultObject

      Vector smash protection is enabled.
      Get-TestResultObject : A parameter cannot be found that matches parameter name ‘WarningList’.
      At C:tempExchangeAnalyzer-Fix-Issue-62TestsEXSRV002.ps1:144 char:39
      + -WarningList $WarningList `
      + ~~~~~~~~~~~~
      + CategoryInfo : InvalidArgument: (:) [Get-TestResultObject], ParameterBindingException
      + FullyQualifiedErrorId : NamedParameterNotFound,Get-TestResultObject

      1. Paul Cunningham

        Most likely cause is you did not update the ExchangeAnalyzer module before running the new script.

  4. Remko de Koning

    Hey Paul, just ran this script in our Environment as well. Showing the same error right after “Generating HTML Report”

    Running the Powershell command directly on the server from an elevated Exchange Powershell Shell.
    Running Exchange 2013 version 15 build 1104.5 on Server 2012 R2
    Powershell Version 4.

  5. Hank Ollanketo

    I get this error when I run the script. The output of the report seems good:
    [PS] C:scriptsExchangeAnalyzer-0.1.1-Beta.2>.Run-ExchangeAnalyzer.ps1
    Vector smash protection is enabled.
    Method invocation failed because [Microsoft.Exchange.Data.Directory.ADObjectId] does not contain a method named
    ‘Split’.
    At C:scriptsExchangeAnalyzer-0.1.1-Beta.2Run-ExchangeAnalyzer.ps1:308 char:80
    + Server: $($server.Name), Site: $(( …
    + ~
    + CategoryInfo : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : MethodNotFound

    1. Jason Trimble

      I get the same error. Not sure why the Split method is trying to be used when the object has a name field which can be used instead:

      Server: $($server.Name), Site: $(($ExchangeServers | Where {$_.Name -ieq $server.Name}).Site.name)

      1. Paul Cunningham

        Code re-use from another part of the tool, basically. Odd that it throws an error there and not elsewhere, but if I can repro the bug it’ll get fixed 🙂

    2. Paul Cunningham

      Can you provide some details about how you’re running the script? Version of Windows? Version of PS? PS Remoting? Running in Exchange Management Shell?

Leave a Reply