Hi!

We have existing Exchange 2007 SP3 with latest rollups on Windows Server 2008 SP2 with all updates + 2 Domain controllers both are Server 2008 SP2 with all updates. Replications between both DC's are fine.

We are installing new Exchange 2013 SP1 in existing organisation on Windows Server 2012 R2 (fully updated), but it fails, when installing Mailbox role, because he can't start Information Store service.

Interesting thing is when i stop other exchange services and then i can start information store service, installation is continuing and everything is installed, but problem with services remains, i cannot start all services. Tried later to update to CU9, but problem remains.  Server resources are enough: 2 x E5-2630 v2 CPU's, 128GB RAM, hard disk enough free space.

Already tried to fully reinstall server OS and installation/uninstallation of Exchange server few times, didn't helped. I am close to despair. :)

Have any ideas, what else could try?

• Edited by Dzeisons Friday, August 14, 2015 8:33 AM

Installation on another (fresh) server failed with the same error.

In EX2007 we already have 5 mailbox databases. Could it be, because of count of the databases?

Both EX servers are Standard, maybe it is the reason?

Standard limits the number of total databases that can be mounted to 5 but not the services that can be started.

Right - and that is on the 2007 servers anyway.

Two things

1. Why do you have 128GB of RAM in that server.  That is over the recommended maximum.  And only two CPUs...?

2.  Check the Exchange setup log file - what is in there?  It is in the Exchange setup folder at the root of C:\

Installation was failing, when Information Store service could not be started, the same is in Exchange log: "Waiting 25000 miliseconds for MSExchangeIS to be started." 

5 databases are for organisation, not for every server?

The Standard Edition limits you to five databases on the server to which the license is applied.  That limit includes a recovery database and a public folder database, the latter of which no longer applies to Exchange 2013.