I've made a simple form in infopath, that looks up information in SQL server.
Using the design tool, I can fill in the form and submit it. All info from SQL server is being retrieved.
The SQL server is used in many different scenario's and accessible through different means. In the first phase I'm using a read/write account to connect to the database.
When I publish it to sharepoint (2010), I get an error the first time the SQL data is being requested.
I get an error that refers to the windows error logs; but I do not have access to the sharepoint environment.
The sharepoint is installed in the same forest, it should be able to get a connection to our sql server.
are the BCS (business connectivity services) necessary for this kind of action?
are there any other reasons why this could fail?
If it's working on your machine in debug mode but not on the server I would check two settings:
Authentication settings as you might be getting a double hop problem.
Security on database, make sure the user has access to the database
Related
I am working on a migration from SharePoint 2010 to SharePoint Online. Where inside the on-premises the customer has a configurable Web Part (Server-side of course), which allow users to do the following:-
Specify a connection string to connect to on-premises SQL server
Specify the Table or Stored Procedure or View to connect with.
optionally to pass a Parameter to the Database.
After that the web part will show the results from the database and allow the users to filter the data which will be shown in a tabular format.
Here is a screenshot of the web part setting:-
Here is a screenshot of a result from one web part instance:-
So can we build similar web part using SPFx? If the answer is Yes, then is there an available 3rd party web part we can benefit from? Finally , i am also open to other approaches to achieve our work other than build/using SPFx web part.
Please note that I am already aware that i can create API for the DB and connect SharePoint Online to On-prem DB using gateways.. but my main question is; how we can develop a dynamic web part (similar to the current on-prem web part), which allow us to show & filter data from on-prem database's Tables,Views & Stored procedure, by just specifying which components (table,view or Stored Procedure) we want to show the data from .. Is there a documentation to create such SPFx web part? or if there are 3rd part SPFx web part that we can benefit from?
You have two possibilities to solve this challenge:
If you only have the possibility to refactor this Farm Solutions
Web Part to SPFx, consider using a local data gateway to
help as an artifact to generate the connections from the local
environment to the cloud, and suddenly, you can persist these
registered connections into a restricted access SharePoint List (for example) and consume with a combo box. But if you
can't make progress with this approach, you'll need to consider the
2nd possibility (this one is more difficult);
Develop a Provider-Hosted SharePoint Add-In, which can be hosted on on-premises IIS and can connect to your various on-premises databases as a shared connection string in your example image above.
I've using Microsoft Graph Connector to pull On-prem SQL data into Microsoft Search (via Microsoft API), and then combine that with PnP Modern Search for query/filter results by selecting Graph as data source.
This feature is listed under MS Search & Intelligence. You can
Specify a connection string to connect to on-premises SQL server
Specify the Table or Stored Procedure or View to connect with
-- You define it in the PnP <Modern Search web part. Note that you can only filter/query/refinable if you've defined it in step 1 or 2 above.
I am working on a task where I need to run SSRS and SharePoint on different servers, but right now, SSRS is working in integrated mode. Is it possible to configure a remote SSRS instance in integrated mode with a sharepoint instance ?
I stand under correction, however, I believe you could use the SharePoint SSRS web-part component and as long as the user executing the request (Your service account on SharePoint) has access to the database it should work.
Ensure that the AD user that is running the SharePoint front-end has access to the database (read / execute) - can be added to a group that has access to the database, or
give the user exclusive access to the database <- not the recommended solution
I am new to windows azure.Can anyone please tell me the process of creating database and tables in windows azure and how to connect to that connection to application .we have windows azure account .please clarify my doubts.any of pdf books for deploying the rest wcf services in cloud let me know the links.
Thanks,
It is May 2014 and that Silverlight online tool just is not really much better.
Best approach is to use SSMS (SQL Server Management Studio) you can even use the free tools tool.
Connect to your Azure with the portal supplied server url / port ... and then your username /password.
Say you scripted out an existing database tables and want to execute that script, you have much more freedom and control with SSMS than online.
For table creation note that a few caveats, One that is common is that not all of T-SQL is supported and a typical script from another database table(s) you end up needed to strip off the two "ON [PRIMARY]" parts of the create statement
Click on the database server in the management portal. 1st thing you would do is manage the allowed IP Addresses which can access this server/database. Allow your local IP address there. After that you have 2 choices:
Use Sql Server Management Studio - It does not have the table editor and you would need to write T-SQL scripts manually.
Use Silverlight based database management utility - to access this, click on the Manage Url link as shown in the screenshot below.
Since you cannot have wizards for Adding/Editing tables, constraints or keys for Azure DB, even if you have connected it through MS SQL Server Management Studio, you can use RazorSQL for this purpose. It gives you a feeling like you are playing with your azure DB in management studio, same as you do with your normal DBs
I have followed all the steps correctly present in
http://msdn.microsoft.com/en-us/library/gg492140.aspx
I am trying to connect to SSAS 2008 via IIS (HTTP). My SSAS is on Machine 1. My excel 2010 client is on Machine 2. I have enabled basic authentication for this. I am able to connect SSAS when I am using the credentials of 'System Administrator' of Machine 1 (on which SSAS is present). But if I am using any another user then I am able to connect to SSAS. Is this a limitation with IIS or SSAS? Please share your views, it's really urgent.
do you have roles defined in the SSAS database granting access to other users? if "system administrator" is a SSAS server admin, it won't need to be explicity granted access to the SSAS database via a role. But other users (who are not SSAS server admins) will need explicit access via a role defined in the particular SSAS database.
My problem is resolved. I don't know weather it's a correct solution or not. I have created few users on machine where SSAS is configured with IIS_IUSERS and now SSAS security is working as expected. Please confirm weather it's a right solution or not? Any comments ahd help is appreciated.
With regards,
Avinash Nigam
First of all you dont need to configure SSAS to be accessed through HTTP to connect to it from excel. Why are you doing that?
Second, the correct way to access a HTTP cube is http://YOUR_SERVER/olap/msmdpump.dll if you go to SSMS on machine 2 and inform that on the connection, does it work?
Third and more important, where is IIS? Same box than SSAS? If yes, fine! If no, you need to configure kerberos because you would be dealing with a double hop situation
I want to perform the data migration between two SharePoint farms located on the same active directory. I don't know on how to migrate the data from one SharePoint from to another new SharePoint Farm
Several ways of doing this:
1) Backup content database on source farm and restore in target farm, then attach to a web application.
2) Create (i.e. export) a content migration package on the source farm and import on the target farm
3) Set up a content deployment path between the source and target farms (probably not appropriate in this case)
All of these are documented extensively on Technet. If you have custom or third-party code you will need to deploy these to the target server also.
The fundamental processes will be like this:
Create a new web application in your new WSS server.
Follow the instructions in Move content databases between instances of SQL Server.
However you may not be able to perform all of the steps exactly as written if your previous server farm is not available. The main thing is that you get the most recent backup of the databases restored on your SQL Server, then follow these steps from the linked article:
In Central Administration, on the Application Management page, in the SharePoint Web Application Management section, click Content databases.
On the Manage Content Databases page, click Add a content database.
On the Add Content Database page, type the exact name of the transferred content database, and then click OK.
Repeat steps 14 and 15 for each database you are adding. Be sure that you select the correct Web application from the Web Application menu for each database.
I don't know your farm topology but if you are sharing the same SQL Server used for the dead server farm, make sure that the dead farm is completely powered off. You don't want two different SharePoint farms accessing the same data (especially if one is in an inconsistent state).
If the old farm is alive and not in inconsistent state then you will be better off using a migration tool even if the versions of new and old are same.
The reason is that service packs, patches as well as order of their installation causes differences in SharePoint instances which can mess backup-recovery mechanism.
Migration is much more forgiving as it pre-assumes that differences exist between source and destination.
Several migration tools are available with Sharegate being my favourite.