locked
Using OCX in ALT/COM server.. RRS feed

  • Question

  • Hi,

    Can anyone let me know if we can use the MSSCript.ocx in a COM server.

    When I add the MSSCript.ocx changes in my COM Server code ,my COM server is not registering using regsvr32 .

    I tried registering OCX also before registering my COM dll.

    Actually the flow is like this--> EXE->DLL->COM DLL->Using OCX



    Please help me on this...

    Thanks,


    • Edited by AbhiMFC Tuesday, April 5, 2016 11:40 AM
    Tuesday, April 5, 2016 10:27 AM

Answers

  • Can you register a COM server without the changes you made for MSScript.ocx?

    Have you tried registering your COM Server from an elevated command prompt if it registers for all users in HKLM?

    What were the "MSScript.ocx" changes in your com server code?

    Have you tried debugging the COM server's registration code?

    In the project's debugging options specify regsvr32.exe as the program to be executed and your DLL's name just as if you were running regsvr32 from the command line.

    Set a breakpoint in the DLLRegisterServer code so that you can step through the code to look for errors.

    • Proposed as answer by Hart Wang Friday, April 15, 2016 8:06 AM
    • Marked as answer by Hart Wang Monday, April 18, 2016 9:44 AM
    Wednesday, April 6, 2016 11:31 AM

All replies

  • Thanks for posting here.

    Try these steps:

    Use regsvr32.exe to re-register the dll, something like: regsvr32 msscript.ocx

    Hosting your web application into a 32-bit host, and copy a 32-bit msscript.ocx into folder ..\windows\syswow64 under 64-bit machine.

    Hope that could help.

    Wednesday, April 6, 2016 7:24 AM
  • Can you register a COM server without the changes you made for MSScript.ocx?

    Have you tried registering your COM Server from an elevated command prompt if it registers for all users in HKLM?

    What were the "MSScript.ocx" changes in your com server code?

    Have you tried debugging the COM server's registration code?

    In the project's debugging options specify regsvr32.exe as the program to be executed and your DLL's name just as if you were running regsvr32 from the command line.

    Set a breakpoint in the DLLRegisterServer code so that you can step through the code to look for errors.

    • Proposed as answer by Hart Wang Friday, April 15, 2016 8:06 AM
    • Marked as answer by Hart Wang Monday, April 18, 2016 9:44 AM
    Wednesday, April 6, 2016 11:31 AM