• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1918
  • Last Modified:

Exchange 2007 SP2 active node mailbox, "Cannot start service MSExchangeTransportLogSearch on computer"

I've tried to install the first Exchange 2007 SP2 active node mailbox role on a Windows 2008 server and get the error below.  I've seen some other posts, but can't figure it out.  There's a lot about it not being able to get to the crl.microsoft.com site, but IE gets there.  Any help would be appreciated.

Mailbox Role Failed Error:
Service 'MSExchangeTransportLogSearch' failed to reach  status 'Running' on this server.
Cannot start service MSExchangeTransportLogSearch on computer '.'.
The service did not respond to the start or control request in a timely fashion

1 Solution
Check to make sure that the service is not set to disabled. I have seen that happen before on a failed install.  Start the service manually and then retry your setup.
What is the Windows Firewall status on your Server 2008? Do you have anyother network firewall blocking outbound? Just because IE can get to that website, doesn't mean the service can. I always turn off Server 2008 firewall (all levels) during E2K7 installation. You can always turn it back on later if needed.
mbrombAuthor Commented:
The service was set to auto, and I did try to start it manually with the same timeout.  the firewall has been completely off.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Just to be thorough, did you check these KB articles?

mbrombAuthor Commented:
I did see those articles. Per article 94475, I put crl.microsoft.com in the hosts file before re-attempting another install with the same results.  This is a windows 2008 enterprise server with .NET Framework version 3.5 SP1 installed.  One of the solutions is:

"Use a switch in the configuration files that are associated with the Exchange services. This switch works in the common language runtime (CLR) 2.0 SP1 environment that is included with the .NET Framework version 3.5."

As far as I can tell,  Those config files are not there until Exchange is installed, and if I'm to create one beforehand it's not clear where to put it.

For the 839803 article, I did not try the reg hack yet.  I'll do that and let you know.
mbrombAuthor Commented:
That worked!  Thanks!

I had the following changes in place:
1) crl.microsoft.com in the hosts file
2) created Program Files\Microsoft\Exchange Server\Bin\MSExchangeTransportLogSearch.exe.config from the template.  The template was there because I didn't uninstall the Exchange management tools.
3) Reg hack from http://support.microsoft.com/?id=839803

I'm not sure which did the trick, but it's working.
mbrombAuthor Commented:
These articles have multiple possible solutions that resolved my issue.  Thanks!
mbrombAuthor Commented:
This happened on the other 2 nodes for the cluster also.  The actual solution was creating the MSExchangeTransportLogSearch.exe.config

First I tried installing the CMS with management tools.  It fails with the MSExchangeTransportLogSearch service error.  I removed the CMS, leaving the management tools which leaves the Program Files\Microsoft\Exchange Server\bin\MSExchangeTransportLogSearch.exe.config.template file.  Copied the template and renamed it to MSExchangeTransportLogSearch.exe.config.  After a reboot to finish the removal I did the install again without problem.  
I have added the hosts file entry and thre registry and it works now.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now