Installing K2.net 2003 on a machine with Windows Vista RTM or later version.

  • 16 February 2021
  • 0 replies
  • 5 views

Badge +3


 




Installing K2.net 2003 on a machine with Windows Vista RTM or later version.














LEGACY/ARCHIVED CONTENT

This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


 


Issue


When installing the K2.net 2003 Client tools on your machine with Windows Vista RTM or later version, you may run into an error caused by the K2.net 2003 installer. This is due to the installer package not being able to resolve the environment variable %SystemDrive% and will prevent you from completing the installation.


 


 


 


Workaround


A registry key needs to be modified. It is strongly recommended to back up the registry before making any changes.


Perform the following steps:



  1. Type "regedit" in the Run command (Windows Key+R) on the Start Menu dialog box to open the "Registry Editor".

  2. Find the following registry key:

    • If you have a 32-bit operating system:

      HKEY_LOCAL_MACHINESOFTWAREMicrosoftInetStpPathWWWRoot




    • If you have a 64-bit operating system:


      HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftInetStpPathWWWRoot





  3. Change the value of this registry key from "%SystemDrive%inetpubwwwroot" or "inetpubwwwroot"" to "C:inetpubwwwroot". If your default website in IIS is stored in a different location, set the value of this registry key to that path.

  4. The original value can be restored after the installation if required.

  5. To prevent studio from crashing when opening, the following steps must be taken

    <configuration>


      <startup>


        <supportedRuntime version="v1.1.4322" />


      </startup>


    </configuration>




 






0 replies

Be the first to reply!

Reply