Scheduled Crystal Report not be sent out.

Matthew,

So Im assuming you defined a PDF Printer as a device? Your upgrading Lawson environment shouldnt have effected LBI unless they share the same server. In that case, did you upgrade Adobe Reader by any chance? First off, check the path that is defined in your Printer Device used for this schedule. Next, login to your Framework Services server (if FS and RS are on separate servers, be sure you are on FS). Open a Windows Explorer and paste that directory in the address. I imagine this isnt the issue, but if you get an error here, you need to update the locaton of the Adobe Reader exe. So assuming this test passes the next thing to check is permissions.

Is the directory that is being written to remote to the FS server? If yes, are you running WebSphere under a network service account that has access to that remote folder?

Post back your results and we can further troubleshoot if none of this uncovers the issue.

According to the systemout.log just prior to the error message Lawson is trying to open Adobe from C:\Program Files\Adobe... however Adobe isn't installed on this new 64bit box. When i try to install it Adobe won't install under C:\Program Files\ only C:\Program Files (x86)\ even though both exist.
I'd like to change the path stored in Lawson but not sure where to find it.

You should be able to chose a custom location when installing Adobe Reader. If you cant get that to work changing the path is no problem but just to clarify, you said "I'd like to change the path stored in Lawson ". I want to make sure we are discussing a printer set up in Lawson Business Intelligence (or more specifically, Framework Services). If this is true, you would:

1. Go to the Tools dashboard
2. Click Delivery
3. Click Manage Devices Types
4. Find the Name that is used in your bursting set up and click it
5. You need to update the field "Path to Acrobat"

Matthew thanks. I did change the path in Lawson Framework services to point to the new Adobe path. While i'm not getting that error message any more I still can't get a scheduled job to go to a printer device however the device test is able to send a test file to the printer device.

i would validate that the report is returning data, that your user that the device is assigned to has permissions and that the bursting is set to go to all report users and report owners, not just owners, if you are not the report owner.

are there any messages in the logfiles when the schedule kicks off?