Software Deployment Question

InstallShield setup.exe exited with error code -3

04/03/2018 2308 views

The Installshield-installer of Zebra_Scanner_SDK_(64bit)_v3.03.0002.exe, see link number one below, have a huge problem. Which is it wont run under or as local system account and I suspect it's the same error as on link 2, 3 and 4.

Therefore I can't deploy it to several computers in our environment with SystemCenter Configuration Manager and maybe have to go around to all of the computers and install it manually. Do any one know how to solve this problem?


View attached log - LocalSystemAccount_Debug_Install_Scanner_SDK_64bit_v3.03.0002.log









0 Comments   [ + ] Show comments


  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

All Answers

This content is currently hidden from public view.
Reason: Determined to be spam through moderation For more information, visit our FAQ's.
start the installation as an admin user on a "clean-machine". Let the pre-requisites be installed but DO NOT start the IS Installation. Look under the %temp% directory (in my case it was %Temp%\{BE1A43B4-D844-49B5-857D-4798E7DC76AA} and get hold of the the sdk msi (Zebra Scanner SDK (64bit).msi).
Once you have the sdk msi, open regedit and look for the Zebra entry in the uninstall area (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield_{13FE0819-1D27-4C6B-811F-F46548A255ED})
You then see the path that was used to install the driver... copy this msi (Zebra CoreScanner Driver (64bit).msi) and you have both the driver and the sdk. You then test to see if you can install the msi's individualy using the system account.

Answered 04/03/2018 by: Pressanykey
Red Belt

  • You could also try to look here... (C:\%UserName%l\AppData\Local\Downloaded Installations)
    • ...or C:\ProgramData\PackageCache\[GUID]
Hi Phil and VBScab
Thanks for your replies and suggestions. I just tried them out and got both the 'Zebra CoreScanner Driver (64bit).msi and Zebra Scanner SDK (64bit).msi' extracted, but unfortunately the 'Zebra CoreScanner Driver (64bit).msi' does not create the 'CoreScanner' Windows Service, which the Installshield-installer does.
Maybe I could create a transform file for the 'Zebra CoreScanner Driver (64bit).msi' which creates the CoreScanner service?
Answered 04/06/2018 by: TheDukeOfITNinja
White Belt

  • Hi, are you sure the serive is not created? Looking at the inf file from the driver it should...
    ; WinUSB service
    Include = winusb.inf
    AddService = WinUSB,0x00000002,winusb_add_service

    DisplayName = "WinUSB - Kernel Driver 05/12/2015"
    ServiceType = 1
    StartType = 3
    ErrorControl = 1
    ServiceBinary = %12%\WinUSB.sys
    • Hi Pressanykey

      Sorry for my very late answer.
      Yes I'm absolutely sure the CoreScanner service is not created after installing the extracted msi packages from the installshield package.
      Please try it your self?

      Powershell dump:

      Get-WmiObject -Class 'Win32_Product' | Where-Object -FilterScript {$_.Name -like '*Zebra*'}

      IdentifyingNumber : {13FE0819-1D27-4C6B-811F-F46548A255ED}
      Name : Zebra CoreScanner Driver (64bit)
      Vendor : Zebra Technologies
      Version : 3.03.0001
      Caption : Zebra CoreScanner Driver (64bit)

      IdentifyingNumber : {BE71481D-B530-456C-84BB-582E341E2995}
      Name : Zebra Scanner SDK (64bit)
      Vendor : Zebra Technologies
      Version : 3.03.0004
      Caption : Zebra Scanner SDK (64bit)

      Get-Service -Name 'Core*' | Format-Table -AutoSize

      Status Name DisplayName
      ------ ---- -----------
      Running CoreMessagingRegistrar CoreMessaging
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