Exchange 2013 cu3 setup fails with 'problem... validating the state of Active Directory... supplied credential... invalid'

Windows Server 2013; Exchange Server 2013 with Cumulative Update 1
Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with
[xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid. See the Exchange setup log for more information on this error.
[xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
[xxx] [0] [ERROR] The supplied credential is invalid.
(Crosses - XXX - replace original values.)
I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely
conincidental:
The Security System could not establish a secured connection with the server
ldap/xxx.xxx/[email protected] No authentication protocol was available.
Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

Hi vhr1,
Based on my knowledge, the Event ID 40961 is a warning message.
This behavior occurs when we restart the server that was promoted to a DC. The Windows Time service tries to authenticate before Directory Services has started.
Found some resources for your reference even if the Exchange Version is mismatched:
http://blogs.technet.com/b/jhoward/archive/2005/04/20/403946.aspx
http://support.microsoft.com/kb/823712/en-us
About the error message, "Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid."
The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.
Found a similar thread for your reference, hope it is helpful:
http://social.technet.microsoft.com/Forums/en-US/98e26ad6-8e43-4ef5-8ff9-e9fee6e76bda/bind-operation-is-invalid?forum=exchangesvrdeploylegacy
Feel free to contact me if there is any problem.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

"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 se

Team,
I am trying to Install Exchange on my Lab, getting below error
message.
The Schema Role is installed on Root Domain and trying to install
exchange on Child domain.
1 Root Domain - 1 Child domain. both are located on single site.
“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 and wait for
replication to complete.”
Followed below articles:
http://support.risualblogs.com/blog/2012/02/21/exchange-2010-sp2-upgrade-issue-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-sche/
http://www.petenetlive.com/KB/Article/0000793.htm
transferred the schema roles to different server on root domain, still no luck.
can someone please help me.
regards
Srinivasa k
Srinivasa K

Hi Srinivasa,
I guess, you didn't completed the initial setup schemaprep and adprep before starting the installation. You can do it as follows:
1. Open command Prompt as administrator and browse to the root of installation cd and run Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
After finishing this,
2. Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms
3. To prepare all domains within the forest run Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms. If you want to prepare a specific domain run Setup.exe /PrepareDomain:<FQDN of the domain you want to prepare> /IAcceptExchangeServerLicenseTerms
4. Once you complete all of the 3 steps, install the pre-requisities for Exchange 2013
5. Finally, run the setup program
Hope this will help you
Regards from Visit ExchangeOnline |
Visit WindowsAdmin

Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site

Have an existing ex2010 sp3 organization.
Could not run ex2013cu1 setup from my newly built 2012 server, getting the error in the subject line. I used the command line to run the AD preparation steps successfully from my 2012 DC/GC, then tried to run setup again from the new 2012 server and
still get the same error. The error itself in the log is pretty useless:
[05/07/2013 01:19:13.0137] [0] **********************************************
[05/07/2013 01:19:13.0137] [0] Starting Microsoft Exchange Server 2013 Cumulative Update 1 Setup
[05/07/2013 01:19:13.0137] [0] **********************************************
[05/07/2013 01:19:13.0152] [0] Local time zone: (UTC-08:00) Pacific Time (US & Canada).
[05/07/2013 01:19:13.0152] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[05/07/2013 01:19:13.0152] [0] Setup version: 15.0.620.29.
[05/07/2013 01:19:13.0152] [0] Logged on user: DOMAIN\ADMINISTRATOR.
[05/07/2013 01:19:13.0168] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0168] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0215] [0] Command Line Parameter Name='sourcedir', Value='\\h1\f$\junk\installers\server\Exchange\2013cu1'.
[05/07/2013 01:19:13.0215] [0] Command Line Parameter Name='mode', Value='Install'.
[05/07/2013 01:19:13.0215] [0] RuntimeAssembly was started with the following command: '/sourcedir:\\SERVER\f$\junk\installers\server\Exchange\2013cu1 /mode:Install'.
[05/07/2013 01:19:13.0215] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0793] [0] Finished loading screen CheckForUpdatesPage.
[05/07/2013 01:19:38.0762] [0] Finished loading screen UpdatesDownloadsPage.
[05/07/2013 01:19:40.0496] [0] Starting file's copying...
[05/07/2013 01:19:40.0496] [0] Setup copy files from '\\SERVER\f$\junk\installers\server\Exchange\2013cu1\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
[05/07/2013 01:19:40.0700] [0] Finished loading screen CopyFilesPage.
[05/07/2013 01:19:40.0840] [0] Disk space required: 1292445007 bytes.
[05/07/2013 01:19:40.0840] [0] Disk space available: 23767240704 bytes.
[05/07/2013 01:19:59.0762] [0] File's copying finished.
[05/07/2013 01:19:59.0965] [0] Finished loading screen InitializingSetupPage.
[05/07/2013 01:20:02.0934] [0] Setup is choosing the domain controller to use
[05/07/2013 01:20:09.0325] [0] Setup is choosing a local domain controller...
[05/07/2013 01:20:11.0794] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
See the Exchange setup log for more information on this error.
[05/07/2013 01:20:11.0794] [0] [ERROR] Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
[05/07/2013 01:20:11.0809] [0] Setup will use the domain controller ''.
[05/07/2013 01:20:11.0809] [0] Setup will use the global catalog ''.
[05/07/2013 01:20:11.0825] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'.
[05/07/2013 01:20:11.0919] [0] Exchange organization container for the organization is 'CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'.
[05/07/2013 01:20:11.0966] [0] Setup will search for an Exchange Server object for the local machine with name 'WEX1'.
[05/07/2013 01:20:12.0028] [0] No Exchange Server with identity 'WEX1' was found.
[05/07/2013 01:20:12.0044] [0] The following roles have been unpacked:
[05/07/2013 01:20:12.0044] [0] The following datacenter roles are unpacked:
[05/07/2013 01:20:12.0044] [0] The following roles are installed:
[05/07/2013 01:20:12.0059] [0] The local server does not have any Exchange files installed.
[05/07/2013 01:20:12.0075] [0] Server Name=WEX1
[05/07/2013 01:20:12.0137] [0] Setup will use the path '\\SERVER\f$\junk\installers\server\Exchange\2013cu1' for installing Exchange.
[05/07/2013 01:20:12.0137] [0] The installation mode is set to: 'Install'.
[05/07/2013 01:20:27.0591] [0] An Exchange organization with name 'DOMAIN' was found in this forest.
[05/07/2013 01:20:27.0591] [0] Active Directory Initialization status : 'False'.
[05/07/2013 01:20:27.0591] [0] Schema Update Required Status : 'False'.
[05/07/2013 01:20:27.0591] [0] Organization Configuration Update Required Status : 'False'.
[05/07/2013 01:20:27.0591] [0] Domain Configuration Update Required Status : 'False'.
[05/07/2013 01:20:27.0841] [0] Applying default role selection state
[05/07/2013 01:20:27.0872] [0] Setup is determining what organization-level operations to perform.
[05/07/2013 01:20:27.0872] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN.
[05/07/2013 01:20:27.0872] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[05/07/2013 01:20:27.0888] [0] InstallModeDataHandler has 0 DataHandlers
[05/07/2013 01:20:27.0888] [0] RootDataHandler has 1 DataHandlers
[05/07/2013 01:20:27.0903] [0] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See
the Exchange setup log for more information on this error.
[05/07/2013 01:20:27.0935] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
See the Exchange setup log for more information on this error.
[05/07/2013 01:21:04.0154] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:21:04.0154] [0] End of Setup
[05/07/2013 01:21:04.0154] [0] **********************************************

Hi,
The cause is clearly described in the log:
[05/07/2013 01:20:11.0794] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
See the Exchange setup log for more information on this error.
[05/07/2013 01:20:11.0794] [0] [ERROR] Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
I'd suggest you check NIC settings and AD configuration.
Hope it is helpful.
Fiona Liao
TechNet Community Support

Exchange 2013 SP1 Setup fails

I am getting very frustrated. It really shouldn't take over a week to install Exchange.
I have two domain controllers, Windows 2003 and Windows 2008 R2. The 2008 is now all Operations Masters for all roles.
I have a clean install of W2K8 R2 SP1 installed under Hyper-V on a separate physical W2K8 server. Before starting the install I used ADSIEdit to ensure there was nothing left in the AD of prior Exchange install attempts. This is the first and only installation
of Exchange.
I am running the install as the Domain\Administrator and naturally that account is a member of all the appropriate security groups. RSAT are installed on the Exchange server and using them to access Users and Computers clearly shows this. The install fails
with the errors below, all of which appear to be incorrect.
*** BEGIN ERROR ***
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:
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: Couldn't find the Enterprise Organization container. See the Exchange setup log for more information on this error.
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:
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:
This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://go.microsoft.com/fwlink/?LinkId=262357). Please install the update, and then restart Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7WindowsIdentityFoundationUpdateNotInstalled.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 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
*** END ERROR
Why can't Exchange installation see the AD when everything else can?

