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

Similar Messages

Execute Process Task - Error :The process exit code was "2" while the expected was "0".

I am designing a utility which will keep two similar databases in sync. In other words, copying the new data from db1 to db2 and updating the old data from db1 to db2.
For this I am making use of the 'Tablediff' utility which when provided with server name, database, table info will generate .sql file which can be used to keep the target table in sync with the source table.
I am using the Execute Process Task and the process parameters I am providing are:
WorkingDirectory : C:\Program Files (x86)\Microsoft SQL Server\90\COM
Executable :      C:\SQL_bat_Files\SQL5\TC_CTI\customer.bat
The customer.bat file will have the following code:
tablediff -sourceserver "LV-SQL5" -sourcedatabase "TC_CTI" -sourcetable "CUSTOMER_1" -destinationserver "LV-SQL2" -destinationdatabase "TC_CTI" -destinationtable "CUSTOMER" -f "c:\SQL_bat_Files\sql5\TC_CTI\sql_files\customer1"
the .sql file will be generated at:  C:\SQL_bat_Files\sql5\TC_CTI\sql_files\customer1.
The Problem:
The Execute Process Task is working fine, ie., the tables are being compared correctly and the .SQL file is being generated as desired. But the task as such is reporting faliure with the following error :
[Execute Process Task] Error: In Executing "C:\SQL_bat_Files\SQL5\TC_CTI\package_occurrence.bat" "" at "C:\Program Files (x86)\Microsoft SQL Server\90\COM", The process exit code was "2" while the expected was "0". ]
Some of you may suggest to just set the ForceExecutionResult = Success (infact this is what I am doing now just to get the program working), but, this is not what I desire.
Can anyone help ?

Jwelch,
Thanks for the input,
"Change the SuccessValue property of the Execute Process task from 0 to 2 (which means that you will get a failure if there are no differences, since TableDiff returns 0 in that case)."
           -- Not possible b'coz if there is no difference in the tables, which is also a possiblility, the job will fail.
"FailTaskIfReturnCodeIsNotSuccessValue to FALSE (which means it won't fail regardless of the code returned)."
          -- Does this mean the job will never fail? Lets say the target table doesnt exist, then, by setting "FailTaskIfReturnCodeIsNotSuccessValue to FALSE " will the job fail? I guess my question is, how is what you've suggested different from setting "ForceExecutionResult = Success". Both the cases will show the task status "Success" even if there is an error.
Is there a way to keep the property of job 'Failure' if there is any generic errors like target table not found or say, the path given for .sql file output is not valid etc.
Thanks again,
Little_Birdie.

SQL 2012 - SSIS Error -The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.

Hi guys
Trying to run this package on SQL 2012 agent and getting below error . No more details I could find so far.
The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
About Package - Its connecting to different version (2000,2005,2008,2008R2,2012) servers and putting Jobs information into one Database table.
Any workaround or fix ?
Thanks
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

New package or one that used to work? Connecting how? How does it poll?
On the surface it is an error from a memory space of the binary/non-managed code, so nothing can be really concluded based on what you decided to share with us.
Arthur My Blog
So Same package is working fine from my local machine which has SQL 2008 R2 and SQL 2012 installed. I am trying to push the package on server which has sql server 2012 Installed .
I don't see any error .
I ran package manually from server using SQL Data tools and ran successfully...
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Job scheduling error : The return value was unknown. The process exit code was -1073741819. The step failed.

I am working in Sqlserver 2008 R2, SSIS 64 bit version
I am getting the below error while scheduling the job in the development server Database.
The return value was unknown. The process exit code was -1073741819. The step failed.
The SSIS front end execution runs fine.
Have anyone faced this issue before?

Hi Venkat,
If you already changed to 64bit and still doesn't work then create proxy account..
To create a proxy account
In Object Explorer, expand a server.
Expand SQL Server Agent.
Right-click Proxies and select New Proxy.
On the General page of the New Proxy Account dialog, specify the proxy name, credential name, and
description for the new proxy. Note that you must create a credential first before you create a proxy if one is not already available. For more information about creating a credential, see How
to: Create a Credential (SQL Server Management Studio) or CREATE CREDENTIAL (Transact-SQL).
Check the appropriate subsystem for this proxy.
On the Principals page, add or remove logins or roles to grant or remove access to the proxy account.
Thanks

