Installation problem, MSI error 1603, Win 7 x64, AppFabric 1.1

Question

Trying to install AppFabric 1.1 on a Win7 Ultimate x64 machine. Getting an MSI error 1603.

Sorry for the long post, but here's the setup log:

2012-03-22 16:22:07, Information           Setup  ===== Logging started: 2012-03-22 16:22:07-07:00 =====
2012-03-22 16:22:07, Information           Setup  File:             c:\0e9a9a31bbd44130682d3b3d320c9b\setup.exe
2012-03-22 16:22:07, Information           Setup  InternalName:     Setup.exe
2012-03-22 16:22:07, Information           Setup  OriginalFilename: Setup.exe
2012-03-22 16:22:07, Information           Setup  FileVersion:      1.1.2106.32
2012-03-22 16:22:07, Information           Setup  FileDescription:  Setup.exe
2012-03-22 16:22:07, Information           Setup  Product:          Microsoft(R) Windows(R) Server AppFabric
2012-03-22 16:22:07, Information           Setup  ProductVersion:   1.1.2106.32
2012-03-22 16:22:07, Information           Setup  Debug:            False
2012-03-22 16:22:07, Information           Setup  Patched:          False
2012-03-22 16:22:07, Information           Setup  PreRelease:       False
2012-03-22 16:22:07, Information           Setup  PrivateBuild:     False
2012-03-22 16:22:07, Information           Setup  SpecialBuild:     False
2012-03-22 16:22:07, Information           Setup  Language:         Language Neutral
2012-03-22 16:22:07, Information           Setup  
2012-03-22 16:22:07, Information           Setup  OS Name:                   Windows 7 Ultimate
2012-03-22 16:22:07, Information           Setup  OS Edition:                Ultimate
2012-03-22 16:22:07, Information           Setup  OSVersion:                 Microsoft Windows NT 6.1.7601 Service Pack 1
2012-03-22 16:22:07, Information           Setup  CurrentCulture:            en-US
2012-03-22 16:22:07, Information           Setup  Processor Architecture:    AMD64
2012-03-22 16:22:07, Information           Setup  Event Registration Source :    AppFabric_Setup
2012-03-22 16:22:07, Information           Setup  
2012-03-22 16:22:07, Information           Setup  Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : Initiating V1.0 Upgrade module.
2012-03-22 16:22:07, Information           Setup  Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : V1.0 is not installed.
2012-03-22 16:22:54, Information           Setup  Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : Initiating V1 Upgrade pre-install.
2012-03-22 16:22:54, Information           Setup  Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : V1.0 is not installed, not taking backup.
2012-03-22 16:22:54, Information           Setup  Enumerating Windows features
2012-03-22 16:22:56, Information           Setup  Process.Start: C:\Windows\system32\msiexec.exe /quiet /norestart /i "c:\0e9a9a31bbd44130682d3b3d320c9b\Microsoft CCR and DSS Runtime 2008 R3.msi" /l*vx "d:\temp\AppServerSetup1_1(2012-03-22 16-22-56).log"
2012-03-22 16:22:57, Information           Setup  Process.ExitCode: 0x00000000
2012-03-22 16:22:57, Information           Setup  Windows features successfully enabled.
2012-03-22 16:22:57, Information           Setup  Process.Start: C:\Windows\system32\msiexec.exe /quiet /norestart /i "c:\0e9a9a31bbd44130682d3b3d320c9b\Packages\AppFabric-1.1-for-Windows-Server-64.msi" ADDDEFAULT=CacheService,CacheClient,CacheAdmin,Setup /l*vx "d:\temp\AppServerSetup1_1(2012-03-22 16-22-57).log" LOGFILE="d:\temp\AppServerSetup1_1_CustomActions(2012-03-22 16-22-57).log" INSTALLDIR="C:\Program Files\AppFabric 1.1 for Windows Server" LANGID=en-US
2012-03-22 16:23:02, Information           Setup  Process.ExitCode: 0x00000643
2012-03-22 16:23:02, Error                 Setup  AppFabric installation failed because installer MSI returned with error code : 1603
2012-03-22 16:23:02, Error                 Setup  
2012-03-22 16:23:02, Error                 Setup  AppFabric installation failed because installer MSI returned with error code : 1603
2012-03-22 16:23:02, Error                 Setup  
2012-03-22 16:23:02, Information           Setup  Microsoft.ApplicationServer.Setup.Core.SetupException: AppFabric installation failed because installer MSI returned with error code : 1603
2012-03-22 16:23:02, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.WindowsInstallerProxy.GenerateAndThrowSetupException(Int32 exitCode, LogEventSource logEventSource)
2012-03-22 16:23:02, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.WindowsInstallerProxy.Invoke(LogEventSource logEventSource, InstallMode installMode, String packageIdentity, List`1 updateList, List`1 customArguments)
2012-03-22 16:23:02, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.MsiInstaller.InstallSelectedFeatures()
2012-03-22 16:23:02, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.MsiInstaller.Install()
2012-03-22 16:23:02, Information           Setup     at Microsoft.ApplicationServer.Setup.Client.ProgressPage.StartAction()
2012-03-22 16:23:02, Information           Setup  
2012-03-22 16:23:02, Information           Setup  === Summary of Actions ===
2012-03-22 16:23:02, Information           Setup  Required Windows components :  Completed Successfully
2012-03-22 16:23:02, Information           Setup  Microsoft .NET Framework 3.5.1 :  Completed Successfully
2012-03-22 16:23:02, Information           Setup  Microsoft CCR and DSS Runtime 2008 R3 :  Completed Successfully
2012-03-22 16:23:02, Information           Setup  AppFabric 1.1 for Windows Server :  Failed
2012-03-22 16:23:02, Information           Setup  Caching Services :  Failed
2012-03-22 16:23:02, Information           Setup  Cache Client :  Failed
2012-03-22 16:23:02, Information           Setup  Cache Administration :  Failed
2012-03-22 16:23:02, Information           Setup  Microsoft Update :  Skipped
2012-03-22 16:23:02, Information           Setup  Microsoft Update :  Skipped
2012-03-22 16:23:02, Information           Setup  
2012-03-22 16:23:02, Information           Setup  ===== Logging stopped: 2012-03-22 16:23:02-07:00 =====

