Prev
Next
Forums Performance Management Lawson Business Intelligence/Reporting/Crystal

Error on Published Crystal Report

 6 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
BradF
Basic Member
Posts: 22
Basic Member
1/7/2010 8:53 PM

    I was wondering if anyone has run into the below error.  The person is using the URL from a published report.

    Thanks,

    Brad

    Error
    Failed to retrieve data from the database. Details: [Database Vendor Code: 73 ] Failed to retrieve data from the database. Error in File C:\WINDOWS\TEMP\{59218E78-26EB-4820-9C3E-3AE4C90056DC}.rpt: Failed to retrieve data from the database. Details: [Database Vendor Code: 73 ]

    Char
    Veteran Member
    Posts: 62
    Veteran Member
    1/7/2010 9:12 PM
      I received a similar error when there was a space in the file name just before the file extension - a report named ABC .rpt failed but when renamed ABC.rpt it was fine.
      Matthew Nye
      Veteran Member
      Posts: 514
      Veteran Member
      1/7/2010 9:28 PM
        This could be a number of things but the most simplistic thing would be to make sure the report can run from the server. If the report is using ODBC make sure you have the correct name specified. If not, make sure the username and password are set correctly.

        Can you post the detailed essage from the log files?

        If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
        Milo Tsukroff
        Veteran Member
        Posts: 47
        Veteran Member
        1/26/2010 3:54 PM
          Matt is right about names ... data source names must be very, very, very correctly aligned between the developer's PC and the LBI Server. All the same name ... or else confusion results. Align the names, publishing works well.

          2 cents!
          BradF
          Basic Member
          Posts: 22
          Basic Member
          2/1/2010 6:08 PM
            Sorry, I've been on a project that took me away from this. I only get this error when using our TEST Server and OLE DB reports. OLE DB Reports work in PROD.
            Milo Tsukroff
            Veteran Member
            Posts: 47
            Veteran Member
            2/1/2010 7:48 PM

              How are the OLEDB sources named in the Test server?  Are they the same name, or a different name?  It looks like OLEDB data source setup may not be the same.  Also you may have to look up other names, such as the JDBC and JNDI names, to see if something's different between the 2 systems.  Good luck!

              BradF
              Basic Member
              Posts: 22
              Basic Member
              2/1/2010 8:53 PM
                Thanks Milo. Another person wrote the report, so I am checking the data source set up.