Hi Rohit,
we had also faced the same issue ( BODS 4.2 SP5 01 ), but we restarted the BODS related services, issue got resolved.
Thanks for the workaround which you had suggested here, that helped us to resolve this issue.
Not sure why we had faced the same issue.