I also found a few error lines in another install log:

SI (s) (88:28) [16:23:01:125]: Note: 1: 1722 2: SCW_Localize_i 3: c:\Program Files\AppFabric 1.1 for Windows Server\Microsoft.ApplicationServer.InstallHelper.exe 4: "powershell.exe" "-command \"$content = Get-Content \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\\\"; $content = ForEach-Object -InputObject $content { $_ -replace \\\"INSTALLPATH\\\", \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\\\\\\" }; Set-Content -value $content -path \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\\\" \"" "d:\temp\AppServerSetup1_1_CustomActions(2012-03-22 16-22-57).log" 
CustomAction SCW_Localize_i returned actual error code -2 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (88:28) [16:23:01:125]: Product: AppFabric 1.1 for Windows Server -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action SCW_Localize_i, location: c:\Program Files\AppFabric 1.1 for Windows Server\Microsoft.ApplicationServer.InstallHelper.exe, command: "powershell.exe" "-command \"$content = Get-Content \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\\\"; $content = ForEach-Object -InputObject $content { $_ -replace \\\"INSTALLPATH\\\", \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\\\\\\" }; Set-Content -value $content -path \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\\\" \"" "d:\temp\AppServerSetup1_1_CustomActions(2012-03-22 16-22-57).log" 


Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action SCW_Localize_i, location: c:\Program Files\AppFabric 1.1 for Windows Server\Microsoft.ApplicationServer.InstallHelper.exe, command: "powershell.exe" "-command \"$content = Get-Content \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\\\"; $content = ForEach-Object -InputObject $content { $_ -replace \\\"INSTALLPATH\\\", \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\\\\\\" }; Set-Content -value $content -path \\\"c:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\\\" \"" "d:\temp\AppServerSetup1_1_CustomActions(2012-03-22 16-22-57).log" 

Can anyone provide help to get this installed?

Thanks!

Answer 1

1603 is a very generic MSI error.

Is the second log you provided part of d:\temp\AppServerSetup1_1_CustomActions(2012-03-22 16-22-57).log ? , If not can you dump that log here ?

Looks like a custom action is failing, would have to look into the custom action to help debug further.

Answer 2

I am facing the same 1603 error trying to install AppFabric cache on my Windows 7 Enterprise x64.

Tried to add features (Caching Services / Cache Administration)

AppServerSetup.log

