Since the error message does not mention what is the name of the module that could not be found, I think the first step is to find out what module is it talking about, and the “Process Monitor” from sysinternals can help on this matter.
- Run Process Monitor (which can be downloaded or run on-line <a href=”http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx”>here</a>)
- Run the application that cannot connect to the database and wait for the error message
- Stop the capture in process monitor
- See the on-screen log to find out what operations made by the application has something different to “SUCCESS” at the “result” column.
Once we have identified the not found module, I think more help can be provided.