-
Bug
-
Resolution: Fixed
-
High
-
10.67
-
1
-
Severity 3 - Minor
-
Avengers - SCORP1
Issue Summary
Time Tracking : Timesheet Export throws error "Operation is not allowed when the object is closed." in the export file, hence it can't be regularly opened in Excel.
- The issue can be noticed when there are huge amount of data being processed.
- The error in the export file looks like:
<p>ADODB.Recordset</font> <font face="Arial" size=2>error '800a0e78'</font> <p> <font face="Arial" size=2>Operation is not allowed when the object is closed.</font> <p> <font face="Arial" size=2>/ReportsGenerator.asp</font><font face="Arial" size=2>, line 3278</font>
- Investigating server-side logs, SQL queries and Stored Procedures, we've found multiple timeout errors while executing RPM_GET_TIMESHEET_EXPORT stored procedure.
Steps to Reproduce
- As a pre-requisite, one must have a huge data set of time tracking-related data to attempt timesheet export.
- Click on Time Tracking
- Go to Reports
- Scroll down and click Timesheet Export
- Set Time Period to Extract Period
- Set Period to any full month long period e.g. "Jan 1 2020 – Jan 31 2020"
- Click Export button
Expected Results
- A consistent report file containing timesheet data for the corresponding selections.
Actual Results
- A report file containing an error message.
- Multiple timeout errors while executing RPM_GET_TIMESHEET_EXPORT stored procedure in the logs.
Workaround
- Narrow down the amount of data getting processed by:
- Informing a single User at a time;
- Shrinking the time period for the report;
- Apply any additional filter which is available on Timesheet Export page: region, time approver, etc
- relates to
-
JIRAALIGN-1031 Timesheet Export produces an empty report when exporting high volume data set
- Closed
-
ALIGNSP-554 Loading...
- mentioned in
-
Page Loading...
- resolves
-
ALIGNSP-2393 Loading...