2012-03-23 14:27:41, Information           Setup  ===== Logging started: 2012-03-23 14:27:41+01:00 =====
2012-03-23 14:27:41, Information           Setup  File:             D:\dev\Install\setup.exe
2012-03-23 14:27:41, Information           Setup  InternalName:     Setup.exe
2012-03-23 14:27:41, Information           Setup  OriginalFilename: Setup.exe
2012-03-23 14:27:41, Information           Setup  FileVersion:      1.1.2106.32
2012-03-23 14:27:41, Information           Setup  FileDescription:  Setup.exe
2012-03-23 14:27:41, Information           Setup  Product:          Microsoft(R) Windows(R) Server AppFabric
2012-03-23 14:27:41, Information           Setup  ProductVersion:   1.1.2106.32
2012-03-23 14:27:41, Information           Setup  Debug:            False
2012-03-23 14:27:41, Information           Setup  Patched:          False
2012-03-23 14:27:41, Information           Setup  PreRelease:       False
2012-03-23 14:27:41, Information           Setup  PrivateBuild:     False
2012-03-23 14:27:41, Information           Setup  SpecialBuild:     False
2012-03-23 14:27:41, Information           Setup  Language:         Language Neutral
2012-03-23 14:27:41, Information           Setup  
2012-03-23 14:27:41, Information           Setup  OS Name:                   Windows Vista (TM) Ultimate
2012-03-23 14:27:41, Information           Setup  OS Edition:                Enterprise
2012-03-23 14:27:41, Information           Setup  OSVersion:                 Microsoft Windows NT 6.1.7601 Service Pack 1
2012-03-23 14:27:41, Information           Setup  CurrentCulture:            de-CH
2012-03-23 14:27:41, Information           Setup  Processor Architecture:    AMD64
2012-03-23 14:27:41, Information           Setup  Event Registration Source :    AppFabric_Setup
2012-03-23 14:27:41, Information           Setup  
2012-03-23 14:27:41, Information           Setup  Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : Initiating V1.0 Upgrade module.
2012-03-23 14:29:19, Information           Setup  Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : Initiating V1 Upgrade pre-install.
2012-03-23 14:29:19, Information           Setup  Microsoft.ApplicationServer.Setup.Upgrade.V1UpgradeSetupModule : V1.0 is not installed, not taking backup.
2012-03-23 14:29:19, Information           Setup  Enumerating Windows features
2012-03-23 14:29:21, Information           Setup  Process.Start: C:\Windows\system32\msiexec.exe /quiet /norestart /i "D:\dev\Install\Microsoft CCR and DSS Runtime 2008 R3.msi" /l*vx "C:\Users\fbe\AppData\Local\Temp\AppServerSetup1_1(2012-03-23 14-29-21).log"
2012-03-23 14:29:22, Information           Setup  Process.ExitCode: 0x00000000
2012-03-23 14:29:22, Information           Setup  Windows features successfully enabled.
2012-03-23 14:29:22, Information           Setup  Process.Start: C:\Windows\system32\msiexec.exe /quiet /norestart /i "{96E70525-4CD1-4920-9C0B-91055C79A962}" ADDDEFAULT=CacheService,CacheAdmin,Setup /l*vx "C:\Users\fbe\AppData\Local\Temp\AppServerSetup1_1(2012-03-23 14-29-22).log" LOGFILE="C:\Users\fbe\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2012-03-23 14-29-22).log" INSTALLDIR="C:\Program Files\AppFabric 1.1 for Windows Server\" LANGID=en-US
2012-03-23 14:29:28, Information           Setup  Process.ExitCode: 0x00000643
2012-03-23 14:29:28, Error                 Setup  AppFabric installation failed because installer MSI returned with error code : 1603
2012-03-23 14:29:28, Error                 Setup  
2012-03-23 14:29:28, Error                 Setup  AppFabric installation failed because installer MSI returned with error code : 1603
2012-03-23 14:29:28, Error                 Setup  
2012-03-23 14:29:28, Information           Setup  Microsoft.ApplicationServer.Setup.Core.SetupException: AppFabric installation failed because installer MSI returned with error code : 1603
2012-03-23 14:29:28, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.WindowsInstallerProxy.GenerateAndThrowSetupException(Int32 exitCode, LogEventSource logEventSource)
2012-03-23 14:29:28, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.WindowsInstallerProxy.Invoke(LogEventSource logEventSource, InstallMode installMode, String packageIdentity, List`1 updateList, List`1 customArguments)
2012-03-23 14:29:28, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.MsiInstaller.InstallSelectedFeatures()
2012-03-23 14:29:28, Information           Setup     at Microsoft.ApplicationServer.Setup.Installer.MsiInstaller.Install()
2012-03-23 14:29:28, Information           Setup     at Microsoft.ApplicationServer.Setup.Client.ProgressPage.StartAction()
2012-03-23 14:29:28, Information           Setup  
2012-03-23 14:29:28, Information           Setup  === Summary of Actions ===
2012-03-23 14:29:28, Information           Setup  Required Windows components :  Completed Successfully
2012-03-23 14:29:28, Information           Setup  Microsoft .NET Framework 3.5.1 :  Completed Successfully
2012-03-23 14:29:28, Information           Setup  Microsoft CCR and DSS Runtime 2008 R3 :  Completed Successfully
2012-03-23 14:29:28, Information           Setup  AppFabric 1.1 for Windows Server :  Failed
2012-03-23 14:29:28, Information           Setup  Caching Services :  Failed
2012-03-23 14:29:28, Information           Setup  Cache Administration :  Failed
2012-03-23 14:29:28, Information           Setup  Microsoft Update :  Skipped
2012-03-23 14:29:28, Information           Setup  Microsoft Update :  Skipped
2012-03-23 14:29:28, Information           Setup  
2012-03-23 14:29:28, Information           Setup  ===== Logging stopped: 2012-03-23 14:29:28+01:00 =====

