TOPIC: Reports triggering logicity.common error

Reports triggering logicity.common error 24 Jun 2019 23:22 #5647

  • mjones
  • mjones's Avatar
  • Offline
Hi Everyone,
I currently have a issue that half my reports are working fine and scheduling whilst the other half are failing to run via the scheduler.

The following logicity.common error pops up Failed to open the connection.
How do you resolve this error ? is this a logicity or crystal error ?
All Database access is identical across all reports.
Help would be greatly appreciated.
Cheers
Mitch
The administrator has disabled public write access.

Reports triggering logicity.common error 24 Jun 2019 23:37 #5648

  • aellis
  • aellis's Avatar
  • Offline
Hey Mitch,
So this is a Crystal error and diagnosing it can be a pain in the rear sometimes. This isn't ideal, but sometimes the best way to diagnose it is to load up the full copy of Crystal where you are trying to run the report via Logicity and get more verbose steps on what is going on. Knowing how painful that might be, here are a few common problems:

- The ODBC connection for your reports (if you use them) need to be set up under the 32-bit ODBC control panel.
- When you 'Set Location' on a report it stores a bunch of details about the connection at the time the designer wrote it - including the server name, user name the DESIGNER connected as, database name, etc. If any of that doesn't align perfectly with your deployment you can get this error.

Hope some of this helps!
Adam
The administrator has disabled public write access.

Logicity Logo White 300

526 S Main St., Suite 805, Akron, OH 44311 USA
855.758.0100
sales@logicitysuite.com