Updated to 9.0.4.2.98 on Thursday in PROD

 4 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
Greg Moeller
Veteran Member
Posts: 1498
Veteran Member
    Updated on Thursday and now gettting repetitive errors in the log about ReportEngine not compatible with CrystalEngine.
    Lawson has a JT opened for it, JT-293938, but we are wondering what we can do in the meantime.

    Can I downgrade LBI by applying a 'Update' ? Hesitant to upgrade to v 10.0.0.0 because of all of the zeros.

    Error involves the scheduling and emailing of reports.. coming out corrupt, or prompting for an Oracle database id/password which MANY users do not have.

    Any thoughts or suggestions?

    Thanks ahead of time,
    -Greg
    Chris Martin
    Veteran Member
    Posts: 277
    Veteran Member
      If you are on Oracle, which JDBC Driver do you have installed on the LBI server? There is a known issue with 11.2. I believe 11.1 works properly.
      Matthew Nye
      Veteran Member
      Posts: 514
      Veteran Member
        i had a similar issue with the ReportEngine not compatible with CrystalEngine and getting prompted for an Oracle username and password when I was using override data source. It was related to the incorrect drivers being copied into the RS lib. I think its because my designer was a different version than the RAS. uninstall all Crystal products, reinstall RAS and Editor but make sure theyre both on the same level, patch RS even if its a repetitive patch.
        If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
        Greg Moeller
        Veteran Member
        Posts: 1498
        Veteran Member
          Thanks all! We haven't changed RAS or the Designer... and it was all working fine before the update. And so far today, I haven't heard of any issues... (That's not saying that there aren't any though...)
          Elena
          New Member
          Posts: 2
          New Member
            we have the same issue, but we're not in LBI Prod right now. The prompt for user and pwd is only with the CR reports that get information from the OLAP cube; we're also researching how to avoid this prompt