Please try to make your issue as clear as possible. Consider the fact that on the other side, there is a person that, at least in the beginning, knows nothing about what your goal is, what have you done or achieved so far, what has happened and how it differed from your expectations.
A good problem report should have these parts:
1.
Steps taken: What you have done, in detail.
2.
Expected result: What you think should have happened.
3.
Observed result: What has happened in reality.
We also recommend that you follow the practices used on the Stack Overflow site:
How to create a Minimal, Complete, and Verifiable example
.
If you have received an error or exception, please copy its error message (and number, if given)
precisely into the problem report (or a picture of it). We have taken great care to provide error messages that allow to diagnose the problem causes easier. It is a bit offensive if your post says only something like "I tried to connect and it gives me an error", because all that effort that has gone into error reporting in the product is nullified by a sloppy problem report that does not bother to say what the error message was. There are literally tens of thousands possible errors - how can we know which one you got?
If this is a .NET exception, please give us contents of its Source property, and, have a look at its InnerException property, too. If the InnerException is not null, we need details about that exception as well, and so forth.
The bottom line is that making good problem report helps solving the problem faster...
