@J-G:
Exactly my initial thought when i posted my first reply
Alas, the exception occurs inside lclproc which suggests that TS is not responsible (well, not directly that is) as TS uses another component that seems to cause the exception. So either there is a oversight/flaw with the used component or TS is doing something 'really fishy'.
Right now it's hard to tell what exactly is the culprit. A back-trace would be able to tell the path of the code, thus what code exactly is responsible. If indeed the component then this will show as well, and hopefully also pinpoint the location.