It appears that these error messages are pure fiction. I went back to ADSI Edit and removed some MS Exchange container and then reran setup /prepareschema again followed by setup /preparead and finally setup /mosde:install /role:clientaccess,mailbox and
it churned away for a long time, apparently working.
It appears than when it says you aren't a member of Schema Admins and that it can't access Active Directory, what it really means is it could find the AD just fine, but didn't like what it saw.
My guess would be very sloppy programming in which the low level error doesn't bubble up and so when something fails it just assumed you didn't have permissions.
It's not quite finished yet, but I am beginning to believe it will finish. So that's almost 6 days of non stop effort to install Exchange. It's hard top believe they are allowed to charge for this stuff.

Exchange 2013 SP1 setup fails at prerequisite Analysis

I installed a completely new server network with Hyper-v 2012R2
I installed two virtual 2012R2 servers: DC01 as the Domain Controller of "testdomain.local" and EX01 as the Exchange server.
EX01 is joined the domain "testdomain" from DC01
I log in on EX01 with an in AD created testdomain\exadmin account who is member of domain admins, enterprise admins, schema admins, administrators and group policy creator owners.
I have run the command 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, Telnet-Client, RSAT-ADDS
on EX01
I have installed the Microsoft Unified Communications Managed API 4.0
Then I run the Exchange 2013 SP1 setup and the prerequisite check gives the following errors:
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: Active Directory server is not available. Error message: Active directory response: The LDAP server is unavailable. See the Exchange setup log for more information on this
error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.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
I can connect with the Active Directory Sites and Domains and other applets to the AD. So Why these errors???
HELP!
Regards, Manu
Manu van Winkel

