did something recently change in your system landscape?
we had this error at a client once after they upgraded BW (to 7.3, being unicode) without changing the source system to unicode (which was not the smartest way of doing things)... I believe we solved it through some OSS note