PM 2010 free - error 2739 even after regsvr32 jscript.dll

Discussion in 'Paragon Partition Manager Product Line' started by poutnikl, Aug 2, 2010.

Thread Status:
Not open for further replies.
  1. poutnikl

    poutnikl Registered Member

    Joined:
    Jul 11, 2010
    Posts:
    9
    I use Vista 64 Home Premium SP2.

    Normally I have no problems in MSI installations.
    But for PM2010free, when I have tried to install MSI instalation package,
    I get Error 2739.Could not access JavaScript run time for custom action .

    I have tried the solution what Google found in the faq: (run as administrator )
    first go to %systemroot\syswow64% folder (usually it's "C:\Windows\syswow64"): cd syswow64
    regsvr32 jscript.dll


    regsvr32 has said registration of dll was successful, but next installation trial produced the same error again.

    Edit: to be sure,I did the same in system32 folder, but it did not help.

    I guess windows scripting host should be present, running e.g. cscript shows Microsoft (R) Windows Script Host verze 5.7
     
    Last edited: Aug 2, 2010
  2. poutnikl

    poutnikl Registered Member

    Joined:
    Jul 11, 2010
    Posts:
    9
    Finally I got it working, by CLI execution of msiexec /i package.msi.
     
  3. Mech_An

    Mech_An Registered Member

    Joined:
    Mar 29, 2010
    Posts:
    855
    Open Command prompt.

    Then for Windows 32-bit run in Command prompt:
    regsvr32 jscript.dll

    For Windows 64-bit first go to %systemroot\syswow64% folder (usually it's "C:\Windows\syswow64"):
    cd syswow64
    regsvr32 jscript.dll
     
  4. poutnikl

    poutnikl Registered Member

    Joined:
    Jul 11, 2010
    Posts:
    9
    Hello,

    Thanks for reply.
    I am not sure, if you have read carefully enough the post you were replying to.
     
  5. poutnikl

    poutnikl Registered Member

    Joined:
    Jul 11, 2010
    Posts:
    9
    It looks that reason was not in jscript.dll registration, as far as the error persisted even if dll was registered successfully ( and i guess it was OK even before ).

    I think the root cause was I was executing context menu installation of MSI package in limited account, waiting for privilege escalation dialog. But it has never come, bringing error first. The error was displayed even after trial reinstalation of already installed PM 2010, if done from limited user account again.

    Instalation with msiexec from privileged cmd.exe, as far as context menu MSI instalation from admin account worked OK.
     
  6. Mech_An

    Mech_An Registered Member

    Joined:
    Mar 29, 2010
    Posts:
    855
    poutnikl

    Sorry :)
     
Loading...
Thread Status:
Not open for further replies.