Installation MS Exchange 2013 Failed

Hello,
Today I make a fresh install of the windows server 2012 STD, installed differents roles et promote my server like Domain controller.
After, I installed MS Exchange 2013 STD on this server with following procedure https://social.technet.microsoft.com/wiki/contents/articles/14506.how-to-install-exchange-2013-on-windows-server-2012.aspx and I encountered the following error during setup
progress (installation GUI).
Erreur :
L'erreur suivante est survenue lors de l'exécution de "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " : "Échec de l'installation du produit « D:\Donnees Entreprise\Messagerie\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASEntIRS.MSI ». Erreur irrécupérable lors de l’installation. Le code
d'erreur est 1603.".
I uninstall MS Exchange, demote DC and delete the folders created during exchange install and reboot.
After, I promote, reinstall exchange and I have a same error. I verify that the IP V6 is enable, I downloaded the source installation a second time (from MVLS), verify that my computer account is member of the exchange admin group...
Could you help me please because I have not got any solution?
Thanks and kind regards
Guillaume

Similar Messages

Installation of Exchange 2013 Failed on Mailbox Role Transport Service

Hi All,
Getting this error when trying to install a new exchange 2013 server. Thanks in advance
Error:
The following error was generated when "$error.Clear();
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Hi,
This problem occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the AD
directory service is corrupted.
Please try to follow these steps to solve this problem.
    1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
Click Start, click Run, type adsiedit.msc, and then click
OK.
Locate the Default Naming Context node, and then locate to the
CN=Users container.
Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
Delete.
    2. Rerun the Exchange Server 2013 Mailbox role setup application.
    3. Create a new federated e-mail account by using the following command:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
If this issue persistes, please let me know.
Best Regards.

Exchange 2013 fails Active Directory Prep

This is a new, new, installation of Windows Server 2012 R2 Essentials followed by Exchange 2013, all on a single server that is also the DC, in a lab environment.   This is to replace an existing SBS2000 installation in a small business.
Server 2012 setup without any significant issues. The first pass at Exchange 2013 resulted in "access denied" when attempting to access the Exchange Management PS and login credentials failure for Exchange EAC (ECP).   After manually
adding the installation Administrator to a number of the Exchange security groups, I was able to access Exchange Manager. I checked that there was a mailbox associated with the Installation Admin ID, attempted to reset passwords and a number of other
things to no avail. I uninstalled Exchange (what a pain).
I reinstalled Exchange. As with the first time, no prerequisite errors and no installation failure alerts.   Again, I could not access Exchange Manager (access denied) or the EAC (login credentials failure).   This time, I was not
able change the security group permissions to gain access to Exchange Manager. Again, checked about everything there was to check on the web and found a reference to Exchange possibly not installing correctly due to lingering entries from the first install.
As I could not access Exchange Manager to perform the uninstall prerequisites, I attempted to manually delete it (nothing to loose at this point), but made the anticipated mess.
Wiped the RAID and started over with a clean sheet install of Server 2012 Essentials-OK. Progressed in the Exchange install prep to "Prepare Active Directory and Domains" (http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx)
and stopped when I could not detect the confirming ADSI entries of AD prep set forth at the close of the TechNet document.
I methodically stepped through the install procedure and again received no prerequisite failures or installation failure alerts. I examined the install logs and found no errors, either.
Any words of wisdom?

Hi,
From your description, Windows Server 2012 R2 Essentials and Exchange 2013 are installed on a single server that is also the DC.
Microsoft does not support installing Exchange Server on a server that is running Windows Server Essentials. You need to install Exchange Server on a second server and then join the second server to the Windows Server Essentials domain.
And it is not recommended to install Exchange server on DC.
Here is a related article for your reference.
Integrate an On-Premises Exchange Server with Windows Server Essentials
http://technet.microsoft.com/en-us/library/jj200172.aspx
Best regards,
Belinda Ma
TechNet Community Support

After fresh installation of exchange 2013 I am not seeing Exchange Management shell EMS and EAC is redirecting to OWA

I am trying to upgrade my Exchange 2010 environment to exchange 2013. I was able to install exchange 2013 on a VM running windows 2012 R2 without any errors, however after installation I am not able to login to Exchange admin center as it keeps redirecting
to OWA and I am not seeing Exchange management shell.

