2012-07-26 26 views
1

我创建了一个SSIS包,将其从Oracle 10g服务器导出到SQL SERVER 2008中。该包运行正常,当我通过Microsoft BIDS运行包时,运行良好,当我创建一个包并在Integration Services中运行它时。当我安排它通过作业调度程序(SQL Server代理)SSIS作业调度程序失败,但在BIDS和MSDB集成中运行良好服务

Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted 
07/26/2012 15:20:12,PATH JOB,Error,0,DSSSERVER,PATH JOB,(Job outcome),,The job failed.   
The Job was invoked by User HHSH\user7199. The last step to run was step 1 (PATH JOB).,00:00:01,0,0,,,,0 
07/26/2012 15:20:12,PATH JOB,Error,1,DSSSERVER,PATH JOB,PATH JOB,,Executed as user: HHSH\DSSSERVER$. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 3:20:12 PM Error: 2012-07-26 15:20:12.93  Code: 0xC0047062  Source: CLINICS ADO NET Source [1]  
Description: Microsoft.SqlServer.Dts.Runtime.DtsCouldNotCreateManagedConnectionException: Could not create a managed connection manager.  
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName<c/> String connStr<c/> 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<c/> Object transaction) End Error Error: 2012-07-26 15:20:12.93  
Code: 0xC0047017  Source: CLINICS SSIS.Pipeline  Description: component "ADO NET Source" (1) failed validation and returned error code 0x80131500. End Error Error: 2012-07-26 15:20:12.93  
Code: 0xC004700C  Source: CLINICS SSIS.Pipeline  Description: One or more component failed validation. End Error Error: 2012-07-26 15:20:12.93  Code: 0xC0024107  Source: CLINICS  
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:20:12 PM Finished: 3:20:12 PM Elapsed: 0.624 seconds. The package execution failed. 
The step failed.,00:00:01,0,0,,,,0 
07/26/2012 15:18:21,PATH JOB,Error,0,DSSSERVER,PATH JOB,(Job outcome),,The job failed. The Job was invoked by User HHSH\user7199. The last step to run was step 1 (PATH JOB).,00:00:01,0,0,,,,0 
07/26/2012 15:18:22,PATH JOB,Error,1,DSSSERVER,PATH JOB,PATH JOB,,Executed as user: HHSH\DSSSERVER$. 
Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 3:18:22 PM 
Error: 2012-07-26 15:18:22.76  Code: 0xC0047062  Source: CLINICS ADO NET Source [1]  Description: 
Microsoft.SqlServer.Dts.Runtime.DtsCouldNotCreateManagedConnectionException: Could not create a managed connection manager.  
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName<c/> String connStr<c/> 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<c/> Object transaction) End Error Error: 2012-07-26 15:18:22.76  
Code: 0xC0047017  Source: CLINICS SSIS.Pipeline  Description: component "ADO NET Source" (1) failed validation and returned error code 0x80131500. End Error Error: 2012-07-26 15:18:22.76  
Code: 0xC004700C  Source: CLINICS SSIS.Pipeline  Description: One or more component failed validation. End Error Error: 2012-07-26 15:18:22.76  Code: 0xC0024107  
Source: CLINICS  Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:18:22 PM Finished: 3:18:22 PM Elapsed: 0.655 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,,0 
07/24/2012 13:48:00,PATH JOB,Error,0,DSSSERVER,PATH JOB,(Job outcome),,The job failed. 
The Job was invoked by Schedule 23 (JOb Schedule for LAb PAthology). The last step to run was step 1 (PATH JOB).,00:00:00,0,0,,,,0 
07/24/2012 13:48:00,PATH JOB,Error,1,DSSSERVER,PATH JOB,PATH JOB,,Executed as user: HHSH\DSSSERVER$. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 1:48:00 PM Error: 2012-07-24 13:48:00.72  Code: 0xC0047062  Source: CLINICS ADO NET Source [1]  Description: 
Microsoft.SqlServer.Dts.Runtime.DtsCouldNotCreateManagedConnectionException: Could not create a managed connection manager.  
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName<c/> String connStr<c/> 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<c/> Object transaction) End Error Error: 2012-07-24 13:48:00.72  Code: 0xC0047017  Source: CLINICS SSIS.Pipeline  Description: component "ADO NET Source" (1) failed validation and returned error code 0x80131500. End 
Error Error: 2012-07-24 13:48:00.72  Code: 0xC004700C  Source: CLINICS SSIS.Pipeline  Description: One or more component failed validation. End Error Error: 2012-07-24 13:48:00.72  Code: 0xC0024107  Source: CLINICS  Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:48:00 PM Finished: 1:48:00 PM Elapsed: 0.639 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,,0 
+0

如果它运行在BIDS中运行时,并且通过IS运行,但是代理失败,那会让我觉得代理有什么不妥。您是否已验证运行该软件包的服务帐户是否具有正确的凭证以与Oracle通信?它是否有文件系统访问任何Oracle驱动程序或什么? – billinkc 2012-07-26 21:34:30

+0

那么我使用Windows身份验证相同。我很困惑,我们如何检查文件系统是否可以访问任何Oracle驱动程序或者什么? – user1141584 2012-07-30 16:20:01

回答

9

大部分在BIDS但不能在SQL作业运行良好的问题出现时它只有失败,原因是这些情况:

  • 数据源连接或文件访问问题(当运行SQL代理的用户没有对数据库或目标文件的正确权限时)。

  • 程序包保护级别(pwd是敏感数据,有时不根据保护级别进行复制)。 (因为没有用于64位系统的Jet驱动程序,当在64位操作系统上运行时,您需要在SQL作业中使用32位DTEXEC或设置“使用32位运行时”选项,它位于“执行选项“选项卡,当您创建SSIS作业步骤时,请查看下面链接中的图像以查看它)。

32Bit runtime option image

有关此主题的信息,我建议你看看下面的文章,它有详细的这些种情况的信息..

How do I troubleshoot SSIS packages failed execution in a SQL Agent job?

希望这可以帮助你..

亲切的问候,

+1

伟大的威尔逊,普拉塔诺威力! ATT。 Frankyboy;) – Fmanin 2017-07-27 08:21:11

0

SQL Server代理程序有一个小故障,我有一个类似的问题,所以我所做的只是再次构建项目,如果你有任何脚本需要我再次构建,然后再次构建项目,删除路径该软件包正在引用,重新创建位于bin文件夹中的软件包的路径,然后计划作业运行,并且在某些时候SQL Server代理没有正确缓存请求。我知道这个帖子是两年前问的,但是这是针对目前有问题的人。并且,如果您在包中包含sendemail任务,并且如果您不是通讯组的一部分列表,则也会在您将其作为工作排定时发送邮件。

相关问题