LBP - Custom URL Failed for an unknown reason.

 3 Replies
 0 Subscribed to this topic
 3 Subscribed to this forum
Sort:
Author
Messages
Lorena
New Member Send Private Message
Posts: 3
New Member
Hi, When trying to run an LBP report I get the following Error Message: "Custom URL Parameter Failed for an unknown reason" Lawson Global Support has not been able to assist thus far and the only article ID:557222 I found did not resolve my problem. After hours of diagnosing if it is a Port issue, URL settings issue, IIS websphere issue, it appears that LBP cannot communicate with LBI. The LBP reports are lawson solution pack reports that were deployed successfully some time ago. Both LBI and LBP are on the same server therefore it is difficult to troubleshoot network traffic. I was told that although my problem is the LBP reports the problem is more likely on the LBI side because LBP and LBI talk to each other thru a parameter servlet setting on the LBP server which sends info back to LBI. Logs were not very helpful, but there was a consistent message about Not able to connect in the systemout.log file. If anyone has experienced this and can advise me of a solution or direction on what else to check, I would appreciate it very much. thank you,
Any ideas?
Veteran Member Send Private Message
Posts: 641
Veteran Member
I ran into the same issue with older verison of LBP. It has since been fixed with the newer release. Which version you are on?
Lorena
New Member Send Private Message
Posts: 3
New Member
Hi, We are on LBP version 9.0.0.10.118 LBI products Framework services, Reporting Service version is 9.0.3.2.111. If I read correctly article 558218 LBP 9.0.0.10 is certified with LBI:9.0.3. I was able to make some progress as far as the messages in the systemout.log file but that did not resolve my original problem. That problem was a data source did not have a correct port. Regarding your comment about version, did upgrading resolve the problem for you? Thank you. Lorena
Lorena
New Member Send Private Message
Posts: 3
New Member
sorry I just noticed that you did say the newest release resolved your problem.