When I execute my SSIS package from SQL Server Agent job or DTEXECUI the
configurations stored in SQL server is not read. The connection to the SQL
Configuration is specified in the command parameters. When running profiler I
can see that the SSIS Configuration table is not accessed at all.

The command line parameters of the actual job step also set up a connection
to the log I am using, and this connection is read ok.

Here is the command parameters of the job step:

/FILE "E:\Program Files\DV BM\ETL\BM\BMKunde.dtsx"
/CONNECTION CONFIG;"Data Source=APOLLOQGJOSQL03\BM;Initial
Catalog=BMPERSIST;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto
Translate=False;"
/CONNECTION LOG;"Data Source=APOLLOQGJOSQL03\BM;Initial
Catalog=BMPERSIST;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto
Translate=False;"
/MAXCONCURRENT " -1 "
/CHECKPOINTING OFF


Any hints?

Additional findings: A job run locally on my developer PC works fine (Windows
XP Prof SP2). It reads the SSIS Configuration table. I have also discovered
that the job step GUI for SSIS packages also reads the SSIS Configuration
table when activating the Data Sources tab.

None of these are working in my test environment (Windows 2003 Server).

"Rolf" wrote:

Seems to be only me having this problem :-)

However I have isolated the problem to be that the command line parameter
for the SSIS Configuration table connection is not read. The connection info
is only read from the dtsx-file

"Rolf" wrote: