SSIS package fails when it is executed by procedure (2008)
Hi there,
I have a very anoying problem with SSIS. I've done new packages into same project, almost identical compared to old ones. They work well in visual studio, but I can't execute them using procedure. Old packages works just fine, but none of the new. Error
message is in the end of my story.
Visual Studio version is 9.0.30729.1 and SQL Server version is 10.0.4000.0. Is it possible, that these not not updated versions could cause this problem?
Package ProtectionLevel is DonSaveSensitive.
Br,
Ville
Error messages, when package is executed by procedure:
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.1600.1 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
NULL
Started: 10:36:48 AM
Error: 2015-03-31 10:36:48.48
Code: 0xC0016016
Source:
Description: Failed to decrypt protected XML node
"DTS:Password" with error 0x8009000B "Key not valid for use in
specified state.". You may not be authorized to access this information.
This error occurs when there is a cryptographic error. Verify that
the correct key is available.
End Error
Progress: 2015-03-31 10:36:48.65
Source: Data Flow Task 1
Validating: 0% complete
End Progress
Progress: 2015-03-31 10:36:48.81
Source: Data Flow Task 1
Validating: 50% complete
End Progress
Progress: 2015-03-31 10:36:48.81
Source: Data Flow Task 1
Validating: 100% complete
End Progress
Progress: 2015-03-31 10:36:48.82
Source: Data Flow Task 1
Validating: 0% complete
End Progress
Progress: 2015-03-31 10:36:48.88
Source: Data Flow Task 1
Validating: 50% complete
End Progress
Progress: 2015-03-31 10:36:48.89
Source: Data Flow Task 1
Validating: 100% complete
End Progress
Progress: 2015-03-31 10:36:48.89
Source: Data Flow Task 1
Prepare for Execute: 0% complete
End Progress
Progress: 2015-03-31 10:36:48.89
Source: Data Flow Task 1
Prepare for Execute: 50% complete
End Progress
Progress: 2015-03-31 10:36:48.89
Source: Data Flow Task 1
Prepare for Execute: 100% complete
End Progress
Progress: 2015-03-31 10:36:48.95
Source: Data Flow Task 1
Pre-Execute: 0% complete
End Progress
Progress: 2015-03-31 10:36:49.03
Source: Data Flow Task 1
Pre-Execute: 50% complete
End Progress
Warning: 2015-03-31 10:36:49.03
Code: 0x80070003
Source: Data Flow Task 1 Destination - tb_month_standard_idx_table_exp_032013-082013_20140307_csv
[34]
Description: The system cannot find the path specified.
End Warning
Progress: 2015-03-31 10:36:49.28
Source: Error Msg
Executing query "insert into
focusbase.dbo.tb_ctrl_package_error_ms...".: 100% complete
End Progress
Error: 2015-03-31 10:36:49.28
Code: 0xC020200E
Source: Data Flow Task 1 Destination -
tb_month_standard_idx_table_exp_032013-082013_20140307_csv [34]
Description: Cannot open the datafile
"D:\Procogs_export_validation\StandardSetup\tb_month_standard_idx_table_exp_032013-082013_20140307.csv".
End Error
Progress: 2015-03-31 10:36:49.29
Source: Error Msg
Executing query "insert into
focusbase.dbo.tb_ctrl_package_error_ms...".: 100% complete
End Progress
Error: 2015-03-31 10:36:49.29
Code: 0xC004701A
Source: Data Flow Task 1 SSIS.Pipeline
Description: component "Destination -
tb_month_standard_idx_table_exp_032013-082013_20140307_csv" (34) failed
the pre-execute phase and returned error code 0xC020200E.
End Error
Progress: 2015-03-31 10:36:49.29
Source: Data Flow Task 1
Pre-Execute: 100% complete
End Progress
Progress: 2015-03-31 10:36:49.29
Source: Data Flow Task 1
Post Execute: 0% complete
End Progress
Progress: 2015-03-31 10:36:49.29
Source: Data Flow Task 1
Post Execute: 50% complete
End Progress
Progress: 2015-03-31 10:36:49.29
Source: Data Flow Task 1
Cleanup: 0% complete
End Progress
Progress: 2015-03-31 10:36:49.29
Source: Data Flow Task 1
Cleanup: 50% complete
End Progress
Progress: 2015-03-31 10:36:49.29
Source: Data Flow Task 1
Cleanup: 100% complete
End Progress
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 10:36:48 AM
Finished: 10:36:49 AM
Elapsed: 0.905 seconds
NULL<o:p></o:p>
<o:p> </o:p>
<o:p> </o:p>
Hi,
That path is not in use?! Yes, it is in error, but not in package. Maybe it has been there before, but now I can't find it. Or actually, path is valid, but not the file name.
I had on error in package configuration file path, but here is the latest error message:
Br,
Ville
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.1600.1 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
NULL
Started: 1:50:59 PM
Error: 2015-03-31 13:50:59.38
Code: 0xC0016016
Source:
Description: Failed to decrypt protected XML node
"DTS:Password" with error 0x8009000B "Key not valid for use in
specified state.". You may not be authorized to access this information.
This error occurs when there is a cryptographic error. Verify that
the correct key is available.
End Error
Progress: 2015-03-31 13:50:59.56
Source: Data Flow Task 1
Validating: 0% complete
End Progress
Progress: 2015-03-31 13:50:59.72
Source: Data Flow Task 1
Validating: 50% complete
End Progress
Progress: 2015-03-31 13:50:59.72
Source: Data Flow Task 1
Validating: 100% complete
End Progress
Progress: 2015-03-31 13:50:59.73
Source: Data Flow Task 1
Validating: 0% complete
End Progress
Progress: 2015-03-31 13:50:59.79
Source: Data Flow Task 1
Validating: 50% complete
End Progress
Progress: 2015-03-31 13:50:59.79
Source: Data Flow Task 1
Validating: 100% complete
End Progress
Progress: 2015-03-31 13:50:59.79
Source: Data Flow Task 1
Prepare for Execute: 0% complete
End Progress
Progress: 2015-03-31 13:50:59.79
Source: Data Flow Task 1
Prepare for Execute: 50% complete
End Progress
Progress: 2015-03-31 13:50:59.79
Source: Data Flow Task 1
Prepare for Execute: 100% complete
End Progress
Progress: 2015-03-31 13:50:59.86
Source: Data Flow Task 1
Pre-Execute: 0% complete
End Progress
Progress: 2015-03-31 13:50:59.92
Source: Data Flow Task 1
Pre-Execute: 50% complete
End Progress
Warning: 2015-03-31 13:50:59.92
Code: 0x80070003
Source: Data Flow Task 1 Destination -
tb_month_standard_idx_table_exp_032013-082013_20140307_csv [34]
Description: The system cannot find the path specified.
End Warning
Progress: 2015-03-31 13:51:00.17
Source: Error Msg
Executing query "insert into
focusbase.dbo.tb_ctrl_package_error_ms...".: 100% complete
End Progress
Error: 2015-03-31 13:51:00.17
Code: 0xC020200E
Source: Data Flow Task 1 Destination -
tb_month_standard_idx_table_exp_032013-082013_20140307_csv [34]
Description: Cannot open the datafile
"D:\Procogs_export_validation\StandardSetup\tb_month_standard_idx_table_exp_032013-082013_20140307.csv".
End Error
Progress: 2015-03-31 13:51:00.17
Source: Error Msg
Executing query "insert into
focusbase.dbo.tb_ctrl_package_error_ms...".: 100% complete
End Progress
Error: 2015-03-31 13:51:00.17
Code: 0xC004701A
Source: Data Flow Task 1 SSIS.Pipeline
Description: component "Destination -
tb_month_standard_idx_table_exp_032013-082013_20140307_csv" (34) failed
the pre-execute phase and returned error code 0xC020200E.
End Error
Progress: 2015-03-31 13:51:00.17
Source: Data Flow Task 1
Pre-Execute: 100% complete
End Progress
Progress: 2015-03-31 13:51:00.17
Source: Data Flow Task 1
Post Execute: 0% complete
End Progress
Progress: 2015-03-31 13:51:00.17
Source: Data Flow Task 1
Post Execute: 50% complete
End Progress
Progress: 2015-03-31 13:51:00.17
Source: Data Flow Task 1
Cleanup: 0% complete
End Progress
Progress: 2015-03-31 13:51:00.17
Source: Data Flow Task 1
Cleanup: 50% complete
End Progress
Progress: 2015-03-31 13:51:00.17
Source: Data Flow Task 1
Cleanup: 100% complete
End Progress
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 1:50:59 PM
Finished: 1:51:00 PM
Elapsed: 0.858 seconds
NULL<o:p></o:p>
Similar Messages
-
SSIS Package Fails when Scheduled as a SQL Server Agent Job
I have an SSIS package that runs without any problems when executed through BIDS.
However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
My question is - what is the advised way of doing this?
Thanks
GaryHi Garyv.King,
When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
For more detailed information about the issue, please following this KB article:
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
http://support.microsoft.com/kb/918760
You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
The following 4 issues are common encountered in the SSIS forum.
1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
2. Data source connection issue.
3. File or registry access permission issue.
4. No 64-bit driver issue.
For more information about it, please see:
How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc
Thanks,
Eileen -
SSIS package fails when Configuration value has value saved into the package
when a package is migrated from dev to QA and to PROD sometimes it fails since the variables have values in them saved into the package.
what we do is clear these values manually and restart the job.
Is there a way we can clear the variables when saving the package or at least programmatically?
eddy.aHello Arthur
Thank you for your response. I should start by apologizing by not making myself clear. We do use indirect configuration that work cross environments however this is the issue that we have:
when the package is first created say you create a DB Variable called A and you enter value A in the variable to test the package. After the package development is tested, you change the configuration values to fetch data whether from an excel file or from
an XML.
when you run on environment A the package runs fine however when you move over to environment B it seems that first it validates against A then overwrites B - if environment A is not there anymore the package sometimes fails.
we are changing these manually for now but I was wondering if there's a way to prevent it.
thanks
eddy.a -
SIS package works in development environment but fails when job scheduler executes, file path invalid
Relatively simple package to get OLE-DB connection to MS FoxPro 9.0 DB
The failure in the job log states that the path is invalid its a network path (\\192.168.1.xxx\foldername) this has been run several ways with the remote computer being mapped as a network drive and through the \\ notation described above.
Thinking it was a security issue between the SQL agent account and my account I tested by subsitution myself as a proxy account for the agent when running this job, again same result failed on network path.
One issue I see is that the remote computer is running Server 2000 (legacy software incompatable with newer versions)
Is it possible that this is a security issue, since if i understand correctly the current MS domain security model didn't exist until Server 2003.Hi REIData,
Have you got the issue resolved? Based on your description, please make sure the target folder is shared properly. If the computer on which the SQL Server Agent job runs doesn’t join the domain as the server that hosts the shared folder, you have to share
the folder with everyone by adding “Everyone” to the people list on the File Sharing page of the folder and assign "Read/Write" permission to it.
Regards,
Mike Yin
TechNet Community Support -
DTEXEC does not fail when SSIS package fails
I need to run my SSIS 2012 packages through the catalog with DTEXEC. This works very well, except that if my SSIS package fails, DTEXEC does not fail. I need DTEXEC to fail, so my scheduler knows that there is an error.
I use the following command:
dtexec /ISServer "\SSISDB\MyFolder\MyProject\MyPackage.dtsx" /Ser MyServer /Par $Package::Partition;201412 /Env 5
When I check the status of the run in the Catalog, it is failed.
When I used SSIS 2008, I had no problem getting DTEXEC to fail when the packages failed.I've had the same problem, and come up with the following prototype for a SQL Script which I run in our JAMS Enterprise Scheduler. It uses SSISDB stored procedures to start the SSIS package and polls every 5 seconds to report any messages, and final
status code of the package. JAMS parameters are delimited by << >> symbols, and will need to be changed for your scheduler/batch process. I guess the script could be converted to a stored procedure. I'm also hoping it will work with SQL High
Availability groups to ensure the SSIS package runs on the server that's hosting the active database.
DECLARE @execution_id BIGINT
DECLARE @status INT= 1
DECLARE @Event_Message_id BIGINT= 0
DECLARE @Last_Event_Message_id BIGINT= 0
DECLARE @message_time DATETIME2(7)
DECLARE @message NVARCHAR(MAX)
--Create a SSIS execution for the required SSIS package and return the execution_id
EXEC [SSISDB].[catalog].[create_execution] @package_name = N'<<pPackageName>>.dtsx',
@execution_id = @execution_id OUTPUT, @folder_name = N'<<pSSISFolderName>>',
@project_name = N'<<pSSISProjectName>>', @use32bitruntime = <<p32Bit>>, @reference_id = NULL
RAISERROR('Starting SSIS package <<pPackageName>> with execution_id %I64d on server %s',0,0,@execution_id,@@SERVERNAME) WITH NOWAIT
--Set the logging level 0-none, 1-basic (recommended), 2-performance, 3-verbose
EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id,
@object_type = 50, @parameter_name = N'LOGGING_LEVEL',
@parameter_value = <<pLogging_Level>>
--Start the package executing
EXEC [SSISDB].[catalog].[start_execution] @execution_id
WHILE @status IN ( 1, 2, 5, 8 ) --created (1), running (2), canceled (3), failed (4), pending (5), ended unexpectedly (6), succeeded (7), stopping (8), and completed (9).
BEGIN
WAITFOR DELAY '00:00:05'
--Get the status to see later if we've finished
SELECT @status = status
FROM SSISDB.catalog.executions
WHERE execution_id = @execution_id
--Are there any event messages since we last reported any?
DECLARE curEventMessages CURSOR FAST_FORWARD
FOR
SELECT event_message_id ,
message_time ,
message
FROM SSISDB.catalog.event_messages
WHERE operation_id = @execution_id
AND event_message_id > @Last_Event_Message_id;
OPEN curEventMessages
FETCH NEXT FROM curEventMessages INTO @Event_Message_id, @message_time,
@message
WHILE @@FETCH_STATUS = 0
BEGIN
--We've found a message, so display it - watch out for % signs in the message, they'll cause an error if we don't replace them
SET @message = CONVERT(NVARCHAR(MAX), @message_time, 113)
+ ' ' + replace(@message,'%',' percent')
RAISERROR(@message,0,0) WITH NOWAIT
SET @Last_Event_Message_id = @Event_Message_id --Make a note that we've reported this message
FETCH NEXT FROM curEventMessages INTO @Event_Message_id,
@message_time, @message
END
CLOSE curEventMessages
DEALLOCATE curEventMessages
END
--@Status indicates that package execution has finished, so let's look at the outcome, and error if there's a problem
IF @status = 7
RAISERROR('Package Succeeded',0,0)
ELSE
IF @status = 9
RAISERROR('Package completed',0,0)
ELSE
IF @status = 3
RAISERROR('Package Cancelled',16,1)
ELSE
IF @status = 4
RAISERROR('Package failed (see error message above)',16,1)
ELSE
IF @status = 6
RAISERROR('Package ended unexpectedly',16,1)
ELSE
RAISERROR('Package ended with unknown status %i',16,1,@status) -
SSIS 2012 Scheduled SSIS package fail to start – Execution timed out
Hi
I am currently running into an issue that seem to have a live Connect issue raised for it. The following is the link to the connect issue https://connect.microsoft.com/SQLServer/feedback/details/783291/ssis-package-fails-to-start-application-lock-timeout-in-ssisdb-catalog-create-execution
There is also a blog post that explains this issue in more detail, however the solution
it provides does not work all the time and I am very reluctant to create custom stored procedures in the SSISDB. http://speaksql.wordpress.com/2013/06/27/ssis-2012-fail-to-start-execution-timed-out/
Just to give some more background. When scheduling 10 or more, in my case I scheduled 14, SQL Server Agent Jobs all executing a package in the SSIS Catalog and all kicking off on exactly the same time about 10% to 20% of these jobs fail stating one of the
following error messages:
The operation failed because the execution timed out. Source: .Net SqlClient Data Provider Started: 12:20:01 Finished: 12:20:07 Elapsed: 5.797 seconds. The package execution failed. The step failed.
Description: Transaction (Process ID 66) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Source: .Net SqlClient Data Provider Started: 14:06:48 Finished: 14:06:53
Elapsed: 4.719 seconds. The package execution failed. The step failed.
This timeout takes place both when using TSQL to start the package in the Job or when the step in the Job is set to start the package as an Integration Services Package.
Steps to recreate this:
1. Create one SSIS package that simply executes for around a minute. For example you can use an Execute SQL Task and simply execute the following TSQL "WAITFOR DELAY '00:01:00'"
2. Create 14 SQL Server Agent Jobs each executing the same package and schedule all of them to run at the same time.
3. Watch the execution of the jobs take place and note the failures. (This does not always happen and you might get one run in which everything executes without a problem. The next run might have 6 or 7 of the jobs fail.)
You can also create 14 different SSIS packages, one for each job, and the result is the same.
I am running on SQL 2012 SP1 CU4. Windows Server 2012 R2 patched to the lastest patch level.
This issue does not happen when the packages are deployed to the SSIS Package Store the way that it was done in SQL2008 and before. It only occurs when the SSIS packages are deployed to the SSIS Catalog.
Any help or feedback on this would be greatly appreciated.
Kind Regards,
Christo OlivierHi Tom
Thank you for the fast response. I went and increased the value by 1024KB instead of the initial
512KB. Unfortunately this seems to only alleviate the issue but does not stop it from occurring. It
is happening much less often now but still occurring intermittently.
Regards,
Christo -
I have a SSIS package that fails when running via sql server agent. I can successfully run it from BIDS. I have created a proxy account that is in the local server administrators group and is sysadmin. SQL Server Agent and SQL
Server Integration Services are running under the same account,
following the the error message:
Error: 2014-02-07 10:29:12.59
Code: 0xC0029151
Source: Execute De-linking Execute Process Task
Description: In Executing "d:\cie\files\working\9426\PowerpointConsole.exe" " 60.ppt" at "d:\cie\files\working\9426", The process exit code was "-532459699" while the expected was "0".
End Error
This package ran successfully on a different server running windows 2003 and sql server 2008 r2. The new environment is windows 7 with sql server 2008 r2.Hi Gaileg,
As Abhinav said, to check whether it is a 32-bit/64-bit issue, please check whether the package runs in 32-bit runtime mode or 64-bit runtime mode in BIDS by checking the Run64bitRuntime property of the project. Then, make sure the package runs in the same
runtime mode in the SQL Server Agent job by checking or unchecking the “Use 32 bit runtime” option for the Execution options of the job step.
If it is not the issue, please create another job that uses a CmdExec type job step to call the executable “D:\cie\files\working\9426\PowerpointConsole.exe”. If this job also fails, the issue is actually occurs because of the issue between executable and
SQL Server Agent rather than the SSIS package itself.
Regards,
Mike Yin
TechNet Community Support -
Hello,
When I move the package from development to production package fails due to excel connection manager.
Error message---
Message
Executed as user: Answers\Administrator. ...lt: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50 Code: 0xC0202009 Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE
DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50 Code: 0xC0202009 Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE
DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50 Code: 0xC0202009 Source... The package execution
fa... The step failed.
Any help would be appreciated.Hi Vinay,
As Visakh mentioned, the issue usually occurs because the package runs in 64-bit runtime, however, the Excel driver is 32-bit. According to your another thread, it seems that you use SSIS 2005, right? In SSIS 2005, there is no “use 32 bit runtime” option
for the package executions of a SSIS package job step. In this condition, you have two choices:
Install the 64-bit Microsoft ACE OLE DB 12.0 Provider on the production server. Here is the download link (AccessDatabaseEngine_x64.exe):
http://www.microsoft.com/en-in/download/details.aspx?id=13255
Create a CmdExec type job step instead of SSIS Package job step, so that we can call 32-bit DTExec.exe to execute the package within command line. For more information, please see:
http://support.microsoft.com/kb/934653/en-us
Regards,
Mike Yin
TechNet Community Support -
SSIS package fails with the error as given below. But its warning messages are incorrect.
My SSIS package loads data from access database to SQL Server database.
It's a straight copy. It fails with the below warnings and error message as shown below:
Error messages:
[OLE DB Source [113]] Error: There was an error with OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID] on OLE DB Source.Outputs[OLE DB Source Output]. The column status returned was: "Text was truncated or one or more characters had no
match in the target code page.".
[OLE DB Source [113]] Error: The "OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID]" failed because truncation occurred, and the truncation row disposition on "OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID]"
specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
There are 3 warning messages even before I run the package. Warnings are all about the mismatch between the source and destination column sizes.
I cross checked the source and destination column sizes. The destination column sizes are fairly high than the source column sizes.
It worked well all the while and when we are going to pre-prod it is throwing errors. Any help is highly appreciated.
Thank you.It worked well all the while and when we are going to pre-prod it is throwing errors. Any help is highly appreciated.
Please check if the dev destination table has same column data types and size as compared with pre prod table
Thanks, hsbal -
I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package. The website and the instance of SQL Server with the agent and SSIS package are
on the same windows 2008 r2 server. When the button is operated no exceptions are raised but the SSIS package did not execute.
When I look in the logfileviewer at the job history of the sql server agent job I see that the job failed with message...
The job failed. Unable to determine if the owner (DOMAINNAME\userid) of job runWebDevSmall has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINNAME\userid'<c/> error code 0x6e. [SQLSTATE 42000] (Error 15404)).,00:00:00,0,0,,,,0
...even though DOMAINNAME\userid is in the logins for the sql server and has admin authorities.
Could someone show me what I need to do to get this to run? Thanks tonnes in advance for any help, RoscoeThis can happen when the network is too slow to allow a timely completion of the verification. Or the account running has no such right.
I suggest you try using the SA account for the job as it does not require to poll the AD.
Arthur My Blog -
SSIS package fails under SQL Server Agent job
Hi All
I have designed a SSIS package to encrypt a file using Cipher (EFS) it works fine from BIDS & Package Execution Utility.
But SQL Server Agent job is failing to do this. I am getting the error as
" In executing C:\Windows\System32\Cipher.exe /e /a C:\Test.txt at "",The Process Exit code was 1 while the expected was 0."
Please help me.
ThanksTwo things that usually come to mind when this happens from BIDS locally to the SQL Agent are
1. Security is not
adequate under the SQL Agent Service Account
Rule the security problem out by setting up a proxy account that you know ahs security to run the needed tasks in the package. Either that or give the service account the permissions needed.
2. 32bit BIDS development and running under a 64bit Platform in your SSIS installation
This can be fixed by selecting run in 32bit more or running the package with the 32bit installed version of DTEXEC found in the Program Files (x86) folder where you installed tools.
Next, setup logging in the package so you get a more detailed error message. Event handlers on the tasks will be much more detailed using the OnError event. you can write that to either a flat file with a data flow in the event handler or simply
insert the event into a table using the ? as the parms. If you need assistance setting that up, here are basic steps for a SQL Server table
1) Select the task and click the event handler tab in BIDS
2) Select OnError event handler in the list
3) Click the enable link and drag a Execute TSQL Task over to the window
4) Create a table in your SQL Server database (create one so you don't litter your user DBs if needed)
5) Open the task and add the connection as needed. Then add this statement
INSERT INTO dbo.TableYouCreated
(PackageName, SourceName, EventInfo)
VALUES (?,?,?)
6) Go to parameter mappings and add 4 new mappings as following
System::PackageName
Input
nvarchar
0
System::SourceName
Input
nvarchar
1
System::ErrorDescription
Input
nvarchar
2
Save and reimport the package and then the event of the errors should insert into the table in detail
Ted Krueger
Blog on lessthandot.com @onpnt on twitter -
SSIS package give an error if execute through SQL server agent
I have created a SSIS package in BIDS 2012. If i execute this package through sql server agent it gives the below error:
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:19:47 AM Error: 2015-01-20
11:19:47.83 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.".
You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:47.94 Code: 0xC0016016 Source:
Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error
occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:48.04 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to
decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct
key is available. End Error Error: 2015-01-20 11:19:48.92 Code: 0xC00291EC Source: alter_keys Execute SQL Task Description: Failed to acquire connection "mstr_warehouse". Connection may not be
configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:19:47 AM Finished: 11:19:48 AM Elapsed: 1.42 seconds.
The package execution failed. The step failed.
so i have change some properties in our package like protectionlevel change from encrypted to dontsavesensitive. After that i have created configuration file for the package and use that configuration file. It executes the package through sql server agent
smoothly.
Thanks
Azhar KhanHi selfdestruct80,
According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
According to my knowledge, the package may not run in the following scenarios:
The current user cannot decrypt secrets from the package.
A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
A task or a connection manager requires that the current user account has correct permissions.
According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
/FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support -
Hi,
I've successfully created a SSIS package and I can execute it manually. Now I am trying to schedule it as a job to run daily at certain time. For this, I tried to create a job through 'SQL Server Agent' in Sql Server Management Studio. But when I configured
the Step properties and clicked 'Ok' it is throwing this error.
TITLE: SSIS Execution Properties
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 encounter errors.".
This occurs when CPackage::LoadFromXML fails.
ADDITIONAL INFORMATION:
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 encounter errors.".
This occurs when CPackage::LoadFromXML fails.
I am using Visual Studio 2010 for creating package and SQL Server 2008 R2. Also, I gave my credentials in the package's connection string. And I am trying to schedule the job with the same package credentials as the job owner.
The Protection Level in Visual Studio was set to 'EncryptSensitiveWithUserKey'.
What am I doing wrong to create a job step?
Thanks for any help!Hi CRMProgrammer,
Based on my research, the error “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 encounter errors.". This occurs when CPackage::LoadFromXML fails.” always occurs when you open or deploy a higher version SSIS in a lower version SQL Server.
Based on your description, it seems that the package is created in SSIS 2012, while you trying to schedule it in SQL Server 2008 R2. SSIS versions are not backwards compatible. Please notice that once a package is upgraded from SSIS 2008 R2 package schema
to SSIS 2012 package schema, the package cannot be downgraded. So we cannot schedule the SSIS 2012 packages in SQL Server 2008 R2 anymore.
To work around this, we should recreate the package in SSIS 2008R2 or schedule the package in SQL Server 2012.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support -
Execute SSIS Package from JOB which contains Execute Process Task calling a .bat file
Hi All,
I have a EXCEL Macro needs to be called from SSIS. We could not use Script task because of some internal reason.
So we have taken an approach to call a .BAT file using Execute Process Task. This .BAT file will call a .VBS file which will execute the EXCEL Macro.
The SSIS Package is running good if I execute the package from BIDS.
But the real problem is with the scheduling this SSIS Package using SQL JOB.
If i execute this SSIS package from SQL Server Job, its executing the whole package successfully except the Execute Process Task.
So the overall issue is SQL Server Job is not executing properly if I call any .BAT file from the SSIS Package.
Please give me suggestion to get rid of the issue. Thanks in advance.Hi Sai.N,
If you run the SQL Server Agent job manually from SSMS, does the package execute properly? If the package executes properly when you run the job manually, the issue should occur due to permission issue. In this case, I suggest that you create a SQL Server
Agent proxy based on the current Windows account which you use to log onto the operating system, and run the job under the proxy account.
If it is not the issue, please enable logging in the package as Visakh mentioned and post the warning/error message for further analysis.
Regards,
Mike Yin
TechNet Community Support -
SSIS Package Fails Immediately in Data Manager
Hey all!
I have an SSIS Package that works perfectly in my Production system. I'm currently trying to test the exact same package in my Test System. The only change I've made to the package was to change the server name to point to our Test Server.
Now, within SSIS, this Test package runs completely fine. However, when I try to run the exact same package through the Data Manager. The package Errors out immediately. Of course, BPC gives no error message at all to help troubleshoot.
Does anyone have any idea why this package would work on our Production system, but not our Test Server? Any hints on what to look for would be extremely welcome!
Thanks much!
SeanFor clarity, you have an SSIS package in production, in the DM file folders, that you are copying over to a file location in the TEST environment. Then you are adding the package via the DM interface. The saving the view. Then trying to execute the package?
-If you edit the package via the DM interface, does everything look correct, regarding settings for the package?
-Does the package have more SSIS tasks than just standard BPC tasks? Do they need to be modified for the new servers.
- WHat does the package do? Is it supposed to run logic? B/c it may need the logic statements to be validated and saved?
Please Let us know.
Maybe you are looking for
-
Random packetloss on my new 27" i7
Hello, I just bought a new 27" iMac i7 in late October. From day one I have been experiencing this problem, that is random packetloss resulting I am unable to browse the Internet while it is happening. My iMac is connected to a switch via the etherne
-
Wrong platform selected. Want to change order. How?
Just upgraded my Elemtents 10 to version 13. Accidentally chosen Windows instead of Mac platform. Now I'd like to change my ordered platform. Need help from support team!
-
I have installed CS5 on a macbook pro 10.9.4. I am unable to get the updater to run to update applications to most current version. It tells me there was an error trying to download the update and to try again later.
-
SubscriberList from a jmxTopic
Hello, is there anyway to get a list of subscribers from a JMX-topic (from within a Server-class)? If I look in the JMX-MBean-view I can see the info I want (AllSubscriptionsCount-attribute and the listAllSubscriptions()-operation) I already have the
-
How to print a list of keyword tags in PSE7 from the XML file?
When choosing keyword tags to add to photos it would be useful to have a printed list, structured in categories and sub-categories. The "Save Keyword Tags to File" command just produces an XML file that seems to have all the data, but I don't have an