Custom Reports- The database login failed. No error

SOLVED

We are having an issue where we are modifying a custom report in Crystal (minor change such as adding a column) and adding the updated report back into sage. Users are not able to run the custom report anymore. The get a "The database login failed. No error" message (screenshot attached) and then nothing happens. We are on Sage 100 2019 Premium. We did notice that issue does not happen for every user. We are not modifying any of the connections to the database that would cause that error. Has anyone seen a similar issue/ can provide guidance?

Parents
  • 0

    You probably clicked the checkbox for the trusted connection instead of typing in the MAS_Reports password.  (This breaks the report for anyone who doesn't have SQL read permissions for their Windows login).

    In CR, click File - Summary Info, remove the Keywords, save, close and run from Sage again. 

    You should be prompted to convert the report, which might fix the data source.

  • 0 in reply to Kevin M

    Thank you for the response. I followed the instructions and had user run from sage and they were prompted to convert the report (which they did) but after still received the same error message.  The strange thing in the past this has not been an issue for modifying crystal reports and I don't believe I changed any settings since it started.

  • +1 in reply to Deshon Beathley
    verified answer

    Using a named DSN can also break a report's functionality (for users on a machine without that DSN configured).

    Either way, to fix a broken data connection, this is what I do.  (Sage may have some other recommendation...).

    Find a custom report that works... open in CR and do a Database - Verify Database.  Type in the MAS_Reports password when prompted (avoiding the Integrated Security checkbox... never use that).

    Don't save changes, closing the functional report, while leaving CR open.  Now open your broken report and click Database - Set Datasource Location. 

    Reassign each table in your report to use the equivalent table in the active connection you made above... it will be shown with a little plug icon in the My Connections list.

    Save, having replaced the broken data connection with one you know does work.

Reply
  • +1 in reply to Deshon Beathley
    verified answer

    Using a named DSN can also break a report's functionality (for users on a machine without that DSN configured).

    Either way, to fix a broken data connection, this is what I do.  (Sage may have some other recommendation...).

    Find a custom report that works... open in CR and do a Database - Verify Database.  Type in the MAS_Reports password when prompted (avoiding the Integrated Security checkbox... never use that).

    Don't save changes, closing the functional report, while leaving CR open.  Now open your broken report and click Database - Set Datasource Location. 

    Reassign each table in your report to use the equivalent table in the active connection you made above... it will be shown with a little plug icon in the My Connections list.

    Save, having replaced the broken data connection with one you know does work.

Children