This probem happens when the limited SQL account used by the SEPM doesn't have permission to use the sp_executesql stored procedure.
Starting with SEPM 14, the Reporting server uses a limited SQL account 'REPORTER_
' to query the information used on the Home, Monitors and Reports pages. This account inherits permission to the sp_executesql stored procedure from the Public role, which is associated with the master database in the SQL instance. If the SQL server has been hardened by removing permission to run the sp_executesql stored procedure from the Public role, the SEPM will be unable to load the SEPM Home page.
Confirm the Public database role has permissions to the extended stored procedure sp_executesql. The following SQL query can be used to add the permission back to the Public role: GRANT EXECUTE ON [sys].[sp_executesql] TO [public]
Note: If you do not want to add sp_executesql permissions to the Public role, you can create a separate database role under the master database, and assign this role to the SEPM reporting SQL user.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe