Tommy, it is more likely that the .net framework was at fault - we used to see a lot of this, regardless of SP version. There seem to have been a number of quiet .net updates that didn't always come down - I don't have time to find links for you at the moment, but search the microsoft site to see all the fixes and repair methodologies.


--=-- My credo: If it's worth doing, it's worth overdoing - just ask my missus, she'll tell ya laugh --=--
You're only paranoid if you're wrong!