Thank you for your reply. We have solved the case by upgrading NSM. To answear your question: we run an old version. It was 3.0. We have upgraded to version 3.1.2 and that has solved the issue. We have never come down to solve the issue itslef though. An upgrade was simply the faster way. : -) Again thanks for your reply. The issue is now solved.