More log:

....
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action Env_PSModulePath_powershell_i, location: C:\Program Files\AppFabric 1.1 for Windows Server\Microsoft.ApplicationServer.InstallHelper.exe, command: powershell.exe "-command \"$str = [System.Environment]::GetEnvironmentVariable(\\\"PSModulePath\\\", [System.EnvironmentVariableTarget]::Machine); $str = $str+\\\";C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\\\"; C:\Windows\system32\setx.exe /M PSModulePath \\\"$str\\\"\"" "C:\Users\xxx\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2012-03-23 14-29-22).log" 
...

Property(S): SourcedirProduct = {96E70525-4CD1-4920-9C0B-91055C79A962}
MSI (s) (70:CC) [14:29:28:091]: Note: 1: 1729 
MSI (s) (70:CC) [14:29:28:091]: Product: AppFabric 1.1 for Windows Server -- Configuration failed.


MSI (s) (70:CC) [14:29:28:091]: Windows Installer reconfigured the product. Product Name: AppFabric 1.1 for Windows Server. Product Version: 1.1.2106.32. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.

Answer 3

Removing the Environment variable PSModulePath solved the problem

Answer 4

The PSModule path issue is sometimes hit during installation ,the problem is usually caused by PSModule path which is not escaped properly, if you have a PSmodule path escaped properly and still giving this issue let us know.

Removing PSModulepath may cause other apps to start throwing errors when they are unable to load their powershell modules, if you can spot the error and fix it in the path, thats better.

Answer 5

I renamed the environment variable PSModulepath and tried to install again. Still did not work.

Did a little more looking at the logs and the issue was that powershell.exe was not in the path so it couldn't be found during installation. Added it to the path and the install worked.

Answer 6

Hi Rick

I am having the exact same problem. However I have checked the PATH variable and Powershell is there and I have no problem running it manually. But the Custom Action Server, as part of the install, can't find it. So I am stuck... Where did you add Powershell to the PATH and for which user...?

Thanks

Answer 7

Hi Rick

I am having the exact same problem. However I have checked the PATH variable and Powershell is there and I have no problem running it manually. But the Custom Action Server, as part of the install, can't find it. So I am stuck... Where did you add Powershell to the PATH and for which user...?

Thanks

Does running powershell from cmd work ?

Can you dump the logs and the path variable here ?

Answer 8

Hi Ankit,

This is the Custom Actions Server error log (which I think is the main cause of the problem).

26/03/2012 12:25:14 EXEPATH=powershell.exe PARAMS=-command "$content = Get-Content \"C:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\"; $content = ForEach-Object -InputObject $content { $_ -replace \"INSTALLPATH\", \"C:\Program Files\AppFabric 1.1 for Windows Server\\\" }; Set-Content -value $content -path \"C:\Program Files\AppFabric 1.1 for Windows Server\\AppFabricServer.xml\" " LOGFILE=C:\Users\STurner\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2012-03-26 12-24-50).log
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Microsoft.ApplicationServer.InstallHelper.Utility.LaunchProcess(String file, String args, DataReceivedEventHandler errorHandler, DataReceivedEventHandler outHandler)
   at Microsoft.ApplicationServer.InstallHelper.Program.InvokeExternalCommand(String[] args)
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Microsoft.ApplicationServer.InstallHelper.Utility.LaunchProcess(String file, String args, DataReceivedEventHandler errorHandler, DataReceivedEventHandler outHandler)
   at Microsoft.ApplicationServer.InstallHelper.Program.InvokeExternalCommand(String[] args)
