SSIS DQS Cleansing Error

Hello,
I have defined a knowledge base with a set of domain cleansing rules on Server A. When I try to access the rules through the DQS Cleansing processor in SQL Server Integration Services on Server B I get the following error:
[DQS Cleansing [2]] Error: System.MissingMethodException: Method not found: 'Void Microsoft.Ssdqs.Component.Common.Utilities.ComponentUtility.FireError(Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData100, System.String, Microsoft.Ssdqs.Component.Common.Messages.ComponentMessage,
System.Object[])'.
   at Microsoft.Ssdqs.Component.DataCorrection.Logic.DataCorrectionComponent.Validate()
   at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostValidate(IDTSManagedComponentWrapper100 wrapper)
[SSIS.Pipeline] Error: DQS Cleansing failed validation and returned error code 0x80131513.
Any help would be greatly appreciated.
Thanks!

John,
  Check the data types between the two. Ensure that the data type in the DQS domain is also the same type as the type coming from your SQL table.

Similar Messages

  • [DQS Cleanse] Error

    All,
          I'm trying to cleanse data and I'm continually getting the error message below.  I'm cleansing data such as first and last name, state and country.  I have been able to process nearly 500,000 but now for some reason
    I'm getting the error below.  Is there a way to determine the actual object that is getting a nullreference exception?
    [DQS Cleanse] Error: An unexpected error occurred in the DQS infrastructure.
    System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Ssdqs.Component.DataCorrection.Logic.DataCorrectionComponent.ProcessChunk(ReadOnlyCollection`1 fieldMappings,
     ReadOnlyCollection`1 records,
     CorrectedRecordsStatusStatistics& correctedRecordsTotalStatusStatistics)
    [DQS Cleanse [376]] Error: Microsoft.Ssdqs.Infra.Exceptions.EntryPointException:
    The attempt to update or delete a DAO object of type 'AKnowledgebase' with id 1000200
    has failed because the object is not up to date or is being deleted from the database.
       at Microsoft.Ssdqs.Proxy.Database.DBAccessClient.Exec()
       at Microsoft.Ssdqs.Proxy.EntryPoint.KnowledgebaseManagementEntryPointClient.DQProjectDelete(DQProject dqProject)
       at Microsoft.Ssdqs.Component.DataCorrection.Logic.DataCorrectionComponent.ProcessInput(Int32 inputID, PipelineBuffer buffer)
       at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper,
     Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket)
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. 
    The ProcessInput method on component "DQS Cleanse" (376)
    failed with error code 0x80131500 while processing input "DQS Cleansing Input" (389).
    The identified component returned an error from the ProcessInput method.
    The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. 
    There may be error messages posted before this with more information about the failure.
    Thanks for any help.

    We haven't heard of it in support. Do you run multiple Dataflows that do cleansing, or just one at a time?
    The failure is happening when deleting the project out of the DQS_PROJECTS (DQProjectDelete)
    Project names for SSIS projects are very long text. I think its like
    -Cleanse.DQS- Cleanse_<date>_<guid>_<guid>
    Maybe its failing there for some reason. Try to shorten the name of the cleansing component in the SSIS Dataflow (rename the Data Cleansing component's name) to something like DQS and nothing longer. We know of one issue with long names in SSIS components.
    To investigate further,
    1. I would run a profiler trace. Looks like its trying to make an update to the table A_Knowledgebase in DQS_MAIN database.
    Get events like
    All Error & Warnings category
    RPC:Starting/Completed
    SP:StmtStarting/StmtCompleted
    TSQL:BatchStarting/Completed
    TSQL:StmtStarting/StmtCompleted
    2. Also check the DQS logs and SQL Errorlogs in case there is any bigger failure going on.
    C:\Program Files\Microsoft SQL Server\MSSQL11.<instance>\MSSQL\Log\ERRORLOG
    C:\Program Files\Microsoft SQL Server\MSSQL11.<instance>\MSSQL\Log\DQServerLog.DQS_MAIN.log
    You can raise the logging level to Debug on the configuration tab of the Data Quality client and it will log the full context of the error. Turn the logging back to normal once you get the error once.
    Thanks, Jason
    Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

  • Unable to access the failure reason inside an SSIS flow, when using DQS Composite domains as part of an SSIS DQS Ceansing step.

    Hi,
    I have followed the  discussions in the (now closed) post titled:
    "Composite Domains in SSIS with spaces in the field"
    re. how best to approach composite DQS domains when inside a SSIS flow.
    I followed the approach recommended i.e.
    " If
    you map (in SSIS) your 2 individual source fields to both the (DQS) domains in your (DQS)Composite Domain, your composite domain automatically participates in the cleansing activity."
    In the example I have, there would be a number of different validation rules  , similiar
    to the rules in that post which were called 'Circle', 'Square', etc.,, associated with the Shapes&Sides CD.
    What I haven't figured out , is how to know from the output of the (SSIS) DQS Cleansing step when I get an
    Invalid result
    - which precise DQS rule (e.g.'Circle', 'Square'..etc) actually failed. ?
    So for an input row (if we take the example from that post)  with a 'Shapes' value of 'Square', and a
    'Sides' value of '3', I would like to get 'Failed Square' (Square being the DQS rule name) as the reason for failure, and to be able to see that from inside SSIS.
    If I use the derived column approach (as discussed at the start of the above discussions) I am able to get
    this type of output by using the '...._Reason' DQS output corresponding to the derived column .
    However I can't use the latter approach because of the issues with the derived column already highlighted
    in that post.
    I am also able to get the failed rule displayed when working fully inside the DQS client (no derived columns
    of course, just working with the DQS Composite Domains).                                                          
    However , as I say, I don't seem to be able to find out how to get it (the failed rule) when I map the individual
    cols separately to the individual domains.                           
    I do get an SSIS overall 'Record Status' = 'Invalid' but I dont know which rule failed. 
    I hope I am missing something, as otherwise I don't see how a user is going to figure out why the record is
    'Invalid', given that there would typically be multiple rules, any one of which could be causing the record's 'Invalid' status.   
    Any help would be much appreciated.
    Thanks,
    Martin

    I raised a similar question on the DQS forum. My domain (not a composite) was failing a rule but I didn't know which. I looked a bit further and was able to answer my own question. I've pasted my answer below. Hope it helps.
    The SSIS DQS component does specify the domain rule that caused a failure in the 'reason' output column from the DQS SSIS component. It was my mistake.
    I added a domain and added 2 domain rules. My source data in my SSIS process failed one of these rules. However, my source data value was already in the Domain Values list in DQS, and so when I ran the SSIS process, it highlighted the fact that my SSIS source
    data was an existing domain value but that domain value was invalid as it failed domain rules, hence the 'domain' value in the DQS SSIS component output column.
    I removed the value from the Domain Values in DQS, re-ran my package and this time my 'new' value failed but in the SSIS 'Reason' output column from the DQS SSIS component, it told me the rule that it failed on.
    One thing to note. If it fails more than 1 rule, the SSIS 'reason' output column concatenates the rule names together.
    So, for example, I had a domain with 3 rules. Length>2, Length>9 and Length>10. My new value was 3 characters in length and so it passed the first rule but failed the next two. The SSIS reason column had a value of 'Failed rule: 'Length >9 Length
    >10'.

  • SSIS(2010) DQS cleansing component

    Hi,
    I am new to SSIS and i want to know the exact usage of DQS cleansing component. On setting the domain rule, the records in the table is segregated as invalid,error,correct like this. Instead of using this component i can use the conditional split to check
    the values directly in the table and based on result i can do necessary changes for each condition. So i just want to know why to use DQS cleansing component.Please help me in this.  Thanks in advance..

    DQS will provide you with much more comprehensive cleansing solution. Here you may create a Knowledge Discovery project which can have multiple domains which can be used as nasis for your cleansing. It also has ability to specify additional business
    rules and you can set threhold based on whether you want particular output to be segregated as Suggested, Invalid etc. You also have flexibility of using a cloud based online data service to use as source repository for your domain to be cleansing against
    it.
    You cant achieve same level of flexibility using a simple conditional split. But for small subset of values you may still proceed with this. But for extensive clensing operations like Address Cleansing etc you've to go for components like DQS cleansing or
    use third party addins like Melissa data cleansing components.
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Example of generating excel dynamically in ssis? geting error [Excel Destination [190]] Error: Opening a rowset for "Excel_Destination$" failed. Check that the object exists in the database.

    example of generating excel dynamically in ssis? geting error [Excel Destination [190]] Error: Opening a rowset for "Excel_Destination$" failed. Check that the object exists in the database.

    Hi Vijay
    Can you be little bit more specific, did you receive this error when you are designing this pacakge using BIDS
    Becuase when you are designing this pacakge in BIDS, you need to manaually create a excel sheet manually for the first time you run,
    are you creating excel sheet using execute sql task and excel connection with input from a variable?
    Did you receive this error in validation phase or execution phase ?
    Can you share your query to create table in excel ?
    http://sqljunkieshare.com/2012/02/28/how-to-create-and-map-excel-destination-dynamically-in-ssis/
    Use the above post

  • SSIS 2008 R2 Error Handling

    Greetings!
    I have a Parent Package that calls several child packages that must be executed in sequence:
    Parent Package A calls Child1, Child2, Child3.  Each Child package has a precedence constraint of on success.
    My goal is to have the parent package stop executing if any one of the child packages fail, as well as send me an email with the error message.  I know that the Event Handler OnError will handle the send mail task, however because we are "Handling"
    the error,  the parent package will continue to execute. 
    Is there a way to send the email and fail the package in the event handler, or is it better to just create the send mail tasks for each child package using the ON FAILURE precedence constraint?

    Hi Val01,
    As Harry said, the failure of any child package will cause the parent package to fail by default. If it behaviors different in your package, it seems that you have made some modifications to the default settings. For example, the ForExecutionResult property
    of a child package may be forced to Success, the System::Propagate variable of a container has been set to False. To email the error message, you can add a Send Mail Task for an OnError event handler for specific executable, and use System::ErrorDescription
    variable and so on in the MessageSource property of the Send Mail Task to display the custom message.
    For more information, please see:
    http://sqlblog.com/blogs/rushabh_mehta/archive/2008/04/24/gracefully-handing-task-error-in-ssis-package.aspx 
    http://bisherryli.com/2010/11/04/ssis-using-system-variables-in-send-mail-task/ 
    Regards,
    Mike Yin
    TechNet Community Support

  • SSIS Package execution error from powershell

    Hi I have written a powershell script to exec SSIS packages. I am passing variable values at runtime by reading it from a text file.
    But it throws an error.
    Here is my script.
    #Read Data from Parameter File
    $variable=Get-Content D:\Batch\Bin\ETLParameters.txt
    $variable.GetType()
     $dest_conn_str=$variable[1]
     $mail_cc=$variable[2]
     $mail_from=$variable[3]
     $mail_str=$variable[4]
     $mail_to=$variable[5]
     $pkg_path=$variable[6]
     $ps_exe_path=$variable[7]
     $ps_script_cmd=$variable[8]
     $ps_script_path=$variable[9]
     $src_conn_str=$variable[10]
     $src_sys_id=$variable[11]
    #Executing SSIS packages from command prompt
    $cmd = 'dtexec /f "' + $pkg_path + 'pkg_ntas_all.dtsx' + '"' + ' /SET \Package.Variables[User::src_conn_str].Properties[Value];"' + $src_conn_str + '"' + ' /SET \Package.Variables[User::dest_conn_str].Properties[Value];"'
    + $dest_conn_str + '"' + ' /SET \Package.Variables[User::src_sys_id].Properties[Value];"' + $src_sys_id + '"' + ' /SET \Package.Variables[User::pkg_file_path].Properties[Value];"' + $pkg_path + '"' +
    ' /SET \Package.Variables[User::mail_str].Properties[Value];"' + $mail_str + '"' + ' /SET \Package.Variables[User::mail_from].Properties[Value];"' + $mail_from + '"' + ' /SET \Package.Variables[User::mail_to].Properties[Value];"'
    + $mail_to + '"'+ ' /SET \Package.Variables[User::mail_cc].Properties[Value];"' + $mail_cc + '"' + ' /SET \Package.Variables[User::ps_exe_path].Properties[Value];"' + $ps_exe_path + '"' + ' /SET
    \Package.Variables[User::ps_script_path].Properties[Value];"' + $ps_script_path + '"' + ' /SET \Package.Variables[User::ps_script_cmd].Properties[Value];"' + $ps_script_cmd + '"'  
    $cmd
    DECLARE @returncode int
    EXEC @returncode = xp_cmdshell @cmd
    Types of error that I get -
    If I run the $cmd directly. Which is the concatenated string of dtexec command with parameters. It doesn't do anything, not even an error and the pwoershell execution just completes.
    If I use exec EXEC @returncode = xp_cmdshell @cmd    ----- Then it throws me the error that the exec is not recognized name of cmdlet.
    Please help as I a noob in any kind of scripting.

    I did but it just printed the entire string on the command line and assigned all the values.
    PS C:\Users\dev_setup> . D:\Batch\Bin\runETL.ps1
    IsPublic IsSerial Name                                     BaseType
    True     True     Object[]                                
    System.Array
    dtexec /f "D:\ETL\test\test\test_ETL\pkg_all.dtsx" /SET "\Package.
    Variables[User::src_conn_str].Properties[Value]";"Data Source=SOURCE1;Initial Catalog=tagtest;Provider=SAOLEDB.11;Integrated Security=SSPI;
    " /SET "\Package.Variables[User::dest_conn_str].Properties[Value]";"destinationDb;User ID=FP_DEV;Password=**********;Initial Catalog=xyz;Provider=SQLOLEDB.1;Persist Security Info=True;Auto Translate=False;Packet Size=10240;" /SET " \Package.Variables[User::src_sys_id].Properties[Value]
    ";"100200" /SET "\Package.Variables[User::pkg_file_path].Properties[Value]";"D:\ETL\test\test\test_ETL\" /SET "\Package.Variables[User::mail_str].Properties[Value]";"SmtpServer=mailhost.test.com;UseWindowsAuthentication=False;EnableSsl=False;" /SET "\Package.Variables[User::mail_from].Properties[Value]
    ";"[email protected]" /SET "\Package.Variables[User::mail_to].Properties[Value]";"[email protected]" /SET "\Package.Variables[User::mail_cc].Properties[Value]";"[email protected]" /SET "\Package.Variables[User::ps_exe_path].Properties[Value]";"C:\Windows\System32\WindowsPower
    Shell\v1.0\PowerShell.exe" /SET "\Package.Variables[User::ps_script_path].Properties[Value]";"D:\ETL\Powershell_Script\" /SET "\Package.Variables[User::ps_script_cmd].Properties[Value]";"create_historical_reject_file.ps1 -input_variable"
    PS C:\Users\svc_sp_fp_dev_setup>
    But when I just run it without passing the parameters it runs. What might be the issue.

  • How to select special character from OLE DB source in SSIS?- Truncation error.

    Hi,
    I have to pull data from one Oracle table and for that I am using OLE DB source in SSIS. In OLE DB source I write query like, 
    SELECT     DESCRIPTION
    FROM         INV.ITEMS_LOCATION
    and packages failed with truncation error. When I redirect this column for truncation I see below result in data viewer,
    ErrorCode
    ErrorColumn
    DESCRIPTION
    ErrorCode - Description
    -1071607693
    8884
    HC Afd Set__ZDV?N07-03075
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel 4DO1-?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel 3DO3-?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel 4DP01-?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel DBDS-10-?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Filter TXW?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__ZDV?N07-03075
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel 4DO1-?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel 3DO3-?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel 4DP01-?
    The data was truncated.  
    -1071607693
    8884
    HC Afd Set__Ventiel DBDS-10-?
    The data was truncated.  
    I don't how to put this value in table. I use code page 65001(UTF-8) and 1252, but it is not working, and giving error like 
    [OLE DB Source [16]] Error: Column "DESCRIPTION" cannot convert between unicode and non-unicode string data types.
    Data Type of 'DESCRIPTION' source(External) column is varchar(240) and same- varchar(240) I used for output column and in my table's data type. I also tried with varchar(1000) for output column in OLE DB Source but same truncation error.
    I also tried to convert DESCRIPTION into navachar using below cast function but got error.
    SELECT   -- TO_NVARCHAR(DESCRIPTION) AS DESCRIPTION,
    --CAST(DESCRIPTION AS NVARCHAR(240)) DESCRIPTION, 
    Please let me know how to load this value in table. Thank you in advance.
    Vicky

    Thanks ArthurZ for reply.
    But for testing I am just using OLEDB source and OLE DB destination only in my ssis package.
    For Column "DESCRIPTION", data type is VARCHAR(240)
    in external column, output column and target table column.
    And I tried to cast source column into nvarchar and also set target column to nvarchar to handle this kind of special characters but package is failing,
    I also tried TO_NCHAR(DESCRIPTION)
    in my source query to convert it to nvarchar but error is something like character mismatch.
    Vicky

  • Data Services Address Cleansing Errors

    Hello all,
    Having trouble getting a US Data Cleansing transform to work.  It's throwing a few errors:
    1.  At least 1 RETAIN_POSTCODE_IF_VALID_FORMAT option must be present in this group
    2.  At least 1 DUAL_ADDRES option must be present in this group
    3.  At least 1 DISABLE_CERTIFICATION options must be present in this group
    4.  At least 1 REPORT_OPTION must be present in this group.
    I'm new to BoBJ DS and I've tried playing around with different options in the transform but can't get these errors to go away, any thoughts as to what could be causing this?  I'm sure it's probably something really simple.

    Hi Guys,
    This problem can usually be remedied by importing the base URAC.atl file:
    1. In Designer, right-click in the Local Object Library
    2. Select Repository > Import From File
    3. Browse to LINK_DIR\Admin\Repo and select the transform to be re-imported (e.g. urac.atl)
    4. Click Open
    5. Select Yes and OK
    If you need to import an .atl from an older version, see the following KB article:
    https://bosap-support.wdf.sap.corp/sap/support/notes/1431746
    Thanks,
    Brandon Jacobson

  • SSIS Package Validation Error

    I receive the error 'Error at Extract Data From Access Table [SSIS Pipelin]: The "runtime conneciton "OleDbConnection" does not have a vlue for the ID property"
    What is causing this to occur and what can I do to rectify it?  All my fields in my Source Table as well as my Destination Table are mapped to one another?

    Are you trying to programmatically create a package?
    if yes see
    http://copydatabasedd.blogspot.in/2012/03/how-to-create-ssis-package-correctly-by.html
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs
    I am trying to create the package using Visual Studio.
    EDIT-
    My project builds okay but when I attempt to run it, that is where it throws the error.
    I am going from Ole DB Source (Access) to a Data Conversion to a Ole DB Destination (SQL Server)
    And it is throwing the above error.

  • How can I troubleshoot an SSIS package with errors ?

    I am testing a package which is a straightforward move from Oracle table-A  to Oracle table-B 
    I have the header and table tables working fine, but the detail table is getting an error, with the errors not being helpful at all. The detail data flow has around 300+ columns, but the error doesn't say anything that points to the specific error. I
    did review the warnings and found two columns that I needed to substring to be able to fit into the destination.  But still getting an error.
    A colleague said the error "The "input "OLE DB Destination Input" (4781)"
     means this is for Column 4781 - but how do I find that ? We looked in Advanced Settings but the column ID's are all above 5000.
    So how do I troubleshoot this ? In SSIS, I can only think to un-map 1/2 the columns, see if that works, then narrow it down from  there.  I can try to replicate the insert statement in Oracle but that's crazy, imo.
    Here are the errors:
    Error: 0xC0202009 at Load Detail Data, Caremark CET Claims Destination [4768]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x00040EDA.
    An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x00040EDA Description: "Multiple-step operation completed with one or more errors. Check each status value.".
    Error: 0xC0209029 at Load Detail Data, Caremark CET Claims Destination [4768]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (4781)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (4781)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.
    Error: 0xC0047022 at Load Detail Data, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Caremark CET Claims Destination" (4768) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (4781). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
    Error: 0xC02020C4 at Load Detail Data, Argus PCT Claiims Source [5281]: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
    Error: 0xC0047038 at Load Detail Data, SSIS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Argus PCT Claiims Source" (5281) returned error code 0xC02020C4. 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.

    I figured out the error outside of SSIS, by trying to insert the data directly in Oracle ("insert into [my_dest_table select * from [my_source_table"), and that showed me the error (trying to insert varchar-2 into varchar-1). so I corrected and got my package
    working.
    Basic takeaway is the error messages don't tell you anything. It seems like the Oracle error would be readable by Sql Server/SSIS and so it would write that in the log.
    So I basically did your "1>" suggestion and that worked.
    I would like to do "3>" but don't know how . . . if you can point me in the right direction I could probably figure it out, I have a couple of books and I have colleagues whom I can ask.
    thanks !

  • SSIS transaction handling error

    Hello All,
    I have set transaction in control flow but if you look at below screen shot this package is keep running forever i don't know what wrong in it and it don't even have huge data record coming in from source table has only 300 records
    NOTE: I cant use in build transaction which is in SSIS like supported , Required and unsupported since I am having DTC transaction error and i cant those properties on server so I have only below option
    for data flow details find below screen shot

    Check all logs/event viewer for related messages:
    http://social.msdn.microsoft.com/Forums/en-US/ee4ebd62-2a87-4edf-892f-93a885451d7e/location-of-sql-server-error-log-and-windows-event-log?forum=sqltools
    SSIS progress display:
    http://stackoverflow.com/questions/1475107/measuring-progress-of-ssis-data-flow
    Kalman Toth Database & OLAP Architect
    SELECT Video Tutorials 4 Hours
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • SSIS Job creating error message.

    Hi All,
    I have a ssis job which is already running in production and our client has created a same job in the new server for our testing purposes. which is pointing to the correct config file in the new server and file paths are mentioned in the table for picking
    the files, till now I don't have any issue it is performing as expected. but when you go to the job history and see it is saying the message similar to the below. but the path which I am getting in the below message is not in the config or the table defined
    for the respective table to pick, but I observed on this thing that path is it is in the package at one of the tasks but that path is  replaced while the package is running(I kept break points in the package for debug purpose and checked). but still
    I am getting this message.... any thoughts guys
    Message
    Executed as user: URBANLSB\svc_TSsisProxy. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4000.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  10:43:59 AM  Error:
    2014-10-02 10:44:03.23     Code: 0xC001401E     Source: FedexFeed Connection manager "FedexFeedExceptionFile"     Description: The file name "\\Database Uploads\Test\FedexFeed\FedexFeedException\\FedexFeedErrorRecords_10022014_104400.txt"
    specified in the connection was not valid.  End Error  Error: 2014-10-02 10:44:03.24     Code: 0xC001401E     Source: FedexFeed Connection manager "FedexFeedExceptionFile"    
    Description: The file name "\\Database Uploads\Test\FedexFeed\FedexFeedException\\FedexFeedErrorRecords_10022014_104400.txt" specified in the connection was not valid.  End Error  Error: 2014-10-02
    10:44:03.25     Code: 0xC001401E     Source: FedexFeed Connection manager "FedexFeedExceptionFile"     Description: The file name "\\Database
    Uploads\Test\FedexFeed\FedexFeedException\\FedexFeedErrorRecords_10022014_104400.txt" specified in the connection was not valid.  End Error  DTExec: The package execution returned DTSER_SUCCESS (0).  Started:  10:43:59 AM  Finished:
    10:44:38 AM  Elapsed:  39.109 seconds.  The package executed successfully.  The step succeeded.

    \\Database Uploads\Test\FedexFeed\FedexFeedException\\FedexFeedErrorRecords_10022014_104400.txt
    since the '\\Database Uploads' part has a space it breaks the package
    Adding double quotes around fixes the issue.
    Arthur
    MyBlog
    Twitter

  • SSIS fails with error : The process exit code was -1073741701

    Hello All,
    I am having issues with SSIS packages running from SQL agent job.
    The server we are running the job is used for SSIS and there are lot of other SSIS jobs that are running.
    We were able to run the job once successfully and the later runs are failing with the below error.(nothing has been changed) 
    The step did not generate any output.  The return value was unknown.  The process exit code was -1073741701.  The step failed.
    Nothing is being logged in the [catalog].[operations] or operation_messages view. When tuned the profiler ON we do not see the job trying to connect to SSISDB at all. I am assuming that the job is failing much before if does any thing.
    I have moved the package to a different server and ran it with the same proxy account and it works fine there.
    Any help or suggestion on this issue would be helpful.
    Thanks !

    Hi SQL_Help,
    You can run the job once successfully and the later runs are failing with the below error ran it as a Job. “The step did not generate any output.  The return value was unknown.  The process exit code was -1073741701.  The step failed.” It
    was really a generic error message with no information with it.
    We can use Process Monitor and Event Viewer to capture the detail error message. Then based on the error message to fix this issue.  The following similar issue is for your reference:
    http://blogs.msdn.com/b/dataaccesstechnologies/archive/2014/05/22/ssis-package-fails-with-error-the-step-did-not-generate-any-output-the-return-value-was-unknown.aspx
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • SSIS New Project Error in VS 2012

    Hello,
    When I start a new SSIS project in VS Ultimate 2012, I received the error message below. 
    VS Version: 11.0.61030.00 Update 4
    SSIS Designer Version: 11.0.3360.12

    It must fall into
    FIX: You can’t create or open SSIS projects or maintenance plans after you apply Cumulative Update 3 for SQL Server 2012 SP1
    http://support.microsoft.com/kb/2832017
    Arthur My Blog

Maybe you are looking for

  • Regarding Creation of  specific  Application scenario..

    Hii All, I am having a requirement where i have to create a application in which in FIRST view i m having a dropdown menu,from where i have select one parameter from dropdown menu, say for example there is list of countries in a drop down menu.when i

  • What's the best for green screen filter  Color Key or Chroma key?

    What is the difference, and what is the best choice for a person standing in front of a green screen. Color Key or Choma key? Which offers the most solutions for dealing with variations in the green background, such as occasional wrinkles/seams in th

  • I turned on magnifier on my 4S and can't shut it off.

    I can't even sign in because the magnification is too large to see where I am. I shut off the phone and restarted but nothing changed. I used one of the Tips to turn on the magnifier just to see how it works and now I'm stuck I have installed the lat

  • Regarding ZDATA Path on App' Server

    hi , i try with ans' posted for this topic but it is not useful..cause. i will tell my scenario clearly... i have selection-sceen..in that s.s 1 radio button called display delta file..ok select this radio button and after press execute button our co

  • Error When Open Pdf

    Hi all, every time I open a pdf file shows this message: error occurred in the application at location unknown software exception 0x00416ba6 Details: windows xp, adobe reader xi