TOPIC: Failed to open the connection. <report name>.rpt

Failed to open the connection. <report name>.rpt 28 Jun 2019 13:50 #5661

  • darrentaylor78
  • darrentaylor78's Avatar
  • Offline
Getting this error on newer laptops and desktops we've added to our environment.
-Licensed user for v1.8 of Logicity.
-All machines are Windows 10 and have same GPO applied.
-Using SQL Server Native Client 10.0 driver for DB connections. Connections tested successfully as well as other applications that rely on them work perfectly fine.
-SAP CR Runtime v13.0.19 installed.
When looking at a user's 'old' PC config and new PC config we can't find any difference in setup. Old PC works great (also Windows 10). We've uninstalled/reinstalled making sure everything was cleaned, still no joy. We've also tried v1.9 with CR Runtime v13.0.23 with the same result.
The administrator has disabled public write access.

Failed to open the connection. <report name>.rpt 28 Jun 2019 14:55 #5662

  • KCrane
  • KCrane's Avatar
  • Offline
Do the old PCs use the SQL Server Native Client also - vs the SQL Server driver? And do the newer laptops and desktops have matching ODBCs as the old PCs?
The administrator has disabled public write access.

Failed to open the connection. <report name>.rpt 28 Jun 2019 15:52 #5663

  • darrentaylor78
  • darrentaylor78's Avatar
  • Offline
Both the new and old PCs are running the SQL Native Client 10.0. ODBC DB connections are setup with the same settings as well. We've tried anything and everything we can think of as it relates to the DB connection. There are other CR reports that use the same ODBC connection that do not have any issues running searches/queries. I may not have noted this originally but the report itself opens fine, it's when we go to run a search/query that we get the error message.
The administrator has disabled public write access.

Failed to open the connection. <report name>.rpt 01 Jul 2019 14:28 #5669

  • KCrane
  • KCrane's Avatar
  • Offline
It may help to install Crystal Reports on one of the newer PCs and run the problematic reports to possibly offer a more verbose error message.
The administrator has disabled public write access.