Hi,
What’s the version of your Exchange 2013 Server. Try updating it to the latest version first.
If you were using an account which is still on the Exchange 2010 MBX server, this could be an issue. Try creating a new admin account on the Exchange 2013 and check if the issue still happens
to it.
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
[email protected]
Simon Wu
TechNet Community Support

SMTP test to Exchange 2013 failing

I have an Exchange 2013 server set up for testing which I am trying to have the internal servers relay off of to EarthLink (My ISP).
The Receive Connector is set up as a FrontEnd Transport, Anonymous and Externally Secured authentication. It accepts all addresses from my internal subnet.
The Send Connector is set up using a Smart connector to smtpauth.earthlink.net. It is set to use port 587 ( which is what EarthLink apparently uses). It uses basic authentication with my credentials to EarthLink. The address space is set
to '*'.
When I am on one of the member servers, I telnet 25 to the Exchange 2013 server and testing it:
220 exchange.home.com Microsoft ESMTP MAIL Service ready at Sun, 23 Nov 201
4 08:41:40 -0500
ehlo home.com
250-home.cave.com Hello [172.16.200.20]
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH
250-8BITMIME
250-BINARYMIME
250 CHUNKING
mail from:[email protected]
250 2.1.0 Sender OK
rcpt to:[email protected]
250 2.1.5 Recipient OK
DATA
354 Start mail input; end with <CRLF>.<CRLF>
Hello
Goodbye
451 4.7.0 Temporary server error. Please try again later. PRX3
I have been searching all over for some insights what this 451 4.7.0 .... PRX3 error is. There are a number of posts about PRX2, PRX4 and so forth. I have already found the information about verifying all DNS servers and creating a record in
the host file. None of that changed anything.
I disabled Symantec thinking it was causing the problem. Nope.
Any suggestions are GREATLY appreciated!

Hi Dolbert
Thank you for your question.
Did you can receive/send email?
If not, you can give me some error in your log or event?
“451 4.7.0 Temporary server error. Please try again later. PRX3” encoded SMTP response for when proxy fails because of connection failures to the destination. It happened at the send connector cannot resolve the correct destination. You can refer to the
following link to set configure internal reply:
http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
If there are any questions, please let me know.
Best Regard,
Jim

Uninstall Exchange 2013 failed on step number 8 Languages

Dear All,
I am not able to uninstall exchange 2013. the process is failing on step 8 Languages. Please advise

Any one please guide how to uninstall Exchange 2013?
Thanks in advance

Exchange 2013 Non Deliverable Messages do not show correct information

I tried looking around for a solution for this but have been unable to.
We have a new (1 month old) single-server installation of Exchange 2013 CU5, running on server 2012. It's in coexistence with an Exchange 2007 box. All users, groups, and everything have been migrated, we actually just shut down 2007 today. However, Exchange
2013 never seems to give accurate or helpful NDRs.
When someone sends an email to, let's say, a user who has left the company, so their mailbox is gone, the user who sent the email will receive an NDR. However, the NDR will not tell you the user who the email failed to. It shows the sender's account and
says "command not allowed". This happens only to internal recipients. When sending to an external domain, we receive the NDR from the other domain with the explanation that the user does not exist or whatever. But within our domain, we never get
a "helpful" NDR. It's just "command not allowed" and the email doesn't get to ANY of the recipients that it was sent to. Any ideas or help would be greatly appreciated!
Delivery has failed to these recipients or groups:
[email protected] Your message wasn't delivered due to a permission or security issue.
It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
Diagnostic information for administrators:
Generating server: mailserver.ourdomain
[email protected] Remote Server returned
'550 5.7.1 Command not allowed'
Original message headers:
Received: from mailserver.ourdomain ([removed]) by mailserver.ourdomain ([removed]) with mapi id 15.00.0913.011; Thu, 17 Jul 2014 10:18:03 -0500 MIME-Version: 1.0 Content-Type:
text/plain Date: Thu, 17 Jul 2014 10:18:03 -0500 Message-ID: <removed > Subject: RE: ASAP

