Your SQL Server database, most likely the one hosting the repository, has a timeout specified. If a connection is not active for xxxx minutes, SQL Server will drop the connection.
Imagine you have a dataflow which takes 10 hours, so for 10 hours it will read and load but not interact with the repository. With this setting the SQL Server drops this allegedly inactive connection.
(12.2) 05-30-11 03:13:36 (E) (6812:6496) CON-120302: Initialization
ODBC call for data source <SERVERNAME\sqlexpressbodi> failed: <[Microsoft][ODBC SQL Server Driver]Timeout
expired>. Notify Customer Support.
(12.2) 05-30-11 03:13:36 (E) (2136:2352) RUN-050406: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY|Data flow DF_COPY_T003T
Data flow <DF_COPY_T003T> received a bad system message. Message text from the child process is < >. The process executing data
flow <DF_COPY_T003T> has died abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical
Support.
(12.2) 05-30-11 03:13:38 (E) (6740:3188) CON-120302: Initialization
ODBC call for data source <SERVERNAME\sqlexpressbodi> failed: <[Microsoft][ODBC SQL Server Driver]Timeout
expired>. Notify Customer Support.
(12.2) 05-30-11 03:13:38 (E) (2136:7304) RUN-050406: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY|Data flow DF_COPY_T016t
Data flow <DF_COPY_T016t> received a bad system message. Message text from the child process is < >. The process executing data
flow <DF_COPY_T016t> has died abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical
Support.
(12.2) 05-30-11 03:13:38 (E) (2136:7304) RUN-050409: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY
The job process could not communicate with the data flow <DF_COPY_T016t> process. For details, see previously logged error
<50406>.
(12.2) 05-30-11 03:13:40 (2136:2352) RUN-050409: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY
(12.2) 05-30-11 03:16:45 (E) (3244:1604) CON-120302: |Data flow DF_COPY_TVFKT
ODBC call for data source <SERVERNAME\sqlexpressbodi> failed: <[Microsoft][ODBC SQL Server Driver]Timeout
expired>. Notify Customer Support.
(12.2) 05-30-11 03:17:21 (E) (7104:7620) CON-120302: Initialization
ODBC call for data source <SERVERNAME\sqlexpressbodi> failed: <[Microsoft][ODBC SQL Server Driver]Timeout
expired>. Notify Customer Support.
(12.2) 05-30-11 03:17:22 (2136:7516) RUN-050406: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY|Data flow DF_COPY_TVTW
(12.2) 05-30-11 03:17:22 (2136:7516) RUN-050409: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY
(12.2) 05-30-11 03:17:24 (E) (4612:5404) CON-120302: Initialization
ODBC call for data source <SERVERNAME\sqlexpressbodi> failed: <[Microsoft][ODBC SQL Server Driver]Timeout
expired>. Notify Customer Support.
(12.2) 05-30-11 03:17:24 (2136:6392) RUN-050406: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY|Data flow DF_COPY_TVBVK
(12.2) 05-30-11 03:17:24 (2136:6392) RUN-050409: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY
(12.2) 05-30-11 03:18:35 (E) (2136:2208) RUN-050406: |Session 400_JO_COPY_T_TABELLEN_DAILY|Work flow WF_COPY_T_TABELLEN_DAILY|Data flow DF_COPY_T016t
Data flow <DF_COPY_T016t> received a bad system message. Message text from the child process is < >. The process executing data
flow <DF_COPY_T016t> has died abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical
Support.
I set the timeout last friday to 0, but nothing happend.