Ssis execute process task error: process exit code was 1 while the expected was 0

Hi Sir,
in my SSIS Package(2012) i am using Execute Process Task which will call bat file. bat file is located on UNC Path.i am having the below script in the batch file.
del \\servername\foldername\name.txt
rcmd \\servername D:\name1.bat
del \\servername\foldername\name2.txt
xcopy \\servername\foldername\file.txt \\server\foldername\outfilefolder
i am getting the below error message:
ssis execute process task error: process exit code was 1 while the expected was 0
i want know at what cases error exit code was 1?
Thanks for your time.

Hi prasad.alm,
The error is generic and can be caused by various factors. Here are some suggestions for your reference:
Manually run the executable to execute the batch file so that we can check whether the command lines in the batch file are correct or not.
Check there are no duplicate/existing files in the destination folder.
Try to run the package in 32-bit or 64-bit runtime mode.
If the issue occurs when running a job, try to create a CmdExec type job step to call the excutable. If this job also fails, it might be an issue between executable and SQL Server Agent rather than the SSIS package itself.
If the issue persists, enable logging for the package, and check if we can obtain more detailed error message for further analysis.
Regards,
Mike Yin
TechNet Community Support

Windows.Launch contract failed with error: The app didn't start..

We have installed windows 8 Prof X64 Edition; none of the Metro apps are not getting launched; the system is added in domain, the event viewer has the below information for one of the app.
Event Under: Applications
App microsoft.windowscommunicationsapps_8wekyb3d8bbwe!Microsoft.WindowsLive.Chat did not launch within its allotted time.
Event Under: AppHost
The App Host has encountered an unexpected error and will terminate. The error is 0x8007000E.
Event Under: Microsoft-Windows-TWinUI/Operational
Activation of the app microsoft.windowscommunicationsapps_8wekyb3d8bbwe!Microsoft.WindowsLive.Chat for the Windows.Launch contract failed with error: The app didn't start..
Regards Ajinkya Ghare MCITP-Server Administrator | MCTS

Hi,
Try to put a machine disjoin the domain to see if the same issue occurs.
Sometimes the Windows 8 machines cannot use metro app once join the domain, you can try this method:
1- Open "Local Group Policy Editor"
2-Navigate to "Computer Configuration - Administrative Templates - Network Isolation"
3- Open "Internet Proxy Servers for Metro Style Apps" and set the value to your proxy server address like 172.16.0.1:8080.
Regards,
Leo
Huang
Leo Huang
TechNet Community Support

In perfdatasource querying for global snapshot failed with error 'the size limit for this '

I received scom alerts from two win 2k8 r2 servers , hosting exchange 2010 mailbox roles , the alerts came almost in same time from both servers ,
can I ignore those alerts
or can someone give a me a clue how can I troubleshoot those alert , please any help would be appreciated
In PerfDataSource, querying for Global Snapshot failed with error 'The size limit for this '
from Ops-mgmt logs
Log Name: Operations Manager
Source: Health Service Modules
Date:
Event ID: 10104
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: server 1
Description:
In PerfDataSource, querying for Global Snapshot failed with error 'The size limit for this '
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2008.OperatingSystem.PercentMemoryUsed.Collection
Instance name: Microsoft Windows Server 2008 R2 Enterprise
Log Name: Operations Manager
Source: Health Service Modules
Date:
Event ID: 10104
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: server 1
Description:
In PerfDataSource, querying for Global Snapshot failed with error 'The size limit for this '
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2008.LogicalDisk.PercentIdle.Collection
Instance name: " edb file path "
Log Name: Operations Manager
Source: Health Service Modules
Date:
Event ID: 10104
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: server 2
Description:
In PerfDataSource, querying for Global Snapshot failed with error 'The size limit for this '
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2008.NetworkAdapter.CurrentBandwidth.Collection
Log Name: Operations Manager
Source: Health Service Modules
Date:
Event ID: 10104
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: server 2
Description:
In PerfDataSource, querying for Global Snapshot failed with error 'The size limit for this '
One or more workflows were affected by this.
Workflow name: Microsoft.ForefrontProtection.FPE.Server.PerformanceCollection.RealtimeScanMessageRate

Hi Blake ,
Thanks for your reply , I appreciate your help ,
I didn't put the alert from scom console because they were same as the events ( same source )
Health Service Modules, I didn't want to spam
more :-)
also the two servers encountered the issue were mailbox servers and part of same DAG , it worth mention the alert were resolved
by Exchange 2010 Correlation Engine service
http://blogs.technet.com/b/kevinholman/archive/2010/10/15/clustering-the-exchange-2010-correlation-engine-service.aspx
http://support.microsoft.com/kb/2592561
also the Opsmgmt logs are full of waring and error event like 2023 , 21402 , 21403 , 1207 !!
Log Name: Operations Manager
Source: HealthService
Date:
Event ID: 2023
Task Category: Health Service
Level: Warning
Keywords: Classic
User: N/A
Computer: server 1
Description:
The health service has removed some items from the send queue for management group "SCOM" since it exceeded the maximum allowed size of 15 megabytes.
1- alert from console >>
In PerfDataSource, querying for Global Snapshot failed with error 'The size limit for this '
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2008.OperatingSystem.PercentMemoryUsed.Collection
Instance name: Microsoft Windows Server 2008 R2 Enterprise
EventSourceName: Health Service Modules

Apple mail problem message reads - Account removal failed with error: "The operation couldn't be completed. Unable to find an account for the UID given.".

Account removal failed with error: “The operation couldn’t be completed. Unable to find an account for the UID given.”. - trying to remove account but get this message please help

Try to remove the account in the Internet Accounts preference pane.

What to do about Backup failed with error: The target volume is read-only

This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

Pondini wrote:
odysseus wrote:
This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
I've tried this before, but it can't be repaired, because it can't be mounted.
Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
I'm backing up to my own sparseimage bundle just fine.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
That checks out fine.
if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

Client installation fails with error: The client version 4.00.6487.2000 does not match the MP version 2.50.4253.3000. The client wil not be installed.

Hello World,
I have this remote server that used to be a sms 2003 secondary site server. We uninstalled the SMS role. And used the server as an SCCM remote distribution point. We also want to install an client agent on that server machine. But no mather how i try
to install the client i always see the same error in ccmsetup.log:
File download 100% complete (17847296 of 17847296 bytes). ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Download complete. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Successfully downloaded client files. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Searching for available transform ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Failed to find resource file 'client.mst' ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
No transform available for this locale. Installation will proceed with no transformation. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
An MP exists on this machine. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
The client version 4.00.6487.2000 does not match the MP version 2.50.4253.3000. The client will not be installed. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
A Fallback Status Point has not been specified. Message with STATEID='318' will not be sent. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Deleted file C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe.download ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
I think the installer finds some remenance of the old SMS_MP. When looking i found some remains in IIS . I tried to remove the remains but still have the same error when installing the client. I uninstalled IIS completly. Can someone tell me where the client
installer looks for the MP version? Would it help if i installed an SCCM MP on that server and the uninstalled it (Upgrade the MP)?

Hello Kent, i ran the ccmclean.exe from the SMS2003 Toolkit. It informed me that my system was cleaned. I ran the sccm client setup manualy and found this in the ccmsetup.log
MSI PROPERTIES are SMSSITECODE=AUTO CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' is MS signed. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
Running installation package
Package: C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi
Log: C:\WINDOWS\system32\ccmsetup\client.msi.log
Properties: SMSSITECODE=AUTO CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: INSTALL. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: WindowsFolder.8AE6A59B_5597_4D75_9BFD_7F566BF56500. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.98C5B086_7EB0_422A_B0A8_674010F525CD. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.4C5E03E8_F8E5_47CB_8FF4_E46FE34D35A6. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: System64Folder.597B26B2_B5D6_40FF_90DA_B8E672626B1D. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: System64Folder.541D9CA5_CE53_4DCE_903A_9B9E5A6EF2C6. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SmsCheckConfig. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:22: SMSValidateClientInstallStamp. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: LaunchConditions. Evaluating launch conditions ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: SmsDetectWindowsEmbeddedFBWF. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: SmsCheckNewRemoteTools. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: AppSearch. Searching for installed applications ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CCPSearch. Searching for qualifying products ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: RMCCPSearch. Searching for qualifying products ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: ValidateProductID. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CcmSetInstallDir. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: BCDSetX64Dir. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CcmSetInstallDirFromCmdLine. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CcmSetPrimaryFolder. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: FindRelatedProducts. Searching for related applications ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: SmsDetectInvalidOrderColocUpgrade. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: An older version of the SMS Management Point is installed. Please upgrade the Management Point before attempting to upgrade the client. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
Installation failed with error code 1603 ccmsetup 8/18/2010 10:48:23 AM 3140 (0x0C44)
Next retry in 120 minute(s)... ccmsetup 8/18/2010 10:48:23 AM 3140 (0x0C44)
Their must be something remaining that ccmclean can't find or can' access so i ran ccmclean /mp. This did some stuff and told me the system was clean again. I reran the client setup.
Guess what
It worked !
Thanxs Kent

