24129 A database error occurred: Ambiguous column name 'ProcSetID'.

  • 16 February 2021
  • 0 replies
  • 35 views

Badge +4
  • Nintex Employee
  • 6 replies
 

24129 A database error occurred: Ambiguous column name 'ProcSetID'

kbt143656

PRODUCT
K2 blackpearl
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue

When Navigating to K2 Workspace > Process Overview > Process > Click on View Flow, the below error occurs:

 

24129 A database error occurred: Ambiguous column name 'ProcSetID'.

 

Image

Symptoms

By reviewing the SQL Profiler trace you will notice that the below query:

exec [ServerLog].[kPSIDFromPIID] @PIID=''Number' will be present on SQL trace.

 

By executing this directly in SQL Query the same error will be generated.

 

Msg 209, Level 16, State 1, Procedure kPSIDFromPIID, Line 8

Ambiguous column name 'ProcSetID'.

 

Please note that this is a K2 Database StoreProc

K2 database modification is not allowed as it might leave the environment in an unsupported state. This must only be done with the assistance of, or when instructed to do so by K2 Support. 

By doing a compare of a clean K2 Database StoreProc and the problematics storeproc you will notice no differences but when investigating the below table it will be discovered that the ProcInst Table had a duplicated entry of ProcSetID column.

 

SELECT * From [ServerLog].[ProcInst]

 

Image

Resolution

Should the results display an extra column, it would indicate that this is causing the error. To resolve this issue, direct database modification will be required.

 

Please log a K2 Support Ticket on the K2 Customer Portal for assistance in resolving the issue.

 

Please Note that direct K2 database modification is not allowed as it might leave the environment in an unsupported state. This must only be done with the assistance of, or when instructed to do so by K2 Support.
Also see here

0 replies

Be the first to reply!

Reply