Current filter:
                                You should refresh the page.
                                  • Description:
                                    The DXperience installation fails with error messages. Can you help?

                                    Answer:
                                    The installation log file might be of great help for us to determine what's wrong and to find a solution to the problem. Please launch the installation with the debug command line switch:
                                    C:\DXperience-6.3.1-2005.exe /debug

                                    A setup_trace.log file will be created in the folder from where you've launched the installation. Please send this file to the Support Team.
                                    Very often, you can manually determine the problem using the installation log file. There are few common issues that usually occur with the installation. Open the log file in the notepad, and search by the word "error". Here are some common errors:

                                    1. GetWebSiteInfo call failed - -2147024894
                                    It appears that the installer has failed to register our ASP.NET demo applications on your IIS (Internet Information Services). If you don't need to run our ASP.NET demos, feel free to ignore this error. If you need DXperience demos for the Web to be installed on your system, reinstall IIS and then re-register ASP.NET filters with the following command:
                                    C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
                                    2. Error - Retrieving the COM class factory for component with CLSID {BA018599-1DB3-44F9-83B4-461454C84BF8} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)).
                                    The ToolboxCreator.exe failed to launch an instance of Visual Studio. Most probably, the cause of the problem is that the system registry is corrupted, or the application does not have enough rights to access the HKEY_CLASSES_ROOT\CLSID{BA018599-1DB3-44F9-83B4-461454C84BF8} registry key. We suggest that you review the Solving setup errors by using the SubInAcl tool to repair file and registry permissions blog, to learn how to solve registry permissions problems.
                                    3. Error - Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
                                    This error can occur on a machine where only the Client Profile version of .NET Framework is installed. This is a bug in the ToolboxCreator configuration file that was fixed in version 2010 vol 1.6. If you have an older version, and do not want to upgrade, you can fix this problem by modifying the TpplboxCreator configuration file as shown below:
                                    [XML]
                                    <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <configuration> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /> <supportedRuntime version="v2.0.50727" /> </startup> </configuration>
                                    4. GetStream: Cannot create file "FILENAME". The requested operation cannot be performed on a file with a user-mapped section open
                                    Cannot extract 6096 file(s) from the data file
                                    Files used by the installation are locked by another program. If you have any antiviral software running on this machine, we suggest that you temporarily disable it, and run the installation again. This solution is applicable to any "cannot create/open file" errors.
                                    5. Access violation at address 004AF7BC in module 'DXperienceUniversal-9.3.2.exe'. Read of address 00000000
                                    This is a bug in version 2009 vol 3.2. This bug was fixed in version 2009 vol 3.3. If you cannot upgrade to this version, you can use a workaround. This bug is reproduced rarely, so you can install our components on a virtual machine, and copy them to your development machine. More information can be found in the Access violation at address 004AF7BC bug report.
                                    6. Unhandled exception: System.ComponentModel.Win32Exception: Unknown error (0xfffffffe)
                                    See the exception callstack. If this exception appears multiple times when executing the System.Diagnostics.Process.Start method, this problem can be related to Internet Explorer 9 Beta. Read the 10.2.5 Installer fails thread to learn how to resolve the problem.
                                    7. Cannot register namespace; ErrorCode = -xxx
                                    If this error occurs with the DXPerienceUniversal installer, try the solution provided in the Installation errors - Cannot register namespace bug report.
                                    7. The configuration system failed to initialize
                                    It appears that your system configuration file is broken. Please check your machine.config file. A similar problem was discussed in the Installation failure: DXperience 8.1.4 (and 8.1.3) thread. Also, please review the Configuration system failed to initialize (One possible solution) blog.
                                    8. Specified cast is not valid.
                                    Stack - at EnvDTE._DTE.get_Windows()
                                    An appropriate version of EnvDTE library is not registered on your machine. Please re-register it by executing the following command from Start | Run...
                                    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe "%PROGRAMFILES%\Microsoft Visual Studio [Version].0\Common7\IDE\PublicAssemblies\envdte.dll"
                                    9. Unable to cast COM object of type 'System.__ComObject' interface type 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{6D5140C1-7436-11CE-8034-00AA006009FA}'failed due to following error: No support for this interface (Exception from HRESULT: 0x80004002 (E_NOINTERFACE) )
                                    This problem might be related to the issue discussed in this forum thread: Object Explorer/Server Explorer Error.
                                    If the log file contains errors that you cannot find here, you can search for similar issues in our Support Center, or feel free to create a new question. Even if the installation log file does not contain any errors, it still contains more useful information. We suggest that you always send us the installation log if you ask the question about installation problems.
                                    10. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
                                    Please see the ToolboxCreator Not working thread, where this problem is discussed in detail.
                                    See Also:
                                    Troubleshooting download problems
                                    How to resolve issues with Toolbox items (Applies to versions prior to 12.1)
                                • Paulo Beduschi 04.12.2013

                                  Thanks for attention.
                                  Now is appear!

                                0 Solutions

                                Creation Date Importance Sort by