When users get this message the first thing they need is to understand why it is giving this error. I can show up for a variety of reasons from within windows, and seems to be a very popular error.
Although the error "logon failed" is a very common error, it is also somewhat generic in its meaning and can be caused from a variety of reasons. I will discuss some of the more common reasons, but this should be used as more of a starting point than a definite solution to the problem.
When considering the possible reasons for this error, one should not over look the obvious. If the application can not verify the users credentials (user name, pass word, etc.) then the reason for the error would be quite obvious.
There are a few different ways in which the login occurs. Your options are Integrated Security, or by entering a unique User name and password. If the user chooses Integrated Security, the program will use the users specific credentials for the login. If User name and password is used, it will connect using SQL server authentication. The file does not store the password for security reasons, and must be re-entered for each file.
Another possible source of the failure is because of the fact the the viewer does not save the login information (again, for security reasons) from report to report, the password information is often missing. This is actually a logical reason, because of the fact that no one would want passwords to be stored, or saved from inside the reports.
In summary, the Crystal Reports viewer is clearly an extremely powerful tool, which when used properly, will allow the user to create professional, in depth reports which can be used in a variety of ways, including online, offline, and can be exported in nearly any format, including as a web service.
When accessing the service, the first thing the user must be sure of is how they want to login, and to be sure that they have proper authentication for the file.
