Depending on the problem, whether it is with your application, your server, or your tools, you might receive a message that indicates that something is wrong. Always record the error message that you see. As simple as this advice sounds, error messages often contain codes that make more sense as you investigate your problem further. You might also receive multiple error messages that look similar, but have subtle differences. By recording the details of each message, you can learn more about the problem.
Think back to what steps led you to this problem. Try those steps again to see whether you can easily re-create this problem. If you have a consistently repeatable test case, you can more quickly determine what solutions are necessary.
Consider the following questions:
Narrow the scope of your problem by eliminating components that are not causing the problem. By using a process of elimination, you can simplify your problem and avoid wasting time in other areas. Consult the release information that comes with the product and other available resources to help you with your elimination process.
Start with these questions:
For information about other support resources and tools, see More support resources.
Jazz.net channel User Education channel |
Agile learning circle Learning circles |
developerWorks forums |
Deployment wiki Support blog |