Having issue with Verint Nextiva Codec software install in System Context. Returns Faulting application path error in system context. Please let me know if anyone has faced thisissue ?

I have this software verint Nextiva Codec which installs fine in User Context both with silent switches and manually by double clicking the exe but in System Context  Used psexec tool and SCCM Software Center install) it doesn't do anything in both and  Event Viewer records the below eveny for this application. has anyone faced this issue or can prodide feedback/suggestions on this ?

when vendor exe was extracted, it had setup.exe and setup.iss file but it behaves the same way like vendor exe. installs fine in user context and doesn't do anything in System context with Psexec tool.

on install of Vendor exe in user context, all it does is just registers some dlls in programfiles\vendor folder. I know we can repackage the software but here at my client repackage is the last option.

Things tried: 1) procmon - not helpful 2) I have set Public environment to all usersprofile in system context- not useful 3) copied the extracted folder to the systemprofile - not useful 4) gave full permissions to programfiles folder, program menu folder,  - not useful

Faulting application name: mmc.exe, version: 10.0.15063.0, time stamp: 0xc39bfa6e

Faulting module name: unknown, version:, time stamp: 0x00000000

Exception code: 0xc0000409

Fault offset: 0x0000000000000000

Faulting process id: 0x3750

Faulting application start time: 0x01d402b33052f21e

Faulting application path: C:\WINDOWS\system32\mmc.exe

Faulting module path: unknown

Report Id: b68680ed-a00c-4db7-8309-7c9e0b728b5f

Faulting package full name:

1 Comment   [ + ] Show comment
  • Those InstallShield setup.exe's are usually capable of writing a log file if you specify either the /f2 command line switch or, in later versions, the /debuglog command line switch. Also if it contains an embedded MSI you may also be able to output an MSI log file with the /V command line switch. I'd be checking that log file in the first instance if I was you.... - captain_planet 2 years ago
    • It's an InstallScript file and it doesn't contain embedded MSI. /f2 command line working only in user context while in system content it doesn't create any log file with /f2.
      /debuglog is not working in both user and system context.

      with /f2 command line in user context, it had the below information in the log file

      [InstallShield Silent]
      File=Log File
      Name=Nextiva Codec
      Lang=0409 - irfansherif 2 years ago

Answers (0)

Be the first to answer this question

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