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
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'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
Is there a way to do either of the following :
1) Transfer an ACL entry on a file that is transferred to a Sharepoint server using the CopyIntoItems.asmx webservice in the Copy object?
OR
2) Access a file/document in a Sharepoint List and add an ACL entry?
I am using the CopyIntoItems.asmx webservice to migrate a file into a Sharepoint Server, but it is not migrating an file-level ACL with it to the Sharepoint server. e.g. domain\user (Read Only) access does not get transferred to the Sharepoint server.
I understand that Sharepoint mainly works with Sharepoint level permissions, but I want to know if there is a way to do what I described with administrator access to the sharepoint server
Thanks ahead of time!
That's because SharePoint does not 'know' your ACL's, it has it's own Security mechanism, SharePoint Groups, which in turn hold for instance an AD security group / user(s). The OOTB web servics do not allow for item level secuirty operations.
You would have to write your own code / webservice and deploy that to the sharepoint server, follow the link in the answer to this question for more info on how to perform security operations on list items:
Permission for a SharePoint document using MOSS web services
Somebody knows how to change the user account and authentication method sharepoint uses to connect to its content database?
It is now setup to connect using Windows Integrated Authentication but I want to change that to a local user account.
Is it even possible to do this?
Thanks in advance
SharePoint supports both types of authentication in SQL Server:
Windows authentication (the default and preferred choice) - windows credentials are used to authenticate against the SQL server. SharePoint uses IIS which runs sites in an application pool worker process. You can change the credentials for a Web application pool here:
Central Administration > Operations > Service Accounts
SQL authentication - a username/password combination is created and stored in SQL server. When you create a content database you can choose SQL authentication and then provide the username/password (which you have already created in SQL). If you want to change the auth type of an existing database, you can detach it by checking the remove option on the database settings page (it removes the database from SharePoint but does not delete the actual data). Then you can re-attach the existing database and choose a different auth type. You can manage content databases here:
Central Administration > Application Management > Content Databases
you can do it by extending webapplication
The below links will helps you
http://weblog.vb-tech.com/nick/archive/2006/06/14/1617.aspx
http://www.codeproject.com/KB/sharepoint/moss_enableforms.aspx
Is it possible to create a user with permissions of both a local administrator and NETWORK SERVICE?
I've got a Sharepoint timer job which runs stsadm for which it needs local administrator permissions. On the other hand temer jobs are also used by other services which need NETWORK SERVICE permissions and those to sets of permissions only overlap, so I need a user with the "sum" of the permissions to run OWSTIMER under.
(I know that most of the operations you can perform with stsadm sharepoint administration API can be used, by in my case it is the operation which moves a site collection between content databases for which there seems to be no API equivalent).
I recommend always using domain accounts - SharePoint works best on servers connected to an Active Directory server. For production environments a best practice is using a least privilege account. I always create the following domain account dedicated to SharePoint services:
DOM\spservice
You do not need to grant any special privileges to this account as SharePoint will automatically do this for you when you specify the account during setup.
I can't help you with the user permissions (Lars hit the important points), but I wanted to share some information that may be of use.
You mentioned that you're trying to move site collections between content databases and haven't found an API the can be leveraged. Have you looked into SharePoint's Content Deployment API (also know as the PRIME API) to see if it can assist? The types of which I'm speaking are located in the Microsoft.SharePoint.Deployment namespace, and they provide you with mechanisms to export (via SPExport) site collections as CAB files and then import them (via SPImport).
SharePoint leverages types in this namespace for its own content deployment paths and jobs (in MOSS); it's also the API that is leveraged by the STSADM.EXE executable for export (STSADM.EXE -o export) and complementary import operations. For that matter, it's also used by SharePoint Designer for it's site "backup" and "restore" operations.
For an example of how this API can be leveraged, check out the SharePoint Content Deployment Wizard tool on CodePlex (http://www.codeplex.com/SPDeploymentWizard).
I hope this gives you a potential alternative to shelling out to a command line in your timer job!