Applied CTPs and now PDF's will not render - only a blank gray box is displayed.

We applied a large batch of CTPs last night (we are on 9.0.1.8 - Windows ). This morning we are noticing that we can no longer view pdf's of the reports. We can view the reports in text format, but the pdf's display as a blank gray screen. The size is 0 kb, so it's an empty file. Has anyone seen this before? I checked the KB, but no luck so far.

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

the PDF files are in the $LAWDIR/print/xxxx/xxxx

directory. Check your Winodws directory permissions.

asztudenyak

Permissions are fine - nothing was change or looks any different than it was. Users are all members of the user group in those folders.

[Updated on 6/16/2014 9:32 AM]

unknown

Is it just the PDF files for reports that were affected by the CTPs? If there is a PDF that already exists for the job in the users print directory, does deleting that allow the new PDF to display?

asztudenyak

The issue is for reports generated AFTER the CTPS were applied last night. Existing pdf reports display fine, as they are not empty files. Viewing a report in TEXT format works fine. But for new reports, the pdf file is being created empty. As you know, the PDF file is not created until the user selects the pdf format. At that point Lawson is creating an empty file, so all the user gets is a blank gray box.

[Updated on 6/16/2014 10:24 AM]

[Updated on 6/16/2014 10:25 AM]

lbecker

Verify that $CGIDIR/cgi-bin/webrpt.exe is setuid to root.

Verify the version of $CGIDIR/cgi-bin/su_webrpt.exe.
Verify the version of $CGIDIR/cgi-bin/webrpt.exe.
Verify the version of $GENDIR/bin/bldxffiles
Try running bldxffiles from a command line to see if it can build a PDF file for you.

Maybe try rolling back one or more of these to a back-up in the patches if you get desperate.

asztudenyak

CGIDIR? Not sure we even have that anymore - isn't that from 8.03?

lbecker

Lawson doens't use it anymore. I kept the variable defined because it was handy. su_webrpt.exe still needs to be somewhere.
It is in $GENIDR/cgi-bin now, on my 9.0.0 environment.

asztudenyak

Hmm. Never knew about bldxffiles before - thanks. I tried it, but it creates an empty file, just like Lawson is doing in portal.

asztudenyak

We are on 9.0.1.8. I see a webrpt.exe under LSF9PRODgencgi-bin. I don't see an "su_webrpt.exe" there.

robert-canham

We've had issues with converting to CSV before after an upgrade. We always run rptgen for the entire product line and that seems to take care of it.

asztudenyak

RPTGEN? Not familiar with it. Is that something that can be run during production hours, or does it have to be run in off hours?

0712050809193544.doc

unknown

RPTGEN should be included whenever a compile is run. Much in the same way, SRGEN is included for online applications.

asztudenyak

Interesting. We've been running Lawson for 12 years now and this is the first time I have heard that. Not saying that you are wrong, it's just really odd that we have never included it as part of our process. Will it affect any users/processes that are currently, if I were to run it now?

[Updated on 6/16/2014 12:47 PM]

unknown

Generally, RPTGEN is run before the application object is created. So, product line compile is suggested. Also, verify the rpt.cfg as well.

asztudenyak

Kevin, will running RPTGEN during production hours affect any users or processes currently running? Should I wait until after hours to run this?

unknown

In case anything goes wrong, I tend to run such product line processes off-hours.

unknown

have you checked the system logs to see if there are errors - if i look in our ios.log file (we run on aix) i can see statements showing when bldxffiles are run - just wondering if it failed if you would see any messages there that might help youi?

asztudenyak

Yes I checked all logs - no errors at all.

asztudenyak

I think the problem is something else. I'll post back after we do a couple of things tonight. Oh, and there are errors in the IOS log for the bldxffiles.

unknown

Sometimes the bldxffiles command can be finicky. I found purging the old .xml files beforehanded helped.

Wichtige Hinweise zur PROFILE Donglelizenzierung.pdf

asztudenyak

Okay, the issue was much bigger than the reports. We also discovered that programs would not run in LID (but working in portal). We had to take the system down, run SRGEN, and compile the entire product line. (In addition, after all that we ened up with a threading problem as the system slowed to a completel crawl - but this was corrected by a reboot). Turns out that because we had added a custom table, AFTER the entire CTPS/reorg/compiles process, we ended up with a mismatch between actual programs and cached programs. Even though we did do did a blddbdict and a reorg, after adding the table, somehow it didn't quite get there...and since we failed to to a cache refresh afterwards, we didn't realize there was an issue.

Sooooo...long story short, srgen, recompile, reboot. Problems fixed.

Copyright © 2025 Infor. All rights reserved.