SQL Server Agent job fails with error : The package execution returned DTSER_FAILURE (1).

Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
at Teradata.Client.Provider.WpMessageManager.CheckForError()
at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
at Teradata.Client.Provider.WpLogonManager.Action()
at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
at Teradata.Client.Provider.TdConnection.Open()
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
Elapsed: 6.692 seconds. The package execution failed. The step failed.
SQL Server agent job fails with above error, Please let me know process tohandle it.
Thanks,
Vishal.

The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

12c agent install fails with error - The plug-in configuration for the oracle.sysman.oh monitoring plug-in may have failed

Hi,
I am trying to install 12c agent on windows 7 64 bit server by following m.note .
It is failing with Agent Configuration failed, please see below error message.
INFO: length of temp is2
INFO: Return value:C:\/Oracle/12.1.0.3.0_AgentCore_233/core
INFO: ** Agent Port Check completed successfully.**
INFO: ERROR: The Management Agent configuration failed. The plug-in configuration for the oracle.sysman.oh monitoring plug-in may have failed, or this plug-in may not be present in the Management Agent software. Ensure that the Management Agent software has the oracle.sysman.oh monitoring plug-in, if not then retry the operation. If the agent software has the oracle.sysman.oh monitoring plug-in, view the plug-in deployment log C:\Oracle\12.1.0.3.0_AgentCore_233\core\install\logs to check if the plug-in configuration for the oracle.sysman.oh monitoring plug-in failed.
INFO:
INFO: perform - mode finished for action: configure
INFO:
INFO: You can see the log file: C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0\cfgtoollogs\oui\configActions2014-10-03_08-48-15-AM.log
INFO:
INFO: C:\Oracle\12.1.0.3.0_AgentCore_233>exit /b 3
INFO: Plugin homes:
INFO: Plugin homes:
INFO: C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0\oui\bin\runConfig.bat ORACLE_HOME=C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0 RESPONSE_FILE=C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0\agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true completed with status=3
SEVERE: ERROR: Agent Configuration Failed
Thanks,

Looks like , J2EE is having a problem connecting to the DB.Pls. chk. the following
-If you have configured the loop-back adapter , if installing on a local system & updated the /etc/host file with your ip address and host name.
or if the system is part of some n/w group and has ip address assigned ?
-Jdk 1.4 version is installed in your system
-Enough free Disk space available in the system
-How much RAM your system has which windows version you are using ?
-Is the DB is coming up properly ? its error related to this. check the logs.
-If the ports used by sap install / run used by other services running on the system ? & user have admin. privileges on the system .
Pls. update with your findings on above same , for the step next ...
Thanks ,
Uppal

Brbackup failing with error "The paramter is incorrect"

