Update Rollup 4 for System Center 2016 Orchestrator is available

Update Rollup 4 for System Center 2016 Orchestrator is available: https://support.microsoft.com/en-us/help/4047355.

But Attention!: Before you install this update, make sure that the SQL Server Native Client is installed on the Management Server and the Runbook Server(s). For more Information see below.

New features:

  • System Center 2016 Orchestrator now supports TLS 1.2 with UR4.

Fixes:

  • When you tried to Re-„Check in“ a Runbook before UR4 with a „Send Email“ Activity including an attachment after „Check Out“ and modify anything in the Runbook, you got the error: „An error occurred saving the activity to the data store. Please check the Orchestrator Management Service trace logs.“
  • When you selected in System Center 2016 RTM Runbook Designer Hep/Abpout you got „Technical Preview 5“.
  • Orchestrator throws an error when more than 23 groups are added to the permissions of the Runbook folders.

There are three separate Updates for Management Server, Runbook Server and Runbook Designer.

Before you install the Update ensure that SQL Server Native Client is installed on Management Server and the Runbook Server(s). This was not needed before UR4. I installed Microsoft® SQL Server® 2012 Native Client – QFE (https://www.microsoft.com/en-us/download/details.aspx?id=50402) also on Windows Server 2016 as well, the Orchestrator database is on an instance of SQL Server 2016. I changed no any other settings on the SQL Server instance.

Without you get „Connection Error: The Server threw an exception.“ opening Runbook Designer.

And if you try you use Data Store Configuration to setup a new connection you get „Error: Could not connect to the specified database server. Message: “ (with empty Message) if SQL Server 2012 Native Client is not present.

In the Orchestrator logs you will find this errors if SC 2016 UR 4 is installed without SQL Server Native Client:

RunbookService.exe.log:

Process ID: 9864
Version : 7.3.149.0
Computer : SCORB1
User : DOMAIN\ServiceAccountSCO

2017-11-13 14:22:13 [7976] 1 DBDataStore: ::Exception caught in long __thiscall CODBDataStore::InitConnection(class _com_ptr_t<class _com_IIID<struct _Connection,&struct __s_GUID const _GUID_00000550_0000_0010_8000_00aa006d2ea4> > &,int):
ODBDataStore.cpp(15479)
<Exception>
<Type>Opalis::Exception</Type>
<Location>
long __thiscall CODBDataStore::GetConnectionString(class String &)
ODBDataStore.cpp(6054)
</Location>
<MsgCode>Unknown database type</MsgCode>
</Exception>

ManagementService.exe.log:

2017-11-14 22:14:04 [7180] 1 DBDataStore: ::Exception caught in long __thiscall CODBDataStore::InitConnection(class _com_ptr_t<class _com_IIID<struct _Connection,&struct __s_GUID const _GUID_00000550_0000_0010_8000_00aa006d2ea4> > &,int):
ODBDataStore.cpp(15479)
<Exception>
<Type>Opalis::Exception</Type>
<Location>
long __thiscall CODBDataStore::GetConnectionString(class String &)
ODBDataStore.cpp(6054)
</Location>
<MsgCode>Unknown database type</MsgCode>
</Exception>

Starten Sie jetzt Ihren Weg zu Azure!

Los geht's

top