MSI Error 1603 installing AppFabric 1.1 / Win7 x64
Posted on 2016-12-22 11:06 挥辉 阅读(781) 评论(0) 编辑 收藏 举报MSI Error 1603 installing AppFabric 1.1 / Win7 x64
I got exactly the same problem. In my case, there is a double quote at the end of "PSModulePath environ variable". After removing that "double quote", the installation succeeded.
Get into Regedit confirm that the path for PSModulePath environ variable is in its proper state.
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager/Enviroment/PSModulePath.
i had the same problem, and after lots of searching, i noticed my psmodulepath had a " at the end of the path.
i deleted it, and all started working like it should.
yours might not be the " , but look through all the paths in it just to be sure
--------------------------------------------------------------------------------------------
Question
-
0
I am receiving MSI Error Code 1603 trying to install AppFabric 1.1 Hosting. A month or so ago, I installed AppFabric 1.1 Caching, and it installed fine. My hunch is that some recent Windows Update caused this issue.
I am running Windows 7 Enterprise 64 bit. I previously had AppFabric 1.0 installed, and completely uninstalled it.
My coworker is having the exact same problem with the exact same history as me - except that she is only now installing AppFabric 1.1 - and only Caching (not Hosting).
Here is the error in the Windows Event Log (Setup). [The installation log file shows no more details than this.]
Microsoft.ApplicationServer.Setup.Core.SetupException: AppFabric installation failed because installer MSI returned with error code : 1603 at Microsoft.ApplicationServer.Setup.Installer.WindowsInstallerProxy.GenerateAndThrowSetupException(Int32 exitCode, LogEventSource logEventSource) at Microsoft.ApplicationServer.Setup.Installer.WindowsInstallerProxy.Invoke(LogEventSource logEventSource, InstallMode installMode, String packageIdentity, List`1 updateList, List`1 customArguments) at Microsoft.ApplicationServer.Setup.Installer.MsiInstaller.InstallSelectedFeatures() at Microsoft.ApplicationServer.Setup.Installer.MsiInstaller.Install() at Microsoft.ApplicationServer.Setup.Client.ProgressPage.StartAction()
Any help would be most appreciated. Thanks.
Thursday, May 03, 2012 8:18 PM
All replies
-
1
1603 is a generic MSI error, can you share the step at which it failed in the logs ?
Also, can you check the value of your PSModulepath environment variable ? We have seen in the past that a wrong value there sometimes throws.
Friday, May 04, 2012 4:39 AM
-
2
Ankit, thanks for your reply.
My PSModulePath seems fine:
PS C:\> $env:PSModulePath
C:\Users\U1FC11\Documents\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModulesBelow is an excerpt from my Detailed Installation report; followed by an excerpt from an even more detailed log that I found.
2012-05-04 12:52:43, Information Setup OS Name: Windows 7 Enterprise 2012-05-04 12:52:43, Information Setup OS Edition: Enterprise 2012-05-04 12:52:43, Information Setup OSVersion: Microsoft Windows NT 6.1.7600.0 2012-05-04 12:52:43, Information Setup CurrentCulture: en-US 2012-05-04 12:52:43, Information Setup Processor Architecture: AMD64 2012-05-04 12:52:43, Information Setup Event Registration Source : AppFabric_Setup 2012-05-04 12:52:43, Information Setup 2012-05-04 12:52:43, Information Setup Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : Initiating V1.0 Upgrade module. 2012-05-04 12:53:32, Information Setup Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : Initiating V1 Upgrade pre-install.