I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2(64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with : Data source name not found and no default driver specified The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here. Thanks

Has anyone got any ideas on this ?

Did you find a resolution? I have the same problem.

I am waiting for a company called Openlink to get back to me they are currently developing some drivers

Thanks. My client isswitching to 32-bit software to resolve this. Good luck.

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS. Any advice or suggestion are welcomed. Thanks, Andy

I'm attempting to answer this since its a top link on search engines when I search for 64-bit Reporting Services... hoping this helps someone else. BIDS (where reports are designed) is always 32-bit, so it can only talk to 32-bit drivers and providers. In SQL 2008, on the server side (where reports are hosted) a 64-bit SQL Reporting Services server, you can only connect to 64-bit providers and drivers to pull in data. As a workaround, some people install SQL Reporting Services 32-bit on a 64-bit box if you have a driver which is only available in 32-bit (x86) flavors. When you run SQL Server 2008 Setup, on the landing page, there is an option to pick 32-bit SQL even when on a 64-bit machine. { Page title: SQL Server Installation Center Last link is the "Options" tab Specify the architecture of the SQL Server to be installed... Processor Type x86 <<--- choose this to install a 32-bit instance on a 64-bit OS x64 ia64 } SQL 2005 RS had dependency on IIS and ASP.Net, which further explained in the second Readme excerpt below: ============== http://msdn.microsoft.com/en-us/library/ms159219.aspx On the report authoring client SQL Server Business Intelligence Development Studio is a 32-bit application. Business Intelligence Development Studio is not supported on an Itanium-based platform. On an x64 platform, to edit and preview reports in Report Designer, you must have 32-bit data providers installed in the (x86) platform directory. On the report server When you deploy a report to a 64-bit report server (either x86 or Itanium), the report server must have natively compiled 64-bit data providers installed. Wrapping a 32-bit data provider in 64-bit interfaces is not supported. For more information, check the documentation for the data provider. ========= From the 2005 Requirements http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/RequirementsSQL2005.htm ²For Reporting Services (64-bit) installations on 64-bit servers, the 64-bit version of ASP.NET must be installed. For Reporting Services (32-bit) installations on the 32-bit subsystem (WOW64) of a 64-bit server, the 32-bit version of ASP.NET must be installed. Reporting Services is not supported in side-by-side configurations on the 64-bit platform and on the 32-bit subsystem (WOW64) of a 64-bit server at the same time. For more information, see the topic for "How to: Configure IIS to Run 32-bit Reporting Services in WOW64 Mode" in SQL Server 2005 Books Online. ========= Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance