Failed to open connection (C#, Sql Server, Crystal Reports)

Question

0.00/5 (No votes)

See more:

, +

Failed to open the connection.
Details: [Database Vendor Code:17]
Failed to Open Connection.
payments11 {D29B3531-EF7D-426E-B1DB-05CD2A63FA5F}.rpt
Details : [Database Vendor Code:17]

My c# application works fine in my machine. When i am trying to run my application on users or target machine while click on report preview button it shows a report. If I refresh crystal report it show the above error. How to solve this error

Posted 28-Oct-14 21:30pm

Mohamed Shakir

Add a Solution

Comments

ashok rathod 29-Oct-14 3:44am

Please Check that your Previous Connection is closed Successfully, have you written any code after operation.Please check Inner Exception as well

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2014-10-28T22:00:00

The chances are that the live machine can't see the database that the connection string you provided refers to: check that you changed the connection string (it should be in a config file, not hard coded) to match the local user network, and check that the authorization details it provides are correct - username, password, that kind of stuf: almost no "live" db systems use windows authentication for security and tracability reasons.