Cannot install Windows Exchange 2013 SP1 64x non-checked build

Hello every one.
I have a problem to setup a lab asigment for school.
I have 2 Windows 2012 standard server
1e AD, DNS, IIS
2e Exchange 2013 SP1 64x
i prepared AD and installed al the features needed for AD and the Exchange server.
But when i run the readines check before i install Exchange 2013 i get to following warning
Warning:
A checked build of the operating system is installed. This can cause system instability issues including crashes, hangs, and other performance problems. It's highly recommended
that the operating system be reinstalled with a non-checked build.
For more information, visit: http:// technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.OSCheckedBuild.aspx
I cant find out what to do, thear is no Boot.ini file in Windows server 2012, any one any idea's to solve this problem
Thanks for the help,
Greatings,

Hi,
Agree with Ed. A checked build Windows is used for debug. Before installing Exchange 2013, please make sure that you use a free build. I'm afraid that you need to reinstall the OS.
What's more, you can refer the following screenshot to determine which Windows build is running. Generally, it should be Free build.
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

Seemingly successful install of Exchange 2013 SP1 turns into many errors in event logs after upgrade to CU7

I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server.
I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online).
I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me).
Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
Issue 1)
After each reboot I get a Kernel-EventTracing 2 error. I cannot find anything on this on the internet so I have no idea what it is.
Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
Issue 2)
I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
https://support.microsoft.com/kb/2870416?wa=wsignin1.0
One of the perf counters fails to register using the script from the link above.
66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
New-PerfCounters : The performance counter definition file is invalid.
At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
+    New-PerfCounters -DefinitionFileName $f
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo
: InvalidData: (:) [New-PerfCounters], TaskException
    + FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
   12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
