Mark,
Thanks for the response.
Since it happened in the evening when other stored procedures were running and using tempdb resources, I will try to reproduce it this evening by first dropping and recreating that stored procedure and then calling it in the batch script as you suggested. Also, I will try to monitor the session using AseTune to see if I can capture any other useful information.
Thanks,
Anil