A couple of ideas for you to consider:
1. Use AERROR() to capture more details about the error event. Something is going wrong on SQL2K and you need to find out what that is before you charge ahead.
2. You could also do some things on the SQL side like creating an Alert that writes more details of the error to your SQL logs.

Good luck :)

Ken