I just tested, and yes, it happens when sending to any invalid SMTP address within our domain. I also tried sending an email to a non-existant user in our domain from my gmail account and received the same message with "command not allowed". We
are running GFI MailEssentials for spam filtering (on the same server), and I also have content filtering and recipient filtering enabled on exchange. For GFI, we exported the config we had for GFI on our 2007 server and imported it into the GFI installation
on our Exchange 2013 server. Should I try disabling content and/or recipient filtering on Exchange? Should I try shutting off GFI and send a test email?
I appreciate your time and effort on this!!
I did a message trace on the test email I sent to a non-existent SMTP address on our domain and this is what I got... Not sure how helpful this is :(
Sorry, my account isn't "verified" yet so I can't post pictures. I put the output up here for now. http://andyslights.com/trace.jpg

Can't install Exchange 2013 after previous uninstall (insufficient user privileges with the same user)

I have installed Exchange 2013 on Windows Server 2012, which ist a member of a Windows Server 2012 R2 Domain. All prerequisites and AD modifications were successfully completed and I could install Exchange 2013. Unfortunately I made a mistake with
the target directory and had to uninstal Exchange 2013. If I start the Setup again, it fails in prerequisite check - the current user should not be a member of Enterprise and Schema admin Group, but it's the same user, which comleted the previous Installation
of Exchange 2013! Do you have any idea how to solve this Problem - I'm running out of ideas.

Inhave tried to run setup /PrepareSchema again and get the following error in exchange setup log:
[03.07.2014 19:25:53.0305] [0] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
[03.07.2014 19:25:53.0337] [0] Validating options for the 0 requested roles
[03.07.2014 19:25:53.0383] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
[03.07.2014 19:25:53.0399] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
After removing all Exchange Parts by ADUC (advanced View) and ADSI Edit (Services) I'm able to install Exchnge 2013 again - the uninstall procedure seems not to work in a clean manner.

Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

Hi there,
We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
===
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
===
I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
with the installation or something else needs to be done first?
Thanks in advance.

I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
That would be a huge disaster!
Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
setup /PrepareAD /IAcceptExchangeServerLicenseTerms

Exchange 2013 cros site blank page OWA/ECP

Hello,
I have an issue with a fresh installation of Exchange 2013 SP1.
The are two AD site in different cities, connected by WAN link (site-to site VPN organized by Cisco ASA).
I installed two Exchange servers in Site A (MBX1 and MBX2, both with MBX+CAS roles), and one Exchange server MBX3 in Site B (also both with MBX+CAS roles).
Each Exchange hosts its own mailbox database (DB1, DB2, DB3 respectively), there are no DAG.
Users spread over all databases. For example, user1 has mailbox in DB1, user2 - in DB2, user3 in DB3.
When user1 opens OWA/ECP on CAS server MBX1 or MBX2, he successfully get into his mailbox.
But, if user1 opens OWA/ECP on CAS server MBX3, he get blank page (no error at all).
And vise versa:
When user3 opens OWA/ECP on CAS server MBX3, he successfully get into his mailbox.
But, if user3 opens OWA/ECP on CAS server MBX1 or MBX2, he get blank page (no error at all).
I know, that Exchange 2013 is able to proxy request cross site.
Where are no custom redirects set on IIS.
Also I check IIS (Back End Site) for right certificate.
There are no error in Windows Event log and IIS event Log.
All ports are allowed between sites.
Everything looks good.
What I did wrong? May be I need to enable cross-site OWA proxy in Exchange somewhere?
Or it is a CISCO ASA misconfiguration?
Any help would be appreciated!
Thank You!
Pavel

Hi,
Firstly, I’d like to confirm if all your Exchange server are internet facing servers.
We can try to clear the Forms based authentication on the non-internet facing server.
And here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/85983a21-3922-46f4-b64a-d53c0a2271a7/issues-with-crosssite-cas-redirect-of-owa-users?forum=exchange2010
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Error upgrading form exchange 2010 to exchange 2013

Hello,
I have Exchange 2010 sp3 running on win server 2012 R2 sp1 standanrd. I would like to upgrade to exchange 2013 and I read that installation of exchange 2013 is coexistent with exchange 2010 already installed. But When I try to install exchange 2013 I keep
getting this error :"Exchange server is in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer to recover this Exchange server." But after closing set up the server is still running
fine.

Hi,
Based on my research, the issue can occur when the Exchange server object already exists within Active Directory.
Thus, I’d like to confirm the following information:
1. Does your new Exchange 2013 server have the same server name with the previous one?
2. Have you change your Exchange 2010 server name to legacy.domain.com?
Here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/20bab6f7-56e6-49b9-94df-48707fb915f7/installation-errorfresh-install-on-a-fresh-clean-server-2012?forum=exchangesvrgeneral
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 Get-ServerHealth NotApplicable

Hi All,
I have a new installation of Exchange 2013. SCOM monitoring in place.
I'v noticed that a lot of errors showing on SCOM regarding the HealtSet is showing unhealthy.
But what is strange to me is that when I run Get-ServerHealth I see that the HealtSets that are showing as unhealthy are also in state
NotApplicable.
What does NotApplicable mean, and why is it event in unhealthy state if its not applicable?
Thanks,
Zarko

Hi,
There is no official document explaining the state "NotApplicable" currently.
To troubleshoot health set issue, here is a related blog for your reference.
http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx
Besides, please check if there is any related events logged for further analysis.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013: This mailbox database is associated with one or more active mailboximport / Cannot uninstall exchange

We have a corrupted installation of Exchange 2013 due to installating CU6
New Exchange server is already installed and mailboxes are migrated over, I am now in the process to uninstall the old exchange 2013 so we can decomission it but I get this error when I try to run uninstall
"This mailbox database is associated with one or more active mailbox import,To get a list of all Mailboximport request associated with this database, run Get MailboxImportRequest | ?{ $_.RequestQueue -eq "<Database ID>"}....
But when i run this command I get an error of" The Get-MailboxImportRequest is not recognized as a cmdlet...
Any advise is appreciated
Thanks.

Hi ,
From the error message i came to know few things i have mentioned mentioned below .
If you want to remove the problematic exchange server , you need to remove the existing mailbox import requests.
For that you should need to have the required permission for the user account from which you are trying to execute the command
Just check your user account is having the Mailbox Import Export role permissions .
If you have the required permissions then go ahead and execute the commands
Get-MailboxImportRequest | ft -au ( this is to see how many no of the mailbox import request are available
Remove-MailboxImportRequest
( this command is to remove the entire mailbox import move request)
Once you have done with that , then you start proceeding uninstalling the exchange server .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2013 Unexpected reboot by MSExchangeHMWorker

I have an Exchange 2013 server installed and noticed that the server unexpectedly rebooted itself. It created a dump file and within the dump file it states that it was caused be the MSExchangeHMWorker.
I know that Exchange 2013 has the Managed Availabilty concept and will attempt to "fix" itself if there is an issue however I would like to know why or what prompted exchange to do this so i don't have this in the future. Is there any known
logs that records why this happened? I am not seeing anything in the event logs.
Thanks
Memory dump info below:
5: kd> !analyze -v
* Bugcheck Analysis *
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffe001d1930900, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
----- ETW minidump data unavailable-----
PROCESS_OBJECT: ffffe001d1930900
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xEF_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from fffff8011bc89dcc to fffff8011b7cdfa0
STACK_TEXT:
ffffd000`2b8a79a8 fffff801`1bc89dcc : 00000000`000000ef ffffe001`d1930900 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2b8a79b0 fffff801`1bbac23e : ffffe001`d1930900 00000000`00000000 00000000`00000000 fffff801`1b7e353c : nt!PspCatchCriticalBreak+0xa4
ffffd000`2b8a79f0 fffff801`1ba090e9 : ffffe001`d1930900 ffffe001`d8eb6900 ffffe001`d1930900 ffffe001`d1930900 : nt! ?? ::NNGAKEGL::`string'+0x7bce
ffffd000`2b8a7a50 fffff801`1ba08e76 : ffffffff`ffffffff ffffe001`d8eb6900 ffffe001`d1930900 ffffe001`d9d89880 : nt!PspTerminateProcess+0xe5
ffffd000`2b8a7a90 fffff801`1b7d97b3 : ffffe001`d1930900 ffffe001`d9d89880 ffffd000`2b8a7b80 00000000`ffffffff : nt!NtTerminateProcess+0x9e
ffffd000`2b8a7b00 00007ffc`4bc5afca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`2d58e3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`4bc5afca
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION:
FAILURE_BUCKET_ID: 0xEF_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: 0xEF_MSExchangeHMWo_IMAGE_wininit.exe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xef_msexchangehmwo_image_wininit.exe
WWT IT

Hi,
What is the solution to fix this issue, even though we have windows 2012 R2 Standard installation o Exchange 2013 CU6
Symbol search path is: C:\Symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (20 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff801`e8e0a000 PsLoadedModuleList = 0xfffff801`e90e0370
Debug session time: Tue Dec 23 17:48:33.358 2014 (UTC + 2:00)
System Uptime: 4 days 6:44:58.859
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe00003744900, 0, 0, 0}
----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
Followup: MachineOwner
3: kd> !analyze -v
*                        Bugcheck Analysis
CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffe00003744900, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
----- ETW minidump data unavailable-----
DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump
PROCESS_OBJECT: ffffe00003744900
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xEF_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff801e9424dd0 to fffff801e8f591a0
STACK_TEXT:
ffffd001`4cf799a8 fffff801`e9424dd0 : 00000000`000000ef ffffe000`03744900 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd001`4cf799b0 fffff801`e934479c : ffffe000`03744900 00000000`00000000 00000000`00000000 fffff801`e8f6ef90 : nt!PspCatchCriticalBreak+0xa4
ffffd001`4cf799f0 fffff801`e91afc11 : ffffe000`03744900 ffffe801`ecf83900 ffffe000`03744900 ffffe000`03744900 : nt! ?? ::NNGAKEGL::`string'+0xba4c
ffffd001`4cf79a50 fffff801`e91af99e : ffffffff`ffffffff ffffe801`ecf83900 ffffe000`03744900 ffffe000`1b3e5080 : nt!PspTerminateProcess+0xe5
ffffd001`4cf79a90 fffff801`e8f649b3 : ffffe000`03744900 ffffe000`1b3e5080 ffffd001`4cf79b80 00000000`ffffffff : nt!NtTerminateProcess+0x9e
ffffd001`4cf79b00 00007ff8`27ef193a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`235ce178 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`27ef193a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION:
FAILURE_BUCKET_ID: 0xEF_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: 0xEF_MSExchangeHMWo_IMAGE_wininit.exe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xef_msexchangehmwo_image_wininit.exe
FAILURE_ID_HASH: {3f0b292e-4bc2-5c6e-99a7-f9a74df1101c}
Followup: MachineOwner
Amit

Outlook Cannot Logon Error - Exchange 2013

Hi all,
I simply cannot create an Outlook (2007 or 2010) account to connect to my new installation of Exchange 2013 in Windows Server Essentials environment:
1) Using autodiscover:
I get green ticks for "Establishing network connection and "Search for [email protected] server
settings". At "Log on to Server" I get the error message "The action cannot be completed. The connection to
Microsoft Exchange
is unavailable. Outlook must be online or connected to complete this action"
2) Using manual configuration:
Outlook Anywhere (RPC over HTTP) Exchange Proxy settings configured using the internal FQDN for the Exchange
server and negotiate for authentication. Clicking "check name" button to resolve servername (internal FQDN) and
username (user email address) gives error, "Outlook cannot logon. Verify you are connected to the network and are
using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be
online or available to complete this action.
3) I can ping Exchange server using hostname and FQDN
4) PC is member of the domain
4) I have verified Exchange certiicate is installed on the client PC (although in the "Other People" certificates folder. Makes no difference when moved to the Trusted Root Certification Authority folder.
5) I can successfully connect to the user mailboxes via OWA
I've been working to resolve this issue for several days now and am at a complete loss as to what to do next to get this up and running.
Any assistance will be greatly appreciated.
RS
RS

Hi RS,
Did you try to run Office Configuration Analyzer Tool (OffCAT) only for Outlook and check the results? If not, proceed and run the Tool and post the results.
Additional info how to run the tool and check the results, you can find here: http://blogs.technet.com/b/catastrophic_failure_joannav/archive/2013/10/30/how-to-view-offcat-report-that-was-created-on-another-computer.aspx
If no
Regards, Catastrophic Failure "JV"

Installation MS Exchange 2013 Failed

Similar Messages

Maybe you are looking for