SDL Tridion 2009 installation on windows 2008 64-bit

By | May 11, 2010

In a standard situation I would strongly advice against installing Tridion software yourself. It is far more efficient to hire a friendly Tridion application engineer to do the installation for you. The reason behind this is simple: They install Tridion on a weekly basis where I struggle to get one installation a year under my belt. Add to that the vast knowledge about known issues that Tridion has available in their knowledge-base and you will arrive to my conclusion.

That said it is useful to install Tridion yourself at least once. Installing Tridion will teach you a lot about the intricacies of the system which will prove useful when facing disturbances.

The first step in any installation is getting the right hardware and OS. So I mailed the Tridion 2009 requirements to the resident system administrator and requested a single virtual server instance with as much memory and CPU as possible. The result was a server with 2GB (note: beg, borrow or steal more) of internal memory and the equivalent of an Intel Xeon CPU @3 Ghz. Pre-installed were:

  • Windows 2008 64-bit
  • Microsoft SQL Server 2005 Enterprise Edition (64-bit)

A system which nicely matched every last table row in the Tridion 2009 prerequisite documentation. A configuration which I expected to be an interesting challenge. Below I listed the highlights from installing the content manager. Most problems are probably avoidable when one follows the manual to the letter. Unfortunately my restless and dauntless nature bars me from using them before I run into trouble.

  1. Install msxml 4
  2. install capicom.
  3. regsvr32 capicom.dll   (run cmd as administrator)
  4. install IIS 6 compatibility components
  5. install Java runtime 6.0
  6. server manager -> webserver IIS  install the role service asp
  7. When receiving the error “The license is invalid. Please contact SDL Tridion Customer Support: EasyLicenser error -12” Turn of User Account controlControl PanelUser Accounts (turn it off for the user that is running Tridion).

Step 7 cost me some time as both myself and Tridion Support were unsure about the origin of this message. Fortunately I was invited to visit Tridion HQ and a friendly Tridion engineer found the solution. In return I only gave them a copy of my Virtual Machine for further study. Thanks for the brilliant support!

Installing and configuring the broker proved to be easier. The only problem I ran into was a jdbc.jar file that was missing. The installer can be found on the MS website: