I have a simple SSIS package that pulls data from a database and creates a file. This file then is FTP'd to another server. I ran into a problem where the FTP server was not available and the package failed without ever sending the file. I would like to be able to have the package continue to attempt the connection until the server comes back up and the FTP can be successful.
Does anyone have an ideas as to how I could make this occur?
In the FTP Connection Manager, not the FTP Task itself, you can set the number of Connection Retries.
Related
I am integrating Quickbooks using SSIS to pull data into our SQL Server Database. The SSIS works fine but the problem is when I run the package from the front-end application. It cannot run it as the credentials to access the Quickbooks API are different than the credentials used to log in on the front end.
I have tried changing the packages and project settings to "DontSaveSensitive" but this causes blank files to be downloaded as it leaves out the credentials for the HTTP Connection.
I tried setting up the proxy tab as well but either get a bad request error, invalid URL error or unable to connect to server error.
Issue was resolved.
The solution was to set the project protection level to "DontSaveSensitive" and then set up a variable for the server password.
In HTTP Connection properties, add an expression (ServerPassword) and set it equal to your new variable.
I Would like to know where I can see the FTP transmission log when I use the "TF Secure FTP Task" locally and from a server?
I've run an SSIS yesterday and all the steps were successful but I was told today that nothing was sent, this is why I'm trying to locate a log file to confirm the transmission.
Thank you
SSIS doesn't automatically log FTP transmissions. If you want to do this in SSIS you will have to code it.
But maybe your FTP server logs transmissions; you should check with the server admin.
I am working on using SSIS FTP task to uploading some files to sftp://apollo.xxx.xxx.com automatically.
I can do that successfully by manually specifying sever name, server port, user name and password in FileZilla.
However, when I setup in the FTP connection manager, the connection fails (could be the issue of SFTP?).
I am just wondering if anyone could provide me some tips?
The native FTP task is just FTP. It does not support sFTP.
As you are not allowed to use third party software, you will be unable to fulfill your request. Based on this question, there does not appear to be a base sftp module in the .NET framework How do I upload a file to an SFTP server in C# / .NET?
I've run into this twice now where I can run my SSIS package in BIDS and Integration Services but it fails when it's run through SQL Server Agent. Both of these packages transfer a file as a final step to a folder on our network.
The error I receive is Could not find a part of the path then the path and file name. When I schedule them in Windows Task Scheduler they execute fine but I'd rather have them run through sql server agent.
Has anyone run into this issue and found a work around? Is there a setting that I'm missing in sql server?
Any help would be appreciated.
You need to run the SQL Server job using a proxy account that is configured to run jobs of type SQL Server Integration Services Packages. The jobs usually run under SQL Server Agent Service account, which does not have access to network folders. To access network folders, you need to set up a proxy with a domain account credentials (preferably) so you can access network path.
Below answer in SO question has the detailed steps on how to set up a proxy account
How do I create a step in my SQL Server Agent Job which will run my SSIS package?
i am working in a client server envirnoment.. i have an SSIS package with xml configuration, when i configure it on a client and execute it, it works find, but when i copy that configured package and try to execute it from another client it is not executed and needs reconfiguration, after reconfiguration it works find...
i also try it with sql server configuration and the same problem was also there...
Is there any way that i configure the ssis package on one pc and can be executed from any client, means no need of reconfiguration when i copy it to another client....
thanks in advance....
When you create an xml file configuration, you provide a connection to that file. But when you move the package to the new client, you have to have the configuration connection as well. Let alone configuration, you need to have the connections set up properly for each and every object that you reference.
Thats the only reason I can fathom why your packages are failing.
executed from any client
Quite possibly not. You're going to need valid permissions (database, file system, ??) for the actions your package takes, and simply copying the package and configuration file won't create those automatically.
You might want to create an SSIS proxy account, grant the necessary permissions to the proxy, then run the package using the proxy. If this is all internal, you enable the proxy account on whatever client systems need to run the package. If you're distributing this to clients, give them instructions for setting up the proxy and they can do the same.