Can’t install Transport HUB in Exchange 2010

Exchange-2010-Logo

When building my latest SharePoint 2010 demo virtual machines, I decided to try installing Exchange 2010 as well.  Now, I’m not an Exchange admin, but I thought “how hard can this be?”  Well, a little more than I thought.

Pretty early during the install, I got an error saying that it couldn’t “install Transport HUB”.  I double checked that my VM was meeting all of the requirements, both hardware and software, and everything looked fine.

After much researching, it turns out that the error was caused by not having IPv6 enabled on the network adapter inside the virtual machine.  I had turned it off because I thought I wouldn’t need it.  I guess Exchange 2010 does.

SharePoint 2010: Taxonomy feature (Feature ID "73EF14B1-13A9-416b-A9B5-ECECA2B0604C") has not been activated

I ran into an error message in SharePoint 2010 that took me a few minutes to figure out.  I was working on a demo of SharePoint 2010’s managed metadata and getting an error when I was adding a Managed Metadata column to a library.  A little Google research turned up this blog post:

The Taxonomy feature (Feature ID "73EF14B1-13A9-416b-A9B5-ECECA2B0604C") has not been activated.

As Michal Pisarek pointed out last June, you get the error because the Taxonomy feature isn’t activated.  Like Michal, I’m not sure how this happened to my installation, but the fix he documented works. (Activating the feature using STSADM)

Rebuilding a Mac Mini (early 2009) --- Update

A couple of months ago I rebuilt the family’s Mac Mini (you can read the details in this post).  Things had gone pretty smoothly until a few weeks ago.  That’s when my wife mentioned that different applications would spontaneously crash.

She kept track for a few days, and it turned out to be any or all of the applications that she uses (Safari, Quicken, Entourage, etc.) .

I did some online research and didn’t really find too much – but then how do you do a proper Google search for “Mac OS 10.5.8 applications crash”.  The best suggestion seemed to be issues around 10.5.8, where people suggested that you go back to a previous version (something like 10.5.6).  The only way to do that is to completely reinstall the OS – which is what I had just done.

leopard-165

SO, instead of doing that, I decided to just reapply the 10.5.8 update by downloading it from Apple (http://support.apple.com/downloads/Mac_OS_X_10_5_8_Combo_Update ).  I had installed the updates after the rebuild through the Apple Update mechanism built into OS X.  I thought maybe the combo update would reinstall some corrupted file (or something).

I did this about a week ago and sure enough, we’ve had one crash this week with the same usage patterns as before.  I still have no idea what was causing the crashes, but at this point, I’m just going to declare it fixed and move on.

Twitter