Hi, thanks for the answer.
I restarted the server and did the "run as administrator": same result.
The first errormessage in the exchangesetup.log is:
[ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server is not available. Error message: Active directory response: The LDAP server is unavailable. See the Exchange setup log for more information
on this error.
When I run dcdiag /s:DC01 from EX01 it passes all tests except:
DFSREvent "The RPC server is unavailable"
KccEvent "The RPC server is unavailable."
SystemLog "The RPC server is unavailable."
Could these be of any influence?
Running dcdiag on DC01 passes all tests.
The only thing I changed after setting up DC01, was changing the fixed IP-adres from 192.168.25.3 to 192.168.25.2, but I ran ipconfig /flushdns and ipconfig /registerdns and dcdiag /fix afterwards.
The only roles installed on DC01 are AD DS (I tried installing exchange before and after adding the AD DS role), AD, DNS, DHCP and Fileservices
I don't know where to look anymore....
Manu van Winkel

Exchange 2013 - Mailbox Setup Failed "The following error was generated when "$error.Clear()" 7 of 14

I am getting the following error when I'm setting up the mailbox server as I'm currently doing a test virtual machine throughHyper-V, it seems to happen during the transport service phase of the installation which is 7/12
Do i know need a D:\ drive for the mailbox server to work? as in my test i only have a c:\ drive but no d:\ drive
Error:
The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;
                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                    $useAttachMode = $true;
                else
                    if ($RoleIsDatacenter -eq $true)
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                $useAttachMode = $true;
                if ($useAttachMode -eq $true)
                    &$command -action a -dataFolder $dataFolderPath -silent;
                else
                    try
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    catch
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                        catch
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
+ " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
        " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".
Warning:
An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;
                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                    $useAttachMode = $true;
                else
                    if ($RoleIsDatacenter -eq $true)
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                $useAttachMode = $true;
                if ($useAttachMode -eq $true)
                    &$command -action a -dataFolder $dataFolderPath -silent;
                else
                    try
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    catch
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                        catch
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
+ " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
        " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".


Hi
Most likely for these kind of issues its better you can delete the hyper-v machine and create a new os , ensure all the prerequisite are met and install the Exchange since this is a new installation.
But as a try you can try giving full access to the admin account to the data folder  'C:\Program
Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. which is giving the error and rerun the setup
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Exchange 2013 Domain Prep Fails: Setup /prepareschema, setup /PrepareAD, Setup /PrepareDomain

Whenever I try to prep for a 2013 exchange install I always get:
"earlier versions of the server roles that are installed were detected"
whenever I try to run Setup /prepareschema OR setup /PrepareAD OR Setup /PrepareDomain
I am working on a Server 2012 standard machine with Exchange 2010 currently installed. This server is a DC (bad I know), DNS, DHCP.
I am trying to prep the domain so that I can install Exchange 2013 on a VM and eventually remove Exchange 2010 from the organization altogether.
There are no other domain controlelrs in the domain. The domain started life as a SBS 2003 machine which was demoted and removed once the server 2012 box was up with exchange 2010 running.
Any help would be greatly appreciated.
Here is some info that may help:
1. PrePare Schema
Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
Ran setup /PrepareSchema
This command should perform the following tasks:
A: Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with
Exchange 2013 specific attributes. The LDIF files are copied to the Temp directory and then deleted after they are imported
into the schema.
B: Sets the schema version (ms-Exch-Schema-Verision-Pt) to a Exchange 2013 value.
This command fails with: Earlier versions of server roles that were installed were detected.
First I confirmed that administrator account for domain is a member of schema admins and enterprise admins.
Next I ran asdiedit.
I navigated to: "CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=BDA,DC=LAN"
and reviewed the current "rangeUpper" attribute.
The ms-Exch-Schema-Verision-Pt is not updated to CU3 range Upper setting.
The current range upper 14734 which means its still at Exchange 2010 SP3 settings.
In short, updaing the schema fails.
2. Prepare Active Directory
Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
setup /PrepareAD [/OrganizationName:<organization name>]
This command fails with: Earlier versions of server roles that were installed were detected.
schema update version 56
I began reviewing the long, long list of the following containers and objects under
CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
which are required for Exchange 2013:
missing cn=Auth Configuration
missing CN=ExchangeAssistance
missing CN=Monitoring Settings
missing CN=Monitoring Settings
missing CN=Monitoring Settings
missing CN=Workload Management Settings
Checked Management role groups within the Microsoft Exchange Security Groups OU
missing Compliance Management group --- Manually created this entry
Step 3 Prepare Domain:
Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
Ran setup /PrepareDomain
This command fails with: Earlier versions of server roles that were installed were detected.
confirmed the following:
ObjectVersion property fails as it is still set to Echange 2010 sp3 - 13040
You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers-DONE
The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.-DONE
On each domain controller in a domain in which you will install Exchange 2013, the Exchange Servers USG has permissions
on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.-DONE
Thanks.

Whenever I try to prep for a 2013 exchange install I always get:
"earlier versions of the server roles that are installed were detected"
Hi,
That tells us that you are trying to run the prep on your combined DC and Exchange 2010 Server - That will not work. Run it on the Server where you plan to install Exchange 2013.
It is not mandatory to run this before the actuall Exchange install - It will run automatically for you, if it hasn't been done already and if you are logged on with an account with the proper permissions.
Martina Miskovic

Exchange 2013 CU3 Fails "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception."

I can't get Exchange 2013 to install in our Server 2008 R2 infrastructure. Setup fails with the following error when preparing AD. This is running on Server 2008 R2 SP1 VM's.
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Organization Preparation
FAILED
     The following error was generated when "$error.Clear();
        install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

I have set the PowerShell Execution Policy to unrestricted. After running setup /PS I get the following output
PS C:\Windows\system32> cd c:\temp\ex2013cu3
PS C:\temp\ex2013cu3> ./setup /ps /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Extending Active Directory schema
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation completed successfully.
PS C:\temp\ex2013cu3>
The installation was started at 10:13am and hung for sometime at 94% of the prereq stage. Installation finally completed at 10:47am. The errors seem to indicate that setup will continue. However upon running setup /prepareAD the installation hangs for sometime
at 21% of Organization Preparation before finally failing with the following output....
PS C:\temp\ex2013cu3> ./setup /prepareAD /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Organization Preparation
FAILED
     The following error was generated when "$error.Clear();
        install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS C:\temp\ex2013cu3>

Test-ReplicationHealth Database Redundandacy and Database Avaliability *FAILED* Exchange 2013 DAG setup

Trying to setup DAG between 2 exchange 2013 servers - one of them being in the remote location with physical point to point line. We have no firewall rules between 2 locations
EX01 ( on site)
EX02 (remote)
ETH01 10.11.1.2/24 - MAPI                       ETH01 10.11.13.15/24
ETH02 10.0.0.1/30 - REPLICATIOn            ETH02 10.0.0.2/30 - REPLICATION
Witness server is in 3rd remote location
These are the test results I get from Test-ReplicationHealth and Cluster Network Validation
I also run a Nmap command to make sure udp port 3343 is open on both sides
alex serdyukov

Hi,
The error message said that current Redundancy Count was 1 but expected Redundancy Count was 2. Therefore, Database 'IT2013' does not have enough copies configured to meet the validation criteria.
Please replicate that database to another server at least. We can refer to Hinte's suggestion to
add another copy for the database 'IT2013' in the DAG then check whether the issue persists.
Regards,
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]
Winnie Liang
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 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

