Let me know what additional info would help. I have an SSIS package that Imports a csv file to SQL Server and moves that csv into a subfolder of the folder where the csv resides. I can run the package from the Integration Services Catalog with no problem, but when running from the Agent Job it says it can't read the .csv file and I've tried different versions of the file. I tried recreating the job also. No luck. Also the C# script task is not moving the csv to the archive folder even when I run the package from the ISC. The agent error tells me to look at the Execution of the package which says basically it can't open the csv.
Related
In the data folder I have over 250 .sql files that must be deployed in the DB when java application starts run.
All the files are reading by liquibase but not executing.
loads 016-.sql and 022-.sql files
executing only 022-*.sql
Who can help, what's the issue?
The files permissions and file encoding are the same (CL)
My SSIS package creates xls files to a folder. When I execute the project in my local machine that works fine. When I execute the job it creates a file that doesn't exist.
What could be the problem?
The jobs says that:
Source: Send Mail Task Send Mail Task Description: Either the
file
"\\bpptvwdw0000001\DTSXs\SubscricaoDirComercial\CustomSubscriptions\dw_PropAprovadasAConcretizar__20200408.xls"
does not exist or you do not have permissions to access the file."
That means the file does not exist or you do not have permissions to access the file, but when I execute it from my machine the project doesn't create that file.
Most likely the account running your job does not have rights to that folder.
I have defined a process that consists of 2 steps:
Deploy an IIS WebSite
Execute a script file
The first step in the process executes without any issues. I am able to upload a nuget package to Octopus Server's built-in package repository and deploy this to my IIS Web Site.
For the second step in the process, where I am asked to specify a script file to run, I am unable to upload a sql file either using the built-in package repository or using a external package repository since Octopus will not allow me to upload a .sql file type.
What is the best way of specifying the SQL Script File to be run?
Should I package it along with my nuget package and then specify the script source to 'Script file inside a package' or is it possible to upload a SQL file to a repository (external or built-in) and specify that file as the SQL script file to execute?
Is there a best practice for this?
Thanks,
Sean
By "Script file" or "Script file inside a package" Octopus means a Powershell script or Bash script. If you want to execute a SQL script as part of your deployment you have two options:
Install an existing task from the Octopus Community Library (https://library.octopusdeploy.com/listing) that executes SQL. Here are two of them:
SQL - Execute Script - https://library.octopusdeploy.com/step-templates/73f89638-51d1-4fbb-b68f-b71ba9e86720/actiontemplate-sql-execute-script,
SQL - Execute Script File = https://library.octopusdeploy.com/step-templates/709b5872-52e2-4cd9-9ec0-b4a135a0444c/actiontemplate-sql-execute-script-file
Create a Powershell or Bash script to execute your SQL script.
I have created an SSIS package which uses a for each loop container and an Excel connection string that I have created from a variable so I can loop through multiple files. My package works without issue and if I have a number of files in my source folder and I simply execute the package it works perfectly looping through all the files doing what I want it to do.
The issue I have is when I deploy the package, If I have files within my source folder it executes without error but when you look at the source folder it still has the files in. When digging a bit deeper in to the package reports it looks like it is reporting that there were no files found. If I manually execute the dtsx file in runs without issue and imports everything as it should.
Is there any reason why after deploying the package it is unable to recognise the files or the variable that I store the file name in?
Sounds like it could be permissions related. Does the SQL Server Service account have permissions to the directory where the files are stored?
I am working with ssis package. and i developed some packages with the configuration file. In the configuration file i given the all relative paths of the connections like FlatFileConnection, OLEDB Connection etc. it is running fine with dtexec command with /config configuration file path.
But now i need to create a sql job to run this ssis package automatically every day. In this case i want to give the relative path of the config file(I dont want to hard code to the path of configuration file. it should take from the same path of the .dtsx file path) . how can i do this?
Thanks in advance.
Eshwer
You can’t!
You must have the path for the config file on your job step.
If you had it configured somewhere else you would need a configuration to show where the cofig file is. Doesn’t make sense, right?
In SQL Server Management Studio, highlight SQL Server Agent -> Start. Highlight Job ->New Job…, name it , myJob.
Under Steps, New Step, name it, Step1,
Type: SQL Server Integration Service Package
Run as: myProxy
Package source: File System
Browse to select your package file xxx.dtsx
Click Ok
Schedule your job and enable it.........