Yes, i found the SET ANSI_WARNINGS option might be related to te result i get. So, i try to turn on and off the option and both also give me same error.

A tough task for me to look into all stored procedures for this kind of error.