'Failed to open the connection' when attempting to run the custom reports through FIMS
  • 02 Jun 2023
  • Contributors
  • Dark
    Light
  • PDF

'Failed to open the connection' when attempting to run the custom reports through FIMS

  • Dark
    Light
  • PDF

Article summary

The ODBC connection will successfully connect through the odbc data source administrator, but fails with the error "Failed to open the connection" when attempting to run the custom reports through FIMS

Answer:
This issue occurs because after the ODBC data source is built, the registry now has two separate entries for data sources which are both assigned to port 2600. They are under HKEY_LOCAL_MACHINE -> SOFTWARE -> ODBC -> DEFAULT and Foundsql92, under the "PortNumber" keys (for 32-bit versions of Windows), and under HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> ODBC -> DEFAULT and Foundsql92 (for 64-bit versions). To solve the problem, right-click on PortNumber, select "Modify," change the "Value Data" entry to 2601 instead of 2600 and hit OK. Then try the report in FIMS again, and you should be able to confirm that it will function correctly

The ODBC connection will successfully connect through the odbc data source administrator, but fails with the error "Failed to open the connection" when attempting to run the custom reports through FIMS

Answer:
This issue occurs because after the ODBC data source is built, the registry now has two separate entries for data sources which are both assigned to port 2600. They are under HKEY_LOCAL_MACHINE -> SOFTWARE -> ODBC -> DEFAULT and Foundsql92, under the "PortNumber" keys (for 32-bit versions of Windows), and under HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> ODBC -> DEFAULT and Foundsql92 (for 64-bit versions). To solve the problem, right-click on PortNumber, select "Modify," change the "Value Data" entry to 2601 instead of 2600 and hit OK. Then try the report in FIMS again, and you should be able to confirm that it will function correctly.

Was this article helpful?