I'm installing Blackberry Desktop 4.0.1.10 (4.0 SP1) using Setup.exe and Setup.ini. If I run the install manually and step through the screens with the default settings, it installs successfully and reports that in the Application log. If I run it with a Setup.exe /s, everything appears to install, but the MSI log and application log report that setup failed. Below is an excerpt from the verbose log (I've bolded what appears to be the problem):

Action ended 16:41:33: ISSetupFilesCleanup. Return value 1.
MSI (s) (24:44): Skipping action: RIM_InstallShellFolderUpdate (condition is false)
MSI (s) (24:44): Skipping action: RIM_InstallCommonControlsUpdate (condition is false)
MSI (s) (24:44): Doing action: RIM_DeleteConnInstallCfgPath
Action start 16:41:33: RIM_DeleteConnInstallCfgPath.
MSI (s) (24:44): Creating MSIHANDLE (896) of type 790542 for thread 2372
Action ended 16:41:33: RIM_DeleteConnInstallCfgPath. Return value 3.

MSI (s) (24:44): Doing action: ISCleanUpFatalExit
Action start 16:41:33: ISCleanUpFatalExit.
MSI (s) (24:44): Creating MSIHANDLE (897) of type 790542 for thread 2372
1: Shutting down the PRC server...
1: RPC server shut down.
Action ended 16:41:33: ISCleanUpFatalExit. Return value 1.
Action ended 16:41:33: INSTALL. Return value 3.

At the end of the log:
=== Logging stopped: 7/21/2005 16:41:34 ===
MSI (s) (24:44): Note: 1: 1708
MSI (s) (24:44): Product: BlackBerry Desktop Software 4.0.1 -- Installation operation failed.

MSI (s) (24:44): Cleaning up uninstalled install packages, if any exist
MSI (s) (24:44): MainEngineThread is returning 1603
MSI (c) (2C:34): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (2C:34): MainEngineThread is returning 1603
=== Verbose logging stopped: 7/21/2005 16:41:34 ===


I need to push this out through SMS and don't want to push it with a log reporting failure. Anyone else encounter a similar problem? Again, everything works and the log reports success if run manually, it's logging failure only when I try running it with a /s. Thanks for any input.

Arlo
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I encountered the exact same problem.

I ended up applying an MST so that the return code of this custom action is ignored and the whole install returns successful.
Answered 07/29/2005 by: packager999
Yellow Belt

Please log in to comment
0
Does anybody have an insight as to why this is happening? What is causing the application to return 1708?
Answered 09/27/2005 by: aramakris21
Senior Yellow Belt

Please log in to comment
0
I was having the same problem and I found a solution from the BlackBerry site:
http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/8021/728075/728944/728556/Known_Issues_-_Failed_to_Initialize_script_support_and_unable_to_delete_registry_key_during_cleanup.html?nodeid=1106182&vernum=3

In a nutshell, the support people tell you to open their main installation MSI file (I used Wise Package Studio) and edit the custom action RIM_DeleteConnInstallCfgPath, change the value from 1 to 65. Save your MSI file and do your silent install. The Event Viewer Application log now shows Blackberry 4.0.1 installation completed successfully.

Hope this helps everyone.
Answered 01/25/2006 by: the.fly
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity