SLAPPA.ORG

Symptoms

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 Access Suite Console, and running discovery reports a warning which states “Could not contact any Web Interface configuration servers.”

Causes

This is caused by installing Microsoft .NET 2.0 on a Web Interface 4.0 server.

WorkAround

Remove .NET version 2.0.

-OR-

Create a file call “mmc.exe.config” in \Windows\system32 directory and add the following lines to the file. You should be able to open the Access Suite Console without any further problems.

sample mmc.exe.config

�

your ads here (468x60) - after 1st post.

Symptom

Users are logged off from the Web Interface 3.0 or 4.0 site after 20 minutes. Changing the session timeout value in Internet Services Manager or other Web server utilities has no effect.

Cause

The ASPX scripts in Web Interface 3.0 and 4.0 run as an ASP.NET application. Therefore, the session timeout value is controlled by the .NET framework instead of IIS. The default session timeout is contained in the web.config file in the /Citrix/MetaFrame/site folder.

On Web Interface 3.0 for UNIX, the Web Interface scripts run in a Java servlet zone and session timeouts are controlled by the WEB-INF/web.xml file.

Resolution

On Web Interface for Windows:

For Web Interface 3.0, edit the wwwroot\Citrix\MetaFrame\site\web.config file using a text editor. Add a sessionState element to the First section of Web.config declaring a new timeout value in minutes. For example, to change the session timeout to one hour, add the following line (in bold) to /Citrix/MetaFrame/site/web.config:

For Web Interface 4.0, edit the wwwroot\Citrix\MetaFrame\web.config file using a text editor. Add a sessionState element to the First section of Web.config declaring a new timeout value in minutes. For example, to change the session timeout to one hour, add the following line (in bold) to /Citrix/MetaFrame/web.config:

Note: Web.config entries are case sensitive and take effect immediately. Use sessionState, not sessionstate.

Additional step for IIS 6.0

When Web Interface 3.0 or 4.0 is hosted by Internet Information Services 6.0 on Windows Server 2003, an additional step may be necessary.

Web Interface 3.0

If the session timeout is increased to a value greater than 20, it is also necessary to increase the idle timeout for the DefaultAppPool application pool. For example:

§ Open IIS Manager 

§ Expand Application Pools > DefaultAppPool

§ Right-click DefaultAppPool and view its Properties

§ On the Performance tab, change the value for Shutdown worker processes after being idle for (time in minutes) to a number that is greater than or equal to the session timeout defined in web.config

If the session timeout is reduced to a value less than 20, the above step should not be necessary.

Web Interface 4.x:

If the session timeout is increased to a value greater than 20, it is also necessary to increase the idle timeout for the CitrixWebInterfaceAppPool application pool. For example:

§ Open IIS Manager 

§ Expand Application Pools > CitrixWebInterfaceAppPool

§ Right-click CitrixWebInterfaceAppPool

§ and view its Properties

§ On the Performance tab, change the value for Shutdown worker processes after being idle for (time in minutes) to a number that is greater than or equal to the session timeout defined in web.config

If the session timeout is reduced to a value less than 20, the above step should not be necessary.

On Web Interface 3.0 and 4.0 for UNIX:

Edit the WEB_INF/web.xml file using a text editor. For example, to change the session timeout to one hour, add the following inside the section:

 

60

Restart the Web service.