Troubleshoot StoreFront
Installation Logs
When StoreFront is installed or uninstalled, the following log files are created by the StoreFront installer in the C:\Windows\Temp\StoreFront directory. The file names reflect the components that created them and include time stamps.
- Citrix-DeliveryServicesRoleManager-*.log—Created when StoreFront is installed interactively.
- Citrix-DeliveryServicesSetupConsole-*.log—Created when StoreFront is installed silently and when StoreFront is uninstalled, either interactively or silently.
- CitrixMsi-CitrixStoreFront-x64-*.log—Created when StoreFront is installed and uninstalled, either interactively or silently.
Event Logs
StoreFront supports Windows event logging for the authentication service, stores, and Receiver for Web sites. Any events that are generated are written to the StoreFront application log, which can be viewed using Event Viewer under either Application and Services Logs > Citrix Delivery Services or Windows Logs > Application. You can control the number of duplicate log entries for a single event by editing the configuration files for the authentication service, stores, and Receiver for Web sites.
Log throttling
-
Use a text editor to open the web.config file for the authentication service, store, or Receiver for Web site, which are typically located in the C:\inetpub\wwwroot\Citrix\Authentication\, C:\inetpub\wwwroot\Citrix\storename\, and C:\inetpub\wwwroot\Citrix\storenameWeb\ directories, respectively, where storename is the name specified for the store when it was created.
-
Locate the following element in the file.
<logger duplicateInterval="00:01:00" duplicateLimit="10">By default, StoreFront is configured to limit the number of duplicate log entries to 10 per minute.
-
Change the value of the duplicateInterval attribute to the set the time period in hours, minutes, and seconds over which duplicate log entries are monitored. Use the duplicateLimit attribute to set the number of duplicate entries that must be logged within the specified time interval to trigger log throttling.
When log throttling is triggered, a warning message is logged to indicate that further identical log entries will be suppressed. Once the time limit elapses, normal logging resumes and an informational message is logged indicating that duplicate log entries are no longer being suppressed.
Powershell and management console logs
Configuration changes made through PowerShell or the management console are logged at C:\Program Files\Citrix\Receiver StoreFront\Admin\logs. The log file names contain command actions and subjects, along with time stamps that can be used to differentiate command sequences.
Diagnostics logging
StoreFront writes diagnostics logs to c:\Program Files\Citrix\Receiver StoreFront\admin\trace
By default, messages of level Error, Warning, and Info are logged. In most cases this includes sufficient information to diagnose any issues.
You can enable additional verbose logging for troubleshooting purposes. This is only required if requested by Citrix support. This may have an impact on performance so you should revert the TraceLevel to Info once troubleshooting is complete.
To enable Verbose logging:
-
Using an account with local administrator permissions, start Windows PowerShell
-
Enter command:
Set-STFDiagnostics -All -TraceLevel "Verbose" -confirm:$False <!--NeedCopy-->This enables “Verbose” logging for all services, without prompting for confirmation. When this command is entered it restarts the Storefront services. Wait for the PowerShell prompt to return to verify that that the services have finished restarting. While these services are restarting, the StoreFront server will not be accessible by users.
-
Reproduce the issue to create the logs.
-
Set the logging back to default level for all services
Set-STFDiagnostics -All -TraceLevel "Info" -confirm:$False <!--NeedCopy-->
You can further customize the diagnostics logging:
-
StoreFront writes a separate log file for each service. By default, each log file is up to 200Mb and StoreFront writes up to five log files per service before purging old log files. If you need to customize the size or number of logs written then you can do this using the
-FileSizeKband-FileCountparameters. -
Change the level of detail logged using
-TraceLevel. Allowed values areOff,Error,Warning,Info, orVerbose. -
Using the parameter
-Allsets the logging parameters for all services. You can customize logging for an individual service using-Service [Service name]
For more information on the Set-STFDiagnostics cmdlet, see the StoreFront PowerShell SDK documentation.
Launch.ica file logging
When a user launches an app or desktop, StoreFront generates a file called launch.ica that Workspace app reads to determine how to connect to the app or desktop. Depending on configuration this file may be stored in memory so not directly accessible. To diagnose launch errors it can be useful to view the contents of launch.ica.
To enable logging of the launch.ica file on the client PC, complete the following steps:
-
Navigate to the following registry key by using the registry editor:
32-bit Systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\Logging64-bit Systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\Logging -
Set the following two string key values:
- LogFile=”path to the log file”
- LogICAFile=true
For example:
LogFile=C:\ica\ica.log LogICAFile=true <!--NeedCopy-->
Note:
The use of an ICA file in your environment for anything other than troubleshooting purposes is further outlined in CTX200126.