[RESOLVED] Error 429 ActiveX component can't create object

[Eduardo-]

My program uses SxS for the OCXs and DLLs. They are not many, 4 custom OCX, Windows Common Controls 1 and 2 (SP6), MSHFlexGrid and RichTextbox.
Only the VB6 main DLLs and DAO 360 that are already in Windows are not used SxS.

One user out of many is reporting that she gets the error "Error 429 ActiveX component can't create object", sending this capture that I guess it must be from Windows 7:



It looks like it is not taking into account the manifest that is inside the exe, IDK...

I still don't have much information because I'm not directly communicating with the user and now is the weekend so... I suppose that she was running a previous version of the program without issue, but I can't confirm that now.

I can confirm that the program is OK, I unregistered all OCXs and DLLs that the program uses in my machine and the SxS installation ran without issue.
Also all the other users run the same program version without issues.

I've tried to check if configuring UAC to the highest level can trigger the problem (according the Perperxity, an AI chat, that could be a cause for the error), but I could not trigger the issue, the program keeps running even at highest security setting of the UAC. BTW: it does not require admin rights, so the UAC prompt never triggers.

Any Idea?

I guess I'll be able to connect using Anydesk to the user machine, probably on Monday.
For that I'm planning to run a script to ensure these DLLs are registered: msvbvm60.dll, olepro32.dll, oleaut32.dll and dao360.dll (this one is not as easy as just use Regsvr32, but I have a *.reg file that fixes registration issues).

Another thing that I'm planning is to check: Control Panel > Administrative Tools > Event Viewer and look under "Windows Logs" > "Application" for any errors related to my program and see if I can get some idea from there.

Also execute gpedit.msc, Computer Configuration > Policies > Administrative Templates > Windows Components settings and check if there is something configured for ActiveX Installer Service.

Anything else?
TIA

[jdelano]

One of the tools I'd often use is dependency walker https://dependencywalker.com/ run it on her PC to see which versions of the DLLs your app is trying to load. Maybe a subsequent app installation changed one and it is causing your app an issue.

[Eduardo-]

Maybe a subsequent app installation changed one and it is causing your app an issue.

It is unlikely that she installed anything after it. Also it is a SxS installation, so it shouldn't be affected by other programs I think.

I has all the DLLs and OCXs in a Bin folder in the app path.

I'll run dependency walker when I have access to her PC, thanks.

[TysonLPrice]

Just as a SWAG check the GUID in the vbp file and scan to see if it is registered.

[Elroy]

Wait, where is the "app path"? Is this in c:\Program Files (x86), or maybe c:\Program Files (x86)\YourProgram?

And then there's a c:\Program Files (x86)\YourProgram\bin subfolder in there?

If that's the case, how are those OCX files getting into that bin folder? During some installation, or during runtime?

