CR for VS2010: Failed to Open Connection [Database Vendor Code: 17 ]

[Former Member]

About once a week for the past 3 weeks, we are getting the following error. Now, this week, it is happening about once a day. Our architecture is we have a Winform client that is hitting a remoting server that is located on our database server. The remoting server uses Crystal Reports to export items to PDF and either store them or return the byte[] to the client. We have received this error twice now in the last 3 weeks and now about 3 times this week.

1. First time we tried just to restart our remoting service, did not fix it. We rebooted and it started working again.

2. Second time we uninstalled Crystal Reports for VS 2010 and installed the Service Pack 1 update. Again we rebooted and it started working.

3. The last few times a reboot worked.

This solution has been in place for months but we have recently added a couple new reports. But once this error starts, it will not go away and no crystal report will work. We dispose of all crystal objects on each call. My problem is why a reboot fixes this? Are we hitting some limit in the free version? Max concurrent threads? I read in one of your documents that only 3 reports run at any given time and then the others are queued. If this is the problem, what is the solution??

Message: Message: Failed to open the connection.

Details: [Database Vendor Code: 17 ]

Failed to open the connection.

SeveranceTaxOklahomaBmp {88F3FD7F-02DC-4958-83F3-A120907104DA}.rpt

Details: [Database Vendor Code: 17 ]

Stack Trace: at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)

at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportOptions options)

at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportFormatType formatType)

at Seminole.Gem.Reporting.CrystalReports.BaseReport.RunPdfReport() in d:\GemAdmin\SeminoleScrum2010\Production\GEM\Source\Seminole.Gem\Seminole.Gem.Reporting\Seminole.Gem.Reporting\CrystalReports\BaseReport.cs:line 131

Inner Exception: Message: Failed to open the connection.

Details: [Database Vendor Code: 17 ]

Failed to open the connection.

SeveranceTaxOklahomaBmp {88F3FD7F-02DC-4958-83F3-A120907104DA}.rpt

Details: [Database Vendor Code: 17 ]

Stack Trace: at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext)

at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

[former_member183750 · Accepted solution]

Look up Database Vendor Code 17 for your database. The error is being generated by the database client and is being passed unaltered through the report engine.

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

[Former Member · Accepted solution]

Error 17 in SQL Server is:

"Error: SQL Server does not exist or access denied. (Error code 17)."

The problem here is the database is working fine, all other remoting calls are working under the same user account. It's just Crystal that can't connect to the database.

So you are thinking this isn't a "load" issue?

[former_member183750 · Accepted solution]

So you are thinking this isn't a "load" issue?

- Does not sound like it to me. It may be that the SQL server is running out of licenses(?), so you may want to monitor that..

Make sure you are using .Close and .Dispose on the report objects as you get done with them.

If you want to explore the load possibilities a bit more, see the article [Crystal Reports Maximum Report Processing Jobs Limit|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/f053713e-3e3d-2c10-2a81-f79259e54023].

Also, make sure you have the latest updates for the SQL server.

- Ludek

[disaia · Accepted solution]

I was opening the same connection to the database twice. Once I removed this, all worked out well. Thank you!!