Hi,
We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers. Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
problems or the Exchange server is down for maintenance".
Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM. Everything is setup as per the Tech-net recommendations.
Checked both these articles but still it is not working:
http://support.microsoft.com/kb/2839517
http://support.microsoft.com/kb/2834139
Please let me know if there are any other ideas.
Raman

Hi,
I recommend you refer to the following articles to troubleshoot the issue:
Troubleshooting Mailbox Auto-Mapping : Autodiscover
Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
correctly
Troubleshooting Mailbox Auto-Mapping : Permissions
When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 CU3 Databases only activate on one mailbox server

Hi, guys
I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will be activated on the mailbox
server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
This caused the database activated on another server.
And I got the message from SCOM, like this:
Alert: Health Set unhealthy
Source: test-mbx - Outlook.Protocol
Path: test-mbx.contoso.local;test-mbx.contoso.local
Last modified by: System
Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
Latency: 00:00:00.0320000
ActivityContext:
Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log:     Mailbox logon verification
        EMSMDB.Connect()
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - ErrorDetails =
        - RespondingRpcClientAccessServerVersion
= 15.0.712.4012
Latency = 00:00:00.0303884
        - ActivityContext =
    EMSMDB.Connect() completed successfully.
        EMSMDB.DoRpc(Logon)
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
        - ErrorDetails =
        - Latency = 00:00:00.0018801
        - ActivityContext =
    EMSMDB.DoRpc(Logon) failed.
    Task produced output:
    - TaskStarted = 11/12/2013 5:15:25 AM
    - TaskFinished = 11/12/2013 5:15:25 AM
    - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
State               Name
TargetResource                     HealthSet
AlertValue     ServerComponent
NotApplicable       OutlookMapiHttpDeepTestMonitor
Outlook.Protocol              Unhealthy      None
NotApplicable       OutlookRpcDeepTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookRpcSelfTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookMapiHttpSelfTestMonitor                                             Outlook.Protocol
Healthy        None
NotApplicable       PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
This test is a cause that mailbox databases in DAG is doing failover to another server
Log Name:      Application
Source:        MSExchangeRepl
Date:          12.11.2013 4:49:46
Event ID:      3169
Task Category: Service
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      test-mbx-2
Description:
(Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="16388">3169</EventID>
    <Level>4</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
    <EventRecordID>1606248</EventRecordID>
    <Channel>Application</Channel>
    <Computer>test-mbx-2.contoso.local</Computer>
    <Security />
</System>
<EventData>
    <Data>DB-01</Data>
    <Data>test-mbx.contoso.local</Data>
    <Data>test-mbx-1.contoso.local</Data>
    <Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
</EventData>
</Event>
I don't know why, anyone know what's the problem?
Thank you.
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Hi,
After deleting all the health mailboxes and restart
the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
[PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
rtvalue -AutoSize
Server state Name AlertValue
MAILBOX1 OutlookRpcDeepTestMonitor Healthy
MAILBOX1 OutlookMapiHttpDeepTestMonitor Unhealthy
MAILBOX1 OutlookRpcSelfTestMonitor Healthy
MAILBOX1 OutlookMapiHttpSelfTestMonitor Healthy
MAILBOX1 PrivateWorkingSetWarning....cclientaccess.service Healthy
MAILBOX1 PrivateWorkingSetError....rpcclientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeWarning....ientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeError....clientaccess.service Healthy
MAILBOX1 ExchangeCrashEventError....pcclientaccess.service Healthy
MAILBOX1 LongRunningWatsonWarning....cclientaccess.service Healthy
MAILBOX1 LongRunningWerMgrWarning....cclientaccess.service Healthy
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Java 2 runtime Environment setup failed with a return code of -1

Hi!
I have tried to install sdk 1_3_1_01 on Windows 2000 with ServicePack 2 and the error "Java 2 runtime Environment setup failed with a return code of -1" occured. As I saw, a lot of people has the problem but couldn't find a solution on this page!
Please help !
Me

I've installed 1.3.1_01 on both W2K Workstation and Server, no problem. There's a bug report, but no workaround or solution.
http://developer.java.sun.com/developer/bugParade/bugs/4412291.html
and it's supposedly 'fixed' in 1.4.0 beta.
http://java.sun.com/j2se/1.4/fixedbugs/fixedbugs-beta2.html
You might try installing the beta version
http://java.sun.com/j2se/

Exchange 2013 MB/CAS integration with legacy Exchange 2007 CAS/MB/Trans server

Hi All,
I have an existing running Exchange 2007 SP3 RU13 server acting as MB,CAS,Transport using a Barracuda SPAM for SMTP (MX Record is assigned to here), and a TMG2010 server performing all ActiveSync, Outlook Anywhere, and OWA connectivity.
I have built a new Exchange 2013 SP1 server that will (for the meantime) act as a MB & CAS server only.
I successfully migrated a testuser mailbox to the new EX2013 server from the EX2007 server. The problem is that once migrated, OWA and Outlook can't access the mailbox.
OWA form our URL gives the message: Outlook Web Access is currently unavailable. If the problem continues, contact technical support for your organization and tell them the following: No Client Access servers of the appropriate version can be accessed from
the Internet
If I run OWA from the EX2013 URL it works ok, but not for MBs on the EX2007 server.
I tested this configuration in a VM lab and it worked ok. All I had to do was move the mailbox, then run Outlook. Outlook automatically found the new server and opened the MB.
Basically what I need to do is move all our existing MBs from the old 2007 server to the new 2013 server. I want to continue to use the exisiting transport/CAS/EDGE services on 2007 without having to rebuild both the internal and external comunications
infrastructure at the present time.
How can I get the EX2013 server to act as the MB server for the EX2007 communications infrastructure?

Hi,
Please try to create a new user on Exchange 2013, and send/receive email via both Outlook and OWA to test whether the Exchange 2013 mail flow well.
If Exchange 2013 works well, please try to bypass the TMG on Exchange 2007 for a little while for testing.
Additionally, we can use CAS 2013 URL to proxy/redirect previous CAS, or publish both CAS 2007 and CAS 2013 to be internet facing server with separate URLs, as Ed suggested.
Thanks
Mavis Huang
TechNet Community Support

Active Directory Certificate Services setup failed with the following error: Overlapped I/O operation is in progress. 0x800703e5 (WIN32: 997)

Hi,
I am trying to install certificate services on a windows 2008 server (R2 ENT SP1) with a PCIe nCipher HSM module installed on it. The version of nCipher SW is = 11.30. It is a RootCA, and I am trying to use a key that is already stored in the HSM (I
have done this before with a PCI HSM (older HW version)). I select “Use existing private key” and “Select an existing private key on this computer” on the wizard, then i change the CSP to nCipher and click on "search" the key I am looking for
appears and I select that one. I repeat, I have done this before and it works with a PCI HSM module.
The installation is finished before being prompted to insert the operator cards, and it ends with two errors:
<Error>: Active Directory Certificate Services setup failed with the following error: Overlapped I/O operation is in progress. 0x800703e5 (WIN32: 997)
And:
<Error>: Active Directory Certificate Services setup failed with the following error: The group or resource is not in the correct state to perform the requested operation.
0x8007139f (WIN32: 5023)
The servermanager.log says:
1856: 2014-07-23 18:27:48.195 [CAManager] Sync: Validity period units: Years
1856: 2014-07-23 18:27:48.928 [Provider] Error (Id=0) System.Runtime.InteropServices.COMException (0x800703E5): CCertSrvSetup::Install: Overlapped I/O operation is in progress. 0x800703e5 (WIN32: 997)
at Microsoft.CertificateServices.Setup.Interop.CCertSrvSetupClass.Install()
at Microsoft.Windows.ServerManager.CertificateServer.CertificateServerRoleProvider.Configure(InstallableFeatureInformation featureInfo, DiscoveryResult discoveryResult, ChangeTracker changeTracker)
1856: 2014-07-23 18:27:48.928 [Provider] CAErrorID: 0, CAErrorString: 'Active Directory Certificate Services setup failed with the following error: Overlapped I/O operation is in progress.
0x800703e5 (WIN32: 997)'
1856: 2014-07-23 18:27:48.928 [Provider] Adding error message.
1856: 2014-07-23 18:27:48.928 [Provider] [STAT] For 'Certification Authority':
And:
1856: 2014-07-23 18:27:49.053 [CAWebProxyManager] Sync: Initializing defaults
1856: 2014-07-23 18:27:49.162 [Provider] Error (Id=0) System.Runtime.InteropServices.COMException (0x8007139F): CCertSrvSetup::Install: The group or resource is not in the correct state to perform the requested operation. 0x8007139f (WIN32: 5023)
at Microsoft.CertificateServices.Setup.Interop.CCertSrvSetupClass.Install()
at Microsoft.Windows.ServerManager.CertificateServer.CertificateServerRoleProvider.Configure(InstallableFeatureInformation featureInfo, DiscoveryResult discoveryResult, ChangeTracker changeTracker)
1856: 2014-07-23 18:27:49.162 [Provider] CAErrorID: 0, CAErrorString: 'Active Directory Certificate Services setup failed with the following error: The group or resource is not in the correct
state to perform the requested operation. 0x8007139f (WIN32: 5023)'
1856: 2014-07-23 18:27:49.162 [Provider] Adding error message.
Has anyone experienced this before? Am I missing something here?
Any help will be very appreciated
Thanks in advance
Best regards
Alejandro Lozano Villanueva

Hi, thanks for your support.
I have been playing around a bit with some ncipher commands and found this:
C:\Program Files (x86)\nCipher\nfast\bin>cspcheck.exe
cspcheck: fatal error: File key_mscapi_container-1c44b9424a23f6cddc91e8a065241a0
9aa719e4f (key #1): 0 modules contain the counter (NVRAM file ID 021c44b9424a23f
6cddc91)
cspcheck: information: 2 containers and 2 keys found.
cspcheck: fatal error occurred.
If I perform the same command on the original server (the server with the original kmdata folder and with the running RootCA services):
E:\nfast\bin>cspcheck.exe
cspcheck: information: 2 containers and 2 keys found.
cspcheck: everything seems to be in order.
Strange?
Moreover, when I do a csptest.exe command (also on both servers, i find this)
On the new server:
C:\Program Files (x86)\nCipher\nfast\bin>csptest.exe
nCipher CSP test software
=========================
Found the nCipher domestic CSP named 'nCipher Enhanced Cryptographic Provider'
Provider name: nCipher Enhanced Cryptographic Provider
Version number: 1.48
User key containers:
Container 'csptest.exe' has no stored keys.
Container 'Administrator' has no stored keys.
Machine key containers:
Container '352dd28a-17cb-4c6f-b6e4-bf39bcf75db5' has a 2048-bit signature key.
Container 'ROOTCA' has no stored keys.
Container 'csptest.exe' has no stored keys.
While in the old server:
E:\nfast\bin>csptest.exe
nCipher CSP test software
=========================
Found the nCipher domestic CSP named 'nCipher Enhanced Cryptographic Provider'
Provider name: nCipher Enhanced Cryptographic Provider
Version number: 1.40
User key containers:
Container 'csptest.exe' has no stored keys.
Machine key containers:
Container '352dd28a-17cb-4c6f-b6e4-bf39bcf75db5' has a 2048-bit signature key.
Container 'ROOTCA' has a 2048-bit signature key.
Container 'csptest.exe' has no stored keys.
As you can see, the container called ROOTCA, which is the one that I use during the installation, says it has no stored keys. While on the old server, it says it contains a key. Why is this happening? I dont know, I am copying the complete
key management folder from one server to another and initialize the security world with that folder as I always do, and i dont have any errors during this procedure.
Do you know what could be the cause of this? or how can I fix this? Thanks a lot, best regards.
Alejandro Lozano Villanueva

Exchange 2013 cu3 setup fails with 'problem... validating the state of Active Directory... supplied credential... invalid'

Similar Messages

Maybe you are looking for