New installation of Exchange Server 2013

After installing Exchange 2013 on a Server running Microsoft Server 2012 I am unable to bring up the (EAC) Exchange Administration Center. I am entering the addresshttp : // <servername> / ecp as listed in my instructions and i am getting
ERROR 404 from the IIS8 Server.
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Hello,
If you to go check on Exchange CAS server, can you access it?
Did you get any error when you install the CAS server?
Thanks,
Evan
Evan Liu
TechNet Community Support

Similar Messages

New Deployment of Exchange Server 2013.

Hello All,
Good Day !!
We are planning to install Exchange 2013 Mailbox and Client Access on single server ( Windows Server 2012 Standard).
Currently Active Directory roles runs on windows server 2008R2 Sp1.
Its a new deployment for exchange as currently we are using Godaddy email server ( Can we migrate all our emails from Go daddy to our exchange Server).
Also confirm current active directory will support the installation and deployment of Exchange Server 2013.
How much HDD, RAM and CPU cores are required to support exchange Server Mailbox and Client Access roles( Users are 30 ).
How many Static IP's and SSl certificates are required for exchange.
Atlast as i said its new deployment please suggest if anything else is missing from my end.

Hello,
I recommend using professional cheat-sheet articles for Exchange 2013 sizing:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part1.html
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part2.html
The server's requirements depend on many factors ie. number of emails received/sent, mailboxes sizes etc.
In addition your AD environment's level supports Exchange 2013 deployment. You will need only prepare your schema and forest for Exchange installation. You will need also at least one public IP address and SSL certificate for that server.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Installation of exchange server 2013

Hi,
can we install ADDS, DNS, and Exchange server 2013 on a single server, and the OS is windows server 2012 r2 Standard Edition.
If it is possible then, is there any dis-advantages that my disturb Exchanger Server 2013 Services.
Thanks & regards,
Anil.

Its not recommended for wide variety of reasons in Production environment... Good to go if you want to just test something and not worried about things...
Configuring Exchange 2013 for Active Directory split permissions isn’t supported.
The Exchange Trusted Subsystem universal security group (USG) is added to the Domain Admins group when Exchange is installed on a domain controller. When this occurs, all Exchange servers in the domain are granted domain administrator rights in that domain.
Exchange Server and Active Directory are both resource-intensive applications. There are performance implications to be considered when both are running on the same computer.
You must make sure that the domain controller Exchange 2013 is installed on is a global catalog server.
Exchange services may not start correctly when the domain controller is also a global catalog server.
System shutdown will take considerably longer if Exchange services aren’t stopped before shutting down or restarting the server.
Demoting a domain controller to a member server isn’t supported.
Running Exchange 2013 on a clustered node that is also an Active Directory domain controller isn’t supported.
Refer:
Installing Exchange on a domain controller is not recommended
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange Server 2013 SP1 - Internal Email Flow slowness

Hi Fellows,
I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
Header analysis shows the message exchange between mailbox servers is taking time. any clue?
Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
Network communication, Storage performance, Server performance are all as good as we love to.
Thanks.
J.A

Hello,
When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
Cara Chen
TechNet Community Support

Exchange Server 2013 Logs Out of Control

I have a fairly new install of Exchange Server 2013 running in full production. Everything has been great except for the high level of log files that are generated on a daily basis. I am able to truncate the Transaction logs everyday with a Server Backup,
but that still does not help me with the other constantly growing log files in C:\Program Files\Microsoft\Exchange Server\V15\Logging. Is there any way to set these to automatically purge after a set amount of days? I have found resources that discuss setting
up a powershell script that will delete everything after a set amount of days, but I want to know if anything in Exchange 2013 will allow me to do this. I am getting tired of expanding my VM disk. Any help would be greatly appreciated.

Unfortunately Exchange 2013 creates alot of log files that it does not clean up on it's own. While there isn't a way to tell Exchange to clean up the files after X number of days, there is a very helpful script someone else has already written that does
the work for you. He has 2 versions, 1 that you have to put on each individual server (I like that one in case I lose the server I put the script on) or 1 that you can run on 1 server that takes care of all of your Exchange Servers.
http://www.c7solutions.com/2013/04/removing-old-exchange-2013-log-files-html
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Exchange server 2013 Installation issue

