A specific installation exception (installation error) when trying to move from the components installation screen to the K2.net® database specification screen and the method of working around it.

The error may be the result of an exception generated from within InstallShield. We have however not yet been able to trap/identify and handle the exception
 
The exception occurs under the following circumstances:
  1.  K2.net Server and K2.net Service Manager are selected with all of their components
  2.   K2.net Studio deslected
  3.  The minimum components selected that is known to cause the exception is K2.net Server(with the Transaction and Log databases)

 For the purpose of replicating this error, do the following:
  • Start the K2.net 2003 with SP2/SP2a (or earlier) installation
  • The installation program loads; continue with an installation as per normal entering the required information when prompted to do so
  • When the "Custom Setup" screen is reached, select the components as shown below for the installation

In the example shown below of the setup screen, K2.net 2003 Studio and K2.net 2003 Additional Components are deselected.
 
  

When the "Next" button is clicked, the following error is received:
 
  

Notice that at the end of the message text is a server name. Interestingly, this will not be the name of the server on which we are trying to install K2.net. This is the main symptom of the problem.To correct this, this server name needs to be changed in the system registry to the name of the local SQL Server.
 
Note: The registry key will only be available for edit if you have SQL Server on your local system.

 To change the server name, do the following:
 
  • Click “Start>Run”
  • Type: “Regedit”, as shown below and click on “OK”
         
 
 
  • Navigate the tree to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
  • In this instance the key was set to: SCMBJHBES01, as was illustrated in the above error message. Change the name to be the name of the local server

Note: Thus far, our investigation indicates that InstallShield is querying for available SQL Servers and possibly failing to connect as it does not have the correct login credentials or it is unable to reach the server it is trying to connect to.The only know issue with InstallShield and SQL Servers is that if you exceed 1000 SQL Servers Install Shield may fail to run correctly. However, this is not the case in this instance.