It looks like we have found the issue that was causing this error. The database had the previous data from Fall 2011(which has been deleted now) and when the application tried to fetch the data it was returning multiple rows.