on 07-28-2022 6:12 AM
Hello,
since this week, our Crystal Report publication is no longer working. No export is created anymore.
The publication worked for years now and was executed once per month.
What it is doing is to check with a Control document how much suppliers there are, and to create one PDF document for each of the relevant suppliers.
The error message is:
"2022-07-27 06:40:57,517 ERROR [PublishingService:HandlerPool-10] BusinessObjects_PublicationAdminLog_Instance_13387079 - [Publication ID # 13387079] - Scheduling document job "Export_Report" (ID: 13,387,094) failed: The field was not found. (CRS 300003) (FBE60502)".
The error is shown in the error log repeating for every supplier that the system wants to process.
Please see screenshots of the relevant publication properties,
As it was working without any problems for years, I guess something in the underlying query has changed.. but we checked it and couldn't find anything.
Maybe do you know what the "The field was not found" could mean?
Thank you
Best Regards,
Johann
What happens if you open the report in Crystal Designer and do: Database, Verify Database... ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Ido,
this is also what we tried because it was described in an SAP Note that sounds quite similar compared to our error message:
1916152 - Publications fail with Error "Some parameters are missing values (CRS 300003) (FBE60502)" ...
The error message is not the same as we have exactly.. the error code is the same but it says "Field was not found".
When veryfing all datasources it always says "The datasource connection has been verified and the report is up to date again". Sounds as if something was found and now its fixed.
We then save the report again.
But the next time we load the report and click on verify, the same message appears again.
Unfortunately nothing changes with this..
Thank you!
Are you checking the data on all of the reports in the publication? It could be that something has changed so that the fields you're using to burst on don't match up.
-Dell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My guess is that a column on the underline table/view was changed (renamed/deleted,...) and now the query could not find it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manuel,
thanks for the answer.
I would also assume that this could be the problem but we checked all underlying BW queries that the export is using and none was changed.
Further, I can "open" the report in BI Launchpad and show all the pages without problems. I could even export page by page manually from there.
Only, the publication job itself is throwing errors.
Thanks
User | Count |
---|---|
75 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.