• I have this occurring on a Server Standard 2003 x64 box with Developers 64 bit SQL 2005 sp 1. I wonder if this is fixed in SP2?