Re: SqlConnection.Open() Which ErrorCodes

Hello Henrik,
Thanks for your reply.

In my opinion, I'd like to provide end users a detailed guide to avoid
possible connect error, rather than teach them how to trouble shoot connect
issue.

You can write some documents (Something looks like Readme or KB) told end
user how to deploy application step by step. If they could follow the
steps, in general, they could avoid all issues.
The document may also involve System Requirements, known issues and FAQ.

On the other side, I don't think the error message from ADO.net or SQL
server is always exact. Sometime, the error thrown by ADO.net is different
from the actual issue. For example: if there is something error with
network or SQL Server doesn't allow remote connection, ADO.net will tell
you it cannot found the remote server. It is really difficult to image all
the possible reason for each error. If they face some special issue, then
let him tell you. After you resolved it, you can add the case into the
document. I think this is a good way to achieve.

Hope this helps
Sincerely,
Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages
Loading