You should be able to enable detailed logging in the EWS Retrieval (or whichever protocol you're using in this case) and find more detail about what was being imported when it failed. It may not give you the specific message necessarily but should get you in the ballpark. I have escalated a feature request to add a debug option of sorts that can be used for cases like this where initial import failed for any reason though!
Kyle Kerst
IT Coordinator
SmarterTools Inc.
www.smartertools.com