$ 0 0 Actually we got this problem while updateing on BI 4.1 SP05, so I don't think that this is a fixed issue.RegardsMarcel