But that one seems unrelated to the ones that still throw errors.
Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: 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.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: 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.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: 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.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Issue 3)
I appear to have some issues related to the healthmailboxes.
I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
I reran setup /prepareAD to try and remedy this but I am still getting some.
Issue 4)
I am getting an MSExchange RBAC 74 error.
(Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
Issue 5)
I am getting MSExchange Assistants 9042 warnings on both databases.
Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server.
If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
Issue 6)
At boot I am getting an MSExchange ActiveSync warning 1033
The setting SupportedIPMTypes in the Web.Config file was missing.
Using default value of System.Collections.Generic.List`1[System.String].
I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.

Hi Eric
Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time.
I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”.
If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering.
Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users.
I then applied an address policy to them and gave it the highest priority.
Then I set a default email address policy for the entire organization.
After reinstalling Exchange all of my system mailboxes were created with the internal domain name.
So issue number 3 above has not come up.
For issue number one above I have created a new thread:
https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
For issue number four I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
Issue number Five I have managed to recreate and get rid of in more than one way.
If I create a new database in ECP and set the database and log paths where I want, then this error will appear.
If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear.
The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service.
If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away.
So my off hand guess is that these are caused by orphaned system mailboxes.
For issue number six I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
So for the remainder of this thread we can try and tackle issue number two which is the perf counters.
The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7.
Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five.
Using all of your suggestions so far has not removed these 5 remaining errors either. Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
to make them go away if possible.

Cannot install Windows server 2003 SP1

Hi all,do you know something about "Not enough free space" issue when upgrading windows 2003 under bootcamp with Service Pack 1?
I'm going crazy but it seems it is an issue related to "boot camp" or well "on macintosh install".
I get an error message when istalling windows 2003 SP1 and it is :" Space on disk in C:..... not sufficient for Service Pack 1 installation. Installer require 3 megabyte additional space.
C: 17 Gb free
i've tried on external HD 180GB not working...
This check is on Space required for uninstall files....
Any suggestions?
Thanks!

Considering the fact that Boot Camp only supports XP SP2, it comes as no surprise that you're having issues with an OS other than XP.
Either way, your question pertains to Boot Camp, so you should re-post it in the Boot Camp discussions:
http://discussions.apple.com/forum.jspa?forumID=1165
Or better yet, the error seems to be with Windows, and completely unrelated to Boot Camp so you should post your question on a Windows discussion board as well.

Exchange 2013 SP1 - healthsets failing

Hi,
I have recently installed two Exchange 2013 SP1 servers in different environments and are experiencing issues on both. Issues that I haven't seen on Exchange 2013 without SP1.
I have 6 healthsets which are unhealthy.
Autodiscover...
ActiveSync.P...
EWS.Proxy
OAB.Proxy
Outlook.Proxy
OutlookMapiH...
I found this article:
http://technet.microsoft.com/en-us/library/ms.exch.scom.ecp.proxy(v=exchg.150).aspx
Which describes, that try to restart the app pool, then an iisreset - and lastly reboot the server. Tried all and none of them helped.
But then I found this error in the Exchang event log:
RecycleApplicationPool-MSExchangePowerShellAppPool-RpsDeepTestPSProxyRestart: Throttling rejected the operation
Which fails almost every minute.
And I guess that this could be the issue. But I can't figure out which throttling that is causing this.
Any one else with this issue on Exchange 2013 SP1?
Thanks in advance.
/Kim

Hi,
I have seen a lot of similar issues with health manager service. For IIS services, we can safely ignore these warnings. Personal experience, we just need to monitor whether there are related
error reports in event log.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 SP1 Installation Errors I Cannot Resolve

Good Afternoon All -
Note: I updated this post an hour after posting. Still no solution, but please see updated info at end of this post)
I'm trying to introduce Exchange into an existing, small environment. The server I'm trying to install it onto is an SBS 2011 server (single server.) Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
had attempted to uninstall it before. Yes, it's being installed onto a server with a DC. I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
Before I started, I made sure all Exchange data had been removed. I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
When I try to install Exchange 2013 SP1, I get the below errors. I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one. I've restarted the server many times when making
changes or applying various updates and still get flagged to restart during installation. I've tried the SBS 2011 repair disc as well, but had many issues with it. In all honesty, the whole server needs to be wiped and re-installed, but
cannot do at this point.
Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below. Also below are system specs. The only edit I made in them is a find/replace for server and domain name.
ExchangeSetupLogs Folder
System Specs
Xeon E31270 3.4Ghz
16gb RAM
Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
C:\ - RAID 1 = 500gb
D:\ - SATA HDD = 320gb
E:\ - SATA HDD = 320GB
Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
Any help would be appreciated - Thanks!
Error:
This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
Without this update, the Outlook Anywhere feature may not work reliably.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
Error:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.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
Ben K.
UPDATE
I just tried fixing a few things and tried again. Still no luck. Below is what I changed as well as the errors received. Only option was Retry. Can I just not install it onto this environment?
What I Changed
Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
Installed KB2619234 for Outlook Anywhere
Installed 12 updates - Server fully patched
Exchange Setup Errors
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.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
Thanks Guys -

Hi,
Agree. Windows Server 2011 SBS x64 can be the problem.
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

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
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 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation

Hi,
We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
onto them. This all went fine and the servers are running stable.
We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
order.
After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
Exchange Health service has killed WININIT which causes the crash.
Thanks!!!
The crash dump text is below:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80192ebb30, Terminating object
Arg3: fffffa80192ebe10, Process image file name
Arg4: fffff80001dc37b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa80192ebb30
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001e4cab2 to fffff80001abebc0
STACK_TEXT:
fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
Followup: MachineOwner

Hi Darrkon,
I suggest checking the status of the HealthMailbox on each of servers.
Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted. Once that service is restarted, it will recreate any mailboxes that it needs.
More details in the following similar thread, just for your reference:
BSOD after creating DAG
http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
Thanks
Mavis
Mavis Huang
TechNet Community Support

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.

Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
move them to the new server and mount them and relocate the mailboxes?
Frank.

Hi,
According to your description, I recommend you consider using DAG to achieve your requirement.
The following steps for your reference:
1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
3.After replication, you can mount all the databases on the new server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
Please Unmark it!
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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.

Cannot write email body in OWA with Exchange 2013 SP1 CU6

Hi,
I have a problem with Exchange 2013 SP1 with CU6.
All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
Have you an idea ?
Thanks in advance!
Sebastien

Hi,
After contacting Microsoft support, we have found the solution.
The problem appear after we have recently install the patch described in this KB 2997209:
https://support.microsoft.com/kb/2997209?wa=wsignin1.0
But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
No need to reboot, or restart IIS, it's working after that!
@+
Sébastien

Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

Hi Everybody,
For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
So i did the traditional cmdlet
Get-SendConnector
Set-SendConnector -Indentity "connector name" -Port 551
Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
When i type Get-ExCommand
Any reference to SendConnector and ReceiveConnector are not on the list.
Am I missing somethings? This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials. However, i very much doubt the on-premise installation add-on to SBS would cause any issues
to missing cmdlets.
I searched all over the internet and found nothing.
Now my biggest fear is to re-install Exchange and import the mailboxes manually.
Any help is greatly appreciated.
MattLok

Hello
check role asigment for your user:
Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
sorry my english

Cannot install Windows 8.1 via Boot Camp on MBPr 13" Early 2013; tried almost everything.

Hi guys,
yesterday, I decided to install Windows 8.1 on my Mac using Boot Camp. I tried to install it, but the first attempt ended into booting to the screen, where it says "Cannot find any bootable device" or something like that. So I googled it up and then tried the EFI Boot. The EFI Boot booted into the Windows installation properly, but I cannot choose the partition I want to install it on. I tried partitioning it in Disk Utility using Tuxera to NTFS, I tried formatting it in the installation itself, always restarted between the processes, I tried to delete the partition and create a new one in the installation, but no luck. I am still stuck on the error "Cannot install Windows on MBR partition. Please, choose a GPT partition". I have a 256GB SSD disk. I browsed the problems and solutions for 3 hours, but no luck. None of the solution helps. The only solution that would work I guess is if I don’t boot into EFI, but into the BIOS installation. But when I do that, I get the "Cannot find any bootable device", so a dead end here. I also tried the tips where they say to remove the USB stick when the Windows installation starts, but didn’t help either.
I am installing using a bootable USB drive, I do not have a Superdrive and cannot even lend it or something like that.
I am really desperate, can anyone please help me?
Thanks in advance,
DavidKop_

Some people have been successful installing 8.1 (me, for instance) despite it not being supported. However this seems to be hardware dependent.
I would have expected the normal WININSTALL option to be available on a Bootcamp-created USB, not just the EFI boot option.
It really depends on whether Bootcamp is creating a hybrid MBR when it creates the Bootcamp partition. Some later model Macs do not. On the Macs that do not create the hybrid MBR Windows may install in EFI mode.
If you remove everything and stretch the Macintosh HD back to the full size of the disc again then reboot and when the system restarts begin the Bootcamp installation again but do not let it restart at that time, you can then run the following code in the terminal and report its output we will be able to see if a hybrid MBR has been created (this is after the partition has been created by Bootcamp, but before it reboots).
sudo fdisk /dev/disk0

Exchange 2013 SP1 database missing?? New install of Exchange 2007 co-exist

Hi all,
Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.
When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:
The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'
Why would I get this error? The install itself was problematic so I am concerned something is broke.
Thank you in advance.

Hello,
Firstly, I recommend you check if the server name "*\ExchangeServerName" exists on DC via ADUC (select Computers).
Secondly, please run the get-exchangeserver | fl name cmdlet to check your exchange server name.
And then please check the exchange setup log to check if the exchange 2013 server is installed successfully. If not, please check if there is any error in setup log.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

HTTP 500 ERROR AFTER EXCHANGE 2013 SP1 INSTALL

Help after exchange 2013 sp1 new install unable to get to the ECP or OWA page with HTTP 500 error in IE the install went ok but not sure what can be causing the error any help would be appriciated.
EXCHANGE 2013--SP1 on WIN2K12--R2 Standard
TY
M4326

See the following:
http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
CK

Lync integration not working after Exchange 2013 SP1 is installed...

Hi,
I have two Exchange 2013 servers running and everything is fine, almost.
The problem is that on the first server we had OWA with Lync integration working before installing SP1, but after the installation of SP1, it doesn't Work any more.
The second server was installed with SP1 from the start, but we can't get the Lync integration to Work on this one either..
When we log in to OWA, it just starts to sign in but then says "there was a problem signing in, if this continues please contact your helpdesk"
I have checked the Exchange server for events, and i can see the event ID 112 everytime i recycle the Application Pool, so there are some connection between Exchange and Lync..
Have any of you Guys seen or experienced any thing like this?
Thanks in advance.
Regards
Kenneth

Hi,
I recommend that you refer to the following article to troubleshoot the issue:
Troubleshooting tips for Exchange 2013 OWA IM Integration to Lync 2013
This post describes how to configure Exchange 2013 OWA to have IM integration to Lync 2013. Here I would like to give some troubleshooting tips in case you can't get the integration to work.
In addition, here is a similar thread for your reference:
Lync 2013 with Exchange 2013 SP1 OWA integration failed
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Cannot install Windows Exchange 2013 SP1 64x non-checked build

Similar Messages

Maybe you are looking for