CMS Snapshot Analysis - Compute Snapshot - Fatal Error - Error while executing Procedure - function diag scope adobest001 does not exist

This page outlines the issue where a snapshot fails at the compute snapshot step "Failed to execute the procedure".
Looking at the corresponding Cast-MS log file, the full stack trace gives the below information:

ERR: 2015-03-03 16:08:35: Error while executing Procedure
com.castsoftware.java.InternalException:Error while executing Procedure
.
.
ERROR: function obs_thetys_local.diag_scope_adobest001(integer, integer, integer, integer) does not exist
Hint: No function matches the given name and argument types. You might need to add explicit type casts.
Position: 15
org.postgresql.util.PSQLException:ERROR: function 
obs_thetys_local.diag_scope_adobest001(integer, integer, integer, integer) does not exist
Hint: No function matches the given name and argument types. You might need to add explicit type casts.
Position: 15

From the error we can see that the failing procedure is diag_scope_adobest001.
This procedure is used by QR "Close SQL connection ASAP" for its metric computation.

The issue is encountered if you are using an assessment model that is imported from the central and not the default one, where this quality rule calculation is wrongly configured. The computing configuration in the imported assessment model is defined based on stored procedure instead of scope and property.
When the metric is computed, the stored procedure called is diag_scope_adobest001(integer, integer, integer, integer) with 4 parameters but the correct and existing procedure is with 6 parameters.

1. Run snapshot
2. It fails with the mentioned error.

Using the correct computing configuration for this QR will resolve this issue.

Solution:

1. Open the metric QR in your imported assessment model
2. Computing settings > Computing configuration
3. Change from computing based on SQL Procedures to computing based on Scope and Property
4. Set the values to:
     SCOPE_ID = 602
     PROPERTY_ID = 140508
5. Synchronize your local and central base.
6. Run the snapshot again

This issue is also planned to be fixed in 7.3.6 SP.