In my case, I yank them out of the EXE and "unpack" them during runtime, so I've got to "drop" them somewhere that won't require UAC permissions (which won't be anywhere in c:\Program Files (x86)\...

If you do it during installation, I might check and make sure all my OCX versions are correct.

Also, it'd be useful to see your manifest for one of these OCX files, as the path specification on these things can get a bit tricky. IIRC, they absolutely must be "relative" paths.

Just some thoughts.

---

In all cases (well, except my home development computer), I run the EXE (and all the OCXs) from a server folder to which full permissions are granted (via a group) to all users who might use the program. And I've virtually never seen this problem, and a variety of Windows versions are using it everyday (in very much a multi-user fashion, typically 3 or 4 users [therapists] per site).

[qvb6]

I guess I'll be able to connect using Anydesk to the user machine, probably on Monday.
For that I'm planning to run a script to ensure these DLLs are registered: msvbvm60.dll, olepro32.dll, oleaut32.dll and dao360.dll (this one is not as easy as just use Regsvr32, but I have a *.reg file that fixes registration issues).

Only DAO360.dll requires installing and registering, the others are protected system files.

Support Statement for Visual Basic 6.0 on Windows:
https://learn.microsoft.com/en-us/pr...support-policy


One issue that could cause this is System Restore. It would restore any recently installed EXE/DLL/OCX to the previous version, not sure if it would restore parts of the registry.

[Eduardo-]

Wait, where is the "app path"? Is this in c:\Program Files (x86), or maybe c:\Program Files (x86)\YourProgram?

Yes, I think all the programs have a subfolder under c:\Program Files (x86)

And then there's a c:\Program Files (x86)\YourProgram\bin subfolder in there?

Yes.

If that's the case, how are those OCX files getting into that bin folder? During some installation, or during runtime?

There is an Inno Setup installer that copies all those files without registering them and makes a shortcut to the main exe. It works for the user exactly as a normal Windows installation, but it is a SxS one.

In my case, I yank them out of the EXE and "unpack" them during runtime, so I've got to "drop" them somewhere that won't require UAC permissions (which won't be anywhere in c:\Program Files (x86)\...

If you do it during installation, I might check and make sure all my OCX versions are correct.

I still could not connect to the user machine to see, but the installer should had uninstalled any previous version.
There was one OCX that was updated in its update, if the installer didn't uninstall the previous version and also didn't overwrite it with the new ocx version, it could possibly cause that error.
But... why it would do that?

Also, it'd be useful to see your manifest for one of these OCX files, as the path specification on these things can get a bit tricky. IIRC, they absolutely must be "relative" paths.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" >
  <assemblyIdentity name="OrganizationName.ProgramName" processorArchitecture="X86" type="win32" version="5.0.0.884" />
  <description>Decriptin of the program</description>
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
        <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
    </application>
  </compatibility>
  <dependency>
    <dependentAssembly>
      <assemblyIdentity language="*" name="Microsoft.Windows.Common-Controls" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" type="win32" version="6.0.0.0" />
    </dependentAssembly>
  </dependency>
  <file name="Bin\MSHFLXGD.OCX">
    <typelib tlbid="{0ECD9B60-23AA-11D0-B351-00A0C9055D8E}" version="6.0" flags="control" helpdir="" />
    <comClass clsid="{0ECD9B64-23AA-11D0-B351-00A0C9055D8E}" tlbid="{0ECD9B60-23AA-11D0-B351-00A0C9055D8E}" threadingModel="Apartment" progid="MSHierarchicalFlexGridLib.MSHFlexGrid.6" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="Microsoft Hierarchical FlexGrid Control 6.0 (SP4) (OLEDB)" />
  </file>
  <file name="Bin\MSStdFmt.dll">
    <typelib tlbid="{6B263850-900B-11D0-9484-00A0C91110ED}" version="1.0" flags="" helpdir="" />
    <comClass clsid="{2B11E9B0-9F09-11D0-9484-00A0C91110ED}" tlbid="{6B263850-900B-11D0-9484-00A0C91110ED}" threadingModel="Apartment" progid="MSSTDFMT.StdDataValue.1" description="StdDataValue Object" />
    <comClass clsid="{6D835690-900B-11D0-9484-00A0C91110ED}" tlbid="{6B263850-900B-11D0-9484-00A0C91110ED}" threadingModel="Apartment" progid="MSSTDFMT.StdDataFormat.1" description="StdDataFormat Object" />
    <comClass clsid="{99FF4677-FFC3-11D0-BD02-00C04FC2FB86}" tlbid="{6B263850-900B-11D0-9484-00A0C91110ED}" threadingModel="Apartment" progid="MSSTDFMT.StdDataFormats.1" description="StdDataFormats Object" />
  </file>
  <file name="Bin\COMCTL32.OCX">
    <typelib tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" version="1.3" flags="control" helpdir="" />
    <comClass clsid="{9ED94440-E5E8-101B-B9B5-444553540000}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.TabStrip.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="Microsoft TabStrip Control" />
    <comClass clsid="{612A8624-0FB3-11CE-8747-524153480004}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.Toolbar.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,actslikelabel,alignable,simpleframe,setclientsitefirst" description="Microsoft Toolbar Control" />
    <comClass clsid="{6B7E638F-850A-101B-AFC0-4210102A8DA7}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.SBarCtrl.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,actslikelabel,alignable,setclientsitefirst" description="Microsoft StatusBar Control" />
    <comClass clsid="{0713E8D2-850A-101B-AFC0-4210102A8DA7}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.ProgCtrl.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,actslikelabel,alignable,setclientsitefirst" description="Microsoft ProgressBar Control" />
    <comClass clsid="{0713E8A2-850A-101B-AFC0-4210102A8DA7}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.TreeCtrl.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="Displays a hierarchical list of Node objects, each of which consists of a label and an optional bitmap." />
    <comClass clsid="{58DA8D8A-9D6A-101B-AFC0-4210102A8DA7}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.ListViewCtrl.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="Displays a collection of ListItems such as files or folders." />
    <comClass clsid="{0713E8C4-850A-101B-AFC0-4210102A8DA7}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="MSDataListLib.RowSource.1" description="ListView Item collection" />
    <comClass clsid="{58DA8D8F-9D6A-101B-AFC0-4210102A8DA7}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.ImageListCtrl.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,invisibleatruntime,alignable,setclientsitefirst" description="Contains a collection of ListImage objects, each of which can be referred to by its index or key" />
    <comClass clsid="{373FF7F0-EB8B-11CD-8820-08002B2F4F5A}" tlbid="{6B7E6392-850A-101B-AFC0-4210102A8DA7}" threadingModel="Apartment" progid="COMCTL.Slider.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="A calibrated control with a slider for setting or selecting values." />
  </file>
  <file name="Bin\RICHTX32.OCX">
    <typelib tlbid="{3B7C8863-D78F-101B-B9B5-04021C009402}" version="1.2" flags="control" helpdir="" />
    <comClass clsid="{3B7C8860-D78F-101B-B9B5-04021C009402}" tlbid="{3B7C8863-D78F-101B-B9B5-04021C009402}" threadingModel="Apartment" progid="RICHTEXT.RichtextCtrl.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="Microsoft Rich Textbox Control 6.0 (SP6)" />
  </file>
  <file name="Bin\COMCT232.OCX">
    <typelib tlbid="{FE0065C0-1B7B-11CF-9D53-00AA003C9CB6}" version="1.1" flags="control" helpdir="" />
    <comClass clsid="{1E216240-1B7D-11CF-9D53-00AA003C9CB6}" tlbid="{FE0065C0-1B7B-11CF-9D53-00AA003C9CB6}" threadingModel="Apartment" progid="ComCtl2.Animation.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="Animation Control" />
    <comClass clsid="{026371C0-1B7C-11CF-9D53-00AA003C9CB6}" tlbid="{FE0065C0-1B7B-11CF-9D53-00AA003C9CB6}" threadingModel="Apartment" progid="ComCtl2.UpDown.1" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="UpDown Control" />
  </file>
  <file name="Bin\vbExtra3.ocx">
    <typelib tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" version="5.0" flags="control" helpdir="" />
    <comClass clsid="{D196D3D8-1007-4421-AF5A-01F51B964A8A}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.CommonDialogExObject" description="" />
    <comClass clsid="{BF2C1C77-FA75-419A-8ED5-CBCD324A00F9}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.FlexFnObject" description="" />
    <comClass clsid="{DF73A190-4030-47EE-9F6A-F0AF63D8EB84}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.PrintFnObject" description="" />
    <comClass clsid="{7201C9B2-C947-4776-8493-D58F7022FB7F}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.FlexFn" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{E8DED9AD-E305-444D-8FAE-38FD8FAD1AB8}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.ComboFn" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{2898443D-E4DE-4A46-BE4E-00C67F4CBDBE}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.PrintFn" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,invisibleatruntime,setclientsitefirst" description="" />
    <comClass clsid="{57FA960F-8610-4AA5-9D39-219AD8E31D8B}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.Global" description="" />
    <comClass clsid="{885F0325-0B91-41A3-A76E-FFC33EB0A7CA}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.GridReportStyle" description="" />
    <comClass clsid="{5397B78D-D9EB-44B8-8C48-5EEB5DD62F74}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.MouseWheelNotifierObject" description="" />
    <comClass clsid="{D4ECA034-4D32-47BC-BD8E-54EF1DD6C381}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.MouseWheelEnabler" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,invisibleatruntime,setclientsitefirst" description="" />
    <comClass clsid="{1AED693D-B09F-44F1-8E81-4FB1A3FCD97E}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.CommonDialogEx" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,invisibleatruntime,setclientsitefirst" description="" />
    <comClass clsid="{2576C886-C17B-4F79-869F-880A46965E9A}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.SmartConcat" description="" />
    <comClass clsid="{54A03B1B-4B20-41EE-993C-7D56B431310D}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.FormMinMax" description="" />
    <comClass clsid="{CFF8D9C1-3496-42AD-8C29-1ABE175C34A7}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.FontPicker" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{0EC4805E-F118-4671-BED1-48B1552140E3}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.ScrollableContainer" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,actslikelabel,alignable,simpleframe,setclientsitefirst" description="" />
    <comClass clsid="{F1DD194F-1229-4917-A05B-D2BFA69B428C}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.ButtonEx" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,actslikebutton,setclientsitefirst" description="" />
    <comClass clsid="{D90B8BA5-4BE6-491B-974A-6F52997142F3}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.ButtonExNoFocus" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,nouiactivate,setclientsitefirst" description="" />
    <comClass clsid="{D6DC4BB5-FE01-45A1-94BF-BD34A28BD1D3}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.History" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{D917A96E-4282-4A8B-9594-F2F0FD2F8F09}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.FontSizeChanger" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{2529E441-456E-4DDA-B925-52E86ACE4ADE}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.PopupList" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{9CC060BB-BC78-4360-A84C-E9BA1D3B270F}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.cSendKeys" description="" />
    <comClass clsid="{262E87CE-F556-41EF-9705-EDD398E08B71}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.ToolBarDA" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,nouiactivate,alignable,simpleframe,setclientsitefirst" description="" />
    <comClass clsid="{655889C1-83B9-4D7D-A2C4-816F10495AF9}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.TrayIcon" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,invisibleatruntime,nouiactivate,setclientsitefirst" description="" />
    <comClass clsid="{4BAFB94E-9BAB-4E1E-AB28-01249CDB5BB1}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.DTPickerEx" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{2EE20A39-5273-4B28-A76D-C3A34A7C0397}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.DateEnter" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{DCF916AE-6918-40DE-8903-6FA2248951C3}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.SizeGrip" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,nouiactivate,setclientsitefirst" description="" />
    <comClass clsid="{EF3E35A9-975A-4358-B46B-6C8A7DD13B13}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.TimerEx" description="" />
    <comClass clsid="{25F975F6-0282-498F-9E89-46CADAD1A797}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.SSTabEx" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,simpleframe,setclientsitefirst" description="" />
    <comClass clsid="{9B437B58-8A7A-4659-8E9B-9A1454E98F1C}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.cTimer" description="" />
    <comClass clsid="{F615B95B-B7C9-4252-B37D-9CDC513F21B1}" tlbid="{F22668DE-E08D-467B-8E41-13900013BD5F}" threadingModel="Apartment" progid="vbExtra.GSubclass" description="" />
  </file>
  <file name="Bin\BSPrin10.ocx">
    <typelib tlbid="{451B73A5-1563-45D5-A6AC-7B2B7D30B778}" version="2.0" flags="control" helpdir="" />
    <comClass clsid="{C4E98C24-F349-4D2B-A7D7-DF49994E208B}" tlbid="{451B73A5-1563-45D5-A6AC-7B2B7D30B778}" threadingModel="Apartment" progid="BSPrinter.Global" />
    <comClass clsid="{04E0110C-1F98-4908-8421-37D512A6425A}" tlbid="{451B73A5-1563-45D5-A6AC-7B2B7D30B778}" threadingModel="Apartment" progid="BSPrinter.GridReportStyle" />
    <comClass clsid="{09607631-1E0B-446C-B311-9D36D64316DA}" tlbid="{451B73A5-1563-45D5-A6AC-7B2B7D30B778}" threadingModel="Apartment" progid="BSPrinter.PrintPreview" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,invisibleatruntime,setclientsitefirst" />
  </file>
  <file name="Bin\TabExC01.ocx">
    <typelib tlbid="{EA478B61-D9EC-47F6-BB21-95A533AF2251}" version="1.1" flags="control" helpdir="" />
    <comClass clsid="{A1462394-2F1F-4B72-AABF-31DC289A86AE}" tlbid="{EA478B61-D9EC-47F6-BB21-95A533AF2251}" threadingModel="Apartment" progid="TabExCtl.SSTabEx" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,simpleframe,setclientsitefirst" description="" />
  </file>
  <file name="Bin\KComCtl1.ocx">
    <typelib tlbid="{38191A02-0F6C-4C3C-98D5-17428751CA6E}" version="1.0" flags="control" helpdir="" />
    <comClass clsid="{92832B28-EE31-4945-BB86-89A909FC7DBF}" tlbid="{38191A02-0F6C-4C3C-98D5-17428751CA6E}" threadingModel="Apartment" progid="KComCtl.CheckBoxW" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,setclientsitefirst" description="" />
    <comClass clsid="{EF6B3890-7E2F-4B92-8F91-BB41A49F98F5}" tlbid="{38191A02-0F6C-4C3C-98D5-17428751CA6E}" threadingModel="Apartment" progid="KComCtl.CommandButtonW" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,actslikebutton,setclientsitefirst" description="" />
    <comClass clsid="{EDB8035C-6882-434C-ACB8-0B2DB8D14099}" tlbid="{38191A02-0F6C-4C3C-98D5-17428751CA6E}" threadingModel="Apartment" progid="KComCtl.FrameW" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,actslikelabel,nouiactivate,simpleframe,setclientsitefirst" description="" />
  </file>
     <asmv3:application>
            <asmv3:windowsSettings  xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
                  <dpiAware>true</dpiAware>
           </asmv3:windowsSettings>
     </asmv3:application>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
        <requestedPrivileges>
          <requestedExecutionLevel level="asInvoker" uiAccess="false" />
        </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

Just some thoughts.

---

In all cases (well, except my home development computer), I run the EXE (and all the OCXs) from a server folder to which full permissions are granted (via a group) to all users who might use the program. And I've virtually never seen this problem, and a variety of Windows versions are using it everyday (in very much a multi-user fashion, typically 3 or 4 users [therapists] per site).

[Eduardo-]

Only DAO360.dll requires installing and registering, the others are protected system files.

Support Statement for Visual Basic 6.0 on Windows:
https://learn.microsoft.com/en-us/pr...support-policy


One issue that could cause this is System Restore. It would restore any recently installed EXE/DLL/OCX to the previous version, not sure if it would restore parts of the registry.

I once had a problem with one user because for some strange reason something misconfigured dao360.
Even after reinstalling Windows he had the same problem, and I was not able to determine what had caused this DAO misconfiguration on his machine, since he had very few programs, Google Earth being one of them I remember.

But the message was something else, not that error 429 ActiveX can't create object.

I just tried in my PC now to unregister dao 360 and I get another message.

Anyway, for that user that had that issue, I could solve it with a reg file, because just registering dao360.dll with RegSvr32.exe is not enough.
I had opened a thread here for that issue.

OK, for anyone needing to register dao360.dll, here is the reg file: RegDao360.zip

Ignore the error message, I left something not needed (that IDK what is it) but it works fine anyway.

That solved the issue with that user, that it seems different to this one now.

[Elroy]

Wow, I've never had any problems with DAO360.dll, and I use it extensively. Since about WinXP, it just seems to be there, and ready to go.

Also, I've never done anything in my manifest regarding DAO360, and I see you don't either. I'll make a note though about your prior problem (and grab the re-registration of it).

Regarding your manifest, I just really wanted to see your OCX paths (as you probably suspected), and they all look fine to me. In fact, the only differences between yours and mine is my subfolder is named "Dependencies", and your OCX set is different from mine.

If it were me, I'd sure have them re-install your program (with an un-install first, if that's possible). I researched the error (because it's worded a bit funny), but it clearly seems to be a problem with your program being unable to access and do instantiations from the specified OCX file.

I wish we knew for sure that it was one of your supplied/installed OCX files. Do you use any other ActiveX files that you just depend on being available? Do you do any automation?

[Eduardo-]

Wow, I've never had any problems with DAO360.dll, and I use it extensively. Since about WinXP, it just seems to be there, and ready to go.

I also use it extensively since Windows 98 and never had any issues...until that one user.
And it was the only case so far.

Also, I've never done anything in my manifest regarding DAO360, and I see you don't either. I'll make a note though about your prior problem (and grab the re-registration of it).

Before I could solve the issue in his machine re-registering DAO, I provided him with a temporary solution that was a special package of the program (exe + Bin folder) with DAO in SxS. That worked fine. But I would have to provide him with a special update just to him whenever was a new program version.
Or to start shipping DAO 360 in SxS for every user (and not just to him), but I was not sure about taking that route.
Well, then I could fix his machine with that reg file, and to date it had not be necessary to fix DAO on that PC again, or any other.

Regarding your manifest, I just really wanted to see your OCX paths (as you probably suspected), and they all look fine to me. In fact, the only differences between yours and mine is my subfolder is named "Dependencies", and your OCX set is different from mine.

If it were me, I'd sure have them re-install your program (with an un-install first, if that's possible). I researched the error (because it's worded a bit funny), but it clearly seems to be a problem with your program being unable to access and do instantiations from the specified OCX file.

That's is the first thing I instructed to do and the only one (before contacting me): to uninstall the program and install it again and test.
So far I have not feedback or contacted with the user (I have still not direct communication with her).

I wish we knew for sure that it was one of your supplied/installed OCX files. Do you use any other ActiveX files that you just depend on being available? Do you do any automation?

Do you mean using CreateObject / GetObject?

I recently added uses of WMI, something that didn't have before, lines like:

Set iDiskInfoObj = GetObject("winmgmts:").InstancesOf("Win32_DiskDrive")

        With GetObject("winmgmts:")
            For Each o In .ExecQuery("SELECT ProcessorID FROM Win32_Processor WHERE ProcessorID is NOT NULL")

And they are executed when the program starts.
Maybe WMI is disabled on that computer, I'm thinking now...

Edit: no, I think it can't be WMI disabled the cause because I have all those calls within On Error...

[qvb6]

When I was using XP around 8+ years ago, I installed a tool from a major microchip maker(silabs.com). It installed ADO and perhaps DAO, to a subfolder in the app folder, and registered those. It basically broke my system, had to do system restore.

You could make code to check the registry and get the DLL path from there, and either ask the user to tell you the full path and version, or get the info yourself before showing the first form. If it's not expected(like lower version than you shipped), then show a message to the user.

[Eduardo-]

When I was using XP around 8+ years ago, I installed a tool from a major microchip maker(silabs.com). It installed ADO and perhaps DAO, to a subfolder in the app folder, and registered those. It basically broke my system, had to do system restore.

You could make code to check the registry and get the DLL path from there, and either ask the user to tell you the full path and version, or get the info yourself before showing the first form. If it's not expected(like lower version than you shipped), then show a message to the user.

The DAO issue is a derivative talk (something that happened to another user in the past), it is 99.99% probable that has nothing to do with the current issue to this other user. And the message was something else, I think there was no message in that case, the program just crashed.

[Eduardo-]

Today I asked and they told me that a technician resolved the issue. I still don't know how but probably reinstalling the program (it is a guess, but I don't think he can do much more).

[Elroy]

Today I asked and they told me that a technician resolved the issue. I still don't know how but probably reinstalling the program (it is a guess, but I don't think he can do much more).

Hey, there have been MANY times that's happened to me ... and I never look a gift-horse in the mouth, typically deciding to put it out of my mind.

---

I once had an installation where certain computers in the building would lose their connection to the database (all on a LAN, no WAN nor internet). This went on for months. I kept saying to look at the switches back to the server, and possibly some switch ports, or maybe even ethernet cabling. They insisted they'd done all that. Then one day, they said the problem was fixed, but never explained what they did, and weren't even willing to. Ohhh, and in those intervening months, they did everything they could to blame my software.

[Eduardo-]

Hey, there have been MANY times that's happened to me ... and I never look a gift-horse in the mouth, typically deciding to put it out of my mind.

---

I once had an installation where certain computers in the building would lose their connection to the database (all on a LAN, no WAN nor internet). This went on for months. I kept saying to look at the switches back to the server, and possibly some switch ports, or maybe even ethernet cabling. They insisted they'd done all that. Then one day, they said the problem was fixed, but never explained what they did, and weren't even willing to. Ohhh, and in those intervening months, they did everything they could to blame my software.

But... the issue is that it should not happen. How that happened?
The installer automatically uninstalls the previous version (if the user didn't manually uninstalled it before), and installs the new one copying all the files... IDK.

For something so simple as reinstalling the program I would not open a thread here.
I will set it as resolved... because it is resolved and if in the future I know more details (and something relevant) I'll post it here.
Thank you all!

[Elroy]

It could have been something as simple as some I.T. guy who "thought" he knew what he was doing, went in and "updated" those OCX files in your BIN folder. If that's the case (or something similar), there's a good chance you'll never get a straight-answer that that's what happened.

This is one reason I wrap my OCX files into the EXE, and then check their versions each time my EXE fires up (and re-extract them if the version is wrong). But again, that means my program is sitting in a place to which the user has create/write permissions.

---

I once had to have an H.R. mediation session with an I.T. person who kept meddling around in a network in places they had no business meddling.

[Eduardo-]

It could have been something as simple as some I.T. guy who "thought" he knew what he was doing, went in and "updated" those OCX files in your BIN folder. If that's the case (or something similar), there's a good chance you'll never get a straight-answer that that's what happened.

That is highly unlikely or almost impossible. That user is a woman that is not IT (as far as I know *), and the installer is a single exe where you cannot choose what to extract or what to install, or what to overwrite or not.

This is one reason I wrap my OCX files into the EXE, and then check their versions each time my EXE fires up (and re-extract them if the version is wrong). But again, that means my program is sitting in a place to which the user has create/write permissions.

That is asking for trouble IMO. I guess AVs don't like that (file droppers, unless they are installers).

*) I really don't know, but if she was some IT person, she would not report the error in the first place, and less if she did something not normal (as decompressing the installer, and manually copying files).

PS: ah, do you mean the one technician who solved the issue?
I don't know what he did, still.

[Eduardo-]

Just to comment on this issue, at the end I could talk to the technician and the issue was that an AV program was blocking some file on the program installation (IDK which one, but I had recently updated an ocx).
It was something simple really, but I did not think about that.

[Elroy]

Just to comment on this issue, at the end I could talk to the technician and the issue was that an AV program was blocking some file on the program installation (IDK which one, but I had recently updated an ocx).
It was something simple really, but I did not think about that.

I'm glad you posted this. AVs, IMHO, are often just viruses in themselves, threading themselves deeply into the OS, doing things they shouldn't be doing, nagging users for updates and money. For years now, I've insisted that Microsoft Defender is all we need, and that all the rest of them are complete garbage.