LBI Monitoring

Monitoring processes in LBI is challenging, especially with back office reports. If it's a timing issue (LBO report run in Portal but necessary files have not been ftp'd and or created on LBI), you will usually see an LBI error, albeit cryptic. Was the user in question ever able to view the report in LBI, or are you still receiving the same error? With a generic IE error, it could've been simply a network issue...especially if it was a one-time error and the user was later able to view the report.

As far as general LBO troubleshooting, you will be very limited without remote access to the servers (LBI and the Lawson App server) involved.

thanks for you reply

The user has never been able to view the report. This same type of thing has happened sporadically in the past. I wonder if it's an ftp failure issue. On the requester side, what causes the "could not display page" to display in I.E.? Is I.E. have some type of mechanism to display this page when it doesn't receive a server response in a set amount of time? Or perhaps, does the LBI server tell the requester process that the data could not be sent?

I'm just wondering so I can point the I.T. folks in the right direction when I ask them to troubleshoot this.

I would start with these steps...

1) Verify that the historical instance exists in LBI
2) Verify that the pdf file was created on the LBI server
3) Verify that the pdf file can be viewed and displays the data as expected
4) View the most recent file in the "Pending" (I believe that's the name) folder under LawsonDocuments on the LBI Server to identify any incomplete jobs

You can also turn off bursting and ask the user to view the reprot. If the user can vuew the report without bursting then check to see whether the bursting rights for this user is set up right.

Thanks Chris

I can see that the historical instance was never created on the LBI server for the all cost center request, however there is nothing in the pending directory to indicate an incomplete job. To double check this, I tried again to recreate the historical instance with all cost centers. The request handler comes back with "The website cannot display the page" in about 10 seconds. Nothing shows up in pending and a pdf is not created. Is there some type of timeout feature that the request handler could be running into?

Ruma,

That is another good troubleshooting suggestion, however I believe the user will see an error related to insufficient rights if this is the case.

 

Jan,

It's difficult to say without looking at it, but it's possible that the necessary files are not being created when the report is being run in Portal.  It's also possible the issue is with the ftp process.

A few questions...

Do you have any other reports utilizing the data source that is pulling the problem report over?
Are you having any issues with these reports as well?
Do you have more than 1 LBI install?
If so, do you have do you have active LBO data sources in more than 1 LBI install pointing to the same Lawson environment/data area that is being utilized to pull over the problem report?

Chris,

 

In this case the instance is not getting cretaed itself. I actually had this issue couple of times and here is what GSC did to help me:

1. I had to verify that the ftp source setup on LBI was working.

2. the datasource for back office was also working. There is a test connection on both of these which when clicked should give valid connection established if working properly.

3. then click the SAVE button on the data source.

hth,

Ruma.

 

Chris,

You are right. I ahve had so many kinds of issues with back office reports and so many different kinds of solutions that have helped resolve. One issue that we had for days before we could resolve was we created a dat source for back office and for months we were able to get instances whenever the back office job would run. Unknowningly the data source name was changed which caused the instances from getting created. Once the data source name switched to its original name the issue was resolved. So when it comes to back office and instances there is no easy solution to any issue related.

So when it comes to back office and instances there is no easy solution to any issue

Couldn't have said it any better!