Hi @mohnishbhagde, 

has this error been resolved? If it has been resolved, how was it fixed? Is it a configuration issue?

(I have the same issue and contacted Databricks about a month ago and have been communicating with them, but they still don't seem to know the cause and it hasn't been fixed yet.)