Hi
I'm running SAP ERP6.0/Oracle 10.2.0.2/Windows 2008 Server. When I attempt a brbackup to disk it fails with the error below
BR0202I Saving I:\ORACLE\PRD\SAPDATA2\SR3_10\SR3.DATA10
BR0203I to E:\prd_oracle\behmebdl\SR3.DATA10 ...
BR0278E Command output of 'copy I:\ORACLE\PRD\SAPDATA2\SR3_10\SR3.DATA10 E:\prd_oracle\behmebdl\SR3.DATA10':
The parameter is incorrect.
0 file(s) copied.
BR0280I BRBACKUP time stamp: 2011-12-20 16.25.26
BR0279E Return code from 'copy I:\ORACLE\PRD\SAPDATA2\SR3_10\SR3.DATA10 E:\prd_oracle\behmebdl\SR3.DATA10': 1
BR0222E Copying I:\ORACLE\PRD\SAPDATA2\SR3_10\SR3.DATA10 to/from E:\prd_oracle\behmebdl\SR3.DATA10 failed due to
Below are some of the paramters set in the init<SAPSID>.sap
backup_root_dir = stage_root_dir = e:\prd_backup
backup_dev_type = disk
backup_type = online_cons
The user SAPServiceDEV has full rights on the folder e:\prd_backup
I'm using the commad below to fire the backup
C:\usr\sap\PRD\DVEBMGS02\exe\brbackup.exe -u / -p initPRD.sap -d disk -t online_cons -m all -c force
Thanks

Thanks for your response Fidel
I'm executing the backup from this script
C:\usr\sap\PRD\DVEBMGS02\exe\brbackup.exe -u / -p initPRD.sap -d disk -t online_cons -m all -c force
Drive e: is not a drive shared over the network. It is an external USB disk attached to the server running SAP. I've given user SAPSERVICE<SID> full rights to drive e:
2) change the fixed "drive" letter to UNC name (like
<server>\<directory_path>
When I use UNC name in place of the drive lettter I get the error message below
#backup_root_dir = E:\prd_oracle
backup_root_dir =
NXXX-HX-PXD1\prd_oracle
BR0259I Program execution will be continued...
BR0051I BRBACKUP 7.00 (42)
BR0282E Directory '
NXXX-HX-PXD1\prd_oracle' not found
BR0182E Checking parameter/option 'backup_root_dir' failed
BR0056I End of database backup: behmicld.log 2011-12-21 12.11.37
BR0280I BRBACKUP time stamp: 2011-12-21 12.11.38
BR0054I BRBACKUP terminated with errors
BR0292I Execution of BRBACKUP finished with return code 3
BR0668I Warnings or errors occurred - you can continue to ignore them or go back to repeat the last action

BMR-SS backup fails with error "the specified network name is no longer available"

We are running DPM 2012 SP1 on a Windows Server 2008 R2 system, backing up a Windows Server 2012 system that is a DC. The agent version is 4.1.3417.0. Both the DPM server and the DC are physical systems - brand new HP Proliant 360's.
When creating the replicas for the 2012 server the first time, the backups work fine, and then for a day or so after that. After a couple of days, the BMR-SS backups fail with the error "the specified network name is no longer available".
I can watch the backup happening in the Windows Server Backup console on the protected server - the BMR backup goes up to 99% and then fails. BMR backups on all the other servers are working - we have a mix of Win2008R2 and Win2012.
Here is what I have tried:
I can connect to the UNC path on the backup server without a problem during and after the backup is happening.
Tried reinstalling the DPM agent.
Tried backing up directly from the protected server to another server's network share, which worked.
I can copy multiple gigabyte files directly from the protected server to the DPM file share without a problem (the same one that DPM uses for the replica)
Tried turning off the SCEP real-time protection during the backup.
Any help would be appreciated - thanks.
KW

llo Boudewijn
I followed Boudewijn's suggestion.
The Windows 2012R2 servers had no recovery partition in disk C. I created one (400MB) following http://support.microsoft.com/kb/2930294/en-us and
DPM system restore worked. But just once.
So this is not the solution to the problem......
Is no one else having issues with DPM bare metal protection of Windows 2012R2 servers?

[Execute SQL Task] Error: Executing the query failed with error: "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION."

I have an package with source , data flow and destination to execute on begin and commit.
in the below i have just used for questioning purpose with diagram removing my Data Flow task explaining my problem
on execution, i get error as
[Execute SQL Task] Error: Executing the query "COMMIT TRAN DimCompanyCode" failed with the following error: "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not established correctly.
as mentioned , i have checked the ResultSet, parameters , connection establish.. all are fine.
Kindly advice on what has to be done.
ShanmugaRaj

To avoid this error, the RetainSameConnection property should set to 'True' for the Connection Manager - Application_DB.
Narsimha

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

Similar Messages

Maybe you are looking for