Orchestrator: Error deploying Service Manager IP to Runbook Servers

I have come across one thing that i thought was nice to mention here. I have been working with a customer that have only one runbook server that includes all the roles.

 

So the other day they needed to add a new runbook server "More horse power" to the solution.

 

So they installed the new server and deployed the new role from the "Deploy manager".

 



 

Select the server name and an account that has administrative privileges to install the Orchestrator runbook server role on the server.

 

 



On the "Deploy Integration Packs or Hotfixes" selected the "Service Manager 2012" integration pack. 

 

 

In the logs the deployment of the Runbook server was successful, but the deployment of the integration pack the status was "Fatal error during installation".

 

 

 

Fatal error in my opinion sounds very bad. So I needed to find some more information about this "Fatal error"....

 

When you deploy new roles, hotfixes and IP in Orchestrator from the Deployment Manager, you can view the logs and see what happened during the installation.

 

Right click and select [View Deployment logs]

 

 

 

Every time you make a change to the roles or add a new feature, there is created a new log.

 

 

So I open up the log from the "Service Manager IP".

 

I searched through the log file and found this:

CAQuietExec: Microsoft (R) .NET Framework Assembly Registration Utility 2.0.50727.5420

CAQuietExec: Copyright (C) Microsoft Corporation 1998-2004. All rights reserved.

CAQuietExec:

CAQuietExec: RegAsm : error RA0000 : Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.

CAQuietExec: Error 0x80070064: Command line returned an error.

CAQuietExec: Error 0x80070064: CAQuietExec Failed

 

When a log often contains "The system cannot find the specified file" it mean that something is missing and the version=3.5.0.0 gave me a clue..

 

.Net framework 3.5....

 

So I logged on to the server and installed the .Net 3.5 and hit the deployment button again.

 

This time the deployment was successful, or as we say in Norwegian "Herlig" (trans:Perfect/lovely).