Update Rollup 5 for System Center 2016 Orchestrator

Update Rollup 5 for System Center 2016 Orchestrator is available: https://support.microsoft.com/en-us/help/4094928/update-rollup-5-for-system-center-2016-orchestrator

It fixes some issues:

  • When you view the activity details of a job instance, the Orchestrator Web Console displays the input parameter as a GUID instead of the Display Name of the parameter.
  • Potential denial of service attack vector through sending invalid characters in runbook parameters.
  • RunbookServerMonitorService.exe and aspt.exe processes run successfully but create entries in the error logs.
  • Changes that you make to activities in a runbook are not saved consistently if the activities are not edited when they are added for the first time.
  • After you upgrade to Update Rollup 4 for System Center 2016 Orchestrator, the RunbookServerMonitorService service stops working because it cannot connect to the database.
  • The purge-the-logs command in the Runbook Designer fails after you apply Update Rollup 4 for System Center 2016 Orchestrator.
  • The Query Database task fails after you apply Update Rollup 4 for System Center 2016 Orchestrator.
  • Runbooks that use the Run Process task cause the Orchestrator server to slow down and face connectivity and performance issues.

If you have applied UR5 for SC2016 Orchestrator you might get the error:

An error occurred saving the activity to the data store. Please check the
Orchestrator Management Service trace log.

And in the trace logs you will see something like:

18-05-15 16:56:32 [2676] 1 DBDataStore: ::Exception caught in long __thiscall CODBDataStore::InternalSaveObjectDataWithoutChunks(wchar_t *,wchar_t *,class _com_ptr_t<class _com_IIID<struct MSXML2::IXMLDOMNode,&struct __s_GUID const _GUID_2933bf80_7b36_11d2_b20e_00c04f983e60> >,wchar_t *,class List<wchar_t *> *,wchar_t *):
ODBDataStore.cpp(4096)
<Exception><Type>_com_error</Type><ErrorMessage>IDispatch error #3119</ErrorMessage><Description>Cannot insert the value NULL into column ‚Service‘, table ‚Orchestrator2016.dbo.TASK_SERVICESTATUS‘; column does not allow nulls. INSERT fails.</Description><HResult>-2147217873</HResult></Exception>

2018-05-15 16:56:32 [2676] 1 DBDataStore: ::Error #-2147217873
Description: Cannot insert the value NULL into column ‚Service‘, table ‚Orchestrator2016.dbo.TASK_SERVICESTATUS‘; column does not allow nulls. INSERT fails.
Source: Microsoft SQL Server Native Client 11.0
Error #-2147217873
Description: The statement has been terminated.
Source: Microsoft SQL Server Native Client 11.0

2018-05-15 16:56:32 [2676] 1 DBDataStore: ::INSERT INTO TASK_SERVICESTATUS ([UniqueID],[Computer],[Service],[Condition]) VALUES (?,?,?,?)

You can workaround that problem modifying table TASK_SERVICESTATUS in your Orchestrator Database. Set „Allow Nulls“ for Column Condition:

 

You can alo use this SQL Statement:

USE Orchestrator6 /*Name of your Orchestrator DB*/
ALTER TABLE [dbo].[TASK_SERVICESTATUS] ALTER COLUMN [Condition] INT NULL

 

Starten Sie jetzt Ihren Weg zu Azure!

Los geht's

top