Link to home
Start Free TrialLog in
Avatar of jtgerdes
jtgerdes

asked on

New Exchange 2007 installation looking for old installation path

We just reloaded our Exchange 2007 server using the “{Drive}:\Setup /m:recoverserver” switch to reload the configuration.  After getting Exchange partially set up, and connecting to the mailbox store, we keep encountering issues with receiving mail – or in this case, NOT receiving mail – and installing the Client Access Role.  

We’ve got two major things going on here (that we know of so far)…
1.       We are unable to receive messages and are getting event IDs 5030, 6003, 9006 referencing that Exchange is unable to locate/create message tracking logs, pickup directory, replay directory, routing table log file or directory, all pointing to a non-existent location of “E:\Exchange\...”

2.      We are unable to install the Client Access Role for Exchange 2007 due to the following error:
The path "E:\Exchange\ClientAccess\OAB" is not on a fixed drive.

On the new server, the Exchange installation path is on the C: drive whereas the old server was installed on a drive using the letter E.

Question 1:  Where is Exchange getting the E:\ drive location that it’s looking for?
Question 2:  How can we change those paths to the correct installation directory?

Since this was a new installation of Exchange on a fresh installation of Server 2008 Enterprise, it’s got to be pulling this configuration data from Active Directory somewhere.  

Due to time constraints, we really can’t do an OS reload to wipe Exchange again, so we’d appreciate any information about how we could fix this.

5030.txt
6003.txt
9006.txt
ClientAccessRole.jpg
ASKER CERTIFIED SOLUTION
Avatar of murli30
murli30
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jtgerdes
jtgerdes

ASKER

Sorry for the delayed response, your fix worked perfect for installing the Client Access role.  We ended up working with Microsoft on the not receiving email issue and we tried so many things I'm not really sure what finally fixed that.