cancel
Showing results for 
Search instead for 
Did you mean: 

Looping login screen in Crystal Reports for Visual Studio 2008

Former Member
0 Kudos

Hello,

I am using Visual Studio 2008 with the Crystal Reports Basic for Visual Studio 2008. Visual Studio and the Crystal Reports Basic Runtime for Visual Studio 2008 (x64) are installed on both the development and production boxes. I am using Crystal Reports via Visual Studio and do not have the full blown version of Crystal Reports installed on my machine.

We have used Visual Studio to create an aspx webpage and would like to use Crystal Reports to display a graph. The report displays fine in debug mode, but displays a looping login screen when moved into production on the web server. The web server is using Windows Server 2008 (x64) with IIS 7. We have tried passing the logon parameters to the crystal report during the page init event with the auto-bind feature enabled on the crystal report viewer. A MySQL database provides the data for the report. All ODBC data sources have been configured the same on both machines.

Any help would be greatly appreciated! Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

Also, see [this|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10d5fa88-2013-2c10-c9a5-f11963607d4e] article.

- Ludek

Former Member
0 Kudos

Hi Ludek,

There were a couple different issues going on. The first was a typo on one of the connection names in the system DSN. This was found by using the process monitor Don suggested. The second, was the web application had to run in a classic pipeline mode in order for Crystal Reports to identify some of the DLL's - the solution was found in the article you had provided. Thanks again!!!!!

former_member183750
Active Contributor
0 Kudos

Notin like team work

Happy new year

- Ludek

Answers (1)

Answers (1)

0 Kudos

Hello,

Use a tool called ProcessMonitor from Microsoft and watch what happens when you try to log on.

Also can you verify you created your DSN using the 64 bit ODBC Admin and that you are using a System DSN so IIS can find it.

And that the MySQL ODBC drive is also 64 bit?

If you can read ODBC trace logs you could enable it also and see what error you are getting.

Thank you

Don

Former Member
0 Kudos

Hi Don,

Thanks for the info on the process monitor - that helped identifying part of the issue (typo on one of the connection names in the system DSN. I appreciate it!