SOLVED SCCM Version upgrade 1710 failed

[Rahul Sapke]

We have SCCM 1706 Installed in our environment and now I am trying to upgrade it to the 1710. But its failing. Have performed lot of Google based troubleshooting but none of them worked. Below are some of log entries from CMUpdate.log file:-

Turned on activation for service broker queue CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:42 3696 (0x0E70)
Failed to apply update changes 0x87d20b15 CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:42 3696 (0x0E70)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:42 3696 (0x0E70)
Error information persisted in the database. CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:42 3696 (0x0E70)
ERROR: Failed to process configuration manager update. CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:42 3696 (0x0E70)
Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, servers will be polled in 1 second... CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:42 3696 (0x0E70)
INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:43 3696 (0x0E70)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:43 3696 (0x0E70)
Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds... CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:08:43 3696 (0x0E70)
There are no pending update package to be processed. CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:18:43 3696 (0x0E70)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:18:43 3696 (0x0E70)
Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds... CONFIGURATION_MANAGER_UPDATE 2018-10-08 13:18:43 3696 (0x0E70)

Please let me know if anyone knows.

 

[Optimo]

I think I've resolved this. The SQL user accounts below did not exist, but these should be created as part of the initial SCCM installation. Not sure why these did not exist in our DB:

- smsdbuser_ReadOnly

- smsdbuser_ReadWrite

- smsdbuser_reportSchema