These problems happen when a PC is not maintained properly and should be fixed immediately to avoid further damage. Defaulted to export symbols for C:\Windows\system32\ntdll.Problem: tabctl32.ocx error occur when the system is incorrectly configured or critical files are missing. *** ERROR: Symbol file could not be found.
When we just use tabctl32.ocx in a form, the software does not break into the debugger, and all of our other EXEs run fine it's just with mscomctl.ocx.Īnd here's a dump of when another app is run with mscomctl.ocx (on load this time): Defaulted to export symbols for C:\Windows\system32\ntdll.dll. ModLoad: 10000000 1000c000 C:\Program Files\VMware\VMware Tools\hook.dll symfix to have the debugger choose a symbol path. * Symbol loading may be unreliable without a symbol search path.
We even tried with a simple VB6 app with just a Form and a ListView control and no code and the same behavior happens.
Starting the application app.exe does not bring up the debugger, but *ending* the application app.exe brings up the debugger.
In our install we put mscomctl.ocx, app.exe, and in the Program Files\App folder.Īll applicable Test Cases pass, except for Test Case 31. Our VB6 app uses the ListView control in mscomctl.ocx.