Hi Amol,
Did you get the solution for the error listed below? I am asking because I hit the same one. Even with the 3.0.3 workbench release, I am still getting this error.
I am still testing on my end too, but any update/help you have about this error is really appreciated.
Regards,
Andy