none
SUP Sync fails with error SUSDB is read-only RRS feed

  • Question

  • Hello,

    I am running a SCCM 1710 with remote SQL instance on AG. Since last week SUP role on primary started throwing error stating SUSDB is read-only mode and today the Sync failed with the same error. Also observed that on WSUS console, it marks the WSUS service is not running when in actual its running. Have tried restarting the services and server a couple of times now.

    Any direction to trouble shooting is highly appreciated.

    Error on wsyncmgr log-> Sync failed: Failed to update database "SUSDB" because the database is read-only. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow

    Tuesday, August 13, 2019 5:26 PM

Answers

  • The message you posted above is pretty clear as to the root cause: "because the database is read-only". You need to work with your DBAs to figure out why the DB is read-only and correct this. Also, keep in mind that technically, the SUSDB DB is not supported in a SQL AG (even though is generally works fine).

    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by SVJV Wednesday, August 14, 2019 3:24 PM
    Tuesday, August 13, 2019 7:47 PM

All replies

  • The message you posted above is pretty clear as to the root cause: "because the database is read-only". You need to work with your DBAs to figure out why the DB is read-only and correct this. Also, keep in mind that technically, the SUSDB DB is not supported in a SQL AG (even though is generally works fine).

    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by SVJV Wednesday, August 14, 2019 3:24 PM
    Tuesday, August 13, 2019 7:47 PM
  • Hi, This suggest folder permissions:

    https://community.spiceworks.com/topic/1902938-wsus-w-sql-express-database-is-read-only

    "Well, you were definitely on the right track, but for some reason it wasn't NT Service\MSSQL$EXPRESS, but NT Service\MSSQL$MICROSOFT##WID.  Maybe b/c it was converted from WID?  Either way I'm back in business.  Thank you to both."

    Tuesday, August 13, 2019 8:39 PM
  • Thank you Jason :)

    Seems the SCCM and WSUS both picked up the secondary DB in AG group , when this was switched back to primary (by removing and readding the SUSDB) the WSUS service picked up and SUP sync worked successfully.

    Wednesday, August 14, 2019 3:27 PM