Failed to locate project named ... in SSIS 2012 package scheduled in agent

Hi
I have 2 packages that are deployed using Project deployment model on a, the are scheduled to run every 1/2 hour, for the last 2days the have been failing with Failed to locate project named ...:A .Net framework error occurred during execution of user defined
routine or aggregate "decript_binarydata": System.IO.LoadException Could not load file or assembly.....The thing is that the package was working without issue, this seems to be a decryption issue, so I believe it is to do with Project Deployment
model, but I am not sure
Any help would be much appreciated
Regards
Andy
CRM 4, SQL Server and .Net developer using C#

Hi Andy,
Based on my research, please refer to the following suggestions to fix this issue:
Change the SQL Server Service Account from built in default “NT Service\MSSQLSERVER“ to another account with admin rights on the system.
Grant appropriate permissions to SQL Server Service Account & SQL Agent Service Account.
1. Note down your SQL Server Service Account & SQL Agent Service Account.
2. Go to Start-> Run-> secpol.msc-> Local Policies->User Rights Assignment
3. Check if these 2 accounts are a part of the following policies.
    • Log on as a service
    • Act as part of OS
    • Adjust memory quotas
    • Logon as batch job
    • Replace a process level token
4. If not, add them explicitly.
5. Reboot the machine
Repair the SQL Server instance to test the issue again.
The following two blogs are for your references:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2012/08/20/error-while-deploying-ssis-2012-project-from-ssdt-to-ssis-catalog-system-componentmodel-win32exception-a-required-privilege-is-not-held-by-the-client.aspx
http://blog.oraylis.de/2013/09/fixing-sql-2012-ssis-deployment-error-6522-a-required-privilege-is-not-held-by-the-client/
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Similar Messages

  • SSIS 2012 package scheduling with SQL Server 2008 R2

    Hi, We have a ssis 2012 package with parameters & would like to schedule this package in SQL Server 2008 R2 agent. Is there a way to pass parameters to the ssis package from SQL Server 2008 R2 agent?
    Thanks in advance..........
    Ione

    You cant use SQL 2008 R2 to schedule it as dtexec 2008 cant execute package created using SSIS 2012. The inverse can be done though
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • SSIS 2012 package runs under SSDT but fails with permission error from SSMS

    I have a simple package that pulls data from a text file located on a Windows file server that runs successfully from SSDT on my client.
    However, when deployed and running the package via SSMS from the client, the package fails with a permission error, with the error stating that the data file could not be opened.
    I have done some investigation and have seen some info that states that a package run from SSMS runs under the account on which you are logged on to the machine, which I would have thought is correct. This is therefore the same account when running from
    SSDT (which works) and I can see from the SSIS Report that the 'Caller' is stated as my account, so if this is the case why isin't the package working.
    I've also seen an MSDN forum answer which stated the opposite that the package when run from the IS Catalog in SSMS doesn't run under the account on which the client is logged on with, which is the opposite of the above, but doesn't indicate which account
    it is using.
    So what account is being used to run SSIS 2012 packages from the IS catalog from within SSMS ?
    If it is the account on which you are logged onto the client running SSMS, why is it not working when the account has the necessary permissions (as provent when running from SSDT) ?

    I am aware it's using my account and not one of the service. There's nothing in the posts above which suggests I'm using the service account. I don't know why people keep assuming that I'm running the package from a job. I've never stated that in any of
    the posts I'm running the package from a job. It's been made quite clear I'm running the package from the IS Catalog on SSMS:
    "This is simply selecting a package from the IS Catalog, right-clicking and selecting Execute package.", as per the Nov 18 post, and in the original post "....So what account is being used to run SSIS 2012 packages from the IS catalog from
    within SSMS".
    Just to be clear, the package is NOT being run from a job. It's using the Execute package option when selecting the package within SSMS from the IS Catalog and it's running under the account on which I am logged on to my client.
    Please read carefully. I was just answering your question "So what account is being used to run SSIS 2012 packages from the IS catalog from within SSMS ?" and stating that you where right and that it uses your account to run the package
    when you execute a package manually from the Catalog and that you can prove that by logging the system variable.
    A good suggestion about using a share in the task to map the drive and I will try this. I would find it strange that SSMS requires this mapping whereas SSDT does not though.
    Ok let us know your findings. If it doesn't work you can also test it with a password and username:
    net use f: \\financial\public  yourpassword /user:username
    Please mark the post as answered if it answers your question | My SSIS Blog:
    http://microsoft-ssis.blogspot.com |
    Twitter

  • Weird question in SSIS 2012 package

    hi folks:
      I've created a SSIS 2012 package in my local machine using 
    Microsoft SQL Server Integration Services Designer
    Version 11.0.3436.0
    This package contains a script task using .NET framework 4 . 
    Everything works fine and I decided to deploy to the QA server.
    On the QA server, the package wont' work then I decided to open in the SSIS designer with the same version 11.0.3436.0
    This is when this weird things happens.  
    On the QA machine, when I opened this deployed pkg directly in SSIS designer and ran it, the pkg failed with the error pointing to the script task.  
      Then, I literally opened the script task and closed it WITHOUT changing anything .   
    After that, I ran the same package in SSIS designer... Guess what, it worked!!!
    Weird!  could anyone here help explain what just happened? this makes my deployment process a nightmare as I have to literally opened the script task after it gets deployed and change the pkg location as SSIS designer will save the "good"
    pkg in a different location other than deployed one.
    Thanks a lot!
     hui
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Hi cat_ca,
    According to your description, the first time you run the SSIS package in SSIS designer, the package failed with the error pointing to the script task, you opened and closed the script task and re-run the package, it worked fine.
    When we debug the SSIS package, the script component will be compiled to binary. In this case, the binary reverse failed due to some reason, so the script task is not normally build. To troubleshoot the problem, we can make use of logging feature to monitor
    execution of an SSIS package.
    For more information, please refer to the following documents:
    https://msdn.microsoft.com/en-us/library/ms136033(v=sql.110).aspx
    http://stackoverflow.com/questions/15004109/can-you-monitor-the-execution-of-an-ssis-package-in-bids-as-it-runs-on-the-ser
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    If you have any feedback on our support, please click
    here.
    Wendy Fu
    TechNet Community Support

  • How to upgrade ssis 2012 packages into ssis 2014

    we upgraded ssis 2012 packages into ssis 2014 but when i execute the packages its showing as validation mode .

    Hi harikiran2010,
    To upgrade packages that were created in earlier versions of Integration Services to the Integration Services format that SQL Server 2014 uses. SQL Server provides the SSIS Package Upgrade Wizard to help in this process. We can double-click the Integration
    Services project to open the project in SSIS 2014, Integration Services automatically opens the SSIS Package Upgrade Wizard, then select the desired packages to upgrade.
    As to the validation issue, I think the issue can be caused by the connection manager validate fails. We can test the connection by right-clicking the connection manager in the Connection Managers area of SSIS Designer and then clicking Test Connectivity.
    Another possibility is you are using some expressions to control some configurations, we can set all of the package and all of the connections to work offline when data sources are not available by
    enable Work Offline from the SSIS menu and set DelayValidation to True on package elements whose configuration is not valid at design time to prevent validation errors.
    References:
    Upgrade Integration Services Packages Using the SSIS Package Upgrade Wizard
    Troubleshooting Tools for Package Development
    If the issue is still existed, please provide us more information about the error message. Then we can make further analysis.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • How to deploy and execute SSIS 2012 packages when only SSDT is installed

    Hi, I am facing a weird situation where we did an upgrade for visual studio to vs 2102 on all the dev machines and as part of that moved to SSDT from BIDS but all the database is still SQL Server 2008 R2. Now I have a few SSIS 2012 packages which I cannot
    schedule & run because DTEXEC.exe is not compatible and I get all sorts of version & “Package Load error 0xC0010014 in CPackage::LoadFromXML” error even though I set it up in 32-bit mode and was trying to save it to msdb. I knew I will not be
    able to schedule this as a job in SQL Server Agent but even saving the package does not work.
    Thanks in advance............
    Ione

    I doubt 2012 ssis packages are backwards compatible with 2008r2. 2008r2 doesn't know anything about the project deployment model and i'm sure there's new tasks and connectors in 2012 so the package deployment model ssis packages won't work either.
    You will need a sql 2012 integration services service installed and running somewhere. You need this to execute your 2012 packages
    Jakub @ Adelaide, Australia Blog

  • How to provide project.params in ssis 2012?

    well i am studying ssis 2012 can i know what steps we have to take to create project parameters and to provide connection string,DB name in ssis project.

    Create a connection and promote to the project level by right-clicking on it:
    And this link explains with pictures how to add a parameter and make it project wide https://msdn.microsoft.com/en-us/library/hh213296.aspx
    Arthur
    MyBlog
    Twitter

  • I try to run a SSIS 2012 package a come with this error Exception has been thrown by the target of an invocation.

    Hi,,
    I making a package in SSIS 2012 that read a Excel file and copy the data into a Excel Destination , I did via Scrip Task using VB 2010 (Visual Studio 2010) the package stop with these error, I try to solve but I don't know, any clue ??
    Thanks
    I execute a SSIS package copy data from a Excel workbook to another using a VB scrip, it show with this error
    Exception has been thrown by the target of an invocation. Also appears this : at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
    RuntimeType typeOwner)   at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)   at System.Reflection.RuntimeMethodInfo.Invoke(Object
    obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
    culture)   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)   at Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTATaskScriptingEngine.ExecuteScript()
    An the package stop , I wan to know really what is happened?, any one please

    >Exception has been thrown by the target of an invocation
    In your script taks you need to "unwrap" this exception by examining its .InnerException.  An easy way is to catch TargetInocationException and re-throw its .InnerException.
    David
    David http://blogs.msdn.com/b/dbrowne/

  • Script Editor takes forever to load with SSIS 2012 packages in VS 2012 when you click on Edit Script... button

    Hi,
    I'm upgrading some SSIS Packages to the SQL 2012 Project deployment model. However, when I click on the Edit Script... button in a Script Editor Task, Visual Studio just sits there for minutes until it sometimes opens, sometimes doesn't. Surely this should
    open up pretty much instantaneously. Can anyone shed any light on why this is happening ?
    Thanks
    Dave Evans

    Hi Dave Evans,
    It might be due to permission issue, please try to uncheck "Check for publisher’s certificate revocation" under the "Security" group in "Advanced" tab in "Internet Options", please see:
    http://stackoverflow.com/questions/13540151/ssis-script-editor-loads-very-slow 
    Thanks,
    Eileen
    Eileen Zhao
    TechNet Community Support

  • How to run ssis 2012 package deployed on SSISDB using stored procedures from [SSISDB].[catalog] by regular AD accounts ?

    Hello, I need to run ssis package by stored proc(pass parameters inside and get result using stored procedures [SSISDB].[catalog].[create_execution]) etc. Do not suggest me to use SQL Agent here as this is not the case. or by pass this using configuration
    for SSIS, I need to know what permission I'm missing if those stored proc run by AD account, with rights described from BOL and I'm having "The current security
    context cannot be reverted. Please switch to the original database where 'Execute As' was called and try it again." If I schedule stored proc to run by Agent and specify parameters - will work, from remote PC - does not.  I have sysdamin
    rights on the server where SSIS and stored proc which is call it exists.   I was digging around and have ugly solution to make it working, I want to use elegant solution using those stored proc from [SSISDB].[catalog] ...
    Any help especially from Microsoft guys here...?
    Vladimir

    >>>>If I schedule stored proc to run by Agent and specify parameters - will work,
    from remote PC - does not. 
    Vova
    If you schedule the job it will be running under SQL Server Agent account security....  What error
    do you get when you run the SP from remote PC?
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • How can I use UC4 instead of SSIS Master Package deployed using project deployment model?

    Hi Folks,
    My team is planning to opt UC4 for scheduling the SQL Jobs and I have to come up with a plan to integrate it. 
    As of now, I do not have software licence in place to do some research. 
    If you have worked on it, can you tell me that how can I schedule SSIS packages using UC4. 
    Also, we are using SSIS project parameters (Project deployment Model). What kind of changes I have to make in SSIS packages to support UC4. Is it possible to pass parameters to SSIS package through UC4? If not, is there any alternativ?
    Appreciate your help!
    Gaurav Gupta

    If you have access to Automic Community, there are details there on how to execute SSIS 2012 packages deployed in SSISDB catalog (project deployment model). Here is the link:
    https://community.automic.com/discussion/4878/how-to-execute-sql-server-data-tools-ssdt-2012-package-synchronously-using-sql-job
    Leonard

  • SSIS 2012: What rights are needed to connect to SSDB via DMO

    I'm trying to connect to the SSDB catalog to execute a package using the .NET object model as per
    http://social.technet.microsoft.com/wiki/contents/articles/21978.execute-ssis-2012-package-with-parameters-via-net.aspx?CommentPosted=true#commentmessage
    The problem is if I do this with a normal user I get
       The server principal "XXXX"
    is not able to access the
    database \"SSISDB\" under the
    current security context.
    If I grant the user sysadmin rights it works, but the old Integration Services model of granting db_ssisadmin doesn't help
    Paul

    As far as I know db_ssisadmin is a msdb role so it wont work well with package access control for packages stored in IS Catalog. It will be relevant only in cases where package is stored in msdb.
    If you're using catalog (2012 deployment) you should be using ssis_Admin role which is what SSISDB provides you with for access control
    see
    http://blogs.msdn.com/b/mattm/archive/2012/03/20/ssis-catalog-access-control-tips.aspx
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

    Hi,
    This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
    Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
    So far I have installed
    http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
    I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
    2012 release.
    Here is the detail of error message:
    TITLE: Package Validation Error
    Package Validation Error
    ADDITIONAL INFORMATION:
    Error at Data Flow Task [Excel Source [2]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection
    Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
    Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
    Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
    Error at Data Flow Task: There were errors during task validation.
    Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "Unspecified error".
     (Microsoft.DataTransformationServices.VsIntegration)
    Here are my environment details:
    SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
    Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
    Services Project2\Integration Services Project2\Package.dtsx.
    Does this kind of Shared drives have any impact to give this issue?
    Thanks in advance!
    Ketan
    P.S.: I had look at this forum question -->
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

    Hi Arthur,
    Thanks for your response.
    Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
    1) Some times excel source files cannot be parsed by excel source connection manager.
    2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage  while destination mapping.
    3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file.  <-- For
    this we tried IMEX setting also
    4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
    I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
    As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
    Do you think it is advisable to convert Excel into CSV or Flat file.
    Thanks,
    Ketan

  • SSIS 2012 is intermittently failing with below "Invalid date format" while importing data from a source table into a Destination table with same exact schema.

    We migrated Packages from SSIS 2008 to 2012. The Package is working fine in all the environments except in one of our environment.
    SSIS 2012 is intermittently failing with below error while importing data from a source table into a Destination table with same exact schema.
    Error: 2014-01-28 15:52:05.19
       Code: 0x80004005
       Source: xxxxxxxx SSIS.Pipeline
       Description: Unspecified error
    End Error
    Error: 2014-01-28 15:52:05.19
       Code: 0xC0202009
       Source: Process xxxxxx Load TableName [48]
       Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Invalid date format".
    End Error
    Error: 2014-01-28 15:52:05.19
       Code: 0xC020901C
       Source: Process xxxxxxxx Load TableName [48]
       Description: There was an error with Load TableName.Inputs[OLE DB Destination Input].Columns[Updated] on Load TableName.Inputs[OLE DB Destination Input]. The column status returned was: "Conversion failed because the data value overflowed
    the specified type.".
    End Error
    But when we reorder the column in "Updated" in Destination table, the package is importing data successfully.
    This looks like bug to me, Any suggestion?

    Hi Mohideen,
    Based on my research, the issue might be related to one of the following factors:
    Memory pressure. Check there is a memory challenge when the issue occurs. In addition, if the package runs in 32-bit runtime on the specific server, use the 64-bit runtime instead.
    A known issue with SQL Native Client. As a workaround, use .NET data provider instead of SNAC.
    Hope this helps.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here
    Mike Yin
    TechNet Community Support

  • SSIS 2012 ETL is failing only at one server (No BIDS) but running successfully from BIDS on different sever . In this ETL, I have used Stored Procedure in OLEDB Source.

    Hi Guys,
    SSIS 2012 ETL is failing only at one server (No BIDS) but running successfully from BIDS on different sever . In this ETL, I have used Stored Procedure in OLEDB Source.
    Note: I have couple of ETLs developed in 2005 using same logic and upgraded to 2012, working perfectly.
    I am getting Error Message:
    SSIS
    Error Code
    DTS_E_OLEDBERROR. 
    An OLE DB
    error has occurred.
    Error code: 0x80004005.
    An
    OLE DB
    record is available. 
    Source: "Microsoft OLE DB Provider for SQL Server" 
    Hresult: 0x80004005 
    Description: "Error converting data type varchar to datetime.".
    Unable
    to retrieve
    column information
    from the data
    source. Make
    sure your target
    table in
    the database is
    available.
    "OLE DB Source"
    failed validation
    and returned
    validation status
    "VS_ISBROKEN".
    I tried below word around and found It is working perfectly.
    I loaded data into a table (dbo.TEMP) using Stored procedure and then I used this dbo.TEMP table in OLEDB source and then found no issue.
    MY SP Details: (This SP I am calling in OLEDB source of ETL) and when I run it from one server IT is working fine and when I run from ETL dedicated Server getting error:   Guys Help me out.
    USE
    [TEST_DB]
    GO
    SET
    ANSI_NULLS ON
    GO
    SET
    QUOTED_IDENTIFIER ON
    GO
    ALTER
    PROCEDURE  [DBO].[SP_TEST]
    --EXEC [DBO].[SP_TEST] '2014-09-30','2014-10-01'
    @FROMDATETIME
    DATETIME,
    @TODATETIME
    DATETIME
    AS
    SET
    NOCOUNT ON
    BEGIN
    DECLARE
    @FROMDATEKEY INT,
    @TODATEKEY INT,
    SET
    @FROMDATEKEY=
    CONVERT(VARCHAR(10),@FROMDATETIME,112)
    SET
    @TODATEKEY=
    CONVERT(VARCHAR(10),@TODATETIME,112)
    IF 1 = 1
    BEGIN
    SELECT
    CAST(NULL
    AS DATETIME) 
    AS TXN_DATE
    , CAST(NULL
    AS DATETIME
    ) AS PROCESS_DATE     
    , CAST(NULL
    AS money)
    AS  S1_AMT
    , CAST(NULL
    AS money)
    AS  S2_AMOUNT
    , CAST(NULL
    AS money)
    AS  S2_INVALID_AMOUNT
    , CAST(NULL
    AS money)
    AS  INVALID_MOVED_IN_VALID_S2_AMOUNT
    , CAST(NULL
    AS VARCHAR(20))
    AS SYSTEM_ID
    , CAST(NULL
    AS money)
    AS  S3_AMT
    END
    SELECT
    TXN_DATE
    ,PROCESS_DATE
    ,S1_AMT
    ,S2_AMOUNT
    ,S2_INVALID_AMOUNT
    ,INVALID_MOVED_IN_VALID_S2_AMOUNT
    ,SYSTEM_ID
    S3_AMT
    FROM
    DBO.TABLE_1
    WHERE TNX_DATE_KEY
    BETWEEN @FROMDATEKEY
    and @TODATEKEY
    UNION
    ALL
    SELECT
    TXN_DATE
    ,PROCESS_DATE
    ,S1_AMT
    ,S2_AMOUNT
    ,S2_INVALID_AMOUNT
    ,INVALID_MOVED_IN_VALID_S2_AMOUNT
    ,SYSTEM_ID
    S3_AMT
    FROM
    DBO.TABLE_2
    WHERE TNX_DATE_KEY
    BETWEEN @FROMDATEKEY
    and @TODATEKEY
    UNION
    ALL
    SELECT
    TXN_DATE
    ,PROCESS_DATE
    ,S1_AMT
    ,S2_AMOUNT
    ,S2_INVALID_AMOUNT
    ,INVALID_MOVED_IN_VALID_S2_AMOUNT
    ,SYSTEM_ID
    S3_AMT
    FROM
    DBO.TABLE_3
    WHERE TNX_DATE_KEY
    BETWEEN @FROMDATEKEY
    and @TODATEKEY
    END
    Data Source Mode: SQL Command for Variable
    "EXEC [DBO].[SP_TEST]  '"+ (DT_WSTR, 24) @[User::V_EXTRACT_FROM_DT]  +"','"+ (DT_WSTR, 24) @[User::V_EXTRACT_TO_DT]  +"'"
    Where variable @[User::V_EXTRACT_FROM_DT] and @[User::V_EXTRACT_TO_DT] is defined as DATETIME 
    Thanks Shiven:) If Answer is Helpful, Please Vote

    Hi,
    Yes you are right. At one sever where I was getting error, DateTime was in USA format and Where It was running successfully was in AUS format.
    I changed from USA to AUS and I did another changes:
    Data Source Mode: SQL
    Command
    EXEC  [DBO].[SP_TEST] 
    @FROMDATETIME = ?,
    @TODATETIME = ?
    and It is working fine.
    Thanks Shiven:) If Answer is Helpful, Please Vote

Maybe you are looking for