Possible cause of Visual Web Designer tools failure during VS Orcas beta 1 setup

As described in this post on S. Somasegar's blog and in other places, Visual Studio codename Orcas beta 1 was recently released.  Some customers (such as in this forum post) have reported that Orcas beta 1 setup is failing on their system while it tries to install the Microsoft Web Designer Tools component.

There is a known issue where the Microsoft Web Designer Tools component will fail if you attempt to install it on a system that has a beta version of Microsoft Office 2007 installed.  This component is produced by the Office team, and the setup wrapper for the component has logic in it to block if it detects beta versions of Office 2007 on the system.  Unfortunately, since Visual Studio setup launches the Web Designer Tools setup in silent mode, the error message only appears in the log file instead of in the UI.

To diagnose this issue, you can look at the Web Designer Tools log file, which is located at %temp%\SetupExe(########).log (where ####### is a unique value with date/time information and a randomly generated ending).  If you attempt to install on a system that has a beta version of Office 2007 installed, there will be an error that looks like the following:

Not showing message because suppress modal has been set. Title: 'Setup Errors', Message: 'Setup is unable to proceed due to the following error(s):

The 2007 Microsoft Office system does not support upgrading from a prerelease version of the 2007 Microsoft Office system.

You must first uninstall any prerelease versions of the 2007 Microsoft Office system products and associated technologies.

Correct the issue(s) listed above and re-run setup.

In order to resolve this issue, you can uninstall any remaining beta versions of Office 2007 from your system using the Add/Remove Programs control panel and then re-run Visual Studio Orcas beta 1 setup.  If you do not see any beta versions of Office 2007 in your Add/Remove Programs control panel, you can use steps like the ones listed in this blog post to locate and uninstall the beta components.  All Office 2007 components have the string 0FF1CE at the end of the product code GUID, so you can search for that string to locate these components in the output from the MSI inventory tool.  When you do this, just make sure that you do not inadvertantly uninstall the final release of Office 2007.  If in doubt, you can tell from the product name whether or not the product in question is a beta or the final release.

Comments (20)
  1. PinalBhatt says:

    I dont have any version of office 2007 installed on my system. I have Office 2003 installed, but still get failure while installing Orcas beta-1 saying failure in installing web designer tools.

    Is it compulsory to have Office 2007? will it not install on Office 2003?

  2. Hi Pinal – No, it is not required to have Office 2007 in order to install the Visual Web Designer tools package.  Could you please zip and send me the file %temp%SetupExe*.log so I can try to narrow down why this is failing on your system?  You can send the log to Aaron.Stebner (at) microsoft (dot) com.

  3. michael.minutillo says:

    Hi Aaron – I’m in the same boat. No office 2007 and the install fails on Visual Web Developer. I’ve already sent you my log file and a copy of the output of msiinv.exe and I look forward to hearing from you.

  4. Hi Michael – I haven’t seen any mail from you with log files for this issue yet.  I will keep an eye out and respond once I get them.

  5. Jeff Arnold says:

    I’m encountering what appears to be the same problem on an Intel® 64 system running Windows(R) Server 2003 Enterprise x64 Edition.  Visual Studio 2005 has been installed along with its SP1 but this system has never seen any flavor of Office.

    Without a work-around, I can’t install Orcas on this system.

  6. Hi Michael – I have received your log files and the error is one I haven’t seen before.  I am trying to find someone on the Office team to help advise because this package uses the Office 2007 setup.exe behind the scenes.

    Hi Jeff – If your install is failing on the Visual Web Designer tools component, can you please send me the file named %temp%SetupExe(########).log from your system so I can try to take a look?  You can send the file to Aaron.Stebner (at) microsoft (dot) com.

  7. Jeff Arnold says:

    RE:  Hi Jeff – If your install is failing on the Visual Web Designer tools component, can you please send me the file named %temp%SetupExe(########).log from your system so I can try to take a look?  You can send the file to Aaron.Stebner (at) microsoft (dot) com.

    Aaron:  Were you able to learn anything from the log file I sent on 2007-05-17?


  8. I’m sorry for the delay getting back to you about this issue.  I’ve been talking to the Office team (since the Web Designer Tools package uses Office 2007 setup behind the scenes).  They suggested to me that the error code in your log file could be caused by an issue with running in terminal server application mode on a 64-bit OS.  If this is the case on your system, could you please try to change to administration mode and then try installing again?

  9. When Visual Studio Codename Orcas beta 1 was initially released back in April, I posted this item about

  10. Jeff Arnold says:

    Changing Terminal Services on the target system from relaxed security mode to full security mode as described in KB927476 allowed the installation of Orcas beta 1 to succeed.

    Thanks for all your help.

  11. Hi Jeff – I’m glad to hear that this workaround helped in your scenario.  For other folks reading this post in the future, I’ve also posted a description of Jeff’s exact problem and a link to the Knowledge Base article at http://blogs.msdn.com/astebner/archive/2007/06/03/3070138.aspx.

  12. Prraful says:

    I am having XP and the same error. I think the solution will be different in my case as I am running 32 bit version of XP.

  13. Hi Prraful – Can you please zip and send me the log file named %temp%SetupExe(########).log from your system so I can take a look and see if I can figure out why this package is failing to install on your system?  You can send it to Aaron.Stebner (at) microsoft (dot) com.

  14. seh says:

    Hello, I have the same problem but with VS Orcas June 2007 CTP with a 32 bit version of XP :

    Visual Web Designer Tools fails :

    [07/25/07,08:59:47] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InternalInstallManager() with HRESULT -2147023293.

    I mailed you the SetupExe*.log file.

    – I have no beta version of Office installed

    – I have installed framework 2.0, 3.0, 3.5 June 2007 CTP

    – I didn’t install Orcas Beta 1

    Thanks for helping

  15. Hi Seh – I’ve been looking at the June CTP build of Visual Web Developer and I think I’ve found a discrepancy in one of the registry values that setup uses internally to detect whether or not the Web Designer Tools package successfully installed on the system.  To test my theory, could you check and see if you have the following registry value on your system?

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWeb Designer Tools12.01033] InstallSuccess = 1

    If you have that value, can you please add the following new value and then re-run Visual Web Developer setup and see if it will succeed this time?

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWeb Designer Tools12.0] InstallSuccess = 1

    If this works for you, I will post a new entry about this on my blog because I’ve heard from 2 other people besides you with the same type of problem so it appears to be a trend now.

  16. ryouj says:

    Hi, I have the same problem, and solved this problem.

    I have the following registry value on my system.

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWeb Designer Tools12.0] InstallSuccess = 1

    I add the following new value.

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWeb Designer Tools12.01033] InstallSuccess = 1

    thn re-run Visual Studio 2008 Beta2 setup and it succeeded.

  17. Hi Ryouj – When this happens during VS 2008 beta 2 setup, it means that there is an older build of the Microsoft Web Designer Tools component left behind on your system.  Changing this registry value will mask the problem and allow VS 2008 beta 2 setup to succeed, but if you run VS 2008 beta 2 and try to use any features that rely on the Microsoft Web Designer Tools component, they will likely not work because you do not have a matching version of this prerequisite component still installed on your system.

    I have posted a new item at http://blogs.msdn.com/astebner/archive/2007/07/30/4135155.aspx that describes how to workaround this installation issue if you run into it during VS 2008 beta 2 setup.

  18. fvillaf says:

    I’m using W2003 SP2 and ORCAS failed to install, until I removed Office 2007. I’m using release version of Office, but localized (spanish)

  19. jarnoburger@hotmail.com says:

    also remove :

    Compatibility Pack for the 2007 Office system (Beta)

    that did it for me

  20. Hi Jarnoburger – Correct, you need to remove any beta Office 2007 product from your system before the Visual Web Designer tools prerequisite component will install successfully as a part of VS 2008 setup.  This includes things like compatibility packs and viewers.

Comments are closed.

Skip to main content