This is a pretty common error to get and it usually means exactly what it says: You have no line coming out of your service so Teamworks can’t route you anywhere. But what do you do when there is a line leading to the next service?

In this case there is a good change you have the wonderful phantom line bug. Even though the UI shows that you have a line to the next service and you can select it, as far as the process server knows it doesn’t exist. You can sometimes see if this if you do an export and look at the XML. The line will not be defined. Other times it will show and you need to delete the nested service and insert it again. More so than most other bugs this one angers me, because it leads to start debugging down the wrong path.

Another shortcoming of this is the lack of information with the error message. This is a common problem throughout Teamworks. It would be incredibly helpful for the error message to give you the name of the last service that completed.

I have no clue what a narrative is but don’t you dare ever go and delete one.

Today we got an error message that basically said: "No more error info available."  So I started trying a bunch of different things trying to figure out what was wrong. After working on this for over  4 HOURS, I come across a line in the debug log that says "Premature end of binary stream after reading 0 bytes".

Searching their website for that text lead me to exactly 1 hit.  The result said that the problem was that a process item had a "narrative" and then someone probably removed it.

Normally, I would have dismissed this error as unrelated.  However, earlier I ran a dif tool that I wrote (why Lombardi doesn’t know how to write this kind of tool is beyond me) and saw that someone had changed a description and removed a "narative".

So - I stuck a narrative back in and now everything works.  Another 4 hours of my life I won’t get back because of Teamworks.

I’m just lucky I’d written my own dif tool or I’d still be looking.  I pity anyone that doesn’t have the ability to do a DIF on Teamworks stuff.