-
Bug
-
Resolution: Fixed
-
High
-
11.2.1
-
1
-
Severity 2 - Major
-
No
Issue Summary
The customer is seeing error with incremental number (e.g.: 2166, and then next 2167, and so on) on the Forecast page after clicking Applying Backlog Rank and choosing Portfolio and Program Increment Level Rank.
This is reproducible on Data Center: (yes)
We could not find a reproducible scenario that would lead to the creation of the duplicate in the Database, but if we manually insert duplicate values for the same epic or standalone feature after the table tblPortfolioRankItems, the query will fail with the above error.
Steps to Reproduce
- Choose Program
- Choose Program Increment
- In Sidebar, go to Forecast
- Set Team level: Program
- Set Work Item Level: Feature (Jira Epic)
- Click 'Apply Backlog Rank'
- Click 'Portfolio and Program Increment Level Rank'
Expected Results
The screen is loaded successfully.
Actual Results
The screen is showing Error #2166
The below exception is thrown in the host-ASPNET-yyyymmdd.log file:
Exception: System.Data.OleDb.OleDbException (0x80004005): The statement has been terminated. Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. at System.Data.OleDb.OleDbDataReader.ProcessResults(OleDbHResult hr) at System.Data.OleDb.OleDbDataReader.NextResult() at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method) at System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) at AgileCraft.Legacy.AdodbRecordSet.GetReadOnlyDataSet(DbProviderFactory dbProviderFactory, String connectionString, String sql, DbParameter[] parameters, AdodbCommand command) in C:\projects\alignweb\AgileCraft.Legacy\Adodb\AdodbRecordSet.vb:line 427 at AgileCraft.Legacy.AdodbRecordSet.Requery() in C:\projects\alignweb\AgileCraft.Legacy\Adodb\AdodbRecordSet.vb:line 397 at AgileCraft.Legacy.AdodbCommand.Execute(Int32& recordsAffected, IEnumerable`1 parameters, Object options) in C:\projects\alignweb\AgileCraft.Legacy\Adodb\AdodbCommand.vb:line 36 at AgileCraft.Legacy.PageFunctions.DbExecParamsConnectionTiming(Object sql, Object sqlParams, Object objConnExec, Object bCaptureTime) in C:\projects\alignweb\AgileCraft.Legacy\OOFunctions\OOFunctionsSql.vb:line 277
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- resolves
-
ALIGNSP-25730 Loading...