Actually after further discussion with MS, the fix for this problem is part of SP 4 and is available as a hot fix for sp3.  We are testing it over...