This incidence happened some 4-5 months ago. I was debugging an issue and found from the error log a particular stored procedure was throwing some exception. I could not find any issue with the procedure. Later, found there was another procedure that threw this exception.
So, why was the error log misleading? I found the developer who created the procedure that failed, had copied the exception block from the first one!!
Copy & paste helps developers a lot. Still, we need to be careful in doing so.