You must be logged in to post a comment.
After UR6 update, when a new maintenance schedule is created below issues are observed:
1) The “create maintenance schedule” template freezes on clicking “Finish” in operations console and need to reopen the console
2) Duplicate entries of every new schedule with different schedule IDs are recurrently created in both database and Console.Ex: 3 new schedules were created and ~250 duplicate entries are continuously added in DB,console and this is stopped only on system center services restart on management server
This appears to be a major defect with maintenance schedule feature after upgrade to UR6.
Please verify the Maintenance Mode functionality and share your comments
I have a repro of this and am investigating.
To resolve this – open the DAS/SDK account SQL login properties, and on the user mapping to the MSDB database, check the box next to “dbowner” role. This will resolve the issue. The workflow needs to select the SYSJOBS table and does not have enough rights to do this.
Updated instructions for UR6 now posted.
Thanks Kevin. We had the same issue, and you solved it :-).
In the Linux agent section you have to restart the HealthService on the Gateway servers as well.
I have done the complete installation in our test environment and cannot see the option for No APM in the install agent wizard or repair dialogue box. This was the key reason for doing the upgrade. What may have gone wrong?
UR6 does not add the NOAPM ability in the agent push install wizard – that was only added starting with 1807.
UR6 simply fixed the bug where the SCOM 2016 agent APM modules were breaking IIS on SharePoint servers.
Thanks for that. I misunderstood the details then having seen the dialogue box for 1807 I thought it would be the same. That means that when we push out the agent it will install APM but switched off? We have a number of agents that have been manually installed to not install APM. If I change them back from manual and upgrade the agent does that mean that APM will be installed on those agents now? It looks like we may have to do some serious testing to bring the SharePoint team on board.