November 28, 2018 at 11:50 pm
Hi All,
Im executing SSIS package by using Batchfile and scheduled batch using SQL job agent.
Now I got error " Process Exit Code 1. The step failed." No more details found.
Sometime job running successfully sometime it is failing. I cant find what is the exact issue which cause failure.
If anybody could help me on this?
Thanks in advance
November 29, 2018 at 2:07 am
squvi.87 - Wednesday, November 28, 2018 11:50 PMHi All,Im executing SSIS package by using Batchfile and scheduled batch using SQL job agent.
Now I got error " Process Exit Code 1. The step failed." No more details found.
Sometime job running successfully sometime it is failing. I cant find what is the exact issue which cause failure.If anybody could help me on this?
Thanks in advance
What do the logs in SSISDB say? Without a descriptive error, and no details of what the package does, how do you otherwise propose we troubleshoot this?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 29, 2018 at 3:45 am
Thom A - Thursday, November 29, 2018 2:07 AMWhat do the logs in SSISDB say? Without a descriptive error, and no details of what the package does, how do you otherwise propose we troubleshoot this?
Actually packages are not in SSISDB., its a package deployment
below scrip will be saved in batch file and batch file will scheduled using sql job.
dtexec /FILE E:\SSISPackages\Packages-Cube\DimProject.dtsx >>E:\SSISPackages-Logs\Log-Cube\DimProject.txt
November 29, 2018 at 4:03 am
squvi.87 - Thursday, November 29, 2018 3:45 AMThom A - Thursday, November 29, 2018 2:07 AMWhat do the logs in SSISDB say? Without a descriptive error, and no details of what the package does, how do you otherwise propose we troubleshoot this?Actually packages are not in SSISDB., its a package deployment
below scrip will be saved in batch file and batch file will scheduled using sql job.
dtexec /FILE E:\SSISPackages\Packages-Cube\DimProject.dtsx >>E:\SSISPackages-Logs\Log-Cube\DimProject.txt
Why aren't you using Project Deployment? There's very little we can do to help you here without a proper error, or knowledge of what the package is doing like I said. You're question is akin to: "My car is broken, can you tell me how to fix it?" however, you haven't given us any details about the car (make, model, fuel), what the problem is (doesn't start, runs badly, makes a funny noise?), and we can't have a look at the car ourselves either.
At a total guess, you have a script task in the package, which is error, and you have no error handling and messages in there? Without some actually "meat" to the subject though, there's nothing anyone here can really do to help you.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 29, 2018 at 4:39 am
Thom A - Thursday, November 29, 2018 4:03 AMWhy aren't you using Project Deployment? There's very little we can do to help you here without a proper error, or knowledge of what the package is doing like I said. You're question is akin to: "My car is broken, can you tell me how to fix it?" however, you haven't given us any details about the car (make, model, fuel), what the problem is (doesn't start, runs badly, makes a funny noise?), and we can't have a look at the car ourselves either.
At a total guess, you have a script task in the package, which is error, and you have no error handling and messages in there? Without some actually "meat" to the subject though, there's nothing anyone here can really do to help you.
I can understand, but SQL server leaves no trace on what is the error, Some time it is running sometime not. If I check logs it seems batch it not even touched. If I run manually it is running successfully. Some post it is said to be access issue on folder or file. I wonder how come it ran successfully some times.
Currently Im checking is there any access issue on filesystem , Will keep you posted if any.
Why aren't you using Project Deployment? Plan is on. but hard to find time to do so
November 29, 2018 at 5:48 am
anything on E:\SSISPackages-Logs\Log-Cube\DimProject.txt?
and if not can you change the command line to be
dtexec /FILE E:\SSISPackages\Packages-Cube\DimProject.dtsx /reporting V >>E:\SSISPackages-Logs\Log-Cube\DimProject.txt
and execute it again - by default /reporting ew should be on so you do get enough detail on the output file.
V will output everything so should be avoided - only asking for it here so enough detail is supplied
November 29, 2018 at 2:18 pm
Are you the author of the SSIS package. If you open it in SSDT you can add logging to a table, file or Windows Event Log.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply