Problem deploying Samsung Kies 2.3
Hey lads,
Recently I've faced some problems with deploying this type of application.
Samsung Kies_2.3.0.12035_16_4.exe generates 2 folders in %temp% location as show below.
The thing is that you won't be able to run Samsung Kies.msi directly without Setup.exe.
Anyway, there is a workaround...
I had to delete a few things from .MST file to be able to install that .MSI without setup.exe. NOTE: adding ISSETUPDRIVEN=1 as a new property didn't help in this situation.
(STANDARD_USE_SETUPEXE property and ISVerifyScriptingRuntime custom action)
After removing those values .MSI starts like a charm but it's where the second problem appears
After installation is complete there is no shortcuts in srtart menu/desktop and the sadest part is that Kies.exe is failing to start.
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: kies.exe
Problem Signature 02: 1.0.0.538
Problem Signature 03: 4f7589cf
Problem Signature 04: Kies
Problem Signature 05: 1.0.0.538
Problem Signature 06: 4f7589cf
Problem Signature 07: 25
Problem Signature 08: 0
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Original Samsung Kies_2.3.0.12035_16_4.exe during installation installs 3 components: 1) .NET 3.5 Framework SP1 2) SAMSUNG_USB_Driver_for_Mobile_Phones
3) Samsung Kies 2.3 itself.
Even after installing those 2 prerequisites program behaves the same way.
NOTE: I've tried to execute Setup.exe from 2nd folder that Samsung Kies_2.3.0.12035_16_4.exe creates and even that setup fails. Everytime I execute this setup.exe it gives an error that there is no Samsung Kies.msi file located in %temp%\{GUID} and everytime i start that setup.exe error shows unique {GUID}.
Any help would be appreciated
Thanks.
Answers (2)
I found this commandline in an old AppDeploy post:
Kies_2.2.0.12014_18_7.exe /L"1033" /S /v"ISALWAYSINSTALLELEVATED=1 /qn
it's for the previous version, but give it a go (especially the /S /v part)
If you absolutely must use the MSI directly, have you tried passing the transform that's with it on the commandline? Final option would be a gap capture, installing the naked msi, then capturing what gets added when you run the setup.exe over it.
Comments:
-
Hi,
Thanks for that information. Indeed, running .exe with /L"1033" /S /v"ISALWAYSINSTALLELEVATED=1 /qn command works like a charm. However, the goal is to deploy .MSI package. It seems that the gap capture method is the only way left? - Usualsuspect 12 years ago
First, System.IO.FileNotFoundException is a teensy-weensy clue-ette.
Second, the presence of an InstallShield Custom Action suggests that the MSI has a dependency on the InstallShield run-time/engine! Put that CA back, install the relevant version of the IS engine and then run the MSI again.
Comments:
-
Hey,
Putting CA back makes .MSI dependant on Setup.exe. Like I said previously- extracted Setup.exe also fails to install the program. So the goal is to deploy .MSI - Usualsuspect 12 years ago
