We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.

Data Failure Push From Assure To Data360 DQ+
#UOCF021 : The system failed to find the rerun-of control data instance with ID {0}.
#UOCF019 : The system failed to find any runs in the most-recent-cycle control entity control_entity_name.
#UCAP003: The Capture Source service failed to initialize.
#UOCF014 : The system failed to find any run for cycle cycle_number in the most-recent-run control entity control_entity_name.
#UOCF006 : The system failed to create a cycle because control data instances for the cycle ID {0} already exist.
#ULAY025 : The system failed to open the URL specified_URL.
#ULAY016 : The system failed to delete layout layout_name. There are total_number_of references that refer to this layout list_of_references.
#ULAY007 : The system failed to generate fields because class class_name could not be found.
#ULAY006 : The XML schema has more than one root element.

#UCAP003: The Capture Source service failed to initialize.

Vikrant Kishore

November 03, 2021 12:44
Updated

Probable Cause: It's an unusual error which is not the product/platform Locking service as it relates to control point concurrency. This is a SQL Server thing, and relates to the lock Timeout property on the database URL for the product

DATABASE_URL=jdbc:sqlserver://${DATABASE_SERVER}:${DATABASE_PORT};databaseName=${DATABASE_NAME};lockTimeout=30000;responseBuffering=adaptive

Above is a 30 second lock timeout.

Resolution : SQL Server management studio reports can be run to understand what locks are present and why. A database restart would also clear everything. we can also find out the SPID by using "sp_who2" and kill the SPID without restarting.

Notes : (Please consult customer support if you are still seeing this)

Comments

0 comments

Please sign in to leave a comment.

Articles in this section