Failed to connect error on some reports under terminal services

[Former Member]

Post Author: spookc4

CA Forum: Data Connectivity and SQL

Crystal XI, using Print Engine, running under Terminal Services on Windows Server 2003:

I'm getting a 'Failed to connect' error on some reports with sub-reports, but not all. I am issuing a PESetNthTableLogOnInfo to all the sub-reports but some reports still fail while others work. No problems when not running under terminal services.

Any assistance would be greatly appreciated.

Ron

[Former Member]

Post Author: spookc4

CA Forum: Data Connectivity and SQL

Brian,

Connecting to MS SQL 2005, using SQLOLEDB.

Yeah, you're right; changing to RDC from the deprecated PE (grumble, grumble) would be a big deal.

I'll give the PELogonServer a try (I think I tried this one once before and had problems with the subreports prompting for db connection info, but will try again) and if that doesn't work, I'll try the PELogonSQLServerWithPrivateInfo.

Thanks for the suggestions!

[Former Member]

Post Author: The Donger

CA Forum: Data Connectivity and SQL

Hi Ron,

What database are you connecting to and what method are you using; ODBC, direct access, etc.?

Seeing as all the reports work on a local machine, how many connections will the problem reports be creating. Understand that PESetNthTableLogonInfo will create a new database connection for the main and each subreport. I would recommend you use either PELogonServer or PELogonSQLServerWithPrivateInfo. These two calls will make 1 logon connection for your reports to share.

Call PEVerifyDatabase and see if there is a problem that comes up.

I do recommend if possible to move away from using the PE calls. The PE calls are not really supported any longer and I don't think there are too many people still using them. The RDC would be a better choice but I'm guessing it would be a huge deal to change.

Hope this help,

Brian