Msi Error 340
Contents |
running IIS 7. The prerequisite knowledge is described in my previous posts. Upon starting the .msi file (or the accompanying setup.exe), I received the webca_settargetsite returned actual error code 1603 error message "The installer was interrupted before Application could be installed. You
Note: 1: 2262 2: Error 3: -2147287038
need to restart the installer to try again. Click "Close" to exit." This Social MSDN entry brought the dirca_checkfx. return value 3 first step to the solution: activate logging using the command line msiexec /i
Mainenginethread Is Returning 1603
the commands cd C:\Windows\Microsoft.NET\Framework\v4.0.30319 aspnet_regiis.exe -i aspnet_regiis.exe -ga MyDomain\MyUserName After registering the framework version, the next error showed in these lines in the log file: INFO : [SetTARGETSITE]: Custom Action is starting... INFO : [SetTARGETSITE]: CoInitializeEx - COM initialization Apartment Threaded... ERROR : [SetTARGETSITE]: FAILED: -2147221164 ERROR : [SetTARGETSITE]: Custom Action failed with code: '340' INFO : [SetTARGETSITE]: Custom Action completed with installation success or error status: 1603 return code: '340' The cause for these errors was that the IIS 6 Management Compatibility feature was not installed on the server. Installation of this feature is easy: go to Control Panel\Programs and Features\"Turn Windows features on or off" and check the IIS 6 Management Compatibility checkbox. (on Server 2008, this can be done in the Server Manager, under Roles, Webserver (IIS)). Visual Studio requires IIS 6 Management Compatibility to be installed on the developer machine: To enable Visual Studio to create and use local IIS Web sites, you must enable metabase compatibility. This lets Visual Studio interact with the IIS metabase and with the IIS 7.0 configuration store. I also found a similar statement in the IIS forum: Visual Studio 2010 web setup project still only targets older IIS versions. This is why the compatibility features are required. So how can a developer detect if the IIS 6 Compatibility feature is installed? The registry path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp contains the IIS version in the keys MajorVersion and MinorVersion. This page contains the list of IIS components that can be detected under the registry p
BizTalk Server 2009 Post Categories General C# Programming Enterprise Library Physics Non Work F# Performance Archives November 2010 (1) October 2010 (1) April 2010 (3) March 2010 (5) June 2009 (3) David Blomqvist << Integration with
Error 1603
Office from Team Explorer stopped working–and how to fix it! | Home The installer was
Msiexec
interrupted before Application could be installed - Installation success or error status: 1603 Comments (76) | Share I was trying to install a windows installer web app that another team member built. this failed with the message: “The installer was interrupted before
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Microsoft Corporation › Windows Operating System › Error 340 How To http://www.solvusoft.com/en/errors/runtime-errors/microsoft-corporation/windows-operating-system/error-340-control-array-element-item-doesn-t-exist/ Fix Runtime Error 340 Error Number: Runtime Error 340 Error Name:Control array element 'item' doesn't exist Error Description: You used an invalid index value to refer to an element in a control array. Developer:Microsoft Corporation Software:Windows Operating System Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC msi error for computer errors. Compatible with Windows 10, 8, 7, Vista, XP and 2000 Symptoms of Runtime Error 340 "Error 340" appears and crashes the active program window. Your PC frequently crashes with Error 340 when running the same program. “Control array element 'item' doesn't exist” is displayed. “You used an invalid index msi error 340 value to refer to an element in a control array.” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your computer periodically “freezes” for a few seconds at a time. These 340 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Windows Operating System) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 340 error occurs is a critical piece of information in troubleshooting the problem. Causes of Runtime Error 340 Corrupt download or incomplete installation of Windows Operating System software. Corruption in Windows registry from a recent Windows Operating System-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files. Another program maliciously or mistakenly deleted Windows Operating System-related files. Runtime Errors such as “Error 340