My problem started with an application that was just deployed. I’m getting an error when the application is closed. This only happens the first time after the initial run of the program where the Connection Wizard is used to configure the connection. After closing the error window I saw that the app was still alive in Task Manager and killed the process.   Re-running the app a second time without running the connection wizard allows the application to exit with no errors.

I went back to the development environment and created a simple app to see if happen there. Attached is screenshot of the error I received there.  

-Larry

Here is a little more info. I enabled unmanaged code debugging on my VB test app and the following showed up. It corresponds to the exception I'm getting.