Exchange 2013 installation error

i have a server running server standard 2012 r2 recently upgraded from server standard 2003
it is a dc,dchp,dns.
i am trying to install exchange server 2013 standard during the installation i get the following error message.
and am unable to continue.
The following error was generated when "$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")
" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\Administrator.example\AppData\Local\Temp\ldif.err'".

Hi,
Agree with Amit. And I also find some information for your reference:
Error 8224 is easily resolved by checking the Windows Firewall Profile and either.
A. Disable Domain Profile firewall as well as Private and Public Profles.
B. Disable or turn off Windows Firewall and change the state of the service to Manual.
More details in the following thread:
Exchange 2013 Error 8224
http://social.technet.microsoft.com/forums/exchange/en-US/318ef90d-59be-49b2-9202-688f80074418/exchange-2013-error-8224
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

Exchange 2013 installation Problem on Hyper-V

Hello,
I have a very interesting problem Exchange 2013 installation step on Hyper-V.
I have 2 server. I installed on server Server 2012 R2 Standart. And then installed hyper-v role for both server.
I created virtual machine for first server and this virtual machine domain controller.
And then I created virtual machine for second server and this virtual machine Exchange 2013.
I installed all prequisites and exchange 2013 finished successfuly. When I opened https://server/ecp it give me http 500 internal error. I checked almost all forums but any recommendation didn't solve my problem.
And then I removed hyper-v role and installed vmware v11. and installed same applications like above.
Very interesting finished installation and opened ecp console. eveythink seen to good.!
Actualy I find problem.
There is exchange feature installation command on microsoft exchange prequisite. When ruunning this command installing two program on program and feature name is "c++ redistrubutable x64 and x32"
I must uninstall this programs before install unified communication api 4.0.
I cannot see on hyper-v when running this feature.
But I can see on vmware this features on programs and feature.
This is very absurt.
Anybody have an idea for this
Thank you for your clarify.

Hi,
Thanks for your reply.
I run this command before Exchange 2013 installation:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering,
RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell,
Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth,
Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging,
Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,
Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
later run this code on vmware platform , installing 2 program in programs and feature. name is Visual
C++ Redistributable package x64 and x86. I know Unified Communications Managed API 4.0
install same program too. But I must unintall Visual C++ Redistributable package before
install Unified Communications Managed API 4.0. But My problem I cannot see this two program
in programs and feature on hyper-v platform.
I tried it many times.

Exchange 2010 Installation error

