Following error occured during an upgrade > 4.9 to 4.9.1. Will anyone would be willing to help me to understand what happened?

System.Data.SqlClient.SqlException: Server user '******' is not a valid user in database 'msdb'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)


CREATE procedure dbo.[Dashboard_GetDbBackups]
AS

SELECT TOP 20
name,
backup_start_date as StartDate,
backup_finish_date as FinishDate,
backup_size as size,
database_name,
CASE type
WHEN 'D' THEN 'Database'
WHEN 'I' THEN 'Differential database'
WHEN 'L' THEN 'Log'
WHEN 'F' THEN 'File or filegroup'
WHEN 'G' THEN 'Differential file'
WHEN 'P' THEN 'Partial'
WHEN 'Q' THEN 'Differential partial'
END as BackupType
FROM
msdb..backupset
WHERE
database_name = DB_NAME()
ORDER BY backup_start_date DESC

 It looks like your database user (specified in web.config) has not sufficient permissions to read MSDB database, where backup jobs are stored. Therefore creation of the querying stored procedure failed during upgrade and any subseqent call will fail as well.

Since MSDB access is not needed for DotNetNuke to work, the dashboard shall check for existance of the stored procedure and display an appropriate error message instead of a disgracefull error. Besides, the stored procedure may be rewritten to run a dynamic query, allowing the stored procedure to be created but fail when being called without permission. this would allow a user to fix the situation to get subsequent calls being successful without a need to re-run upgrade script.

you may create a blank stored procedure with same name to avoid an error when calling dashboard module.

Logged in Gemini: DNN-9631