I am trying to connect to SharePoint hosted on the Microsoft cloud using the OData source. I am trying to pull the Project related data into the sql table from the SharePoint list and process it into the data warehouse.
When I manually login into the SharePoint ,it has got the necessary permissions to read the data and export into excel. But when I connect through the Odata Source in 2012, I encounter the below error. I am using the visual studio Professional 2015 for the SSIS development.
Identity Client Runtime Library (IDCRL) could not look up the realm information for a federated sign-in.
(Microsoft.SqlServer.IntegrationServices.ODataConnectionManager)
Has any one of you encountered this issue any time?
I was able to download the list data from sharepoint to SQL using the 32 bit OData source component.The trick is to use the suffix "/_vti_bin/listdata.svc".
For Ex: If your URL for the List data is :https://sharepoint.com/sales the service document location URL should look like
https://sharepoint.com/Sales/_vti_bin/listdata.svc. Also Enable the Microsoft Online Services Authentication=True in the Connection manager settings.
Thank you
Sharath
Related
I am installing Srs Data Connector for MS Dynamics CRM, but on the systems checking were encountering an error "There is no such object on the server". I've tried googling it but to no avail.
UPDATE: Added some details
I'm running on 2 VM one for CRM app and the other for MSSQL
I'm installing the srs data connector to the MSSQL Server
Both Server is running on Windows 2008 r2
SQL Server is MSSQL 2008
Could be the permissions issue. Make sure NTAUTORITY\NETWORK SERVICE have permissions to access MSCRM_CONFIG. You might also need to reset IIS on CRM Machine after sorting out the access issue.
Is this on-prem?
If that's the case you may want to program in SQL as opposed to fetchxml - It's a lot more flexable.
That being said, if you want to continue to use fetchxml - make sure to point the ssrs data connector to your crm server and not the database server.
Just want to share the resolution and the cause of the problem (Well not the detailed cause).
The problem was caused by an issue on the AD configuration and the installation of the CRM and MSSQL.
After 2 weeks of trying to resolve various errors on the CRM installation including the above post the problem seems to be with the AD config.
We have many Domain controllers and changes on each DC were scheduled to be copied on the other controllers each afternoon. That's why some setup done by the CRM were not copied immediately.
We have tried re-installing the CRM and MSSQL but it also failed. The trick is to set up the CRM and MSSQL in the same DC then disable the CRM and MSSQL servers to connect to the other domain controller OR to replicate the configurations in the DC in real time.
After that all errors and warnings will be gone...
Thanks,
In my project I need to publish an Access database into Sharepoint. I need to add a web form into it. Is it possible to add a WebForm that can be shown in the Sharepoint site, using ODBC(Database from SQL server on local machine)?
I can connect to that database and edit records in it. But I can't make a form with that web icon on it. Is that even possible to publish something from Access to Sharepoint using local SQL server and make a form to show data from it?
I found something like that:
I totally missed the fact that this was a web app. Access web apps
work with SharePoint, no other data source. That's true for Access
2010. But in Access 2013, there is a hybrid solution possible: Access Client + Access Web + SQL Server. It's still very new and not
common yet, and unfortunately there isn't a migration path from Access
2010 web forms to Access 2013 web forms. You have to build the web app
from scratch. But it's a better platform than Access 2010 offered.
that means i should use access 2013 ?
I am no expert and can't test my ideas, but I read that if you publish an Access db with Access tables to SP, Access tables will be converted to a SQL Server table by SP. Perhaps you could then delete or rename the SP created table on SP's SQL Server and create a view with the same name which points to you table on the other server ?
Have a look at the SP site: https://sharepoint.stackexchange.com/q/104005
Here's the scenario:
MVC web project
Three MS SQL Server database projects
One of the databases must be populated with lookup tables
Other tables are user data and don't need data uploading
GoDaddy hosting
Visual Studio 2013
I'd like to deploy everything (web project, sql schemas, reference data) to GoDaddy in one fell swoop, but they appear to only offer FTP uploading. When using FTP in the Web Publishing Wizard, it says "Database preview not supported for this method" which I'm taking "method" to mean FTP. I can publish the web project fine in FTP, but of course without the databases the web application generates errors.
So here are my questions
There is a "Web Deploy" publish method listed in the wizard, but GoDaddy has no information on how to set this up. Can this be used with GoDaddy and will it publish DBs also?
How does one configure the project to use the local SQL Server when running on localhost, but when deployed it uses the GoDaddy SQL Servers?
Can the data in the local DB be uploaded as part of the publishing wizard process, or is SQL Server Management Studio the tool of choice?
Thanks!
I don't believe GoDaddy supports WebDeploy. They didn't when I left their service a few years ago. You can talk to them to confirm whether this has changed.
This is the role of Web.Config Transforms. For an intro to the topic, see here; the article is a little out of date and doesn't mention one of the most useful points - you can add transforms for each publish profile, so they're applied according to your publish settings.
You probably can't upload the local DB file. In almost every hosting situation, the SQL server and the web server are two separate machines, and don't share any files (corollary: the web server doesn't have the SQL service installed). One workaround you can try is to publish the DB directly from your own machine. That is, if you can connect to the DB from your machine, you can do a Web Deploy publish to your own machine but it will send the SQL changes to your GoDaddy DB server.
A more advanced workaround for #3:
Set up your FTP publishing settings for your files
Figure out how to publish your DB through WebDeploy only/from the command line (you can refer to here for a sample using WebDeploy from the command line; note this is going from GoDaddy -> Local, but it's trivial to turn it around)
Customize the web publish pipeline to insert an MSBuild target to execute your WebDeploy command line (see here for an example of modifying the pipeline; you can add the target directly in your .pubxml file if you're not intending to use it for multiple projects).
This will give you a single publish profile which will separately publish your files (via FTP) and your DB (via WebDeploy).
Hi I have installed a Team Foundation Server 2010, and it works perfectly over my Lan, but I need it to work over the internet too.
My problem is that when Im connected to my team server over the internet, I get the following error, when I try to create a new Team project.
TF218027: The following reporting folder could not be created on the server that is running SQL Server Reporting Service:
//TfsReports/myTeam. The report server is located at:
http://my-server/reports. The error is: The remote name could not be resolved: 'my-server'
From the looks of it, its trying to resolve my lan name.
I have already made sure, that its possible to access the Sql server Reporting, from the internet, with this url. team.mywebsite.com/Reports and team.mywebsite.com/reportserver
What do I need to change, for it to use team.mywebsite.com instead of my-server
And just for the record, team foundation server 2010, Sql Server 2008 R2 and Sharepoint 2010 is all installed on the same server.
You can change the url's where tfs is published in the TFS Server Administration Console.
There is several url's that you need to change, so that you can access all the parts of the tfs server from the outside using team.mywebsite.com and the project creation to be successful:
The tfs notification url. (Changed under the Application Tier node)
Sharepoint url (Changed under the SharePoint Web Applications node)
Reporting services ReportManager and webservice (Changed under the Reporting node)
I have a cube developed using SQL Server Analysis Services (2005). Its hooked up to an excel front end.
At the moment users have their own logon to the reporting server and access the reports that way. However, it would be nice of they could access the reports over the web.
Are there options for this? I could upgrade to 2008 if there was a compelling case.
The reporting server runs on IIS, so you'd need to treat this as any other IIS server. Common practice is to not expose a database server directly to the internet, so you would want to have a separate server hosting reporting services, which needs another SQL license - if you are not already configured that way.
I'm not sure if you're asking for a way to connect a local excel to the cube, or if you're just wanting to get into the reports interface.
I highly recommend using the aspxpivotgrid to expose your cube data within a web app. http://www.devexpress.com/Products/NET/Controls/ASP/Pivot_Grid/
note: not an employee of developerexpress
CellSetGrid is an Open Source ASP .Net (c#) control, which offers pivot table like functionality.
[This used to be available for download in this site:
www.SQLServerAnalysisServices.com
Now the site does not host this control anymore. So I have uploaded the source of the control - CellSetGrid here.
http://www.box.net/shared/6gi0n79q6t
1) You can build the source
2) Add this as a Control in Visual Studio toolbox.
3) Drag and Drop control to a web form
4) Set the connection string to the cube
5) This will show all the dimensions and measure groups so you can drag n drop what you want to get a pivot table like functionality
SSRS is running on IIS, meaning user can access the reports over web with proper access permission.
Also you can build a custom ASP.NET application with ReportViewer control which is using almost the same report file used in report server.