View Full Version: Lbi Back Office Reporting

LawsonTalk > Reporting (NEW!!) > Lbi Back Office Reporting



Title: Lbi Back Office Reporting
Description: Back Office files are incomplete.


mwhatley - November 15, 2007 06:37 PM (GMT)
Our LBI server inconsistently stops converting the prt/lxr files to pdf for LBI in the middle of publishing a report from the back office. Typically the reports are around 20-25 MB. This has been going on since we went live on LRS in June 2007. Most of the time it works fine, but sometimes it stops creating the pdf before it processes all of the cost centers tagged in the prt file. We are currently on LBI 9.0.1.6. and 8.0.3 ENV. We do not cache LBI reports.

Sometimes the LXR file is not fully created and sometimes the PDF is not all there. I can rerun the report two and three times and then run the report again and it will create the LXR, XML and PDF correctly. It is very inconsistant.

Has anyone else seen this problem?

Milo - November 29, 2007 07:35 PM (GMT)
We are running on LSF9 and LBI 9.0.1.8. Went "live" at the beginning of Sept. 07. We've seen a few problems with report creation early on, during the Spring. Lawson advised to go to Business Objects and get updates from them. One update did make LBI run better; I think it was SP2... The next time we had trouble, I tried the absolute latest update from BO, which I believe was SP3, and it screwed things up, so I backed it out. We've been fine since.

So you might want to look at your Business Objects Crystal Reports RAS. Not saying it's a 100% cure, but it's something to consider.

mnye - December 3, 2007 06:52 PM (GMT)
frst thing I would do is apply the latest patch, if you dont want to go through major conversion hoops, go with 9.0.1.10 patch. There were a lot of bugs in RS prior to 9.0.1.8. If you go to 9.0.2.2 there are some repository database changes that are required that can get a bit tricky.

mwhatley - December 27, 2007 04:06 PM (GMT)
We figured out what the problem was. Our test environment was trying to pull the reports at the same time the production environment was. Once our test environment was repointed we were fine.




Hosted for free by InvisionFree