Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Friday, March 6, 2020 11:40 AM
Dear members,
I have been trying, for a few days now, to install Exchange 2019 into a Exchange 2016 setup.
I started off with Exchange 2019 CU4, but also tried CU3.
the inventory is as follows
Server1 : Exchange 2016
Server2 : Exchange 2016
Server3: NEW Exchange 2019
Server4: NEW Exchange 2019
I have recently done another installation of Exchange 2019 CU3 (3 servers) install on an existing Exchange 2016 deployment without any issues.
The current setup simply fails at the CAS Role with following error
The same error even occurs when i do a 2019 ONLY lab install which does not have any existing 2016 environment .. not sure where i am
"
[03/05/2020 21:43:54.0071] [2] Active Directory session settings for 'New-OwaVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC-001.DOMAIN.local', Preferred Global Catalog: 'DC-001.DOMAIN.local', Preferred Domain Controllers: '{ DC-001.DOMAIN.local }'
[03/05/2020 21:43:54.0071] [2] User specified parameters: -Role:'Mailbox' -WebSiteName:'Exchange Back End' -DomainController:'DC-001.DOMAIN.local'
[03/05/2020 21:43:54.0071] [2] Beginning processing new-OwaVirtualDirectory
[03/05/2020 21:43:54.0086] [2] Searching objects "Server2.DOMAIN.local" of type "Server" under the root "$null".
[03/05/2020 21:43:54.0149] [2] Previous operation run on domain controller 'DC-001.DOMAIN.local'.
[03/05/2020 21:43:54.0149] [2] Processing object "Server2\owa".
[03/05/2020 21:44:04.0071] [2] [WARNING] A failure occurred while trying to enable the ISAPI filter.
[03/05/2020 21:44:04.0071] [2] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'.
[03/05/2020 21:44:04.0086] [2] [ERROR] ISAPI extension owaauth.dll in group MSExchangeClientAccess wasn't found and its status can't be changed. Please make sure this ISAPI extension (IIS Web service extension) is still listed in IIS Manager. If it's not, it may need to be added again.
[03/05/2020 21:44:14.0539] [2] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'.
[03/05/2020 21:44:14.0539] [2] [ERROR] ISAPI extension owaauth.dll in group MSExchangeClientAccess wasn't found and its status can't be changed. Please make sure this ISAPI extension (IIS Web service extension) is still listed in IIS Manager. If it's not, it may need to be added again.
[03/05/2020 21:44:14.0539] [2] Ending processing new-OwaVirtualDirectory
[03/05/2020 21:44:14.0571] [2] Active Directory session settings for 'Set-OwaVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC-001.DOMAIN.local', Preferred Global Catalog: 'DC-001.DOMAIN.local', Preferred Domain Controllers: '{ DC-001.DOMAIN.local }'
[03/05/2020 21:44:14.0571] [2] User specified parameters: -Identity:'Server2\OWA (Exchange Back End)' -FormsAuthentication:'False' -WindowsAuthentication:'True'
[03/05/2020 21:44:14.0571] [2] Beginning processing set-OwaVirtualdirectory
[03/05/2020 21:44:14.0586] [2] Searching objects "Server2\OWA (Exchange Back End)" of type "ADOwaVirtualDirectory" under the root "$null".
[03/05/2020 21:44:14.0586] [2] Previous operation run on domain controller 'DC-001.DOMAIN.local'.
[03/05/2020 21:44:14.0586] [2] [ERROR] The operation couldn't be performed because object 'Server2\OWA (Exchange Back End)' couldn't be found on 'DC-001.DOMAIN.local'.
[03/05/2020 21:44:14.0586] [2] Ending processing set-OwaVirtualdirectory
[03/05/2020 21:44:14.0602] [1] The following 2 error(s) occurred during task execution:
[03/05/2020 21:44:14.0602] [1] 0. ErrorRecord: An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'.
[03/05/2020 21:44:14.0602] [1] 0. ErrorRecord: System.InvalidOperationException: An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'. > Microsoft.Exchange.Management.Metabase.ManageIsapiExtensionCouldNotFindExtensionException: ISAPI extension owaauth.dll in group MSExchangeClientAccess wasn't found and its status can't be changed. Please make sure this ISAPI extension (IIS Web service extension) is still listed in IIS Manager. If it's not, it may need to be added again.
at Microsoft.Exchange.Management.IisTasks.ManageIsapiExtensions.SetStatus(String hostName, String groupID, String extensionBinary, Boolean allow)
at Microsoft.Exchange.Management.Metabase.OwaIsapiFilter.Install(DirectoryEntry virtualDirectory)
at Microsoft.Exchange.Management.SystemConfigurationTasks.OwaVirtualDirectoryHelper.EnableIsapiFilter(ADOwaVirtualDirectory adOwaVirtualDirectory, Boolean forCafe)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory.InternalProcessMetabase()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
End of inner exception stack trace
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[03/05/2020 21:44:14.0617] [1] [ERROR] The following error was generated when "$error.Clear();
$windowsAuthenticationEnabled = $true
[Reflection.Assembly]::LoadWithPartialName('Microsoft.Exchange.Clients.Owa2.ServerVariantConfiguration');
try
{
$snapshot = [Microsoft.Exchange.VariantConfiguration.OwaServer.OwaServerConfiguration]::GetSnapshot([Microsoft.Exchange.VariantConfiguration.MachineSettingsContext]::Local)
if (($snapshot -ne $null) -and ($snapshot.WindowsAuthenticationDisabled -ne $null) -and $snapshot.WindowsAuthenticationDisabled.Enabled)
{
Write-ExchangeSetupLog -info "WindowsAuthenticationDisabled is true, disabling windows authentication on vdir..."
$windowsAuthenticationEnabled = $false
}
else
{
Write-ExchangeSetupLog -info "WindowsAuthenticationDisabled is false, enabling windows authentication on vdir..."
}
}
catch
{
Write-ExchangeSetupLog -info $_
}
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController;
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$windowsAuthenticationEnabled;
" was run: "System.InvalidOperationException: An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'. > Microsoft.Exchange.Management.Metabase.ManageIsapiExtensionCouldNotFindExtensionException: ISAPI extension owaauth.dll in group MSExchangeClientAccess wasn't found and its status can't be changed. Please make sure this ISAPI extension (IIS Web service extension) is still listed in IIS Manager. If it's not, it may need to be added again.
at Microsoft.Exchange.Management.IisTasks.ManageIsapiExtensions.SetStatus(String hostName, String groupID, String extensionBinary, Boolean allow)
at Microsoft.Exchange.Management.Metabase.OwaIsapiFilter.Install(DirectoryEntry virtualDirectory)
at Microsoft.Exchange.Management.SystemConfigurationTasks.OwaVirtualDirectoryHelper.EnableIsapiFilter(ADOwaVirtualDirectory adOwaVirtualDirectory, Boolean forCafe)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory.InternalProcessMetabase()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
End of inner exception stack trace
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[03/05/2020 21:44:14.0617] [1] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'.
[03/05/2020 21:44:14.0617] [1] [ERROR] ISAPI extension owaauth.dll in group MSExchangeClientAccess wasn't found and its status can't be changed. Please make sure this ISAPI extension (IIS Web service extension) is still listed in IIS Manager. If it's not, it may need to be added again.
[03/05/2020 21:44:14.0617] [1] 1. ErrorRecord: The operation couldn't be performed because object 'Server2\OWA (Exchange Back End)' couldn't be found on 'DC-001.DOMAIN.local'.
[03/05/2020 21:44:14.0617] [1] 1. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Server2\OWA (Exchange Back End)' couldn't be found on 'DC-001.DOMAIN.local'.
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Func`2 notFoundError, Func`2 multipleFoundError, ExchangeErrorCategory errorCategory)
at Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase`3.ResolveDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.ResolveDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetVirtualDirectory`1.PrepareDataObject()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.PrepareDataObject()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebAppVirtualDirectory`1.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.InternalValidate()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebAppVirtualDirectory`1.InternalValidate()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirtualDirectory.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[03/05/2020 21:44:14.0617] [1] [ERROR] The following error was generated when "$error.Clear();
$windowsAuthenticationEnabled = $true
[Reflection.Assembly]::LoadWithPartialName('Microsoft.Exchange.Clients.Owa2.ServerVariantConfiguration');
try
{
$snapshot = [Microsoft.Exchange.VariantConfiguration.OwaServer.OwaServerConfiguration]::GetSnapshot([Microsoft.Exchange.VariantConfiguration.MachineSettingsContext]::Local)
if (($snapshot -ne $null) -and ($snapshot.WindowsAuthenticationDisabled -ne $null) -and $snapshot.WindowsAuthenticationDisabled.Enabled)
{
Write-ExchangeSetupLog -info "WindowsAuthenticationDisabled is true, disabling windows authentication on vdir..."
$windowsAuthenticationEnabled = $false
}
else
{
Write-ExchangeSetupLog -info "WindowsAuthenticationDisabled is false, enabling windows authentication on vdir..."
}
}
catch
{
Write-ExchangeSetupLog -info $_
}
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController;
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$windowsAuthenticationEnabled;
" was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Server2\OWA (Exchange Back End)' couldn't be found on 'DC-001.DOMAIN.local'.
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Func`2 notFoundError, Func`2 multipleFoundError, ExchangeErrorCategory errorCategory)
at Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase`3.ResolveDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.ResolveDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetVirtualDirectory`1.PrepareDataObject()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.PrepareDataObject()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebAppVirtualDirectory`1.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.InternalValidate()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebAppVirtualDirectory`1.InternalValidate()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirtualDirectory.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[03/05/2020 21:44:14.0617] [1] [ERROR] The operation couldn't be performed because object 'Server2\OWA (Exchange Back End)' couldn't be found on 'DC-001.DOMAIN.local'.
[03/05/2020 21:44:14.0617] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponent___62bd834915a7470798aa47ba1f2b6800 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/05/2020 21:44:14.0617] [1] Setup is stopping now because of one or more critical errors.
[03/05/2020 21:44:14.0617] [1] Finished executing component tasks.
[03/05/2020 21:44:14.0649] [1] Ending processing Install-ClientAccessRole
[03/05/2020 21:44:14.0649] [0] CurrentResult console.ProcessRunInternal:198: 1
[03/05/2020 21:44:14.0649] [0] CurrentResult launcherbase.maincore:90: 1
[03/05/2020 21:44:14.0649] [0] CurrentResult console.startmain:52: 1
[03/05/2020 21:44:14.0649] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
[03/05/2020 21:44:14.0649] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[03/05/2020 21:44:14.0649] [0] CurrentResult main.run:235: 1
[03/05/2020 21:44:14.0649] [0] CurrentResult setupbase.maincore:396: 1
[03/05/2020 21:44:14.0649] [0] End of Setup
"
Appreciate any help and pointers in the direction to complete the setup.
Thanks in advance.
Friday, March 27, 2020 1:26 PM ✅Answered
Here is a brief summary about replies above for quick reference.
Issue Symptom:
I have been trying, for a few days now, to install Exchange 2019 into a Exchange 2016 setup. I started off with Exchange 2019 CU4, but also tried CU3.
I have recently done another installation of Exchange 2019 CU3 (3 servers) install on an existing Exchange 2016 deployment without any issues.
The current setup simply fails at the CAS Role with following error:
An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'.
The operation couldn't be performed because object 'Server2\OWA (Exchange Back End)' couldn't be found on 'DC-001.DOMAIN.local'.
The same error even occurs when i do a 2019 ONLY lab install which does not have any existing 2016 environment.
Possible Cause:
The OWA virtual directory cannot be created successfully.
Troubleshooting Steps so far:
Please make sure Microsoft .NET Framework 4.8 and Visual C++ Redistributable Package for Visual Studio 2012 are installed. Also, please pay attention that only Windows Server 2019 is supported with Exchange 2019.
Install the Exchange with the Setup wizard.
Next Step:
You can remove the unfinished Exchange server from ADSI Editor in your lab, then reinstall Exchange. This error may be caused when IIS is running in 32-bit mode on 64-bit computer. You can try to run the following command to switch IIS to 64bit mode, then reinstall Exchange.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
The issue has been sorted out now. No technical activity involved.
steps taken
1. un-install Exchange using command line --> completes successfully.
2. clean up ADSI edit for any remnants of Exchange Server that failed.
3. Reboot server and re-install pre-requisites if needed ( script from technet verfies)
4. Install Exchange CU4 via the GUI.
5. installation completes successfully.
in the previous instance, the exchange installation was tested on the half-baked exchange installation which is why it was failing.
I still have no clue why the EXCHANGE GUI works well, but not the CMD line install. :(
problem solved in terms of installation, but actual underlying problem is still unknown .. thread can be closed..
Sunday, March 8, 2020 5:13 PM
Hi
Its complaining about the ISAPI filter. Did you install all the prerequisites for Exchange 2019?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Monday, March 9, 2020 8:43 AM
Hi,
Do you mean you have the same error when install Exchange 2019 cu4 in your test environment?
Do you extend schema and prepare AD successfully before installing Exchange 2019?
Please make sure Microsoft .NET Framework 4.8 and Visual C++ Redistributable Package for Visual Studio 2012 are installed. Also, please pay attention that only Windows Server 2019 is supported with Exchange 2019.
For more details about Exchange 2019 cu4, you can check: Cumulative Update 4 for Exchange Server 2019.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Monday, March 9, 2020 9:24 AM
Hi
Its complaining about the ISAPI filter. Did you install all the prerequisites for Exchange 2019?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hi Edward,
Yes, the pre-requisites were installed properly. I did multiple VM tests for the sake of sanity testing.
one VM was with manual steps provided by Microsoft and the second VM was done with a powershell script provided by another MVP at this location. Exchange 2019 Pre Requisites installation - Powershell
Monday, March 9, 2020 9:25 AM
Hi,
Do you mean you have the same error when install Exchange 2019 cu4 in your test environment?
Do you extend schema and prepare AD successfully before installing Exchange 2019?
Please make sure Microsoft .NET Framework 4.8 and Visual C++ Redistributable Package for Visual Studio 2012 are installed. Also, please pay attention that only Windows Server 2019 is supported with Exchange 2019.
For more details about Exchange 2019 cu4, you can check: Cumulative Update 4 for Exchange Server 2019.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Hello LYdia,
Do you mean you have the same error when install Exchange 2019 cu4 in your test environment? -->
The answer to the lab question is also yes.. I get the same ERROR..
The answer is yes, i have installed all the pre-requisites and also done the schema/AD preparation.
Kind Regards,
Prashant Divakaran
Tuesday, March 10, 2020 9:00 AM
Does OWA work well in your production environment?
In you lab environment, since there is no other Exchange server, you can try to install Exchange 2019 cu3, then upgrade to Exchange 2019 cu4. Check if the same issue is reproduced.
Additionally, you can install the Exchange with the Setup wizard: Install Exchange Mailbox servers using the Setup wizard.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Tuesday, March 10, 2020 10:18 AM
Does OWA work well in your production environment?
In you lab environment, since there is no other Exchange server, you can try to install Exchange 2019 cu3, then upgrade to Exchange 2019 cu4. Check if the same issue is reproduced.
Additionally, you can install the Exchange with the Setup wizard: Install Exchange Mailbox servers using the Setup wizard.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Yes, it does work well in the production environment.
The CU3 installation also fails with the same error message.
I have also tried installing the Mailbox servers in the lab using the SETUP wizard which started off from where it failed, but no luck. still errors .
Wednesday, March 11, 2020 8:46 AM
You can remove the unfinished Exchange server from ADSI Editor in your lab, then reinstall Exchange. This error may be caused when IIS is running in 32-bit mode on 64-bit computer. You can try to run the following command to switch IIS to 64bit mode, then reinstall Exchange:
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False
For your reference: New-OwaVirtualDirectory : An error occurred while creating the IIS virtual directory
For how to remove the unfinished Exchange server from ADSI Editor:
Locate to CN=Configuration,DC=domain,DC=com > CN=Services. Since there is only one Exchange server, you can just remove CN=Microsoft Exchange and CN=Microsoft Exchange Autodiscover. Then update the schema and force AD replication.
Important: ADSI Edit must be handled with care. Modifying the attributes using ADSIEdit can cause significant issues with your infrastructure if something is done in a wrong way. We would suggest you make a backup before modifying.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Tuesday, March 17, 2020 7:27 AM
Just checking in to see if above information was helpful. If you have any questions or need further help on this issue, please feel free to post back.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Thursday, March 19, 2020 8:59 AM
Here is a brief summary about replies above for quick reference.
Issue Symptom:
I have been trying, for a few days now, to install Exchange 2019 into a Exchange 2016 setup. I started off with Exchange 2019 CU4, but also tried CU3.
I have recently done another installation of Exchange 2019 CU3 (3 servers) install on an existing Exchange 2016 deployment without any issues.
The current setup simply fails at the CAS Role with following error:
An error occurred while creating the IIS virtual directory 'IIS://Server2.DOMAIN.local/W3SVC/2/ROOT/owa' on 'Server2'.
The operation couldn't be performed because object 'Server2\OWA (Exchange Back End)' couldn't be found on 'DC-001.DOMAIN.local'.
The same error even occurs when i do a 2019 ONLY lab install which does not have any existing 2016 environment.
Possible Cause:
The OWA virtual directory cannot be created successfully.
Troubleshooting Steps so far:
Please make sure Microsoft .NET Framework 4.8 and Visual C++ Redistributable Package for Visual Studio 2012 are installed. Also, please pay attention that only Windows Server 2019 is supported with Exchange 2019.
Install the Exchange with the Setup wizard.
Next Step:
You can remove the unfinished Exchange server from ADSI Editor in your lab, then reinstall Exchange. This error may be caused when IIS is running in 32-bit mode on 64-bit computer. You can try to run the following command to switch IIS to 64bit mode, then reinstall Exchange.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Monday, March 30, 2020 1:22 AM
Glad to hear that, and thanks for your sharing. Anyway, it's great that the Exchange 2019 CU4 can be installed successfully.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Tuesday, March 31, 2020 9:02 AM
Glad to hear that, and thanks for your sharing. Anyway, it's great that the Exchange 2019 CU4 can be installed successfully.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
i have also upgraded the installation from CU4 to CU5...
did not try cmd line.. but the GUI install.. that worked flawlessly.
Regards,
PD