Skip to Content
avatar image
Former Member

Crystal reports for VS 2010 connection failure

I am using Crystal reports for .Net and Visual Studio 2010. The application was running absolutely fine on Windows server 2008. Last month we migrated to Windows server 2012. Crystal Reports connection has been failing since then. Any help in this regards wil be appreciated.

Thanks,

Manju

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jul 06, 2015 at 05:35 PM

    Hi Manju,

    What database and version are you using and how are you connecting to it? 

    What errors are you getting? 

    Is your development machine Windows 2012 or did you just reinstall your application on Windows 2012? 

    If the reports are using ODBC, make sure you have the 32 bit ODBC installed and working if your application is compiled as 32 bit.  This is a common problem because trying to determine whether the datasource is 32 or 64 bit can be difficult. 

    Thanks,

    Brian

    Add comment
    10|10000 characters needed characters exceeded

    • As Ludek mentioned, get the latest runtime and try with that. 

      Can you verify if the application is running in 32 or 64 bit mode? 

      From your application server, can you connect to SQL Server using SSMS or something else? 

      If your application is running in 32 bit mode, can your OLEDB driver connect in 32 bit mode on the 2012 server? 

      If the error is happening when the report is connecting, I'm leaning towards the 32 bit application not finding a valid 32 bit database connection. 

      If you can track down exactly when it errors out that would help.  More information is better for this.  It may be possible something else is causing the error and not the connection itself. 

      A couple of things to look at: what version of .NET Framework do you have installed on your 2012 server?  What version of .NET Framework is your application compiled with?  This has caused me issues in the past. 

      Good luck,

      Brian