We are experiencing a named pipe error:
3812 8816 FIL-080133
9/17/2014 12:05:20 PM The database client cannot connect to named pipe
<\\.\pipe\159d2cbc-5800-4d15-9dec-2f8f7e99c9ff>.This happens at exactly 10 minutes of launching the job, and is
presumably caused by a timeout between a parent and child subflow. We are
running a DISTINCT as a separate process because without it we hit the 32bit process memory limit of 2 GB.
The complex flow works successfully when the database queries return
in less than 10 minutes. Our production queries are coming back in about 12
minutes. I tried updating the DSConfig.txt file and setting
DFRegistrationTimeoutInSeconds = 900 (was 300) and restarted the DS
service. But this did not affect the timeout.
Can someone advise if the 10 minute timeout is configurable and where I
would adjust that setting?
Steps for Reconstruction
Create a dataflow with a SQL query that takes longer than 10 minutes in the
database. Set a QUERY transform to do a distinct as a separate process, and
then join that into another SQL query. It appears the first query times out
waiting on the second query’s subflow.
cfachris 
(BOB member since 2003-09-03)