Dear Experts,
Thanks in advance...
I am not able to Install Exchange server 2013. I have tried my best to Install but not success. Please find my system configuration.
Dell Laptop Intel I5 1.7 GHZ
RAM -8GB
Vmware workstation 9.
Steps I followed
Created a VM inside Vmware and Installed windows 2012 Std. Edition
Memory assigned to VM is 1 GB
All prerequisites completed and tried to Install Exchange server 2013 SP1
During installation it asked me to select the role to Install and I selected Mailbox server role and CAS
Exchange setup process started at 3 P.M till 9 P.M setup was not finished finally setup process halt and I got the error setup could not completed .
Please find the logs for your reference.............
04/13/2015 08:41:02.0303] [0] **********************************************
[04/13/2015 08:41:02.0303] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
[04/13/2015 08:41:02.0303] [0] **********************************************
[04/13/2015 08:41:02.0303] [0] Local time zone: (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi.
[04/13/2015 08:41:02.0303] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[04/13/2015 08:41:02.0328] [0] Setup version: 15.0.847.32.
[04/13/2015 08:41:02.0328] [0] Logged on user: WIN-4D2C2JMF5R1\Administrator.
[04/13/2015 08:41:02.0336] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/13/2015 08:41:02.0368] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/13/2015 08:41:02.0600] [0] Command Line Parameter Name='sourcedir', Value='C:\Softwares\Exch-13'.
[04/13/2015 08:41:02.0615] [0] Command Line Parameter Name='mode', Value='Install'.
[04/13/2015 08:41:02.0632] [0] RuntimeAssembly was started with the following command: '/sourcedir:C:\Softwares\Exch-13 /mode:Install'.
[04/13/2015 08:41:02.0632] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/13/2015 08:41:05.0504] [0] Finished loading screen CheckForUpdatesPage.
[04/13/2015 08:41:13.0567] [0] Starting file's copying...
[04/13/2015 08:41:13.0599] [0] Setup copy files from 'C:\Softwares\Exch-13\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
[04/13/2015 08:41:13.0794] [0] Finished loading screen CopyFilesPage.
[04/13/2015 08:41:15.0033] [0] Disk space required: 1826493368 bytes.
[04/13/2015 08:41:15.0033] [0] Disk space available: 46620041216 bytes.
[04/13/2015 08:42:55.0484] [0] Finished loading screen InitializingSetupPage.
[04/13/2015 08:42:55.0484] [0] File's copying finished.
[04/13/2015 08:43:13.0922] [0] Setup is choosing the domain controller to use
[04/13/2015 08:43:28.0885] [0] Setup is choosing a local domain controller...
[04/13/2015 08:43:32.0221] [0] [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.
[04/13/2015 08:43:32.0335] [0] [ERROR] Active Directory server
is not available. Error message: Active directory response: The LDAP server is unavailable.
[04/13/2015 08:43:32.0366] [0] [ERROR] The LDAP server is unavailable.
[04/13/2015 08:43:32.0366] [0] Setup will use the domain controller ''.
[04/13/2015 08:43:32.0366] [0] Setup will use the global catalog ''.
[04/13/2015 08:43:32.0596] [0] No Exchange configuration container was found for the organization. Message: 'Active Directory server
is not available. Error message: Active directory response: The LDAP server is unavailable.'.
[04/13/2015 08:43:32.0707] [0] The following roles have been unpacked:
[04/13/2015 08:43:32.0721] [0] The following datacenter roles are unpacked:
[04/13/2015 08:43:32.0739] [0] The following roles are installed:
[04/13/2015 08:43:32.0739] [0] The local server does not have any Exchange files installed.
[04/13/2015 08:43:32.0834] [0] Server Name=WIN-4D2C2JMF5R1
[04/13/2015 08:43:33.0032] [0] Setup will use the path 'C:\Softwares\Exch-13' for installing Exchange.
[04/13/2015 08:43:33.0084] [0] The installation mode is set to: 'Install'.
[04/13/2015 08:43:51.0460] [0] Exchange organization name is required for this mode.
[04/13/2015 08:43:51.0460] [0] Active Directory Initialization status : 'False'.
[04/13/2015 08:43:51.0472] [0] Schema Update Required Status : 'False'.
[04/13/2015 08:43:51.0472] [0] Organization Configuration Update Required Status : 'False'.
[04/13/2015 08:43:51.0472] [0] Domain Configuration Update Required Status : 'False'.
[04/13/2015 08:43:51.0536] [0] Applying default role selection state
[04/13/2015 08:43:51.0565] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:43:51.0565] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:43:51.0565] [0] InstallModeDataHandler has 0 DataHandlers
[04/13/2015 08:43:51.0565] [0] RootDataHandler has 1 DataHandlers
[04/13/2015 08:43:52.0848] [0] CurrentResult launcherbase.maincore:90: 0
[04/13/2015 08:43:53.0067] [0] Finished loading screen WelcomePage.
[04/13/2015 08:44:06.0654] [0] Finished loading screen EULAPage.
[04/13/2015 08:44:10.0679] [0] Finished loading screen RecommendedSettingsPage.
[04/13/2015 08:44:13.0814] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:13.0814] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:13.0814] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:13.0844] [0] InstallModeDataHandler has 8 DataHandlers
[04/13/2015 08:44:14.0048] [0] Finished loading screen RoleSelectionPage.
[04/13/2015 08:44:18.0619] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0619] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0619] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 9 DataHandlers
[04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 10 DataHandlers
[04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 11 DataHandlers
[04/13/2015 08:44:18.0648] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0648] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0648] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0648] [0] InstallModeDataHandler has 12 DataHandlers
[04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:22.0644] [0] InstallModeDataHandler has 13 DataHandlers
[04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:22.0656] [0] InstallModeDataHandler has 14 DataHandlers
[04/13/2015 08:46:00.0423] [0] Finished loading screen InstallationSpaceAndLocationPage.
[04/13/2015 08:46:28.0427] [0] Finished loading screen ExchangeOrganizationPage.
[04/13/2015 08:46:30.0221] [0] Finished loading screen
Regards
Biswajeet

