microsoft / microsoft/CSS-Exchange

[Issue] SetupAssist.ps1 Failed to properly run Test-ValidHomeMDB

Open
#1,827 0 comments 0 reactions 1 assignee View on GitHub

@dpaulson45 is already working on this.

Since Dec 6, 2024.

Issue Setup Setup Assist
Dominant language
PowerShell
Stars
1.3k
Forks
395
Avg merge
14h 7m
Merged PRs (30d)
5

Description

Describe the issue
Setup Assist Version 23.08.15.2342
When running the script it passes and states that no results did not pass, but there is an error "Failed to properly run Test-ValidHomeMDB : Exception calling "FindAll" with "0" argument(s): "Unknown error (0x80005000)""

Expected behavior
Error should not show and script should run successfully.

Script Output

[PS] C:\Scripts>.\SetupAssist.ps1
Setup Assist Version 23.08.15.2342
Failed to properly run Test-ValidHomeMDB
 : Exception calling "FindAll" with "0" argument(s): "Unknown error (0x80005000)"
Inner Exception:    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
   at System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)
   at System.Management.Automation.PSScriptCmdlet.DoEndProcessing()
   at System.Management.Automation.CommandProcessorBase.Complete()
Position Message: At C:\Scripts\SetupAssist.ps1:1850 char:12
+     return $searcher.FindAll()
+            ~~~~~~~~~~~~~~~~~~~
Script Stack: at Search-AllActiveDirectoryDomains, C:\Scripts\SetupAssist.ps1: line 1850
at Test-ValidHomeMDB, C:\Scripts\SetupAssist.ps1: line 1862
at RunAllTests, C:\Scripts\SetupAssist.ps1: line 5300
at Main, C:\Scripts\SetupAssist.ps1: line 5310
at <ScriptBlock>, C:\Scripts\SetupAssist.ps1: line 5406
at <ScriptBlock>, <No file>: line 1

TestName                             Result  Details
--------                             ------  -------
User Administrator                   Passed  DOMAIN\username SID
Exchange AD Level                    Passed  Exchange 2019 CU12 Mar23SU
Execution Policy                     Passed  Unrestricted
Exchange Services                    Passed
Services Cache Files                 Passed
Computers Container Exists           Passed
DC DNS Host Name                     Passed
Multiple Active Sync VDirs Detected  Passed
Install Watermark                    Passed
Msi Cache File                       Passed
IIS URL Rewrite                      Passed  Installed Version 7.2.1993
UCMA Installed                       Passed  Installed Version: 5.0.8308.0
Microsoft Visual C++ 2012            Passed  Visual C++ 2012 Redistributable
Microsoft Visual C++ 2013            Passed  Visual C++ 2013 Redistributable
Other Well Known Objects             Passed
Pending Reboot                       Passed


-----Results That Didn't Pass-----


Setup Log Reviewer Results
--------------------------

Setup.exe Run Date: 03/19/2023 12:53:25
Setup.exe Build Number: 15.2.1118.7
Looks like we weren't able to determine the cause of the issue with Setup.
Address all Failed tests above, if any.
If that doesn't find the cause, please notify 'ExToolsFeedback@microsoft.com' to help us improve the scripts.
WARNING: Ran into an issue with the script. If possible please email 'ExToolsFeedback@microsoft.com' of the issue that
you are facing including the SetupAssist-Debug.txt file.
Do you like the script? Visit https://aka.ms/ExchangeSetupAssist-Feedback to rate it and to provide feedback.

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.