I have a large Visual Basic 6 application which has been running for about 6 years on Windows XP, SP3. I've made a few changes to it to accomodate using it on Windows 7, and have built an install setup.exe using the Package and Deployment wizard. The install was used to install it on more than one Windows 7 test computer, where it ran without problems. The install was also used by the client to build a Radius package for their network installation. It turns out that as time passed the Windows 7 enviroment changed, or in some way the Radius package was flawed, and installations made with it, although no errors were observed, have caused the application complain of the error in the title above, and when the only button (OK) or the X on a red field is clicked the application terminates. So far as I can tell all the necessary files are in the setup's .CAB file and were installed and registered.
I added several (dozens) of logging messages to the application in an attempt to isolate the problem. This has not yet been productive. The database is on a SQL server and the same data was used for the test systems and the systems now having problems.
What I would like is access to a way to obtain a log of .dll and .ocx calls made by the application as it starts up, with an indication of any problems encountered. I've heard that Winternals Process Explorer (of which I have the most recent version) might do this, but I'm not sure how to obtain this, and have not found any concise explanation. Buying a book on Amazon is a possible recourse, but I had hoped to find something more to the point on line.
Can anyone help?