Solved

Unable to schedule the CData SSIS job in sql server Agent job.

  • 26 April 2024
  • 1 reply
  • 36 views

Userlevel 2
Badge

Hi Ethem Q,

i have created the ssis package using the CData workday drivers. package is running smoothly when it is in SSIS compailor. and i am trying to schedule this package as agent job in sql server, it is failing with below error. kindly help me in this..

 

Message
Executed as user: XXXXXXXXX\RKASEE. Microsoft (R) SQL Server Execute Package Utility  Version 15.0.2000.5 for 32-bit  Copyright (C) 2019 Microsoft. All rights reserved.    Started:  2:13:56 PM  Error: 2024-04-26 14:15:59.96     Code: 0xC0047062     Source: Workday_BankAccounts CData Workday Source [609]     Description: CData.SSIS.Workday.WorkdayException (0x80004005): [500] Request timed out. Either there is a server issue, or you've entered wrong credentials or wrong callback url. ---> jwo230k.Rx: Request timed out. Either there is a server issue, or you've entered wrong credentials or wrong callback url.     at jwo230k.FFZ.Ra(Rx )     at jwo230k.FFZ.pg(uNj )     at jwo230k.uPB.K(WP , uNd )     at jwo230k.uPB.G(WP , uTN )     at jwo230k.uPB.kz(uTN , Boolean )     at jwo230k.uTN.q(ucY , uGa , BRG , uGa , uGa , String )     at jwo230k.uTN.c(WP , uGa , BRG , uGa , uGa )     at jwo230k.uNd.s(String , WP , uTl )     at jwo230k.uNd.gp(WP , uTl )     at jwo230k.FjP.pg(uNj )     at jwo230k.uPB.K(WP , uNd )     at jwo230k.uPB.G(WP , uTN )     at jwo230k.uPB.kz(uTN , Boolean )     at jwo230k.ucl.J(ucl , uTN )     at jwo230k.ucl.qa(uTN )     at jwo230k.uPs.G(uTN )     at jwo230k.uPs.r(uPs , uTN )     at jwo230k.uPs.qa(uTN )     at jwo230k.uPs.qa(uTN )     at jwo230k.uGE.OI(uTN )     at jwo230k.EZ.m(uNj , vO )     at jwo230k.EZ.V(uNj , vO , ulu )     at jwo230k.BxR.kv()     at jwo230k.Bxu.kv()     at jwo230k.lB.m(Int32 , Object , ulu , Int32 , hk )     at jwo230k.lB.G(Int32 )     at jwo230k.lB.H(Boolean )     at jwo230k.lB.x(xp , Boolean , Boolean , sx )     at jwo230k.lB.o(hk )     at jwo230k.hE.Connect()     at jwo230k.BOO.Connect()     at jwo230k.Pq.qV()     at jwo230k.Pq.qg()     at jwo230k.Pq.pf()     at jwo230k.PE.pf()     at jwo230k.Ps.Acquire(String , String , ulu )     at jwo230k.TY.Open()     at jwo230k.aqZ.Open()     at jwo230k.aqZ.Open()     at CData.SSIS.Workday.WorkdayConnMgr.AcquireConnection(Object txn)     at Microsoft.SqlServer.Dts.Runtime.ManagedWrapper.AcquireConnection(Object txn)     at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.AcquireConnection(Object txn)     at jwo230k.FcO.AcquireConnections(Object )     at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)  End Error  Error: 2024-04-26 14:15:59.96     Code: 0xC0047017     Source: Workday_BankAccounts SSIS.Pipeline     Description: CData Workday Source failed validation and returned error code 0x80004005.  End Error  Error: 2024-04-26 14:15:59.96     Code: 0xC004700C     Source: Workday_BankAccounts SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2024-04-26 14:15:59.96     Code: 0xC0024107     Source: Workday_BankAccounts      Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  2:13:56 PM  Finished: 2:15:59 PM  Elapsed:  123.438 seconds.  The package execution failed.  The step failed.

  

icon

Best answer by Ethem Q 27 April 2024, 00:32

View original

1 reply

Userlevel 5
Badge

Hi @Renukachari_Kasee 

The issue you are seeing is due to the OAuth process failing to complete. It is most likely happening because the browser is trying to launch but it is failing to start under the SQL Server Agent. Please note that the SQL Server Agent can only access public paths. 
  
To fix this, you should copy the OAuthSettings.txt file from ‘C:\Users\User\AppData\Roaming\CData\Workday Data Provider’ to a public path (e.g., ‘C:\Users\Public\Documents’) and then set the OAuth Settings Location in your connection settings to this new path in the connection configuration.

In case you encounter any other issues feel free to reach out to our support team at support@cdata.com.

Reply