asked on

Exchange 2019 Installation 8 of 14 Error Could not load file or assembly 'Microsoft.Exchange.Transport.Extensibility,

I created a whole new Domain Server 2019 and have an Exchange Server 2019 and trying to install Exchange with the install Wizard and am stopped at 8 of 14.

Error:
The following error was generated when "$error.Clear();
$agentName = "Mobile Message Receive Agent";
$agent = get-transportagent -Identity:$agentName;
if ($agent) {
uninstall-transportagent -Identity:$agentName;
};
" was run: "System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Transport.Extensibility, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Exchange.Transport.Extensibility, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at Microsoft.Exchange.Management.AgentTasks.GetTransportAgent.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage taskStage, Action initFunc, Action mainFunc, Action completeFunc)
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
".
ExchangeSetup--1-.log

ASKER CERTIFIED SOLUTION

Shreedhar Ette

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Adam Brown

From the log:

[03/08/2019 03:19:38.0214] [1] Failed [Rule:CannotAccessAD] [Message:Either Active Directory doesn't exist, or it can't be contacted.]
[03/08/2019 03:19:38.0214] [1] [REQUIRED] This computer isn't part of an Active Directory domain.
[03/08/2019 03:19:38.0214] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ComputerNotPartofDomain.aspx
[03/08/2019 03:19:38.0230] [1] [REQUIRED] The user isn't logged on to an Active Directory domain.
[03/08/2019 03:19:38.0230] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LoggedOntoDomain.aspx
[03/08/2019 03:19:38.0230] [1] [REQUIRED] This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
[03/08/2019 03:19:38.0230] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
[03/08/2019 03:19:38.0230] [1] [REQUIRED] A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
[03/08/2019 03:19:38.0230] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
[03/08/2019 03:19:38.0230] [1] [REQUIRED] The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
[03/08/2019 03:19:38.0230] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
[03/08/2019 03:19:38.0230] [1] [REQUIRED] Setup encountered a problem while validating the state of Active Directory: Active Directory server is not available. Error message: Active directory response: The LDAP server is unavailable.

The logs are saying that the computer you're installing on isn't part of an Active Directory Domain. Is this the case? If not, make sure the computer can properly talk to AD by pinging the domain name like this:

ping domain.local

Open in new window