ExitCode=-2

Powershell works just fine everywhere else; from CMD and as part of other installs (SharePoint local install etc).

As for the PATH... The following is in the system variables PATH.

                %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

Any thoughts..?

Thanks.

Answer 9

I added this to my PATH:

%SystemRoot%\system32\WindowsPowerShell\v1.0

Is it possible that you are running the install program as Admin and it's not in the path for the Administrator?

The error you are getting is exactly the one that lead me to adding the above to my path because the install program couldn't find pwershell.exe.

Answer 10

Hi Rick

Yes. I have checked the Admin account. I have also run the install as a couple of other accounts, all of which can run Powershell normally (from cmd). But I am still stuck.

However, I am certain this is the route cause of the problem. The issue is working out which account to correct. The only thing I can assume is that the Custom Action Server is run as a different account on this machine.

By the way I have sucessfully installed AppFabric 1.1 on another machine with no problem. It is just this one machine (which I need to work unfortunately).,....

Thanks again

Answer 11

Just ran into the same problem. My problem was due to the PSModulePath.

I checked the  custom Actions log which showed this

09/04/2012 3:18:28 PM EXEPATH=powershell.exe PARAMS=-command "$str = [System.Environment]::GetEnvironmentVariable(\"PSModulePath\", [System.EnvironmentVariableTarget]::Machine); $str = $str+\";c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\"; c:\Windows\system32\setx.exe /M PSModulePath \"$str\"" LOGFILE=C:\Users\Walter\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2012-04-09 15-18-05).log
Error: ERROR: Invalid syntax. Default option is not allowed more than '2' time(s).
Error: Type "SETX /?" for usage.

 I had also just installed SQL Server 2012 and looking at my PsModulePath,  that install looks to have added in a second path.  C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files
(x86)\Microsoft SQLServer\110\Tools\PowerShell\Modules

So I removed  this reference to the SQL server module and reran the install this time I had a successful install.

Answer 12

I have the same problem................add the pah   %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ to variable path..........it work for me

Answer 13

Hi,

Thanks for all the ideas, but I have finally fixed it. I check the PsModulesPath and that was actually fine. Powershell has always been in the Path and runs fine from CMD and everywhere else.

The problem was one of those obscure situations that I will remember for a long time.

I am running on a lenovo T520 with dual graphics cards, an on-board intel and a dedicated nVidia card. The nVidia card comes with drivers and services that allow you to switch between the two cards. There was a bug that meant that when it switched cards the service was over writing the whole of the Path environment variable.

I upgraded to the latest version of the nVidia drivers and all is great and AppFabric 1.1 installs just fine....

Thanks

Answer 14

Hi all. After a long period of analisys, I've found the solution and the probably cause of the error.

Every time that I tried to reinstall the AppFabric, I got the following:

Executing action : Microsoft.ApplicationServer.InstallHelper.FirewallExceptionAction

13/07/2012 11:25:56 EXEPATH=powershell.exe PARAMS=-command "$str = [System.Environment]::GetEnvironmentVariable(\"PSModulePath\", [System.EnvironmentVariableTarget]::Machine); $str = $str+\";C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\"; C:\Windows\system32\setx.exe /M PSModulePath \"$str\"" LOGFILE=D:\Users\lcmas_001\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2012-07-13 11-25-19).log

Error: ERROR: Invalid syntax.

Default option is not allowed more than '2' time(s).

Error: Type "SETX /?" for usage.

ExitCode=1

Well. Taking a look in the code, it concatenates the Enviroment Variable with more data. Write?

Looking at enviroment variable (HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager/Enviroment/PSModulePath), I have:

;C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Powershell\Modules

And the app increase the value with: ;C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules

To solve the question, I have deleted the PSModulePath variable from Enviroment Variables. Simple.

After that, everything worked fine.

I belive the problem is at "Variable disposing" when unistalling and in the logic for concat the values.

Regards

---

[MSP RJ] Lucas Massena

---

[MSP RJ] Lucas Massena

