Friday, March 24, 2006

CTX: Web Interface and .NET Framework 2.0 are NOT Compatible

Beware, Citrix Web Interface 4.0 is not compatible with Microsoft .NET Framework 2.0, if just won’t be able to communicate. For example, you might experience the following error(s)
The Access Suite Console is no longer able to properly communicate with Web Interface. The option to Create Sites is no longer available in the Common Tasks Pane of the ASC, Access Suite Console, and running discovery reports a warning which states “Could not contact any Web Interface configuration servers”.
Cause:Installing Microsoft .Net 2.0 on Web Interface 4.0 server breaks the ability for the ASC, Access Suite Console, to create sites or run discovery.

Workaround:Remove .net version 2.0

Resolution:Citrix is currently investigating this issue – for more information please refer to:
CTX108104 - Error: Could not Contact any Web Interface Configuration Servers ..or the (Create Site) option is not available.

This being said, I was browsing through the Citrix forums and I came upon this awesome workaround developed by Matt Carter (

Matt documented the following workaround:

On a server that .Net 2.0 has NEVER been installed on

  • Install WI 3.0, and verify functionality
  • Install .NET 2.0
  • Open your IIS Console. Right click on Default Web site > Properties > home Directory Tab > Configuration button On mappings, click ADD button
    For the executable, browse to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
    Set extension to “ica”, Verbs Limit to GET;HEAD;POST;DEBUG
    Click OK
  • It will prompt to modify the child nodes. SELECT ALL and click OK.
  • Go IMMEDIATELY to the ASP.NET tab
  • Change the version to 1.1.4322.0 (or whatever your 1.1 version is)
  • If your MPS3.0 server is an upgrade from MPS-XP you may need to change the application pool to CtxAdminPool, otherwise, you should be able to leave it at the default pool.
  • Click Apply, OK.
  • Stop and restart your IIS Server (iisreset)

1 comment:

paul r said...

Great link to that Citrix workaround using mmc.exe.config.