I wish I had a better answer for you other than upgrade to VirtualCenter 2.5.0U3. The fix is in the release notes, so I can only assume it was a known issue in previous releases.
Good Luck!
please consider awarding points for helpful/correct answers.