Archive for April 2012

The nominated Exchange server for offline address book 'Default Offline Address List' has been deleted.

I was helping out one of my friend in installation of Exchange Server 2010 SP2 in existing exchange 2003 environment.

Environment:
2 Domain Controller
Exchange Server 2003 SP2
Exchange Server 2010
Exchange Server 2010 on domain controller

After installing all the prerequisite for windows and completing the active directory switches which are
Setup.com /pl, Setup.com /ps, Setup.com /preparead and Setup.com /preparedomain we started the exchange installation and readiness check failed with error.

Client Access Role Prerequisites
Failed
Error:
The nominated Exchange server for offline address book 'Default Offline Address List' has been deleted. Nominate a valid server and restart setup.
Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=d2b0382e-6f51-46ca-bf12-2dafaa9af2c9

After digging into it, I found that exchange server 2003 OAB generation server is pointing to the server which do not exist in the environment.
OAB
Open Exchange System Manager…>Recipients…>Offline Address List…>Right click properties of Default Offline Address List…Click brows on Offline address list server and select the running exchange 2003 server in the environment.

Correct OAB
After changing the server, started the installation and it completed successfully.
I read on the internet regarding the same issue and found that people suggesting that you should delete Default Offline Address Book (List) from adsiedit.msc which is not correct.

If you delete Default Offline Address Book (List) and run the setup again than you will get error saying, Default Offline Address Book cannot be found.


Cheers,

Exchange Server 2010 SP2 installation fails with error code ’2147504141′

I was doing installation of Exchange server 2010 SP2 in the LAB in Hyper-V. I have done tons of installation in the past and on all the occasions installation went fine without any issue, except for this time.

Exchange server configuration:
Single domain
One domain controller with GC and DNS
Exchange server is running on domain controller (I know it's recommended)
Windows Server 2008 R2 with SP1

After installing all the prerequisite for windows server 2008 R2, I started installation. Readiness check passed without any error, well there were warnings for Exchange running on DC and Microsoft Office 2010 filter pack, which can be ignored.

Installation started and it failed on Hub Transport Role with error message.

“An error occurred with error code ’2147504141′ and message ‘The property cannot be found in the cache.”

 
Did some research, found that the issue is with Time Sync on HyperV. Disabled the Time Sync on the machine by doing the following steps
1.Open up the settings for the VM
2.Under Management, highlight the Integration Services option and you will get a list of the Integration Services installed and enabled
3.Uncheck the Time Synchronization service and press Apply.

Note:All time synchronization that is done by the Hyper-V time synchronization integration service is time zone aware.  If you disable the Hyper-V time synchronization integration service you will disable all the time synchronization aspects of Hyper-V that are time zone aware – and only leave the initial RTC synchronization active – which is not time zone aware.

Started the installation again and it failed with error.

Delete the Action and Install registry key from the location HKLM\Software\Microsoft\Exchange\V14\HubTransportRole.

Rebooted the server and started the installation but it failed again with the same error.
Now here is the best part of the resolution, to fix the issue you will have to uninstall exchange entirely from the server (control panel) if you fail to uninstall the server from control panel than you will have to remove the server manually. Check my blog how to remove exchange server 2010 manually from the computer.

This is a BUG and I was hopping that it will get fixed in RU2 at least but unfortunately it didn't. Hoping that it will be fixed in RU3.

Cheers,

EXCHANGE RANGER