Share
Report
2,005We are having a very odd issue when we run the Accrued Purchases report (VendAccruedPurchases_NA) and I have searched both this forum and life cycle services and have not seen a solution to this issue, mainly because what we have done to try and figure out what is actually going on here, but at this point I am stumped.
The scenario is that in our Production environment, when we run the Accrued Purchases report in certain companies, we receive a result set that contains results that look like it is just returning a collection of initialized table buffers. What I mean by this is that if the report were to run properly in those companies we would receive something like 29 pages of rows in the report and we do receive that many rows, but every row looks as though it has been initialized to hold the default value of the field, so strings become the empty string and reals and integers become zeros. To compound matters however, the report only behaves like this in our Production environment. If I move the dataset to a test or development environment, the report runs just fine in those companies (to the point that we are currently running the report in the test environment, which is updated from the production environment nightly, and giving the output to the affected users.) As such, there is no way for me to debug what is actually happening here. So with that in mind, I wrote a job that would mimic running the report and passed an instance of the VendAccruedPurchasesDP_NA data provider to try and generate the data in the affected companies and then dump it into an infolog in order to see if the data was generated properly or if the record buffers returned in the dataset would return to their initialized state. We imported the job into the Prod environment and the data was returned properly, which indicates to us that the issue MUST be happening somewhere between the end of the DP execution and when the report renders in SSRS. However, as I started to dig, I found out that this report uses TempDB tables to generate the output, but at the same time, does NOT extend the SRSReportRunRdpPreProcessTempDB class in the VendAccruedPurchasesDP_NA class. At this point, I get a little lost, as the documentation indicates that the TempDB and Regular table report data sources are reports that use pre-processing, but the data provider class that serves as the parent does not appear to have any of this functionality, even though the report itself has dynamic filters set and the report has the AX_RdpPreProcessedId parameter as part of its design. I can't help but think that it is the AX_RdpPreProcessedId parameter that is leading to the result we are seeing in those companies, but I am not sure how that works and can't speculate further.
I have noted that the VendAccruedPurchases_NA report has had a number of hotfixes released over the years, but the fact that this report works fine in every environment I run it in for every company EXCEPT PRODUCTION makes me believe that the hotfixes we have not applied would have no impact on resolving this issue.
Has anybody seen anything like this or know why this may be happening? At this point I have tried everything I know and apart from getting my SQL admin to monitor a report run (which is scheduled, but I wanted to post this while I have been thinking about it) I am not sure what else I can do here.
Any knowledge you guys have would be very appreciated.
Brandt
All responses (
Answers (
