Hello HomerJ,
I have found that in the past when this issue occurred the user accounts weren't correctly provisioned within the DB for either the td user or the tdadmin user. The first thing that needs to be done is run the SQL queries:

EXEC sp_change_users_login 'Report'
EXEC sp_change_users_login 'Update_One', 'td', 'td'
EXEC sp_changedbowner 'td_admin'

*Note the td_admin is the database administrator with the required database privileges and your account may be named differently.

This musty be done after restoring any project schema (to include the qcsiteadmin schema) into the new DB.

These accounts must have the correct permissions as documented within the installation and upgrade guide. If these permissions differ in any way (more or less permissions issues can and more than likely will arise during the installation process. Check these permissions and if necessary delete all the schemas from the new DB and then remove the users and readd them insuring the correct permissions are assigned. In the past this has always resolved the issue I have sen aris,

Hope this helps,
Dan