Hi All,
I'm at my over 10th installation of Exchange 2010 server and it is the first time I have to admit that I can't resolve the issue i'm faced off ;-)
Here is some info about my issue. The installation is on a Windows 2008 R2 (Virtual) sit on a Windows 2012 R2 server with Hyper-V and it is a fresh vanilla installation that I'm trying to install for the 3rd time. Each attempts returned me the same error
at the same steps.
The Exchange installation is a typical, common, CAS, Mailbox and HUB installation without any particular configuration in the setup.
Here is the error I get:
Client Access Role
Failed
Error:
The following error was generated when "$error.Clear();
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element'
could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
I Googled every single point of failure indication and I didn't get reliable fix or work around.
I used ADSI edit to see if the IIS folders are there and yes they are except the EWS one which is mentioned in
the error message. Forest, Domain and AD have been prepared as it should, DCDIAG doesn't return any problem and the security has been set
properly for Legacy migration with an Exchange 2003 organisation.
Here is the par of the Exchange setup log where it stopped:
[03-06-2014 16:15:26.0488] [1] Processing component 'Client Access Services Configuration' (Configuring Client Access services.).
[03-06-2014 16:15:26.0488] [1] Executing:
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
[03-06-2014 16:15:26.0503] [2] Active Directory session settings for 'New-WebServicesVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'powerhouse.parasuco.com', Preferred Global Catalog: 'powerhouse.parasuco.com', Preferred
Domain Controllers: '{ powerhouse.parasuco.com }'
[03-06-2014 16:15:26.0503] [2] Beginning processing new-WebServicesVirtualDirectory -WindowsAuthentication:'True' -WSSecurityAuthentication:'True' -InternalNLBBypassUrl:'https://mtl1ex01.parasuco.com/ews/exchange.asmx' -DomainController:'powerhouse.parasuco.com'
-Force:'True' -GzipLevel:'High'
[03-06-2014 16:15:26.0636] [2] Searching objects "MTL1EX01.parasuco.com" of type "Server" under the root "$null".
[03-06-2014 16:15:26.0649] [2] Previous operation run on domain controller 'powerhouse.parasuco.com'.
[03-06-2014 16:15:26.0650] [2] Processing object "MTL1EX01\EWS".
[03-06-2014 16:15:29.0130] [2] [ERROR] Unexpected Error
[03-06-2014 16:15:29.0130] [2] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0131] [2] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
[03-06-2014 16:15:29.0138] [2] Ending processing new-WebServicesVirtualDirectory
[03-06-2014 16:15:29.0139] [1] The following 1 error(s) occurred during task execution:
[03-06-2014 16:15:29.0139] [1] 0. ErrorRecord: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0139] [1] 0. ErrorRecord: System.InvalidOperationException: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'. ---> System.Configuration.ConfigurationErrorsException:
The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension,
Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config
line 2373)
at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.Configuration.GetSection(String sectionName)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.WebConfigReflectionHelper.CommitToWebConfig(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task, String path, String site, String server, Boolean isTokenCheckingSpecified,
Boolean isSpnListSpecified)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.CommitToMetabase(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessMetabase()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewWebServicesVirtualDirectory.InternalProcessMetabase()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
--- End of inner exception stack trace ---
[03-06-2014 16:15:29.0139] [1] [ERROR] The following error was generated when "$error.Clear();
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
[03-06-2014 16:15:29.0139] [1] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0139] [1] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
[03-06-2014 16:15:29.0140] [1] [ERROR-REFERENCE] Id=ServicesComponent___ca981854eaa74c1ca684178d9ea52fff Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03-06-2014 16:15:29.0140] [1] Setup is stopping now because of one or more critical errors.
I appreciate the time anybody would spend to help me with my issue

Well, here is a status of what I did.
After running the Cleanup tool, I ran the Exchange server setup again without re installing anything and I got the same error and I have found .NET issue in the application's event logs (Event ID 1111 .NET runtime optimization service with this error code:
- Error code 0x80029c4a =
Cannot Load Library); . Why that? because there still Windows Kernel Mode and User Mode .NET 1.11.
So I uninstalled them and ran the exchange setup again. It failed a the same point but nothing in the application log that time.
Going further to see if it is a .NET issue, I re installed from Windows Update the .NET
1.11 packages (Which are required prior to reinstall .NET 4.5) restart the server + re install version 4.5.1 and ran the setup again without the two available security patches for .NET 4.5.1. Guess what, same issue. No .NET error and no specific or related
log except the Exchange setup installation error.
From the MSExchange Management log, i have found that 2 errors are logged each time I run the setup:
Cmdlet failed. Cmdlet Install-ClientAccessRole, parameters {DomainController=powerhouse.parasuco.com, UpdatesDir=E:\Updates, ExternalCASServerDomain=webmail.parasuco.com}.
Cmdlet failed. Cmdlet New-WebServicesVirtualDirectory, parameters {WindowsAuthentication=True, WSSecurityAuthentication=True, InternalNLBBypassUrl=https://mtl1ex01.parasuco.com/ews/exchange.asmx, DomainController=powerhouse.parasuco.com, Force=True, GzipLevel=High}.
So it seems to me to be a IIS and security issue. Again, All other IIS virtual folders have been created without any problem. Why does the setup can't create the EWS one???

Exch 2013 Installation Error "Database is mandatory on UserMailbox"

A previous admin installed a trail edition of Exchange 2013 in our 2007 environment for testing. When he tried to uninstall it there was an issue and it left some Exchange AD debris in the Active Directory structure.
Surprise, but now he is nowhere to be found.........
Now the company is going to upgrade and we cannot install Exchange 2013 because of these mailbox errors. The old server and database has been cleared out of ADSI and the one user that was in the old 2013 database has had all the Exchange attributes
cleared from their AD profile.
We are still getting the "Database is mandatory on UserMailbox" error when I try to install Exch2013 on the new server. I tend to think there is some other mail-enabled object in AD that is causing the conflict, but I cannot find it.\
Obviously I cannot nuke the entire ADSI Exchange folder, because I still need 2007 to work. :-)
Any help would be appreciated......

