Our accounting department ran a Journal Listing for the previous month, and it reported this error in the System Monitor:
Program Ice.Services.Lib.RunTask when executing task 10615306 raised an unexpected exception with the following message: RunTask:
Ice.Core.SsrsReporting.SsrsCaller.SsrsException: The SSRS server returned the status code 500 (InternalServerError) with the following error text:
Excel Rendering Extension: Number of rows exceeds the maximum possible in a worksheet of this version. Rows requested: 1054048. Maximum rows: 1048575. —> Microsoft.ReportingServices.ReportProcessing.HandledReportRenderingException: Excel Rendering Extension: Number of rows exceeds the maximum possible in a worksheet of this version. Rows requested: 1054048. Maximum rows: 1048575. —> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors
We got around this by running the report for shorter date ranges, but we’re now wondering by the report is pulling this many rows.
It appears that journal entries are being created for every STK-MTL transaction.
There are large numbers of rows in GLTrnDtl table with a description like this:
STK-MTL Part:19P583-01 Job:807379/11/160
They seem to coincide with when the Capture COS/WIP Activity process was run.
We updated to Kinetic 2024.2 a couple of months ago, and it started happening shortly afterwards.
Does anyone have any idea what’s happening here?