Answer 15

Hi there,

In my case it turned out that the following had been added to the PSModulePath:

C:\Program Files (x86)\Microsoft SDKs\Windows Azure\PowerShell\

When I removed it the installer Custom Actions completed fine and the install was successful.

In turn I reset the PSModulePath so that the Azure SDK wouldn't be upset  :-)

Rgds,

P.

Answer 16

I had a similar problem

9/21/2012 11:28:01 AM EXEPATH=powershell.exe PARAMS=-command "$str = [System.Environment]::GetEnvironmentVariable(\"PSModulePath\", [System.EnvironmentVariableTarget]::Machine); $str = $str+\";c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\"; c:\Windows\system32\setx.exe /M PSModulePath \"$str\"" LOGFILE=C:\Users\amccool.PCTS\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2012-09-21 11-27-26).log
Error: ERROR: Invalid syntax. Default option is not allowed more than '2' time(s).
Error: Type "SETX /?" for usage.

My issue was the PSModulePath having an improper " in it

it was:

C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules"

removing it corrected the issue

Answer 17

In my case i had caching service configured first.  First i uninstalled the caching and re-installed the appfabric hosting and caching together it worked.  I still dont know the exact cause of the problem.

Answer 18

I fixed this error in my deployment. It only occured for me if I had run the installer once before. As soon as you start the Installer, it will create a temporary folder. Copy that folder and save it off with a different name. Now cancel that install.

Open Regedit and search (CTRL+F) for "AppFabric". You should find an entry under HKEY_CLASSES_ROOT\Installer\Products{SomeStringOfCharacters}. Under that check SourceList it will have a Key called LastUsedSource. Update the folder path within it to match the temporary folder we just saved off. Also check SourceList/Net. It will likely have multiple keys with numeric Names. Make sure the Data value for them match your temporary folder path as well.

Now go into your temporary folder and run Setup.exe. It should complete now. I've seen behavior like this with other installers that first extract files to a temporary folder. Re-running the installer mostly works from the new temporary folder but some aspect of it holds on to the old temporary folder in the registry and tries to load something up from the old location.

---

Matt Poland - Manager of Application Development

Answer 19

I'm doing an offline SharePoint2013 install on Server2012 with SQL2012.  I had tried 1st manually installing AppFabric, but started running into the error during my SharePoint PreRequisiteChecker that it wasn't configured, so I thought I'd remove it and re-run the checker....

I ended up renaming my PSModulePath env var to psmodulepath2, running the PreRequisiteChecker again, then after it completed copying contents of new PSModulePath (which is only the appfabric path) to PSModulePath2, deleting the PSModulePath then renaming PSModulePath2 to PSModulePath...  Hope this helps somebody :-)

 Below are the errors posted in my log: C:\Users\jeharris\AppData\Local\Temp>notepad "AppServerSetup(2013-02-22 00-35-37).log"

2013-02-22 00:35:39, Information           Setup  Process.Start: C:\Windows\system32\msiexec.exe /quiet /norestart /i "d:\cfb1f46696df8cc9fb98ccdfa7ece2c6\Packages\AppFabric-1.1-for-Windows-Server-64.msi" ADDDEFAULT=CacheService,CacheClientGac,CacheClient,CacheAdminGac,CacheAdmin,Setup /l*vx "C:\Users\jeharris\AppData\Local\Temp\AppServerSetup1_1(2013-02-22 00-35-39).log" LOGFILE="C:\Users\jeharris\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2013-02-22 00-35-39).log" INSTALLDIR="C:\Program Files\AppFabric 1.1 for Windows Server" LANGID=en-US
2013-02-22 00:36:09, Information           Setup  Process.ExitCode: 0x00000643
2013-02-22 00:36:09, Error                 Setup  AppFabric installation failed because installer MSI returned with error code : 1603
2013-02-22 00:36:09, Error                 Setup 
2013-02-22 00:36:09, Error                 Setup  AppFabric installation failed because installer MSI returned with error code : 1603
2013-02-22 00:36:09, Error                 Setup 

Answer 20

I was completely unable to install AppFabric with the same errors occurring as described above.  In the end I was only partially successful. I was able to get the installer and configuration to complete by only installing the Caching Service, Caching Client and Cache Administration.

Extremely frustrating!

Fortunately in our current environment we don't need to the other services.

---

- dw

Answer 21

Removing the trailing quote character from PSModulePath was the solution for me.