Hi MConnelly20,
Guess you didn't cleanup the Schema Prep, not a feasible option anyways. (The only supported/guaranteed way to roll back a schema change is a full forest recovery.)
You must have followed article like this http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/, please cross check if you haven't.
Next thing would be analyzing the Eventvwr logs and the Exchange Setup Logs (These logs are written to C:\ExchangeSetupLogs by default.)
Also check if your AD is in a healthy state.
References:
When I look at the Schema with ADSI edit, I still see all the ms-exch attributes from the initial Schema Prep that was conducted. Both the Schema Prep and AD Prep was conducted successfully, but when Exchange 2013 SP1 combined was loaded, OWA never worked right and I was having issues connecting properly with SP 2013. I did use a similar blog about uninstalling Exchange, that went into more depth that the one you listed. Here is a copy of my Exch Setup Logs when I attempt to run Prepare AD:
[04/23/2015 20:10:12.0108] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
[04/23/2015 20:10:12.0108] [0] **********************************************
[04/23/2015 20:10:12.0108] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[04/23/2015 20:10:12.0108] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[04/23/2015 20:10:12.0108] [0] Setup version: 15.0.847.32.
[04/23/2015 20:10:12.0124] [0] Logged on user: TSYSDEV\MConnelly.
[04/23/2015 20:10:12.0140] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/23/2015 20:10:12.0187] [0] Command Line Parameter Name='preparead', Value=''.
[04/23/2015 20:10:12.0187] [0] Command Line Parameter Name='organizationname', Value='ExchangeDev'.
[04/23/2015 20:10:12.0187] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[04/23/2015 20:10:12.0187] [0] Command Line Parameter Name='domaincontroller', Value='tsysdevdc2.tsysdev.net'.
[04/23/2015 20:10:12.0187] [0] Command Line Parameter Name='sourcedir', Value='E:\Source'.
[04/23/2015 20:10:12.0390] [0] RuntimeAssembly was started with the following command: '/PrepareAD /OrganizationName:ExchangeDev /IAcceptExchangeServerLicenseTerms /domaincontroller:tsysdevdc2.tsysdev.net /sourcedir:E:\Source'.
[04/23/2015 20:10:12.0405] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[04/23/2015 20:10:12.0405] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[04/23/2015 20:10:12.0421] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/23/2015 20:10:12.0421] [0] Copying Files...
[04/23/2015 20:10:12.0437] [0] Starting copy from E:\Source\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[04/23/2015 20:10:18.0484] [0] Finished copy from E:\Source\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[04/23/2015 20:10:18.0499] [0] File copy complete. Setup will now collect additional information needed for installation.
[04/23/2015 20:10:18.0499] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[04/23/2015 20:10:22.0593] [0] Setup is choosing the domain controller to use
[04/23/2015 20:10:22.0687] [0] We have a user-specified or previously-chosen domain controller: tsysdevdc2.tsysdev.net
[04/23/2015 20:10:22.0734] [0] [ERROR] Exception has been thrown by the target of an invocation.
[04/23/2015 20:10:22.0734] [0] [ERROR] Method not found: 'Boolean Microsoft.Exchange.Data.Mime.MimeAddressParser.IsValidDomain(System.String, Int32, Boolean)'.
[04/23/2015 20:10:22.0734] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
[04/23/2015 20:10:22.0749] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[04/23/2015 20:10:22.0749] [0] CurrentResult main.run:235: 1
[04/23/2015 20:10:22.0749] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/23/2015 20:10:22.0749] [0] CurrentResult setupbase.maincore:396: 1
[04/23/2015 20:10:22.0749] [0] End of Setup
Checked the registry and the keys it is looking for are not there, but no sure if I need to manually create them. Any assistance would be created appreciated or if I need to conduct the back-out plan, I can try that.
Hi MConnelly20,
Before I dig in try these.
Option1.
- Extend the Active Directory schema again.
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
- Re-run the Setup
Option2.
- Go to-Regedit-
- Open ComputerHKEY_Local_Machine\Software\Microsoft\ExchangeServer\V15\Cafe Role ----
- Check out for Watermark Key\if it is exist Delete it
- Re-run the Setup.
There can be issue with the SetupFiles. Download CU8 and try.
Post the logs again if fails.
Provide more info about your environemnt, DC, Exch OS, etc.
References for additional troubleshooting:
Exchange 2013 Watermark Key Path in Registry..
Hello, the error listed earlier is what I receive when I attempt the Schema update, which is:
[04/23/2015 20:10:22.0734] [0] [ERROR] Exception has been thrown by the target of an invocation.
[04/23/2015 20:10:22.0734] [0] [ERROR] Method not found: 'Boolean Microsoft.Exchange.Data.Mime.MimeAddressParser.IsValidDomain(System.String, Int32, Boolean)'.
[04/23/2015 20:10:22.0734] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
[04/23/2015 20:10:22.0749] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
I get the same error whether I tried the SchemaUpdate or PrepareAD. There are no Exchange registry keys. Environment is two Windows 2012R2 servers with one server having the CAS role and other the Mailbox role. Is there is way to cleanup or remove the exchange attributes that remain in the Schema now? Feel something is not listed right there and that is why it is failing.
Hello,
I remember one of my customer encountered the same error in the setup log when installing the Exchange Server 2013. We found that Exchange Servers group was not present under Manage auditing and security log. You can check about this point.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com
Hi MConnelly20,
As said earlier, The only supported/guaranteed way to roll back a schema change is a full forest recovery.
Before that I insist that give it a shot with fresh CU8 Setup download.
- Prior to that remove\ re-install .NET and other pre-requisites once again on the Exchange Boxes. (How about you get a fresh Windows Install on the Exchange Boxes)
- Make sure as well Windows Management Instrumentation and IP Helper services are started and have startup type Automatic. (Hope there is no Exchange Services listed here and in Disabled State)
- WMI, IIS, WWW Publishing service Automatic and Started
- Reboot the server
- Run CU8 Setup
Found below steps, in relation with the error:
https://support.microsoft.com/en-us/kb/2626696
This issue occurs if the Internet Information Services (IIS) configuration is missing the svc-Integrated handler mapping.
Note Before you follow these steps, back up your IIS configuration.
To resolve this issue, run the ServiceModelReg.exe r command to reinstall the handler mappings in IIS. To do this, follow these steps:
- On the Exchange Server 2010 hybrid deployment server, open a Command Prompt window, and then move to the following folder:
C:\Windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\ - Type the following command, and then press Enter:
ServiceModelReg.exe r
Note You may have to restart IIS after you run this command.
Few articles point towards DC issue:
Exchange 2013 Exception has been thrown by the target of an invocation
Is your exchange reachable to Active directory. Please run dcdiag /s:[Domain Controller Name] from command line.
Hi,
Is there any update on this thread?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com
Hi MConnelly,
Please list out the actions to results \ errors from my earlier troubeshooting posts.