SSIS package error while executing the job from SQL Server Agent

Gani_tpt 1,506

I have developed one SSIS package and trying to make jobs in SQL server agent.

After configuring the packages in SQL Server Agent, When i run the jobs i am getting the below error.

Error : Argument "Excel" for option "connection" is not valid. The command line parameters are invalid. The step failed.

Below is the server settings :

Windows server 2019 - 64-bit version

SQL Server Business Intelligence studio - Microsoft Visual Studio 2008

User's image

pls. tell me where is the problem and how to solve this....?

Yitzhak Khabinsky 24,946 Reputation points

2023-03-30T16:09:19.1333333+00:00

What is your SSIS run-time SQL Server version on the server?
Gani_tpt 1,506 Reputation points

2023-03-31T07:22:57.6566667+00:00

Hi @Yitzhak Khabinsky ,

Thanks for your reply.

I am using SQL Server 2008 version.

and Visual Studio 2008 for SQL Server Business Intelligence Studio

MS Excel = Excel 2010

above all are using in server.

3 answers

Bjoern Peters 8,781 Reputation points

2023-03-30T13:41:03.5933333+00:00

Hi Gani

You should provide more information about your connection, how it is configured, where you are executing the package during development, whether Excel is installed on that server, etc.

And maybe it is not the best idea to use such old VS ;-)

I hope my answer is helpful to you,

Your

Bjoern Peters

If the reply was helpful, please upvote and/or accept it as an answer, as this helps others in the community with similar questions. Thanks!
Please sign in to rate this answer.
Gani_tpt 1,506 Reputation points

2023-03-31T08:50:44.7966667+00:00

Hi...

Gani_tpt 1,506 Reputation points

2023-03-31T09:29:34.3133333+00:00

Hi @Bjoern Peters ,

Thanks for your reply.

pls. find below screent shot.

Excell already Installed - Excel 2010

Packages developed in server.

Connection and DB also the same server.

pls. let me know if you need any more details.
Sign in to comment
ZoeHui-MSFT 32,821 Reputation points

2023-03-31T06:09:03.36+00:00

Hi @Gani_tpt,

It seems that the error thrown at your Excel Source.

Please uncheck the Excel Connection Manager under Data sources tab in SQL Server Agent Job Step. Besides, make sure that you have check the ‘Use 32 bit runtime’ checkbox under Execution options tab in SQL Server Agent Job Step.

Regards，

Zoe Hui

If the answer is helpful, please click "Accept Answer" and upvote it.
Please sign in to rate this answer.
Gani_tpt 1,506 Reputation points

2023-03-31T08:45:32.8833333+00:00

Hi @ZoeHui-MSFT ,

Gani_tpt 1,506 Reputation points

2023-03-31T09:23:52.8966667+00:00

Hi @ZoeHui-MSFT ,

Thanks for your reply.

I did the changes like you mentioned.

But, i am getting different error.

Executed as user: SVR09AQ01\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:48:12 PM Error: 2023-03-31 13:48:13.87 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 Error: 2023-03-31 13:48:14.15 Code: 0xC0202009 Source: Package Connection manager "SVR09AQ01.PROJ21.SRVRUSR2198" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'SRVRUSR2198'.". End Error Error: 2023-03-31 13:48:14.15 Code: 0xC020801C Source: Data Flow Task OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SVR09AQ01.PROJ21.SRVRUSR2198" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2023-03-31 13:48:14.15 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2023-03-31 13:48:14.15 Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2023-03-31 13:48:14.15 Code: 0xC0024107 Source: Data Flow Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:48:12 PM Finished: 1:48:14 PM Elapsed: 1.407 seconds. The package execution failed. The step failed.

Gani_tpt 1,506 Reputation points

2023-03-31T09:31:55.32+00:00

Hi,

pls. find below.
Sign in to comment
ZoeHui-MSFT 32,821 Reputation points

2023-03-31T09:31:30.8066667+00:00

Hi @Gani_tpt,

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.

This behavior occurs when you try to run the SSIS package by using a different computer or a different user account than the computer and user account that were used to create the SSIS package.

To resolve this behavior, change the value of the ProtectionLevel property in the SSIS package.

More details you may refer the official documentations:

error-loading-message-run-integration-services-package

access-control-for-sensitive-data-in-packages

Regards，

Zoe Hui

If the answer is helpful, please click "Accept Answer" and upvote it.
Please sign in to rate this answer.
Gani_tpt 1,506 Reputation points

2023-03-31T09:36:53.2433333+00:00

Hi @ZoeHui-MSFT ,

Thanks for your quick reply.

Can you pls. share the screenshot when we could find the ProtectionLevel property in the SSIS package and what we need to change...?

ZoeHui-MSFT 32,821 Reputation points

2023-03-31T09:41:21.37+00:00

Hi @Gani_tpt,

Please check below image:

Gani_tpt 1,506 Reputation points

2023-03-31T11:09:00.6+00:00

Hi @ZoeHui-MSFT ,

Thanks for your reply.

Actually, SSIS package has developed in one person and implementing this package in SQL Server Agent in another person.

In this case, what type of ProtectionLevel have to use...?

Gani_tpt 1,506 Reputation points

2023-04-03T06:41:58.4733333+00:00

I tried all the steps as mentioned above. still not working.

Can i have some sample packages for testing and scheduling in SQL Server Agent...?
Sign in to comment