Yossi Dahan [BizTalk]

Google
 

Monday, May 12, 2008

Flush failed to run error when using DES

A quick one -

If you're using one of the DirectEventStream BAM API and you're seeing an error "Flush failed to run", check the connection string (and related permissions) to the database.

Happened three times to me recently (don't ask!) - all of which were related to configuration problems.

Labels: ,

2 Comments:

  • I had this issue on an XP machine new to Biztalk.

    I could not run tracking pipeline with the "failed to flush" error, as per your post, when debugging the pipeline I found that the problem was my ASP NET worker account did not belong to BizTalk Application Users (only Isolated Host users). The TDDS sp's in BizTalkMsgBoxDb have exec perms for the Application Users group. These sp's are required for tracking to work

    By Anonymous Anonymous, at 12/01/2009, 15:57  

  • Yossi - you are a life saver! Had this again on a new environment and was struggling to understand why! Hope you are well. Cheers, Dan.

    By Anonymous Anonymous, at 18/07/2011, 09:58  

Post a Comment

<< Home