SSIS Package with Scheduled Task

Question

Hi there,
We have on a SQL-Server some SSIS Packages which refers to Navision. If I start the job manually directly in Navision, it works fine. If I start the Job in MSSQL manually (SQL Server Agent --> Jobs --> 'MyJobPackage' --> Start Job at Setp) or through
the Job Activity Monitor ('MyJobPackage' --> Start Job at Step) it works also fine without any problems. But if the Job starts automatically (Scheduled Job in MSSQL) it will never end. So the Job is running endless. Now, we thought we could try to start
this SQL Job with a Scheduled Task in Windows. So I created a cmd-File with the following line:
dtexec /f "E:\SSIS Schnittstelle\TEST_Navision2XAPF\Navision2X.APF\bin\EGHU.dtsx" /De MyPassword
And then I get this errors:
C:\Users\exprma\Desktop>dtexec /f "E:\SSIS Schnittstelle\TEST_Navision2XAPF\Navision2X.APF\bin\EGHU.dtsx" /De MyPassword
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started:  10:17:44
Progress: 2014-03-12 10:17:45.32
   Source: Dimensionen
   Validating: 0% complete
End Progress
Error: 2014-03-12 10:17:45.34
   Code: 0xC0047062
   Source: Dimensionen Dimension [134]
   Description: System.Data.Odbc.OdbcException: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
   at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)
   at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle)
   at System.Data.Odbc.OdbcConnectionOpen..ctor(OdbcConnection outerConnection, OdbcConnectionString connectionOptions)
   at System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.Odbc.OdbcConnection.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-03-12 10:17:45.34
   Code: 0xC0047017
   Source: Dimensionen SSIS.Pipeline
   Description: component "Dimension" (134) failed validation and returned error code 0x80131937.
End Error
Progress: 2014-03-12 10:17:45.34
   Source: Dimensionen
   Validating: 4% complete
End Progress
Error: 2014-03-12 10:17:45.34
   Code: 0xC004700C
   Source: Dimensionen SSIS.Pipeline
   Description: One or more component failed validation.
End Error
Error: 2014-03-12 10:17:45.34
   Code: 0xC0024107
   Source: Dimensionen
   Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started:  10:17:44
Finished: 10:17:45
Elapsed:  0.999 seconds
So what could I try at the next step?
Regards
ÖFES

Answer 1

Hi Öfes,
Based on the error message when executing the package from batch file and the solution provided by Visakh, we can conclude that the package uses 32-bit ODBC drivers. Now let’s go back to the original SQL Server Agent job issue. Since you can run the job
manually from SSMS, the package should run in 32-bit SSIS runtime mode, e.g. the “Use 32 bit runtime” option should be checked for the package executions with in the job step. In this case, SSIS automatically uses the 32-bit DTExec utility, therefore, we don’t
need to specify the 32-bit DTExec utility in the command line for the job step.
Based on the current information, the issue may occur due to two possible factors:
The Dimension component in the package uses User DSN rather than System DSN.
The user account under which the job runs doesn’t have sufficient permissions to execute the package.
So, please try the following steps:
Open the C:\Windows\SysWOW646\odbcad32.exe, and make sure the DSN is a System DSN which can be accessed by any user on the server.
Create a new SQL Server Agent proxy account which has sufficient permissions to execute the package, for example, the user account that you execute the job manually from SSMS.
Reference:
http://technet.microsoft.com/en-us/library/ms190698(v=sql.105).aspx 
Regards,
Mike Yin
TechNet Community Support