I just encountered this problem yesterday and can attest that it is directly related to the SP3 update.  I contacted microsoft tech support who confirmed it and provided the following link...