I'm trying to extract the data from http://reports.office.com/pbi/v1.0/#tennantID/TenantClientUsage using odata connection in SSIS
I'm able to connect to reports.office.com/pbi/v1.0/#tennantID and put the list of reports into a collection. However, when I select the report I want I get the following error
Unable to cast object of type 'Microsoft.Data.DataFeedClient.DataFeedODataEdmWrapper' to type 'Microsoft.Data.DataFeedClient.DataFeedODataEdmWrapperV3'.
It seems like an authentication issue?
If its not possible to connect to this data using SSIS, what is the best method to pull this data into a SQL server?
Report 1 (Works): I have an SSRS package deployed to Server_A which pulls data in a database also from Server_A. The following URL works so I can download the report. http://Server_A/ReportServer?/SSRS_Package_Name_A/SSRS_RDL_Name_A&rs:Command=Render&rs:Format=EXCEL
Report 2 (Report Viewer Works, Direct URL Doesn't Work): I have a second SSRS package also deployed to Server_A, but it pulls data from a database that's on Server_B. If I use a similar URL, then SSRS displays the following error message in my browser:
Error during processing of ‘Reporting_Period’ report parameter. (rsReportParameterProcessingError)
The Reporting_Period parameter in SSRS references a column within a dataset that runs a query against a view in Server_B that pulls the min and max dates. Adding the Reporting_Year parameter to the URL didn't work, and it seems like I'm getting this error because the SSRS Server_A can't connect to Server_B.
Going to the report viewer in my browser and manually downloading the report works for both reports above. I just can't download the report automatically in the background by going to the URL for the 2nd report (Need to automatically download multiple reports using SSIS automatically).
Report 3 (Report Viewer & Direct URL Do Not Work): I then tested what was happening by first creating a new SSRS package with a simple textbox and deploying it to Server_A. Downloading the report in Report Viewer worked and using the direct URL worked. I then created a data connection to Server_B, and now the following error is displayed when attempting to view the report in Report Viewer:
An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection) For more information about this error navigate to the report server on the local server machine, or enable remote errors
I deleted the data connection and the Report Viewer and direct URL worked again. I'm now even more stumped because "Report 2" can at least download the report manually using Report Viewer.
I have the following problem when I want to display an image in a column of type "Hyperlink or Picture" of Sharepoint List, the image comes from a column in a SQL Server table of data type "Image". To give more context to the problem that I am presenting, I will explain the process in detail.
I have an application developed in PowerApps which is connected to SQL Server, this application stores information in a table and among that information that I save is an image, which is the one I mentioned above and I save in the SQL Server table.
As I mentioned, the image is saved in an "Image" data type with the following information "0xFFD8FFE000104A46494600010101004800480000FFE…" something like that, since the information chain is very long, I do not add it completely.
In the same application I have a display screen of the image which I can see without any problem after saving the record.
In addition to this application, I have a workflow developed with Power Automate which is a scheduled flow that runs at a certain time of the day. What this flow does is get the rows from my table in SQL Server and then create an element in a Sharepoint list, I do this to export the information from SQL Server to a Sharepoint list.
Among that information that I export, the "Image" column does not appear, as I show it in the flow below.
For this reason after the flow ends, I go to the Sharepoint list and the image is not stored.
It is for this reason that I request help to correctly display the image from SQL Server in the Sharepoint list.
Is there something wrong that I'm doing in my workflow in Power
Automate?
Why is the image not displayed in the Sharepoint list?
Any other solution to store the image and then be displayed correctly
in the Sharepoint list?
Or do you think I have to change the data type with which I am
storing the image in the SQL Server table?
Conditions to take into account.
It is not possible to connect the PowerApps application to the Sharepoint list directly, since the SQL Server table will be used by other external applications and that information is required to be in a SQL Server table.
Update 1:
I am currently getting an error when running the flow.
The error is in a particular record and it is in one of the records which has an image in SQL Server, this image must be stored in the Sharepoin list. But the flow throws the following error:
OpenApiOperationParameterTypeConversionFailed. The 'inputs.parameters' of workflow operation 'Create_item' of type 'OpenApiConnection' is not valid. Error details: Input parameter 'item/Image' is required to be of type 'String/uri'.
We are getting below error msg in the pop-up windows, when trying to view the generated XML in SSMS - Sql Server.
Microsoft SQL Server Management Studio
Unable to show XML. The following error happened: Unexpected end of
file while parsing Name has occurred. Line 1, position 2097154.
You will not be able to fix this beyond what SSMS can support when it comes to viewing the XML data in SSMS. I would suggest any of the following resolutions:
Change the parameters of what is pushing that XML data into your server so that the overall size can be limited. For example, if this XML data contains all values for a data point for the past year, perhaps break it up into quarters instead and push them separately into the server.
Export the data instead of trying to view it in SSMS.
Have just deployed my Project on to my reporting Server.
I have multiple datasets which are referencing views which exist on the db on that server.
When I try to go into any report part I am getting this message:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'dataset1'. (rsErrorExecutingCommand)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Can anyone help?
I enabled remote errors to pinpoint the problem.
I identified that a column in a particular dataset (one of my views) was throwing an error.
So using a tool "SQL Delta", I compared the development version of the database with the live version on the reporting server. I noticed that one of the views had an extra column on the development server, that was not on the live version of the db.
SQL Delta generated the script I needed to run to update the view on my live db.
I ran this script, re-ran the report, everything worked.
I encountered a similar error message. I was able to fix it without enabling remote errors.
In Report Builder 3.0, when I used the Run button to run the report, an error alert appeared, saying
An error has occurred during report processing. (rsProcessingAborted)
[OK] [Details...]
Pressing the details button gave me a text box where I saw this text:
For more information about this error navigate to the report server
on the local server machine, or enable remote errors
----------------------------
Query execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand)
I was confused and frustrated, because my report did not have a dataset named 'DataSet1'. I even opened the .rdl file in a text editor to be sure. After a while, I noticed that there was more text in the text box below what I could read. The full error message was:
For more information about this error navigate to the report server
on the local server machine, or enable remote errors
----------------------------
Query execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand)
----------------------------
The execution failed for the shared data set 'CustomerDetailsDataSet'.
(rsDataSetExecutionError)
----------------------------
An error has occurred during report processing. (rsProcessingAborted)
I did have a shared dataset named 'CustomerDetailsDataSet'. I opened the query (which was a full SQL query entered in text mode) in SQL Server Management Studio, and ran it there. I got error messages which clearly pointed to a certain table, where a column I had been using had been renamed and changed.
From that point, it was straightforward to modify my query so that it worked with the new column, then paste that modification into the shared dataset 'CustomerDetailsDataSet', and then nudge the report in Report Builder to recognise the change to the shared dataset.
After this fix, my reports no longer triggered this error.
Like many others here, I had the same error. In my case it was because the execute permission was denied on a stored procedure it used. It was resolved when the user associated with the data source was given that permission.
I experienced the same issue, it was related to security not being granted to part of the tables. review your user has access to the databases/ tables/views/functions etc used by the report.
The solution for me came from GShenanigan:
You'll need to check out your log files on the SSRS server for more detail. They'll be somewhere like: "C:\Program Files (x86)\Microsoft SQL Server\MSRS10_50.DEV\Reporting Services\LogFiles\"
I was able to find a permissions problem on a database table referenced by the view that was not the same one as the where the view was. I had been focused on permissions on the view's database so this helped pinpoint where the error was.
I just dealt with this same issue. Make sure your query lists the full source name, using no shortcuts. Visual Studio can recognize the shortcuts, but your reporting services application may not be able to recognize which tables your data should be coming from. Hope that helps.
I had the similar issue showing the error
For more information about this error navigate to the report server on
the local server machine, or enable remote errors Query execution
failed for dataset 'PrintInvoice'.
Solution:
1) The error may be with the dataset in some cases, you can always check if the dataset is populating the exact data you are expecting by going to the dataset properties and choosing 'Query Designer' and try 'Run', If you can successfully able to pull the fields you are expecting, then you can be sure that there isn't any problem with the dataset, which takes us to next solution.
2) Even though the error message says "Query Failed Execution for the dataset", another probable chances are with the datasource connection, make sure you have connected to the correct datasource that has the tables you need and you have permissions to access that datasource.
In my situation, I created a new SSRS report and new stored procedure for the dataset. I forgot to add the stored procedure to the database role that had permission to execute it. Once I added the permissions to SQL database role with EXECUTE, all was fine!
The error message encountered by the user was "An error occurred during client rendering. An error has occurred during report processing (rsProcessingAborted). Query execution failed for dataset "DataSet1'. (rsErrorExecutingCommand) For more information..."
Very grateful I found this great post. As for my case, the user executing the stored procedure did not have EXECUTE permissions. The solution was to grant EXECUTE permissions for the user within the stored procedure by adding below code to the end of the stored procedure.
GRANT EXECUTE ON dbo.StoredProcNameHere TO UsernameRunningreports
GO
I also had a very similar issue with a very similar error message. My issue was that the database could not be connected to. In our case, we have mirrored databases and the connection string did not specify the Failover Partner. So when the database couldn't connect, it never went to the mirror and was throwing this error. Once I specified the Failover Partner in the connection string for my datasource, it resolved the issue.
BIGHAP: A SIMPLE WORK AROUND FOR THIS ISSUE.
I ran into the same problem when working with SharePoint lists as the DataSource, and read the blogs above which were very helpful. I had made changes in both the DataSource and Data object names and query fields in Visual Studio and the query worked in visual Studio. I was able to deploy the report to SharePoint but when I tried to open it I received the same error.
I guessed that the issue was that I needed to redeploy both the DataSource and the DataSet to SharePoint so that that changes in the rendering tools were all synced.
I redeployed the DataSource, DataSet and the Report to sharePoint and it worked.
As one of the blogs stated, although visual studio allowed the changes I made in the dataset and datasource, if you have not set visual studio to automatically redeploy datasource and dataset when you deploy the report(which can be dangerous, because this can affect other reports which share these objects) this error can occur.
So, of course the fix is that in this case you have to redeploy datasource, dataset and Report to resolve the issue.
I was also facing the same issue - I checked below things to fix this issue,
If you have recently changed pointing database-name in data-source
then first check that all the store procedures for that report exist
on changed database.
If there are multiple sub reports on main report then make sure each
report individually running perfectly.
Also check security panel - user must have access to the databases/
tables/views/functions for that report.
Sometimes, we also need to check dataset1 - store procedure. As if you are trying to show the report with user1 and if this user doesn't have the access(rights) of provided (dataset1 database) database then it will throw the same error as above so must check the user have access of dbreader in SQL Server.
Also, if that store procedure contains some other database (Database2) like
Select * from XYZ inner join Database2..Table1 on ... where...
Then user must have the access of this database too.
Note: you can check log files on this path for more details,
C:\Program Files\Microsoft SQL Server\MSRS11.SQLEXPRESS\Reporting Services
I got same error but this worked and solved my problem
If report is connected to Analysis server then give required permission to the user (who is accessing reporting server to view the the reports) in your model of analysis server.
To do this add user in roles of model or cube and deploy the model to your analysis server.
Using SSRS, Report Builder 3.0, MSSQL 2008 and query to an Oracle 11G database,
I found that the oracle stored procedure ran well, produced consistent results with no errors. When I tried bringing the data into SSRS, I got the error as listed in OP's query. I found that the data loaded and displayed only if I removed the parameters (not a good idea).
On Further examination, I found that under dataset properties>parameters I had set the start date to parameterName P_Start and parameter Value to #P_Start.
Adding the Parameter value as [#P_Start] cleared the problem, and the data loads well, with parameters in place.
This problem was caused by an orphaned SQL Login. I ran my favorite sp_fixusers script and the error was resolved. The suggestion above to look at the logs was a good one...and it led me to my answer.
This might be the permission issue for your view or store procedure
In addition to the above answers, it could be due to a missing SQL stored-procedure or SQL function. For example, this could be due to the function not migrating from a non-prod region to the production (prod) region.
Removing all comments from the Select Query fixed this for me. My dataset was working in the Preview but when I went to Design/Query Designer and and tried the query there I was getting ORA-01006;bind variable does not exist. After removing all comments from the select it worked.