Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SSRS 2012 with MS Excel ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found an

Status
Not open for further replies.

nelsonsk2

Technical User
Oct 17, 2005
34
US
I'm hoping someone here can help me sort this out. I've got an Excel spread sheet that I built a report in using VS2010. The shared datasource is set up as an 32-bit ODBC DSN. It runs fine on my development machine (win 7 Pro 64-bit). I deploy the report to my SSRS 2012 report server and everything is there, Datasource, dataset, report. I'm getting an error when I run it and when I test the datasource within SSRS. The error is "ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified".

The server is Windows Server 2008 64-bit, has MS Office 2007 installed and the MS Office Access database engine 2010. I have triple checked that the ODBC DSN precisely matches the one on my Development machine, both created from C:\Windows\SysWOW64\odbcad32.exe. The authentication for the odbc dsn and datasource are configured to use Windows Authentication, so I could understand an error for some users who tried to run it but in all tests I'm using a domain admin account which has full permissions on the network folder where the Excel spread sheet is stored. All other reports on the report server are running perfectly, but are all using SQL db datasources. This is my first attempt at deploying a report with an Excel DS.

I've been through a number of posts on Technet, SQLServerCentral, and others but can't seem to find a solution that works for my case. The only difference I'm seeing between the two environments is that on my dev machine SSDT is installed and for some reason it wasn't on the SQL Server. Could that be the problem, considering the datasource is actually an excel spreadsheet and not a SQL DB?

Thank you, in advance, for any insight you can offer.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top