1603 Error WiseGetIISFeaturesEnabled PlannerRuntime 1.0
Hello,
i have a problem by installing a software (PlannerRuntime 1.0) over SCCM and the same in manual method.
Any idea whats the problem?
Server:
Citrix TS
2008R2 Enterprise
This ist the Log:
=== Protokoll gestartet: 18.11.2014 11:29:28 ===
Aktion 11:29:28: INSTALL.
Aktion gestartet 11:29:28: INSTALL.
Aktion 11:29:28: WiseGetIISFeaturesEnabled.
Aktion gestartet 11:29:28: WiseGetIISFeaturesEnabled.
CustomAction WiseGetIISFeaturesEnabled returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Aktion beendet 11:29:28: WiseGetIISFeaturesEnabled. Rückgabewert 3.
Aktion 11:29:28: Fatal_Error.
Aktion gestartet 11:29:28: Fatal_Error.
Info 2898. For MSSansSerif8 textstyle, the system created a 'MS Sans Serif' font, in 1 character set, of 13 pixels height.
Aktion 11:29:28: Fatal_Error. Dialog created
Aktion beendet 11:29:28: Fatal_Error. Rückgabewert 2.
Aktion beendet 11:29:28: INSTALL. Rückgabewert 3.
=== Protokoll beendet: 18.11.2014 11:29:28 ===
MSI (c) (68:0C) [11:29:28:857]: Produkt: Planner Runtime 1.0 -- Installation fehlgeschlagen.
MSI (c) (68:0C) [11:29:28:862]: Das Produkt wurde durch Windows Installer installiert. Produktname: Planner Runtime 1.0. Produktversion: 4.1.4. Produktsprache: 1031. Hersteller: SIEDA GmbH, Kaiserslautern. Erfolg- bzw. Fehlerstatus der Installation: 1603.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
10 years ago
- Firstly, please edit your post and use the 'Code' style for the log text.
- Secondly, the 1603 error is a classic Microsoft "something went wrong, we don't know what, but have to tell you something" error and is too generic to be any real value. However, the fact that it was tripped by the Custom Action 'WiseGetIISFeaturesEnabled' prompts me to ask whether or not IIS is installed/set up on the target machine.
If the app doesn't need IIS, disable that CA's execution by adding an impossible-to-meet condition - I like to use '0=1' - in the 'Conditions' column for the CA in the 'InstallExecuteSequence' table.
- Secondly, the 1603 error is a classic Microsoft "something went wrong, we don't know what, but have to tell you something" error and is too generic to be any real value. However, the fact that it was tripped by the Custom Action 'WiseGetIISFeaturesEnabled' prompts me to ask whether or not IIS is installed/set up on the target machine.
If the app doesn't need IIS, disable that CA's execution by adding an impossible-to-meet condition - I like to use '0=1' - in the 'Conditions' column for the CA in the 'InstallExecuteSequence' table.
Posted by:
EdT
10 years ago
Is this application being installed to a Citrix server for remote execution? It would be helpful to clarify what the target system is for this installation.
As for the error message, VBScab is correct in his assessment. It would appear that there might be a dependency on IIS being enabled. So the next step is to consult the vendor documentation and check for any pre-requisites that the software requires. Since you are getting the same error on a manual install, it certainly appears that your target environment is not adequate for the installation of this software, or the software is badly written and you need to contact the vendor for further assistance.
Comments:
-
i think so too
i check in next day's all requirements for this software. i figured out with wisepackager that their need "windows installer runtime 1.2" or higher, after i have changed it in "every Version" the installation was fine. - transporter1989 10 years ago
