>>>>No, I didn't see a call to my SP
>>>>Yes, I used the default template
>>>
>>>Do you have batch completed and procedure completed events? These are the only two you need. If you don't see calls to your SP after you run the trace, then your SP is not called.
>>
>>Then why is it saying that it can't find the SP on the 2nd time through? I do see connection_resets being called in the trace and the only SP I see being called is some generic getbatchid proc.
>
>Post a screen shot of your profiler trace.
>Also, try placing a break point on the SQLEXEC line and see if anything is shown in the trace after you click on it.

I'm stepping through the code anyway - so no need for the break point.

3 lines had gone by on the trace when I paused it to take the screen shot. You're going to tell me that the SP isn't firing off, which brings me right back to my original question. Why isn't it? Why isn't it reporting back an error until the 2nd time I run it in the same loop?