Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 525
  • Last Modified:

SQL Reporting Services Error - Ad Hoc Query Error

Hello Experts,
I'm changing up a recent question a little bit to see if I can make any headway on this issue.

I'm getting an SQL reporting error:

An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set 'GoldMine'. (rsErrorExecutingCommand)
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. The provider did not give any information about the error. Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

My SQL Reporting Services Server is remotely connecting to my SQL 2005 Server. Is there any error log which could give me a little more information on the real failure???
3 Solutions
Seems like your datasource is not working..

Why are you using "OLE DB provider "Microsoft.Jet.OLEDB.4.0" as datasource??

Have you tried "Microsoft SQL Server (SqlClient)"??

I second srm74 idea. Just check whether your report can connect to the server and fetch the data. I perfer doing if form BIDS.
ottobockAuthor Commented:
Thanks for the ideas. The datasource is a simple XLS spreadsheet. What I now believe is the connection string (that I cannot find!) is looking for a drive rather than a share. (\\server\e$\share\xls instead of \\server\share\xls). I've gone back to the developer of this process to investigate further, as I've spent a ton of time trying to find where this connection is defined.

Side note: I can run this query successfully, and return the spreadsheet contents:
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=\\server\share\file.xls', 'SELECT * FROM [Sheet1$]')

This is why I was hoping there could be some log file I missed that may help me out. I'm a few hairs less after getting this problem. :-)
ottobockAuthor Commented:
Issue found.

Nearly the same query as above was embedded into the reports themselves. Problem was that the query was looking for the XLS using a UNC with was no longer valid...

So the creator of the reports had to drudge through each individula report and fix the query.

Thanks everyone!

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now