none
Packages failed to install - Visual Studio 2012 Premium

    Question

  • Selected portions of the log follow:

    [20E8:2FEC][2012-08-16T14:10:23]: Burn v3.6.3014.0, Windows v6.1 (Build 7601: Service Pack 1), path: E:\swlib\Microsoft\Visual Studio 2012 Premium\vs_premium.exe, cmdline: ''

    [13C0:184C][2012-08-16T14:48:03]: Applying execute package: aspnetwebpages_1020, action: Install, path: C:\ProgramData\Package Cache\{631471BE-DEAB-454B-A9AC-CE3EB42C28B3}v1.0.20105.0\packages\WPT\aspnetwebpages.msi, arguments: ' MSIFASTINSTALL="7"'
    [1988:1934][2012-08-16T14:48:07]: MUX:  ExecuteError: Package (aspnetwebpages_1020) failed: Error Message Id: 1722 ErrorMessage: 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. 
    [13C0:184C][2012-08-16T14:48:03]: Applying execute package: aspnetwebpages_1020, action: Install, path: C:\ProgramData\Package Cache\{631471BE-DEAB-454B-A9AC-CE3EB42C28B3}v1.0.20105.0\packages\WPT\aspnetwebpages.msi, arguments: ' MSIFASTINSTALL="7"'
    [1988:1934][2012-08-16T14:48:07]: MUX:  ExecuteError: Package (aspnetwebpages_1020) failed: Error Message Id: 1722 ErrorMessage: 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. 
    [13C0:184C][2012-08-16T14:48:10]: Error 0x80070643: Failed to install MSI package.
    [13C0:184C][2012-08-16T14:48:10]: Error 0x80070643: Failed to execute MSI package.
    [1988:1934][2012-08-16T14:48:10]: Error 0x80070643: Failed to configure per-machine MSI package.

    [13C0:184C][2012-08-16T14:48:13]: Applying execute package: aspnetmvc3_1000, action: Install, path: C:\ProgramData\Package Cache\{DCDEC776-BADD-48B9-8F9A-DFF513C3D7FA}v3.0.20105.0\packages\WPT\aspnetmvc3.msi, arguments: ' MSIFASTINSTALL="7"'
    [1988:1934][2012-08-16T14:48:13]: MUX:  ExecuteError: Package (aspnetmvc3_1000) failed: Error Message Id: 0 ErrorMessage: This product requires Microsoft ASP.NET Web Pages 1.0. Please install the missing component, then try to install this product again.
    [13C0:184C][2012-08-16T14:48:13]: Error 0x80070643: Failed to install MSI package.
    [13C0:184C][2012-08-16T14:48:13]: Error 0x80070643: Failed to execute MSI package.
    [1988:1934][2012-08-16T14:48:13]: Error 0x80070643: Failed to configure per-machine MSI package.

    Thursday, August 16, 2012 7:27 PM

Answers

  • Hello Rick

    The first thing to do is read http://support.microsoft.com/kb/2531566 and determine if the root web.config file of .NET 4 contains any of the problematic items described under the Causes section of the KB article. If you have a 64-bit OS, be sure to check both the Framework and Framework64 config folders.

    The biggest culprit we've seen in the past is having sections in the root web.config that has allowOverride="false". This attribute is intended to lock section modifications out of child configurations, but the framework enforces this inside the current configuration level so our custom action would file since it's not allowed to make these changes. The work around as described in the KB article is to simply edit your config files, set the allowOverride="true", install the product (in this case Visual Studio) and then edit the config files back to their original settings.

    If you haven't cleared out %temp% yet, there should be a log file for the ASP.NET Web Pages 2 runtime install. Judging from your post, it sounds like that one succeeded. The Web Pages 2 installer is a bit more robust when dealing with configuration problems: it has a number of fallback mechanisms built in and will also write more information to the setup logs. That might help to determine why Web Pages 1 failed to install. It's likely that the Web Pages 2 installer encountered the same problem and worked around it by using a fallback mechanism. Also, if Web Pages 2 completely fails to modify the config file, it will actually continue and complete the install, unlike Web Pages 1 that aborts the install and reports an error.

    Thanks,

    Jacques

    Friday, August 17, 2012 10:28 PM

All replies

  • Hi Rick,

    I am sorry that you get such an issue during your VS2012 installation, and please try the following steps to see if it helps:

    1). Re-download the VS2012 Premium installer from Microsoft official site here: http://www.microsoft.com/visualstudio/11/en-us/downloads#premium
    2). Temporally turn off your anti-virus/antispyware software.
    3). Clean your %temp% folder and run the installer with Administrator permission.

    Please update your result after you finished the above steps.

    Thanks.


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us

    Friday, August 17, 2012 9:41 AM
    Moderator
  • The main log indicates a problem we'll only find if you download and run http://aka.ms/vscollect. After it completes, upload %TEMP%\vslogs.cab to an Internet share (like http://skydrive.com using the same Microsoft account you use for these forums) and share the URL here so we can diagnose it.

    The first error caused the second error, so we'll need to look at the associated logs in vslogs.cab.


    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment

    Friday, August 17, 2012 10:38 AM
    Moderator
  • Friday, August 17, 2012 1:27 PM
  • Configuring ASP.NET is failing with a StackOverflowException:

    MSI (s) (1C:D8) [14:48:05:933]: Executing op: CustomActionSchedule(Action=WebConfigCA_Install,ActionType=3090,Source=C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\WebConfig\WebConfigCA.exe,Target=-i,)
    MSI (s) (1C:D8) [14:48:07:652]: Note: 1: 1722 2: WebConfigCA_Install 3: C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\WebConfig\WebConfigCA.exe 4: -i
    MSI (s) (1C:D8) [14:48:07:652]: Note: 1: 2205 2:  3: Error
    MSI (s) (1C:D8) [14:48:07:652]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722
    CustomAction WebConfigCA_Install returned actual error code -532462766 (note this may not be 100% accurate if translation happened inside sandbox)

    I will forward this thread to the responsible team who can better assist you with diagnosing the actual problem.


    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment

    Friday, August 17, 2012 7:24 PM
    Moderator
  • Hello Rick

    The first thing to do is read http://support.microsoft.com/kb/2531566 and determine if the root web.config file of .NET 4 contains any of the problematic items described under the Causes section of the KB article. If you have a 64-bit OS, be sure to check both the Framework and Framework64 config folders.

    The biggest culprit we've seen in the past is having sections in the root web.config that has allowOverride="false". This attribute is intended to lock section modifications out of child configurations, but the framework enforces this inside the current configuration level so our custom action would file since it's not allowed to make these changes. The work around as described in the KB article is to simply edit your config files, set the allowOverride="true", install the product (in this case Visual Studio) and then edit the config files back to their original settings.

    If you haven't cleared out %temp% yet, there should be a log file for the ASP.NET Web Pages 2 runtime install. Judging from your post, it sounds like that one succeeded. The Web Pages 2 installer is a bit more robust when dealing with configuration problems: it has a number of fallback mechanisms built in and will also write more information to the setup logs. That might help to determine why Web Pages 1 failed to install. It's likely that the Web Pages 2 installer encountered the same problem and worked around it by using a fallback mechanism. Also, if Web Pages 2 completely fails to modify the config file, it will actually continue and complete the install, unlike Web Pages 1 that aborts the install and reports an error.

    Thanks,

    Jacques

    Friday, August 17, 2012 10:28 PM
  • Hello Rick,

    I am marking Jacques' reply as answer. If you still have anything unclear, please post back.

    Thanks.


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us

    Monday, September 03, 2012 2:57 AM
    Moderator
  • I am getting a big list of package failed errors too, almost all the feature set seems failing on my new clean / virgin Windows server 2012 box.

    I dont buy the corrupt ISO reason which most are suggesting, the same ISO installed it like a charm on my other SharePoint 2010 / Windows Server 2008 R2 box.


    new to every thing


    • Edited by Adil Baig Monday, August 26, 2013 10:43 PM text change
    Monday, August 26, 2013 10:41 PM