We have a scheduled SQL Job which runs the SSIS package and process the files (Hourly Job, and 24 execution's daily).
From past few weeks we are seeing minimum 2 failures in a day randomly, post failure also Job executes run fine in next execution cycle i.e = next hour.
Very recently we have upgraded our SSMS to 2019
Error
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 15.0.2000.5 for 64-bit Copyright (C) 2019 Microsoft. All rights reserved. Started: [TIME] Error: [DATE TIME] Code: 0x00000005 Source: File count File count Description: Failed to compiled scripts contained in the package. Open the package in SSIS Designer and resolve the compilation errors. End Error Error: [DATE TIME] Code: 0x00000005 Source: File count File count Description: The directory is not empty. (Exception from HRESULT: 0x80070091) End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: [TIME] Finished: [TIME] Elapsed: #### seconds. The package execution failed. The step failed.
Related
Using SQL Server 2016, I was able to run the package on another SQL Server 2016 but when I moved the SSIS package it failed with this error:
02/10/2021 16:20:31,ARGUS_DataEngine,Error,1,HORAE,ARGUS_DataEngine,Rename dhc File,,Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 13.0.4224.16 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 4:20:31 PM Error: 2021-02-10 16:20:31.87 Code: 0xC001F02A Source: ARGUS_DHC_Rename Description: Cannot create a task from XML for task "Script Task Rename File" type "Microsoft.ScriptTask" due to error 0x80070057 "The parameter is incorrect.". End Error Error: 2021-02-10 16:20:31.88 Code: 0xC0010018 Source: Script Task Rename File Description: Failed to load task "Script Task Rename File" type "". The contact information for this task is "". End Error Error: 2021-02-10 16:20:31.88 Code: 0xC0010026 Source: Script Task Rename File Description: The task has failed to load. The contact information for this task is "". End Error Error: 2021-02-10 16:20:31.89 Code: 0xC0024107 Source: Script Task Rename File Description: There were errors during task validation. End Error Error: 2021-02-10 16:20:31.89 Code: 0xC0010025 Source: ARGUS_DHC_Rename Description: The package cannot execute because it contains tasks that failed to load. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:20:31 PM Finished: 4:20:31 PM Elapsed: 0.328 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,,0
Check the paths and the delyvalidation options in the package.
Are the new paths accessible from the new location of the package?
Is the account running the package granted this path?
It looks like you are running the package from the SQL Server Agent : NT Service\SQLSERVERAGENT
Please explain more the situation, did you deployed the package to another server?
Also check the 32 bits option, from the agent options, a screenshot of this options is available here: https://techcommunity.microsoft.com/t5/sql-server-integration-services/use-32bit-runtime-option-for-sql-agent/ba-p/387433
I am getting an error when I schedule a SSIS package in SQL server job
but if run manually the package as well as job also executing successfully.
Even if I am creating the package in same server where data present in the database.
But when it is running via scheduler I am getting this error
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 11:00:00 PM Error: 2019-05-09 23:00:22.74 Code: 0xC002F304 Source: Send Mail Task Send Mail Task Description: An error occurred with the following error message: "Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX5 ". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:00:00 PM Finished: 11:00:22 PM Elapsed: 21.859 seconds. The package execution failed. The step failed.
I created a SQL agent Job to run a package which uses FTP connection. The package contains a script task to get run time variable values and create a new output file. package runs locally successfully, When I run through job it throws below error.
CORP\U4PWMCA1. Microsoft (R) SQL Server Execute Package Utility Version 10.50.6560.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 3:06:26 PM Error: 2019-04-25 15:06:27.79 Code: 0x00000008 Source: SCR_Set_Global_Variables Description: The script returned a failure result. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:06:26 PM Finished: 3:06:27 PM Elapsed: 1.078 seconds. The package execution failed. The step failed.
Can you please suggest what is the issue?
I have a SSIS package to export out .crd file.
When I execute it from Integration Service, it works file. But if I call the package from SQL job agent I will get bellow error.
The funny think is if I change the connectionString from .crd to .csv it will just run fine from both Intergration Service and SQL Agent.
thanks.
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server
Execute Package Utility Version 11.0.6020.0 for 64-bit Copyright (C)
Microsoft Corporation. All rights reserved. Started: 11:47:32 AM
Error: 2016-03-30 11:47:32.70 Code: 0xC020200E Source: Data
Flow Task 1 Destination - #_crd [2] Description: Cannot open the
datafile "\export file path####.crd". End Error Error: 2016-03-30
11:47:32.70 Code: 0xC004701A Source: Data Flow Task 1
SSIS.Pipeline Description: Destination - #_crd failed the
pre-execute phase and returned error code 0xC020200E. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started:
11:47:32 AM Finished: 11:47:32 AM Elapsed: 0.391 seconds. The
package execution failed. The step failed.
I have an SSIS package on Server2 (2008, 64 bit)and I am trying to call it from server1(2005, 32 bit) using xp_cmdshell using command,
exec xp_cmdshell 'dtexec /FILE "\\Wdvwd99a0234\PWOSSIS\RTS_SSIS\RTS_ETL.BE_2_DUNSMasterPackage.dtsx"'
It keeps giving error:
Microsoft (R) SQL Server Execute Package Utility Version 9.00.5000.00
for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights
reserved. NULL Started: 1:00:42 PM Error: 2012-11-29 13:00:42.83
Code: 0xC001700A Source: Description: The version number in
the package is not valid. The version number cannot be greater than
current version number. End Error Error: 2012-11-29 13:00:42.83
Code: 0xC0016020 Source: Description: Package migration from
version 3 to version 2 failed with error 0xC001700A "The version
number in the package is not valid. The version number cannot be
greater than current version number.". End Error Error: 2012-11-29
13:00:42.83 Code: 0xC0010018 Source: Description: Error
loading value "3" from node
"DTS:Property". End Error Could not load package
"\Wdvwd99a0234\PWOSSIS\RTS_SSIS\RTS_ETL.BE_2_DUNSMasterPackage.dtsx"
because of error 0xC0010014. Description: The package failed to load
due to error 0xC0010014 "One or more error occurred. There should be
more specific errors preceding this one that explains the details of
the errors. This message is used as a return value from functions that
encoun ter errors.". This occurs when CPackage::LoadFromXML fails.
Source: Started: 1:00:42 PM Finished: 1:00:42 PM Elapsed: 0.078
seconds NULL
As others have commented, the version of dtexec.exe needs to match the version of the target package. Your options are
Install the 2008 Integration Services components on Server1. You would need to provide an explicit path to the dtexec to ensure xp_cmdshell runs the 2008 version.
Run the package on the remote (Server2) machine. Lowest barrier of entry would be to create a SQL Agent job on Server2, unscheduled, that simply runs the package RTS_ETL.BE_2_DUNSMasterPackage.dtsx You would then start the job in place of the current xp_cmdshell. EXECUTE msdb.dbo.sp_start_job 'RTS_ETL.BE_2_DUNSMasterPackage' Two caveats to this approach
You can have as many concurrent dtexec calls running as your machine can support. A specific SQL Agent job cannot be running more than once.
If you were providing dynamic run-time options, that also isn't going to work with an agent job.
A 2008 package cannot be ran with the 2005 package utility.