(again...) Issue reloading Operations Monitor after June 2017 upgrade

paolo_mapelli — Thu, 06 Jul 2017 13:52:48 GMT

Good Morning,

as many other before me (including me...), yet another issue on reloading operations monitor after an upgrade of QS.

2017-07-06 15:40:30 2079 CALL reloadSummary

2017-07-06 15:40:30 0879 TRACE Working on Reload Summary

2017-07-06 15:40:30 0879 Working on Reload Summary

2017-07-06 15:40:30 0880

2017-07-06 15:40:30 0881 Reload_1:

2017-07-06 15:40:30 0882 Load

2017-07-06 15:40:30 0883 If([Reload from Hub]=1,TaskId,ProxySessionId) as ProxySessionId,

2017-07-06 15:40:30 0884 LogTimeStamp as [Reload Start],

2017-07-06 15:40:30 0885 If([Reload from Hub]=1,'Reload from Hub of ' & ObjectName,SubField(ObjectName,'|',1)) as [Task Name]

2017-07-06 15:40:30 0886 RESIDENT LogContent

2017-07-06 15:40:30 0887 WHERE TaskExecution = 0 OR [Reload from Hub] = 1

2017-07-06 15:40:30 Error: Field 'Reload from Hub' not found

2017-07-06 15:40:30 Execution Failed

2017-07-06 15:40:30 Execution finished.

Upgrade: from 3.1SR4 to June 2017.

Any idea?

Thank in advance for support.

Paolo.

topic (again...) Issue reloading Operations Monitor after June 2017 upgrade in Management & Governance