The database login failed. Failed to open the connection: Failed to open the connection: {GUID}.rpt when printing a report or form

Description

Error: “The database login failed. Failed to open the connection: Failed to open the connection: {globally unique identifier – GUID}.rpt” when printing a report or form in Sage 100 ERP
Examples as follows:

  • The database login failed. Failed to open the connection: Failed to open the connection: SO_SalesOrder1{F235ED01-ADD3-35B9-3EAF-E91A19B11562}.rpt
  • The database login failed. Failed to open the connection: Failed to open the connection: PO_PurchaseOrder2{F235ED01-ADD3-35B9-3EAF-E91A19B11562}.rpt

Disclaimer

Operating System Warning
This solution requires advanced knowledge of your computer’s operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions.

Cause

  • The Sage 100 ERP workstation client was not installed in the correct manner.
  • Files associated with the Crystal Reports runtime engine may not have been registered properly, or may have become corrupted.
  • The SOTAMAS90 DSN is corrupted or incomplete.
  • If using the Client Server ODBC Driver for Sage 100 Advanced, it may have stopped running.

Resolution

Section I: Reinstall Workstation Setup

  1. Uninstall the Workstation Setup client for Sage 100 through Control Panel, Programs and Features
    • For further details, refer to Article ID 18240 How to uninstall Workstation Setup for Sage 100 ERP
  2. Run Workstation Setup for Sage 100 ERP following the proper steps and procedures to ensure prerequisites are correctly installed and registered with the correct permissions
    • For further details, refer to Article ID 18248 How to install Workstation Setup
  3. If a clean workstation reinstall does not resolve, proceed to Section II

Section II: SOTAMAS90 DSN may be damaged or missing

  1. From the Windows Desktop, open Start, Control Panel, Administrative Tools, Data Sources.
    • (Note: For 64-bit operating system, you must run ODBCAD32.EXE from the “C:\Windows\SysWOW64” folder to access the 32-bit ODBC Data Source Administrator.
  2. On the User DSN tab, check for SOTAMAS90
  3. If SOTAMAS90 exists, delete the SOTAMAS90 entry manually using the Remove button
  4. Uninstall the Workstation Setup client for Sage 100 through Control Panel, Programs and Features
    • For further details, refer to Article ID 18240 How to uninstall Workstation Setup for Sage 100 ERP
  5. Run Workstation Setup for Sage 100 ERP
    • For further details, refer to Article ID 18248 How to install Workstation Setup

Section III: If using Sage 100 Advanced Client/Server ODBC Driver

  • If using the Client/Server ODBC Driver for Sage 100 Advanced, restart the Service

Support

If necessary, seek the assistance of Acute Data Systems to help provide assistance with this process.