Hi,
Please find the DC Health check report.
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>dcdiag
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = EX-13
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\EX-13
      Starting test: Connectivity
         ......................... EX-13 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\EX-13
      Starting test: Advertising
         ......................... EX-13 passed test Advertising
      Starting test: FrsEvent
         ......................... EX-13 passed test FrsEvent
      Starting test: DFSREvent
         ......................... EX-13 passed test DFSREvent
      Starting test: SysVolCheck
         ......................... EX-13 passed test SysVolCheck
      Starting test: KccEvent
         ......................... EX-13 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... EX-13 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... EX-13 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... EX-13 passed test NCSecDesc
      Starting test: NetLogons
         ......................... EX-13 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... EX-13 passed test ObjectsReplicated
      Starting test: Replications
         ......................... EX-13 passed test Replications
      Starting test: RidManager
         ......................... EX-13 passed test RidManager
      Starting test: Services
         ......................... EX-13 passed test Services
      Starting test: SystemLog
         An error event occurred. EventID: 0x0000272C
            Time Generated: 04/14/2015   18:01:37
            Event String:
            DCOM was unable to communicate with the computer fec0:0:0:ffff::1 us
ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
m32\dcdiag.exe).
         An error event occurred. EventID: 0x0000272C
            Time Generated: 04/14/2015   18:01:49
            Event String:
            DCOM was unable to communicate with the computer fec0:0:0:ffff::2 us
ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
m32\dcdiag.exe).
         An error event occurred. EventID: 0x0000272C
            Time Generated: 04/14/2015   18:02:02
            Event String:
            DCOM was unable to communicate with the computer fec0:0:0:ffff::3 us
ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
m32\dcdiag.exe).
         ......................... EX-13 failed test SystemLog
      Starting test: VerifyReferences
         ......................... EX-13 passed test VerifyReferences
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running partition tests on : NETMAGIC
      Starting test: CheckSDRefDom
         ......................... NETMAGIC passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... NETMAGIC passed test CrossRefValidation
   Running enterprise tests on : NETMAGIC.IN
      Starting test: LocatorCheck
         ......................... NETMAGIC.IN passed test LocatorCheck
      Starting test: Intersite
         ......................... NETMAGIC.IN passed test Intersite
