how to export a file to sharepoint (office 365) using ssis sql agent job? - ssis

i tried to copy the file using copy/xcopy from batch file, but it is not working.
then i downloaded ssis integration tool kit from (http://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-sharepoint/download ) and tried to create a sharepoint connection manger to send the file using file system task, but getting error as unknown namespace type for user in sharepoint connection manager while creating connection manager.
is there any other way to send the files to sharepoint.

Thank you for downloading our software.
It looks like you were not able to build the connection with SharePoint. Can you post the full error message so that we can better assist you?
Once you have created the SharePoint connection manager, it would be fairly easy to upload files to SharePoint using the Premium File Transfer Task which comes with our SharePoint Toolkit.
You can also reach out to us through our official support channel if you have any further questions.
Best regards,
KingswaySoft Support

Related

Loading data from CSV file in Sharepoint to SQL Server table

Is it possible to load data from "CSV file in Sharepoint online" to "Sql Server table" using SSIS without downloading the file to local folders. (I need to deploy the package to Integration Service Catalogs in Sql Server)
Could anyone help me on solving this issue.
You can use the Odata Source with a OData Connection to Access Sharepoint Lists with files. There are a couple tutorials:
https://www.sqlshack.com/how-to-configure-odata-ssis-connection-for-sharepoint-online/
https://www.timmitchell.net/post/2021/01/08/connecting-to-sharepoint-lists-with-ssis/

Share an access Database on Sharepoint

I have created quite a large Access 2016 db. It is now ready to share with the business and needs to be put onto SharePoint. I've tried just uploading the file to a SharePoint document library, however users cannot edit the database (there is a lot of VBA code that runs SQL commands that write data input by users into the database).
Is there a way to share the database that allows users to open it from SharePoint and let the VBA write to the database/tables?
That is not possible as SharePoint isn't an SMB fileshare, neither is OneDrive, DropBox, etc.
The SMB fileshare is offered by a Windows Server or a Linux box with Samba installed.

Deploy SSRS Report to Remote Server

I'm trying to deploy an SSRS report to a remote server (that is not on my network). I'm not sure how to do this. For a machine on my network, I would just change the TargetURL, but I'm guessing there should be somewhere that I can associate credentials to deploy to a remote server, but I'm not finding it.
I know this is an old post but if someone is wondering about the same question.
I am using vs2017 enterprise. So when you configure your remote url and folder name and everything is perfect to build your project, you hit F5 or deploy your project. Upon successful building vs will prompt you for your report servers credential. Then you do the usual and vs will do its own job. In a moment you will be able to access your report.
Just read about the permission requirements before you try it.
Hope it will help someone.
Thanks
I face a similar issue delivering reports to various servers (customers and dev,qa,staging and production.) In visual studio the best way to do it is start a new project for the new server and import the new reports into it. You end up with a new project for each server.
I found TFS / VS unwieldy and my workflow to manage it unfortunately is doing it manually, or using one of a few open source report uploading tools (there are powershell scripts to do it but I find the tools are more user friendly.)
Best thing to start with is doing it manually; which will sort your initial problem.
Save the file out of your report writer to disk.
In Internet Explorer log into the Report Manager of the remote server http(s)://remoteservername/reports and navigate to the folder you want. Then upload the report.
When its uploaded you may need to fix the connection to the database.
Once you get used to doing this you can use a tool like reportsync to easily and quickly move reports between servers.

SSIS: How to I specify the server for the file connection manager (specifying existing directory)?

I'm fairly new to SSIS and am having trouble figuring out something that seems like it should be straight forward:
On server A, I have 10 files in "C:\SourceFiles\Patients" (these files are PDFs). I know the names of these 10 files and they won't change. Also, there is a server B which is the DB server and is where the SSIS package will be located. My goal is to loop through a DB table containing patients, add some patient data to the 10 source files (renaming the file) and then save this new file to server A.
I have most of this running already. Currently, all of this is happening in a script task using ADO.NET for the DB access (I'm already accessing the DB table on server B) and I'm accessing the source files on my local C drive.
I am having trouble figuring out how to specify server A in the Package Configuration for the source files. I have a file connection which specifies an existing folder (C:\SourceFiles\Patients), but it only specifies the location of the folder NOT the server. How to I specify server A for this file connection? Or, how do I use this file connection with a server A connection? I'm having real difficulty grasping this for some reason!!
The technologies I'm using are:
Visual Studio 2008,
C# in the SSIS script task,
ADO.NET in the SSIS script task and
SQL Server Management Studio 2008 (SSIS package will be imported here).
Thanks for pointing me in the right direction!
I see some issues with what you are trying to do.
PDF is an image format (an image of a document) and as such is not easily manipulated by SSIS. Generally if you are acting on a file from within SSIS, it would be a flat file of some sort, like a CSV or some other text format.
Using a script task to do all of your work within SSIS is failing to use the power of SSIS properly. If all you have in your SSIS project is a script task, you should just be using C# or VB.net directly and not involving SSIS in your project at all.
That all being said, you should access your files on server A using UNC (Universal Naming Convention) paths. You will need to pay close attention to your permissions within SSIS to make this work. When an SSIS job runs, it runs under a specific user, usually the SQL Server Agent user, and that user will need permissions to access the folder on server A remotely. When all of these permissions are set correctly, you can use something akin to \\ServerA\ShareName\Patients\ as the pointer to your directory with pdf's in it.

Error using Microsoft Access Database to create ASP.NET website

I am creating a simple C# CMS system using a Microsoft Access database
This is my connection string in the web.config file
<add name="VirtualCMSConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0; Data Source=|DataDirectory|ASPNetDB.mdb" providerName="System.Data.OleDB"/>
I have used the "Access Provider" module found here: http://blog.krisvandermast.com/UsingAccessInsteadOfSQLServerForYourASPNETApplicationServices.aspx
The problem I am having is that when I try to create a Dataset with the dataset designing I recieve an error when I try to choose the connection string for the table adapter.
Failed to open a connection to the database
"Cannot obtain provider factory for
data provider named
'System.Data.OleDb'
Check the connection and try again
Could anyone please help me on this matter.
Thanks.
Have you downloaded the .vsi, extracted it, built the SampleAccessProviders.dll and added it to your project?
Now that we have created the assembly
it's time to actually use it. Open
your Visual Studio or Visual Web
Developer Express and create a new
website. In the project you create a
new subfolder called bin. After
creation right click on it and choose
Add existing item... from the context
menu that appears. Navigate to the
place where the built assembly is. Add
it to the bin folder of the website
project. After that repeat the same
thing with the access database
(ASPNetDB.mdb) file but this time put
it in the dedicated folder App_Data
which is one of the predefined ASP.NET
2.0 subfolders.