SQL Sharepoint Integration using oData connector with SSIS - sharepoint

SSIS Sharepoint Connection using OData connector. I was able to connect to Sharepoint site fine and was able to see the data thru preview and all.. but when i execute the task i get below error.
[OData Source [2]] Error: The OData Source was unable to process the data. Object reference not set to an instance of an object.
Task: OData as Source(with SP connection information) and OLE DB Destination.

I worked with this SharePoint connector a couple of years ago and recall it being somewhat tricky to set up. Check the following link to see if you may have left out any steps.
http://dataqueen.unlimitedviz.com/2011/06/how-to-use-a-sharepoint-list-as-a-data-source-in-your-ssis-package/
Also, I remember that by default the SharePoint connector mapped every column, most of which were not needed. This resulted in a memory limitation and was resolved by removing the mappings not needed.

Related

Why can't I see tables in SSMS

I recently created a Microsoft Azure SQL Data Warehouse and used the AdventureWorks sample database. When try to access the database in SSMS, I can not see any of the database Tables, yet I am able to query them.
Researching on the internet, led me to believe this might be a permission issue, so I right clicked the database, selected Properties | Permission to review the View permission. However, when I this, I get the following error message:
I've also upgraded to the latest edition of SSMS, I also dropped and reloaded all the tables making sure I used dbo as the Schema.
As anyone come across this problem and do you have a workaround or fix.
In scripting options, make sure that the engine edition is set as “Microsoft Azure SQL Data Warehouse Edition” and engine type is “Microsoft Azure SQL Database”.
Tools -> Options -> SQL Server OE -> Under General scripting options
Please let us know if this issue persists. We have a fix in the upcoming release for SSMS which will automatically detect the database source to populate these settings.
Thanks!

Alternatives to pulling data from ATOM Data Feed

I did some extensive searching and was unable to find the answer to my question:
Are there alternatives to pulling data using ATOM Data Feeds other than Microsoft Powerpivot? I am trying to set up a connection to MS Access so I can populate some tables using data that currently has to be accessed through an SSRS embedded on a Sharepoint dashboard. I do not have access to the server, so I can't create my own connection at this time. Powerpivot has been the only method that returns data outside of manually going to the Sharepoint. I want the data to automatically populate in MS Access 2010.
I would try the Power Query Add-In - it can connect to SharePoint Lists or OData feeds:
SharePoint:
http://office.microsoft.com/en-au/excel-help/connect-to-a-sharepoint-list-HA104019822.aspx
OData:
http://office.microsoft.com/en-au/excel-help/connect-to-an-odata-feed-HA104019824.aspx

We were unable to refresh one or more data connections in this workbook

I use SharePoint 2013 and Excel Services and PoverPivot Services.
I have a Pover Pivot report . When I see this in SharePoint and I want refresh my data from Data menu,
I get this error :
External Data Refresh Failed
An error occurred while working on the Data Model in the workbook. Please try again.
We were unable to refresh one or more data connections in this workbook.
The following connections failed to refresh:
I fond this Link but this not work.
I run into the same issue.
In my case my powerpivot datamodel was pointing among Others also to a second Excel file, stored in a DocumentLibray.
Once you have followed all steps in the article below:
http://technet.microsoft.com/en-us/library/jj879294.aspx
You should enable VERBOSE log for "PowerPivot Service" category.
Trigger a manual refresh in order to produce the log output.
I you find this error in the log:
The provider 'Microsoft.ACE.OLEDB.12.0' is not registered.
This is related to missing x64 OLEDB driver.
In my case I had Office 2013 x32 installed in the SharePoint server, and that's the point.
SharePoint is x64, so it could not load the proper OleDB driver (x64) which I downloaded and installed from:
http://www.microsoft.com/en-us/download/details.aspx?id=13255
(it is the same driver for Office 2010 and 2013 actually).

Data connectivity issue when publishing PowerPivot Excel file to SharePoint, and how to work around it?

One of my customers is very impressed with the capabilities of PowerPivot, particularly the analysis capabilities but even more the publishing capabilities. With that I mean the ability to publish a dashboard to a SharePoint site, after which it can be experienced directly in the browser, including filtering and slicing for end-users.
As we publish our PowerPivot results to a SharePoint site, we get the following error for any action that triggers the data connection to refresh:
The data connection uses Windows Authentication and user credentials
could not be delegated
I've done a lot of research on this one and it seems it is a configuration issue on the SharePoint side. Note though that we are using a cloud hosted SharePoint thus the environment is not under our control. In addition, even our own team mentions this to be a security restriction that will not be lifted.
Therefore, I'm not working on solving the above problem, rather on avoiding it alltogether:
My first experiment was to build a "normal" Excel file without PowerPivot. Same data and I managed to build the same pivots. Both the data and the pivots are in the same file, without a data connection. Publishing it works just fine. The error is not experienced this time, and even interacting with the report via slicers works.
As a second experiment, I wanted to follow the same scenario, but this time using PowerPivot. From data in an Excel sheet I created a so-called "linked table" in PowerPivot. Next, I created some pivots that make use of this table. The pivots are in the same Excel file as the original data. When I publish this file to SharePoint, I get the same error mentioned before when doing anything that refreshed the data connection. Even though the data and pivots are in the same file, it still pops up with this security error, which surprises me.
How can I work around this data connection issue when a PowerPivot is published? We'd like to have both the analytical power of PowerPivot as well as having the rich publishing options of Excel, without running into the data connectivity issue. Is it possible to "flatten" a PowerPivot file to "normal" Excel, since experiment #1 shows that this works fine. How can I remove the data connection from PowerPivot and tell it to just use the Excel data in the very same file?
Do you have PowerPivot for Sharepoint installed?
Is it Pivotstream providing the cloud service?

How do I deploy SSRS reports to CRM 2011 Online that contain SQL Server DataSources and T-SQL Queries?

I'm creating custom SSRS reports for a client that uses CRM Online. However, I'm not able to deploy reports that have SQL DataSource connections to them. I get the following error:
"Invalid Data Source. This report type is not supported. Microsoft Dynamics CRM Online supports only reports that use Fetch XML data sources."
However, this error is somewhat untrue. Reason: When I download other custom reports from their CRM, the DataSources are all SQL connection strings with T-SQL queries.
So, there MUST be a way to deploy these reports. From within the client's network perhaps? I've not been able to find any details online thus far. Help?
I'm afraid there is no solution. CRM Online will only allow you to upload fetchXml based reports. There is no workaround (that I have heard of at least).
Are you sure that the other reports you downloaded are definitely custom (CRM allows some system reports to be SQL based) or if custom do they actually work (nevermind how they got there in the first place!).
Yes it's possible with couple of work around.
You need to create your data source for SQL and upload it on your CRM server. Do you have SSRS services running on your CRM server ? if yes then there would be 2 data sources available. One for CRM data source (fetch XML) and another for SQL server.if it's not there you need to create it .
Once you have those data source you are good to get your data in your SSRS report. Make sure your data source name should match with your SSRS report data source. (I have on-promise environment for my CRM 2011)

Resources