Regards
Biswajeet

Exchange Server 2013 SP1 Standard: Installation failing can't progress

I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
do they think they're running?).
The error message:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
Parameter name: VirtualDirectoryName".
And I have to remove this config using ADSI Edit, which just returns me to the first error.

1. Prodution
2. Just 1 DC for 1 site.
3. Setup.EXE
4. Matches SP1 version numbers
5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
6. Here is the log files:
[03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
[03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
[03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
[03/23/2015 22:06:52.0941] [1] Executing:
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
[03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
[03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
[03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
[03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
[03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
[03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
[03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
[03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
[03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
[03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
[03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

New Exchange Server 2013 in a Exchange 2007 Org, can't get cu's to install

Hi,
We have an Exchange Server 2007 in our organization. I installed an Exchange Server 2013 but could not get the CU3 to install, would throw exceptions. I tried CU2 and it got a lot further but failed to start a service near the end. Don't ask for specifics
as I got frustrated and blew this machine away and installed a fresh VM. I read that you can install the CU's as if they are a fresh installation. I tried this but it fails saying "the Exchange server is in an inconsistant stet....recover". There
IS no Exchange server yet!!
What am I doing wrong? I used the command line for CU3, like: setup /mode:install /roles:ca,mb,mt /IAccept blah blah blah. I didn't set powershell execution policy, not sure if that was it. Are there switches I am missing? I want to see if I can install
the Exchange CU3 right from the get-go.
HeLp!

Hi,
According to the error message, this issue may occur if the previous Exchange installation or un-install failed to complete. This situation leaves the Exchange server
object in Active Directory and prevents a new installation.
We can try:
1. Install ADSI Edit.
2. Launch ADSI Edit. To do this, click Start, click Run, type adsiedit.msc in the text box, and then click OK.
3. Locate the Exchange server object by going to the following location: CN=Configuration, DC= Domain Name, DC=com, CN=Services, CN=Microsoft Exchange, CN=<Organization
Name>, CN=Administrative Groups, CN= <Exchange Administrative Group>, CN=Servers, CN=<Server Name>.
4. Delete the server object.
5. Remove the Exchange server's machine account from Security groups Exchange Servers and Exchange Install Domain Servers.
Regards,
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

Exchange Server 2013 installer will not start or complete

Hello,
I am trying to MS Exchange Server onto a Windows Server 2012R2 with Active Directory network. I had started an installation process and it shot out a list of pre-requisites that server need before it can attempt to install. I fulfilled every pre-requisite.
Rebooted the server. Now whenever I attempt another installation process again. It starts, gathers information, and quits with event log:
Windows Installer installed the product. Product Name: Microsoft Exchange Server. Product Version: 15.0.516.32. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.
MS Exchange Server is not listed in Programs and Features to even remove, is it a faulty Microsoft Installer? I have already rebooted numerous times to no avail.
EDIT: Here's a copy of the MSI log, I couldn't find anything to indicate what's going wrong myself, http://pastebin.com/LwCAimuF

Hi,
I've downloaded (as per instructions above):
Microsoft Exchange Server 2013 Service Pack 1 (SP1)
http://www.microsoft.com/en-us/download/details.aspx?id=41994
Again, the installer repeats the same behavior as before, right now I am running a repair tool on .Net repair tool.
New log http://pastebin.com/SDynMaDe
Edit: Looks like there's long list of issues trying to fulfill Exchange Pre Requisite.
Windows Management Framework 4.0
http://www.microsoft.com/en-us/download/details.aspx?id=40855
"The certificate for the signer of the message is invalid or not found"
It would probably be best to re-install Windows Server again

Exchange Server 2013: Installation fails

Migrating SBS 2008 to Windows Server 2012 R2 (no virtualization) and Exchange Server 2013 SP1
(1) ADprep on SBS 2008 went fine
(2) Installed necessary feature for Exchange (website “Part 1: Step-by-Step Exchange 2007 to 2013 Migration”)
A) the first time I installed Exchange 2013, the setup succeeded, however there were several ecp/WinRM errors.
B) restored Windows Server 2012 R2 to the state (2). Removed from AD (ADSI Edit)
… CN=Services; CN=Exchange; CN=First Organization; CN=Exchange Administrator Group; CN=Servers
delete new Win 2012 server
Run Exchange setup again:
The following error was generated when "$error.Clear();
if ($RoleStartTransportService)
start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40
" was run: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".
Checked:
- IPv6 is enabled, but was setup correctly after installing ADDS role)
- Administrators (Group) is a member of the Exch. Trusted Subsystem
Probably there is an AD problem, after the restoration (B) (bare metal) of the Win 2012 server.
Please help!
Fulco

Hi
the error states that the MSExchangeTransport service failed to start. Can you manually try starting the service and then run the setup again?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange Server 2013 Installation error

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

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

Installation error for Exchange Server-2013

I am trying to install exchange server-2013 on my Windows server-2012
machine. I have configured per-requisite applications and develop the server environment with active directory roles.
At my readiness check option, it shows the following error:-
"An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later and windows server-2012".
I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
Regard
Azad
Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through the
exchange 2013 management shell
"Get-Exchangeserver"
However still not able to connect to https://localhost/eac and when i re-run setup
01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
[01-28-2014 21:10:16.0804] [0] **********************************************
[01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
[01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
[01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
[01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
[01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
[01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
[01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
[01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked:
[01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
[01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
[01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
[01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
[01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
[01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
[01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
[01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
[01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[01-28-2014 21:10:39.0664] [0] Applying default role selection state
[01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
[01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
[01-28-2014 21:15:30.0513] [0] End of Setup
[01-28-2014 21:15:30.0513] [0] **********************************************

Cannot Access EAC/ECP on exchange server 2013 after installation

Hi,
I can not Cannot Access EAC/ECP on exchange server 2013 after installation . Error 404.4 code 0x80070002
Help!
Thanks,

Hi Florin
Did you try accessing EAC by using below link
https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
Please access EAC via Internal URL: https://<CASServerName>/ecp
Finally ensure that you have logged in as administrator as well as this might be problem as well
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 Server 2013 installation error at Step 10/15

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

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

How can I clone a completed Exchange Server 2013 in a Lab Enviroment?

I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken
(1)Clone the Exchange1 and turn it off
(2) Brought the Clone Exchange2, renamed it, change the IP configurations,
(3) Re-ran the ADprep/Doamin prep
(4) Checked the ASDIedit to verify the Schema/configuration in AD
(5) Restarted I and was able to logon to the Exchange2
(6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database
What I did to fix this:
(7) Rejoin the Exchange1 to the domain - and was able to logon
(8) Unable to access ECP or OWA of any of the two servers.
(9) Errors received - Fix the configuration file of the application
My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?

Unless you are cloning an entire environment, and then bringing it up in a seperate isolated environment, it is not supported to simply clone an Exchange Server, and then bring it online in an existing environment and rename it to save on setup and configuration
time.
You can script the setup and configuration of Exchange through Powershell, either with scripts or with another product controlling it - something like
System Center Orchastrator.
From the script side of things there are many available on peoples blogs. Check
here.
Edit: and to be clear, there is no need to re-run any prep tasks against Active Directory when installing a new Exchange Server, unless you are installing into a new domain as part of your Forest.
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

New installation of Exchange Server 2013

Similar Messages

Maybe you are looking for