2012-07-26 33 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任務,並且如果您不是通訊組的一部分列表,則也會在您將其作爲工作排定時發送郵件。

相關問題