This issue should be resolved with Hotfix 2.0.2:
If this issue persists, please post a comment in the above thread.