Exchangesetup.log file should indicate which mailbox is that. Then rehome it using adsiedit homeMDB attribute on E2007 database, or perhaps remove that, if it is system mailbox...
Refer: http://social.technet.microsoft.com/wiki/contents/articles/25342.exchange-2013-setup-error-database-is-mandatory-on-usermailbox.aspx ---
However you won't be able to use Powershell to get info as you don't have any Exchange 2013 server in org...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange Server 2013 installation error at Step 10/15

I try to install Exchange Server 2013 on a fresh install of Windows Server 2012.
Windows Server 2012, have already install on it:
AD CD
DNS
IIS
Exchange 2013 Prerequisites for Win.Server 2012 like described here
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
And the (winner) error message is:
Exchange Server component Mailbox role: Client Access service failed.
Error: Error:
The following error was generated when "$error.Clear();
Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Could not grant Network Service access to the certificate with thumbprint ABC7C6378BF63CED166794CFBF410C73B29EDD3A because a cryptographic exception was thrown.".
I search online for a solution and I found many others with same problem but any solution yet. :(
If anyone can help me I am able to dedicate him my next ode.
Thank you,
Adrian

I am experiencing the same problem except that mine is definitely NOT a domain controller. The error code indicates that the process is attempting to grant Network Access to the Certificate during Setup, but fails.
"...Could not grant Network Service access to the certificate"
Exchange 2013 is being installed on Windows Server 2012 R2 but it is a member server with no domain responsibilities. Granting rights to the certificate during the Setup process is the root of the problem.
Here is the complete error comment:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Could not grant Network Service access to the certificate with thumbprint 681FC4E2C66D726EFB91A8E0FF7FF6F98942C2F4 because a cryptographic exception was thrown.".

Installing Exchange 2013 SP1 - Errors MSExchange ADAccess & MSExchange Common

The topology first:
AD-server + Exchange-server
What I am trying to do is just install a full version of Exchange 2013 sp1.
But the problem is that install wizard freezes on the "initializing setup" page. Also eventviewer gives 2 different error messages, MSExchange ADAccess & MSExchange Common.
MSExchange ADAccess:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ExSetup.exe
2964
Get Servers for mydomain.com
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:01.9984949. TCP error code 10061: No connection could be made because
the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.ICommunicationObject.Open()
   at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
   at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message table
MSExchange Common:
The description for Event ID 106 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
2
Time in Resource per second
MSExchange Activity Context Resources
The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.get_RawValue()
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
Last worker process info : Last worker process info not available!
Processes running while Performance counter failed to update:
1044 VSSVC
1064 spoolsv
4032 notepad
1416 svchost
700 dwm
3100 SMSvcHost
3616 msdtc
2564 csrss
336 csrss
424 winlogon
244 smss
688 LogonUI
2556 Taskmgr
596 svchost
1124 inetinfo
1920 svchost
1652 SMSvcHost
1400 svchost
2916 taskhostex
492 lsass
2688 dwm
396 wininit
484 services
1104 svchost
388 csrss
384 svchost
1896 svchost
3052 svchost
744 svchost
1180 mmc
3404 conhost
1800 explorer
3668 Setup
552 svchost
712 svchost
2864 svchost
2964 ExSetup
2948 rdpclip
2592 winlogon
900 svchost
808 svchost
4 System
1164 mqsvc
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Activity Context Resources : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange
activity context resources. Error Details: 2
   at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
   at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
the message resource is present but the message is not found in the string/message table

I solved this problem or at least managed to get a workaround for it.
I tried to install Exchange using rdp connection and the installation media was mapped on my local computer. After I copied it to server itself, everything started to work and now I am able to send emails.

Exchange 2013 installation fails

We're in the process of migrating from Exchange 2007 to Exchange 2013. I've followed the prerequisites, and have the necessary account permissions, but when I start the installation it fails at step 1 of 5 (mailbox role:mailbox service).
This warning shows up in the application log:
Event ID 2397
Process ExSetupUI.exe (PID=9844). Object [CN=Mailbox Database 1783948598,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<domain>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=local]. Property [Server] is set to value [<Exchange 2013 server name>
DEL:492ae292-f89f-4a29-b009-22a60973a4bf], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
This error shows up in the Exchange install console, as well as the application log:
Event ID 1002
Exchange Server component Mailbox role: Mailbox service failed.
Error: Error:
The following error was generated when "$error.Clear();
if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
else
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
" was run: "The Exchange server for the database object "Mailbox Database 1783948598" wasn't found in Active Directory Domain Services. The object may be corrupted.".
I should also mention that this installation was attempted once before by an ex-coworker, and it failed. I've spent hours searching Google but haven't come up with a solution. Does anyone have any ideas?

Check it at Exchange 2007 side, Get-MailboxDatabase -Server E2007ServerName or via EMC to confirm but if msExchOwningServer/msExchMasterServer
points to the server which is stale 2013 server then it shouldn't be connected to E2007 by any way and you are good to remove those...
But I wouldn't touch another DB which has just server name and not servername\0ADEL:guid
as it is not giving error (at least yet...) in the setup
Blog |
Get Your Exchange Powershell Tip of the Day from here

MS Exchange 2013 certificate error.

we just setup Exchange 2013 but I cant configure outlook . it brings two error messages.
1. There is a problem with a proxy server's security certificate. the name on the certificate is invalid or does not match the name of the target site.
2. The connection to Microsoft exchange is unavailable. outlook must be online or connected to complete this action

Hi Stefo266,
Great checklist from S.Nithyanandham.
Which method do you setup your Exchange account into Outlook?Automatically or manually? If failed to setup account automatically, please try to setup manually.
Thanks
Mavis Huang
TechNet Community Support

Exchange Server Installation Error.

Please any one can help me to solve this issue.I am trying to Install Exchange server 2013 on Windows Server 2012 R2 . I have installed all Prerequisites for Exchange Server and The user is already a member of enterprise admin and schema admin but I am
getting following Error.
Error:
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.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run
setup with the /prepareAD parameter on a computer in the domain devcn and site Default-First-Site-Name, and wait for replication to complete.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx

Did you run setup.exe /PD or setup.exe /preparedomain
It does make a difference.....
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 "Server Error in '/owa' Application" - System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1

Out of nowhere...literally this started happening to our standalone Exchange server / Domain Controller
Operating System: Microsoft Windows Server 2012 Standard
Problem Child: Microsoft Exchange Server 2013
Error: When i try to login to the OWA or ECP i receive the listed errors above.
OS and Exchange installed on C:\
Mailbox Databases installed on D:\
Mailbox Logs on E:\
Outlook is still working for the end-user, but Outlook Web Access, ECP and all other features required to make this server manageable are failing. I can access the login screen, though at:
https://<servername>/owa
or
https://<servername>/ecp
I have tried reset of virtual directories. Tried IISRESET /NOFORCE after this, but no success.

Hi MRXennix,
Base on my research, the issue is caused by corrupted Killbit.xml file on "ClientAccess\owa\15.0.xxx.x\owa2\ext\killbit".
I recommend you refer to the following method to solved the issue:
1. Remove the Killbit.xml file and restart IIS
2. Install the latest CU builds of the exchange 2013.
Best regards,
Niko Cheng
TechNet Community Support

Move Exchange 2013 installation to new virtual machine

Currently have: 1 virtual server - Server 2012 (DC, Global Catalog), Exchange 2013 CU1 installation (yes I know- dont install Exchange on DC etc etc ... ). Server2012/Exchange2013 is installed on one VMDK, EDB and logs are saved on another VMDK.
Want to do: Create second virtual machine and install Server 2012 (different name), add it as a member to the same domain (also in the same network), install Exchange 2013, move all mailboxes to the new server, uninstall the old Exchange 2013.
Question is- is it possible to somehow unmount the existing database (I am only using one database for mailboxes and public folders) and mount it to the new server or do I have to create a new database on the new server and move the mailboxes there? I've
heard that the Exchange EDB databases were supposed to be portable between same versions of Exchange.
Any advice is appreciated.

Hi,
Agree with Andy, to avoid down time, we can depend on database portability.
And here are the steps you can refer to:
1. Install new Exchange server on the member server.
2. Move Mailbox Database using Database Portability:
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
3. Move the public folders (if any), re-home the offline address book, and move your SMTP connectors
http://support.microsoft.com/kb/822931
4. Remove the old Exchange server.
Thanks,
Angela Shi
TechNet Community Support
Thanks for the reply.
I'm a bit confused on the instructions from
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx- does step 4 instruct me to overwrite the newly created database (on the new server) with the old database and then mount it on the new server? Also, as the public folders are now in
a mailbox on the same database- aren't they moved with the database without extra hassle?
Also the link you gave me in Step 3 in your post refers to Exchange 2003.
Thanks in advance.

Exchange 2013 Installation

I am installing Office 365 online for my network. The present setup is that I have pop 3 mailboxes with my ISP - I don't have any exchange installation.
My question is should I install Microsoft exchange 2013 locally and then move online OR should I simply install online -- when I look at the Exchange Server Deployment Assistant it seems to work with upgrading installations as opposed to clean installs.
Apols if this Q has an obvious answer.
Rgds
O

Hi
As per the information and details provided by you, I think you should install Exchange 2013 on a member server.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

Exchange 2013 Installation Issues

Let's document my frustrations with installing and setting up Exchange 2013 on my Server 2012 Standard Edition Server.Steps taken before hitting install:Installed Server 2012 Standard and rebootedCreated a VSS for posterity sake.Downloaded CU2 fromhereInstalled Server Roles in PowerShell: Install-WindowsFeature RSAT-ADDSInstall-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,...
This topic first appeared in the Spiceworks Community

Hi,
As additional, I want to double confirm whether external user cannot receive message send from your environment and contain attachment, or cannot send message with attachment for external mail flow.
If it’s the former, it means mail flow works fine in your environment. You can contact administrator for destination forest to check attachment filter and transport rule.
If it’s the latter, this issue may be caused in your own configuration. We can check anti-spam filter, transport rule and send connector, run message track log and protocol log to find out the node for this issue.
More details about Anti-Spam and Antivirus Mail Flow, for your reference:
https://technet.microsoft.com/en-us/library/aa997242(v=exchg.141).aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Introducing Active Directory sites AFTER exchange 2013 installation

Hi
We have multiple physical sites and only 1 active directory site. Email environment is pure on-premises exchange 2013. Each physical site has CAS/Mailbox servers. There are not IP restrictions between these physical sites. Everything
is outlook anywhere obviously.
I would like to introduce NEW AD sites for each of these physical locations.
Do you see any major issues that I need to be aware of?
Can this be done in the middle of the day?
Will there be pop ups in outlooks and disconnects?
I appreciate your help.

I haven't had to do this before, but I would probably schedule this at night as there are some changes that will need to be made on the Exchange side of things.
Once you have the new AD Sites configured (Make sure you have at a minimum one Global Catalog, although I would recommend at least 2 in each AD site). You should cycle the AD Topology Service on each Exchange Server (this is going to cause all services
to restart so do it one at a time).
You should also use Set-ClientAccessServer and set the proper site scopes that you want Autodiscover to respond to.
I'm sure there's more, but that's what I can think of at the moment.
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

Exchange Server 2013 Installation error

Hi Support,
I have try to install exchange server 2013 on server 2012. after configure active directory when try to install exchange server command Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>CD\
C:\>E:
E:\>cd pradeep\Ex Setup 2013
E:\pradeep\EX Setup 2013>Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseT
erms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis FAILED
A reboot from a previous installation is pending. Please restart the system
and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.RebootPending.aspx
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
E:\pradeep\EX Setup 2013>

Hi ,
Please have a look in to the error message
"A reboot from a previous installation is pending. Please restart the system
and then rerun Setup."
Reboot the server and try again .
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2013 installation error

Similar Messages

Maybe you are looking for