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
Articles in this section
- 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.
Comments
0 comments
Please sign in to leave a comment.