LBI Error when publishing Crystal Report

Sort:
You are not authorized to post a reply.
Author
Messages
Jan
Veteran Member
Posts: 55
Veteran Member
    I've just published a Crystal Report into Lawson LBI, and receive the following error when I view it:

    Invalid table number. CR Labor Utilization - Monthly {1D97554B-8470-4553-A3C3-D4B42702C5B1}.rpt

    The report runs fine in Crystal.
    Matthew Nye
    Veteran Member
    Posts: 514
    Veteran Member
      Id check for are special characters in formulas. But first, there should be a more verbose error in your application server logs. can you post that?

      matt
      If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
      Jan
      Veteran Member
      Posts: 55
      Veteran Member
        Thanks for the reply Matthew.  Here's more informatio about the error

        Message: Invalid table number. CR Labor Utilization - Monthly {D4180E43-DEB6-4686-85D6-22DBE5CFB31F}.rpt  
        Description: Report Request Failed For: CR Labor Utilization - Monthly.rpt
        Additional Text: Publication Key: (COMPANY\equal to\1)(ACCOUNTING UNIT\equal to\1B0007)(COMPANY\equal to\1)(ACCOUNTING UNIT\equal to\1C0007)(COMPANY\equal to\1)(ACCOUNTING UNIT\equal to\1D0007)(COMPANY\greater than or equal to\1)(ACCOUNTING UNIT\equal to\*)


        Exception Stack Trace
        com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException: Invalid table number. CR Labor Utilization - Monthly {D4180E43-DEB6-4686-85D6-22DBE5CFB31F}.rpt---- Error code:-2147483142 Error code name:failed at com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException.throwReportSDKServerException(Unknown Source) at com.crystaldecisions.proxy.remoteagent.s.a(Unknown Source) at com.crystaldecisions.proxy.remoteagent.r.long(Unknown Source) at com.crystaldecisions.proxy.remoteagent.r.int(Unknown Source) at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.if(Unknown Source) at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.do(Unknown Source) at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.refreshReportDocument(Unknown Source) at com.lawson.efs.ers.ReportEngines.CrystalEngine.processReportRequest(CrystalEngine.java:178) at com.lawson.efs.ers.ReportEngines.ReportEngine.processReportRequest(ReportEngine.java:79) at com.lawson.efs.ers.ReportEngines.ReportRequest.process(ReportRequest.java:495) at com.lawson.efs.ers.web.RequestHandlerServlet.doPost(RequestHandlerServlet.java:893) at com.lawson.efs.ers.web.RequestHandlerServlet.doGet(RequestHandlerServlet.java:92) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
        Matthew Nye
        Veteran Member
        Posts: 514
        Veteran Member
          Can you Verify Database within Crystal, Save and publish?
          If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
          jrbledsoe001
          Veteran Member
          Posts: 91
          Veteran Member
            Hello,

            This error message is familar to me. I got this error message when I did not have a field on the report to burst. In my case the field (accounting unit) was embedded in the page header group text. Lbi could not read the field to burt. I added the field accounting unit to the report and the error message went away. I hope this helps you because this one was driving me crazy.
            Jan
            Veteran Member
            Posts: 55
            Veteran Member
              Thanks jrbledsoe - I checked my report to make sure the bursted fields were there. They were in the group header. Just in case, I moved the same fields into the detail and suppressed them, then republished. The report still hits the same problem though. One thing I thought may be the problem - and it still may be - is that my main Crystal table was created with the 'Add Command' in database expert. The fields I burst on are from this table. I don't know if this can cause the problem I'm seeing.

              For Matthew, I did verify the database within Crystal - that worked fine. I then republished but I still get the error.
              Jan
              Veteran Member
              Posts: 55
              Veteran Member
                Hi Matthew,

                I verified the database within Crystal, saved and republished it.  I still get the same error.  Do you  know if LBI has problems bursting on fields that come from a Crystal 'add command' query?
                Matthew Nye
                Veteran Member
                Posts: 514
                Veteran Member
                  Not that I know of but also, you are publishing the report new correct? So at this point in the process, bursting shouldnt be a factor.
                  If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
                  Char
                  Veteran Member
                  Posts: 62
                  Veteran Member
                    I can see how it might work differently for command reports; I opted not to use bursting because my client would have had too much maitenence associated with it. Instead, I pass the UserID from LBI into the report through appended record selection on the maintain parameters screen but I couldn't do this for my command reports, I had to instead create a parameter within the command and link that parameter to the UserID within LBI. Matthew certainly knows more than I do about the bursting but depending on whether or not LBI tries to pass in the bursting information pre-query or not, it could be a similar issue - it can't be done pre-query with a command.
                    Jan
                    Veteran Member
                    Posts: 55
                    Veteran Member
                      just an FYI on this. Thanks to one of our I.T. guys, this problem has been resolved. The issue was the database driver that was in use. Apparently if the report is driven by a sql script (in the command object) you need to use the oracle db driver. We had been asked to use the Microsoft db driver for Oracle and never had a problem - until I developed this Labor Utilization Report. This report is by far the most involved I've written and most of the report's data is supplied by the command object. As I mentioned earlier, I could always run the report in Crystal, but it always failed in LBI. Once we switched the DB driver to Oracle, it worked both in Crystal and LBI.
                      You are not authorized to post a reply.