Enumerating Pre-install Packages
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.
Hi, I see in the documentation that I can install custom R packages (pasted relevant text below), but I have a few that I need installed to complete a very short task. Extending the Package Manager Console. Some packages install new commands for the console. For example, MvcScaffolding creates commands like Scaffold shown below, which generates ASP.NET MVC controllers and views: Setting up a NuGet PowerShell profile.
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). Hi Ankit, I think we're one step closer. I did exactly as you said - except that I don't have an E: drive. But I copied packages appfabric-1.1-for-windows-server-64.msi to C: (root) and D: (root) and set read permissions to 'everyone'.
I got the same install error, but different messages in the super-detailed log, as below. MSI (s) (C0:A0) 16:00:55:269: Closing MSIHANDLE (69) of type 790541 for thread 5792 MSI (s) (C0:A0) 16:00:55:269: SOURCEMGMT: Source is invalid due to client source out of sync (product code is the same). MSI (s) (C0:A0) 16:00:55:269: Note: 1: 1731 2: - 3: appfabric-1.1-for-windows-server-64.msi MSI (s) (C0:A0) 16:00:55:269: SOURCEMGMT: Processing net source list.
MSI (s) (C0:A0) 16:00:55:269: Note: 1: 1706 2: - 3: appfabric-1.1-for-windows-server-64.msi MSI (s) (C0:A0) 16:00:55:269: SOURCEMGMT: Processing media source list. MSI (s) (C0:A0) 16:00:55:271: Note: 1: 2203 2: 3: - MSI (s) (C0:A0) 16:00:55:271: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (s) (C0:A0) 16:00:55:271: Note: 1: 1706 2: - 3: appfabric-1.1-for-windows-server-64.msi MSI (s) (C0:A0) 16:00:55:271: SOURCEMGMT: Processing URL source list. MSI (s) (C0:A0) 16:00:55:271: Note: 1: 1402 2: UNKNOWN URL 3: 2 MSI (s) (C0:A0) 16:00:55:271: Note: 1: 1706 2: - 3: appfabric-1.1-for-windows-server-64.msi MSI (s) (C0:A0) 16:00:55:271: Note: 1: 1731 2: 3: appfabric-1.1-for-windows-server-64.msi MSI (s) (C0:A0) 16:00:55:271: SOURCEMGMT: Failed to resolve source MSI (s) (C0:A0) 16:00:55:271: Product: AppFabric 1.1 for Windows Server - Error 1731.
The source installation package for the product AppFabric 1.1 for Windows Server is out of sync with the client package. Try the installation again using a valid copy of the installation package 'appfabric-1.1-for-windows-server-64.msi'.
The source installation package for the product AppFabric 1.1 for Windows Server is out of sync with the client package. Try the installation again using a valid copy of the installation package 'appfabric-1.1-for-windows-server-64.msi'.
MSI (s) (C0:A0) 16:00:55:274: User policy value 'DisableRollback' is 0 Any further thoughts? Thanks so much for your help. 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 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 lcmas001 AppData Local Temp AppServerSetup11CustomActions(2012-07-13 11-25-19).log Error: ERROR: Invalid syntax. Default option is not allowed more than '2' time(s). Error: Type 'SETX /?'
ExitCode=1 Well. Taking a look in the code, it concatenates the Enviroment Variable with more data. Looking at enviroment variable (HKEYLOCALMACHINE/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.
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. Hi - not sure if im being helpful but i had exactly the same problem - background: Fresh install of Server 2012 Essentials RC Installed AppPatch as part of the SharePoint 2012 install pre-requisites alongside SQL 2012 essentials, Deleted everything as it didnt work (SQL config issues!) The PSModulePath environ variable clearly was not cleared during the un-install as discussed above. Deleted it in the registry - install ran without any problem!! Scott Just a plain old end user 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. Ankit, Thanks for all of your assistance. I think I previously had been unclear about something. I had AppFabric 1.1 Caching installed, but not Hosting - and when trying to Add Components Hosting, I kept receiving the 1603 error.
After several months, I came back to this today. When Adding Components Hosting, I got the same 1603 error. But then I tried something that I don't know why I hadn't tried before. I completely uninstalled AppFabric 1.1 and then re-installed it (Caching + Hosting).
Everything installed successfully, and it's now patiently waiting for me to go through the Configuration Wizard.:) Thanks again, Dave. In my case, the resolution was similar to Rob Vanmeert. The initial attempt failed to install AppFabric 1.1 due to not having the Windows Update Service running.
However the install had created the ASObservers group (but not the ASAdministrators). After removing the ASObservers group and re-running I had a successful install. I was installing on Windows Server 2012 and only installing the hosting options, not the caching. The service manager showed the relevant event logs which detailed the ASObservers account as the issue Source= MsiInstaller, Log=Application.
How to reinstall and update packages. 5 minutes to read. Contributors.
In this article There are a number of situations, described below under, where references to a package might get broken within a Visual Studio project. In these cases, uninstalling and then reinstalling the same version of the package will restore those references to working order. Updating a package simply means installing an updated version, which often restores a package to working order.
Updating and reinstalling packages is accomplished as follows: Method Update Reinstall Package Manager console (described in ) Update-Package command Update-Package -reinstall command Package Manager UI On the Updates tab, select one or more packages and select Update On the Installed tab, select a package, record its name, then select Uninstall. Switch to the Browse tab, search for the package name, select it, then select Install). Nuget.exe CLI nuget update command For all packages, delete the package folder, then run nuget install. For a single package, delete the package folder and use nuget install to reinstall the same one. In this article:. When to Reinstall a Package.
Broken references after package restore: If you've opened a project and restored NuGet packages, but still see broken references, try reinstalling each of those packages. Project is broken due to deleted files: NuGet does not prevent you from removing items added from packages, so it's easy to inadvertently modify contents installed from a package and break your project. To restore the project, reinstall the affected packages.
Package update broke the project: If an update to a package breaks a project, the failure is generally caused by a dependency package which may have also been updated. To restore the state of the dependency, reinstall that specific package. Project retargeting or upgrade: This can be useful when a project has been retargeted or upgraded and if the package requires reinstallation due to the change in target framework. NuGet shows a build error in such cases immediately after project retargeting, and subsequent build warnings let you know that the package may need to be reinstalled. For project upgrade, NuGet shows an error in the Project Upgrade Log.
Reinstalling a package during its development: Package authors often need to reinstall the same version of package they're developing to test the behavior. The Install-Package command does not provide an option to force a reinstall, so use Update-Package -reinstall instead.
Constraining upgrade versions By default, reinstalling or updating a package always installs the latest version available from the package source. In projects using the packages.config management format, however, you can specifically constrain the version range. For example, if you know that your application works only with version 1.x of a package but not 2.0 and above, perhaps due to a major change in the package API, then you'd want to constrain upgrades to 1.x versions. This prevents accidental updates that would break the application. To set a constraint, open packages.config in a text editor, locate the dependency in question, and add the allowedVersions attribute with a version range. For example, to constrain updates to version 1.x, set allowedVersions to 1,2): In all cases, use the notation described in. Using Update-Package Being mindful of the described below, you can easily reinstall any package using the in the Visual Studio Package Manager Console ( Tools NuGet Package Manager Package Manager Console): Update-Package -Id –reinstall Using this command is much easier than removing a package and then trying to locate the same package in the NuGet gallery with the same version.
Note that the -Id switch is optional. The same command without -reinstall updates a package to a newer version, if applicable. The command gives an error if the package in question is not already installed in a project; that is, Update-Package does not install packages directly. Update-Package By default, Update-Package affects all projects in a solution. To limit the action to a specific project, use the -ProjectName switch, using the name of the project as it appears in Solution Explorer: # Reinstall the package in just MyProject Update-Package -ProjectName MyProject -reinstall To update all packages in a project (or reinstall using -reinstall), use -ProjectName without specifying any particular package: Update-Package -ProjectName MyProject To update all packages in a solution, just use Update-Package by itself with no other arguments or switches. Use this form carefully, because it can take considerable time to perform all the updates: # Updates all packages in all projects in the solution Update-Package Updating packages in a project or solution using always updates to the latest version of the package (excluding pre-release packages). Projects that use packages.config can, if desired, limit update versions as described below in.
For full details on the command, see the reference. Considerations The following may be affected when reinstalling a package:. Reinstalling packages according to project target framework retargeting. In a simple case, just reinstalling a package using Update-Package –reinstall works. A package that is installed against an old target framework gets uninstalled and the same package gets installed against the current target framework of the project.
Apple Enumerating Pre-install Packages
In some cases, there may be a package that does not support the new target framework. If a package supports portable class libraries (PCLs) and the project is retargeted to a combination of platforms no longer supported by the package, references to the package will be missing after reinstalling.
This can surface for packages you're using directly or for packages installed as dependencies. It's possible for the package you're using directly to support the new target framework while its dependency does not.
If reinstalling packages after retargeting your application results in build or runtime errors, you may need to revert your target framework or search for alternative packages that properly support your new target framework. requireReinstallation attribute added in packages.config after project retargeting or upgrade. If NuGet detects that packages were affected by retargeting or upgrading a project, it adds a requireReinstallation='true' attribute in packages.config to all affected package references.
Because of this, each subsequent build in Visual Studio raises build warnings for those packages so you can remember to reinstall them. Reinstalling packages with dependencies. Update-Package –reinstall reinstalls the same version of the original package, but installs the latest version of dependencies unless specific version constraints are provided. This allows you to update only the dependencies as required to fix an issue.
However, if this rolls a dependency back to an earlier version, you can use Update-Package to reinstall that one dependency without affecting the dependent package. Update-Package –reinstall -ignoreDependencies reinstalls the same version of the original package but does not reinstall dependencies. Use this when updating package dependencies might result in a broken state.
Reinstalling packages when dependent versions are involved. As explained above, reinstalling a package does not change versions of any other installed packages that depend on it.
Enumerating Pre-install Packages
It's possible, then, that reinstalling a dependency could break the dependent package.