Hi, 

Yes! A workaround we discovered is to wrap the pyodbc script in some error handling code. Our particular script was throwing some exceptions/outputs which were ignored by Databricks in a notebook, as well as when installed as a global init script. Apparently....the cluster could not ignore the exceptions when the pyodbc script was installed in the Volume. Once the script in the Volume stopped "outputting".....the shared cluster was able to read it and start up.

Hope that helps you!

Benni