scorchking

Issue  After this update rollup is applied, Orchestrator 2016 stopped logging Events under Events Tab in Runbook Designer Error: There is no event information to display Verify the issue by querying the events table in SELECT [UniqueID]       , [Type]       , [Computer]       , [DateTime]       , [Summary]       , [Message]    FROM [Orchestrator] . [dbo] . [EVENTS] Cause There is a stored procedure in the Orchestrator database named sp_insertevent which has a parameter @message. If the datatype of the @message parameter is nvarchar(max), then the Log Purge function may fail. Fix To fix this issue,  change the datatype of the @message parameter from nvarchar(max) to nvarchar(4000). You can use the code below or SQL Server Management Stud...

Issue  After migrating to System Center Orchestrator 2016,  you encounter this error: An error occurred saving the activity to the data store Please check the orchestrator management service trace logs  The Management Service log (C:\ProgramData\Microsoft System Center 2012\Orchestrator\ManagementService.exe\Logs) contains only thes line for every attempt 2015-10-15 12:45:02 [3752] 1 COpalisManager::ModifyObject::CheckAccess (HRESULT=0x80070005) 2015-10-15 13:16:09 [3176] 1 COpalisManager::ModifyObject::CheckAccess (HRESULT=0x80070005) 2015-10-15 13:17:21 [3176] 1 COpalisManager::ModifyObject::CheckAccess (HRESULT=0x80070005) Cause This happens because the Runbook has an Email activity with attachment. This is a known bug with System Center Orchestrator 2016. Workaround If you only have few runbooks with  Email activity with attachment .you can perfrom these 2 workarounds: 1)  You need to remove the attachements and re-add in order to ch...