July 24, 2017 at 7:12 am
Hi,
I've created a dataset (using an excel data source)
the query that drives the dataset is:
SELECT * FROM [2017 New & Lapsed$]
it works correctly in VS 2012 and provides me with the data needed.
However when I deploy the report
when I open the report using Report Builder 3.0 and try to run it - I get an error message
An error occurred while executing the query.
Invalid object name '2017 New & Lapsed$'. (Microsoft SQL Server Report Builder)
However when I run it via VS 2012 it works correctly (where it was deployed from)!
Any idea of how to resolve this?
Thank you for your time
Andy
July 25, 2017 at 6:53 am
Hey guys, I am really stuck 🙁 any ideas?
July 25, 2017 at 8:47 am
andyc76 - Tuesday, July 25, 2017 6:53 AMHey guys, I am really stuck 🙁 any ideas?
Not sure how you are creating or managing the data source in SSRS but it looks like your VS 2012 is not the same as the report server. You need to have the same drivers, configurations, etc for it setup on the SSRS server.
Try just setting up and testing a data source to the Excel file from SSRS. You don't need to keep it but try testing the data source that way.
Sue
July 25, 2017 at 9:06 am
Another thought - does your SSRS server have access to the Excel file? If it is on a network share, are you using the full UNC filename or the drive letter? You will likely need to use the UNC filename.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
July 25, 2017 at 10:46 am
bmg002 - Tuesday, July 25, 2017 9:06 AMAnother thought - does your SSRS server have access to the Excel file? If it is on a network share, are you using the full UNC filename or the drive letter? You will likely need to use the UNC filename.
Sorry that's what I meant by configuration - should have been more explicit and added more details.
Did you look at the Data Source in Report Manager to see if it's correct? What you use in Visual Studio may not be the same as what is used by SSRS
Since you could likely be using a DSN, you need to set up the DSN on the SSRS server as well which should be a system/machine DSN.
You should be using the same provider on the SSRS server as you are using on the computer with VS 2012 since there are differences with the different versions.
This would be the server where the report services is installed if you have the databases separated out from the services.
If you have a scale out configuration, you need to do the same on each server where you have installed the services.
Sue
July 27, 2017 at 6:27 am
Hi,
The development "VS2012" and deployment environment "Report Server" are both on the same machine.
I've setup ODBC Excel DSN drivers using both 32bit and 64bit versions
In VS 2012 I can only see the x32 driver
In Report Server I can only see the x64 driver
after LOTS of checking, researching and trial and error!
ive reverted to using OLE DB (instead of ODBC)
i had to install both the 32bit and 64bit version by extracting the package "aceredist.msi" and running it in /passive mode
Thank you so very much bmg002 and Sue_H for your time!
https://social.msdn.microsoft.com/Forums/en-US/37643580-bf1f-4a3a-b63b-7d5aba2a940d/the-providermicrosoftaceoledb120-provider-is-not-registered-on-the-local-machine?forum=adodotnetdataproviders
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply