replacing old version of dcom with updated causing 429 Activex error

[den2005]

Hi,

It has been quite a long while I visited this site. I inherited a classic asp project that uses vb6 dll registered using regsvr32 and added in component services. I considers myself a newbie in classic asp and vb6. Here is scenario, when site uses previous version of dll, there is no 429 ActiveX cannot create issue but when I use modified dll it has this issue. I unregister old version and register new version, add it to component services. I even tried by cleaning up registry entries by deleting duplicate entries pointing to same dll file location. Inside the dll, it calls another dll which has not been modified or touched. Even tried unregister and register both these 2 dlls. Can anyone point where could be possible source of this issue? In the project properties, there is a component tab, there is Version Compatability. What would be effect if project or binary compatability is selected and compiled. Thanks in advanced.

[dilettante]

DCOM clearly isn't involved here if you are using regsvr32.

You are breaking binary compatibility. This isn't trivially "fixed" after the fact and it requires a bit of discipline while making changes.

The process is covered in the VB6 documentation, and there is also the:

Binary Compatibility Add-in at Additional Visual Basic 5.0 & 6.0 Samples

[den2005]

thanks for replying, dilettante. Aside from Binary Compatability, is there other possible cause for this issue?