Version 7.1.5 Error after Upgrade (Modules), DB queue not processing

Why do you think that you need to run the statements from the knowledge base article in the first place? The article quotes a different error message "Database error 50000: Cannot enable broker because of other users are active." which does not appear in your log.

The error in your log appears because the system still thinks it is running in single-user mode due to the migration.

I suggest checking the columns DialogDatabase.SingleUserProcess and DialogDatabase.SingleUserStart. They are normally set to 0 and Null respectively.

By the way, while the update is running, the message in the log is totally normal as the migration turns on the single-user mode.

Hi Markus,

As I said above, while upgrading the DB, I got this error "Database error 50000: Cannot enable broker because of other users are active." .
Then as per knowledge article I followed the steps and then continued with the upgrade and successfully completed.

I can see DialogDatabase.SingleUserProcess and DialogDatabase.SingleUserStart values are 0 and Null. 

Any other check/workaround to solve this.

Regards,

AAD

Did you check the database journal for any issues? If in doubt, contact support.

This is the error message.

It looks like one of your custom decision rules contains invalid SQL code.

Yes, but is this error dependent with Database Error 5000 processing is disabled ?

If you take a look into your DBQueue I assume that it is not empty and this error might prevent some calculations to run that lead to that error.

I suggest contacting support.

Hi Markus,

I have contacted support and want to update you as well.

I have found and fix the approval procedure and that error has been removed now for the DB queue.

Still the new DB queue calculation is not working, I tried restarting the service too.

Then I found something strange, as my error in job service logs complains about the procedure QBM_PJobQueueLoad.

I tried of "exec sp_helptext QBM_ PJobQueueLoad " which returns back very few lines.When I tried same on higher environment, I get a huge procedure back and I guess after I added my new modules the actual procedure got vanished and overridden. I can copy the procedure from my other environment and am not sure about the impact and also the right way.

Regards,

AAD.

This looks like your migration hasn't been finished completely. I suggest starting the migration again to restore all ootb functions and procedures.

I restored my backup and gave a try one more time, which ended up in same.