TOPIC: Failed to Open the Connection!

Failed to Open the Connection! 11 Nov 2014 19:39 #1710

  • CLAITE
  • CLAITE's Avatar
  • Offline
Receiving the following error during execution.

"FAILED TO OPEN THE CONNECTION. FAILED TO OPEN THE CONNECTION. XXXX INPUT{REPORT NAME}.RPT. "

Is there anyway to find out what the problem is? Have tested ODBC connections and returned successful. These reports were executing (saving/emailing/printing) up until recently.
The administrator has disabled public write access.

Failed to Open the Connection! 11 Nov 2014 19:41 #1711

  • bellis
  • bellis's Avatar
  • Offline
Are you passing authentication to the report?

Thanks!
Brian
The administrator has disabled public write access.

Failed to Open the Connection! 11 Nov 2014 19:42 #1712

  • CLAITE
  • CLAITE's Avatar
  • Offline
Yes, credentials are listed in each Action.
The administrator has disabled public write access.

Failed to Open the Connection! 11 Nov 2014 19:43 #1713

  • bellis
  • bellis's Avatar
  • Offline
Do you have multiple datasources on the report?
The administrator has disabled public write access.

Failed to Open the Connection! 11 Nov 2014 19:46 #1714

  • CLAITE
  • CLAITE's Avatar
  • Offline
No, just the one.
The administrator has disabled public write access.

Failed to Open the Connection! 11 Nov 2014 19:48 #1715

  • bellis
  • bellis's Avatar
  • Offline
Are your odbc connections configured for 32-bit ODBC or 64-bit ODBC?

Thanks!
Brian
The administrator has disabled public write access.

Failed to Open the Connection! 11 Nov 2014 19:50 #1716

  • CLAITE
  • CLAITE's Avatar
  • Offline
32-bit
The administrator has disabled public write access.

Failed to Open the Connection! 11 Nov 2014 19:55 #1717

  • bellis
  • bellis's Avatar
  • Offline
My email is bellis @ saberlogic.com

Can you email me your RRD file?

Thanks!
Brian
The administrator has disabled public write access.

Failed to Open the Connection! 10 Dec 2014 21:40 #1753

  • Steve_SIH
  • Steve_SIH's Avatar
  • Offline
I was having the same problem. In the dialog box for the database info I entered the datasource name as it was defined in my report and that fixed the problem. Originally I had entered the actual server name.
The administrator has disabled public write access.