Created On: 21 February 2012
Problem:
After installing SilkCentral Test Manager in IIS if you are unable to connect to the Frontend server then you should check the IIS Manager.
Under the Default Web Site there should be a virtual directory called "silkroot", see below:

Under the Default Web Site there should be a virtual directory called "silkroot", see below:

Resolution:
If the silkroot virtual directory does not exist then go to the Web Sites folder level, see below:

Note that the identifier for the Default Web Site is '1', if there is not a Web Site available that has the identifier of 1 then the installation will fail with no error messages. This is because SilkCentral Test Manager will only use the Web Site with the identifier of 1.
To resolve the issue:
1. Uninstall SCTM
2. Change the identifier of an existing Web Site by running the following commands one by one via the command line:
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs STOP_SERVER W3SVC/2
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs MOVE W3SVC/2 W3SVC/1
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs START_SERVER W3SVC/1
The command above will change the identifier of a web site from 2 to 1.
3. Reinstall SCTM
Now if you view the Web Site the silkroot virtual directory should exist and you should be able to connect to the Frontend server.

Note that the identifier for the Default Web Site is '1', if there is not a Web Site available that has the identifier of 1 then the installation will fail with no error messages. This is because SilkCentral Test Manager will only use the Web Site with the identifier of 1.
To resolve the issue:
1. Uninstall SCTM
2. Change the identifier of an existing Web Site by running the following commands one by one via the command line:
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs STOP_SERVER W3SVC/2
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs MOVE W3SVC/2 W3SVC/1
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs START_SERVER W3SVC/1
The command above will change the identifier of a web site from 2 to 1.
3. Reinstall SCTM
Now if you view the Web Site the silkroot virtual directory should exist and you should be able to connect to the Frontend server.
Incident #2560457