AppsAnywhere Log Files

Introduction

When troubleshooting or contacting AppsAnywhere Support in relation to an issue, the log files are essential.

They provide extensive data about the launch process, virtualization process, environment, server, and end user device when an error is encountered.

Reviewing the logs, as well as providing AppsAnywhere Support with a copy and remote access, particularly to the servers, can lead to a much quicker issue resolution time. Without them, the support team may not be able to identify the root cause.

Log files can be found in the following locations and a full, extended (verbose) copy should be provided from as many servers and client machines as possible when contacting AppsAnywhere Support.

Client Logs

AppsAnywhere Client

The AppsAnywhere Client log (S2HubTracelog.log) provides information about the users environment, details of the validation request and the response from the server.

Windows

The AppsAnywhere Client validation log for each user can be found in the following directory on client machines:

%localappdata%\software2\AppsAnywhere\Log

A PowerShell command AppsAnywhere_Export_Client_Events.txt (rename to .ps1) can be run with administrator permissions to export to a .csv file.

MacOS

The AppsAnywhere Client validation log on MacOS (com.s2.uk.AppsAnywhere <date>.log) for each user can be found in the following directory on client machines:

~/Library/Logs/Software2 

or

/Users/username/Library/Logs/Software2

From the Finder menu select the Go to Folder... option

Enter ~/Library/Logs/Software2 and Go

The Finder will now display the folder containing the log files e.g.

Cloudpaging Player

StreamingCore.log provide extensive information about the virtualization process and virtual applications along with detailed information on server responses.

Ensure extended logging is enabled in File > Options > Log and reproduce the steps that caused the error.

The log file can be found in the following directory:

C:\ProgramData\Endeavors Technologies\StreamingCore\Log

Cloudpaging Player Analyzer

In addition to the Player log, this also provides information about the device.

1. Download NumecentClientAnalyzer_Multilanguage.txt (appsanywhere.com)
2. Change the file extension to *.vbs 
3. Double click the *.vbs file to execute
4. Follow the prompts to complete the data collection
5. Attach the "Numecent_Support_Analysis_Bundle(date-time).zip"  to the support ticket

Full details are available on the Cloudpaging Player Analyzer article.

Parallels Client

The Parallels Client log location depends on Operating System being used. You can enable extended logging via Tools > Options:

 

 

Linux and Igel 

~/.config/2X/Client/ClientLog.log

macOS

~/Library/Containers/com.2X.Client.Mac/Data/ParallelsClient.log

or 

~/Library/Containers/Parallels Client/Data/ParallelsClient.log

Windows

%AppData%\2XClient\ClientLog.txt

Android

/storage/emulated/0/Android/data/com.parallels.client/files/logs/

Cloudpaging via Parallels RAS

The following list covers the logs that are generated in sequence during the launch of a Cloudpaging app via Parallels RAS. If there is an issue with this type of launch, it is often necessary retreive all sets of log files to determine exactly where the error occurs.

For a faster resolution please provide one or all of:

1. AppsAnywhere Client log from the end user device
2. Parallels Client log from the end user device 
3. AppsAnywhere Client log from the RDSH servers (or the one that the user has connected to). The RAS admin console can be used to look at the session and see which server it is connected to.
4. Cloudpaging Player log from the same RDSH server(s)
5. Parallels RAS server logs

Web Browsers

The in built developer tools can provide useful information on network requests and the server response. 

To generate a browser log (.har) file 

1. Open the web browser
2. Press F12 or navigate to Developer Tools
3. From the panel opened, select the Network tab
4. Look for a round Record button, and make sure it is activated
5. If it is grey, click it once to Start Recording
6. Check the box Preserve Log
7. Click the Clear button to clear out any existing logs from the Network tab
8. Reproduce the issue 
9. Right-click on the grid of network requests, select Save as HAR with Content, and save the file
10. Upload the .har file to a ticket or attach it to an email response

Server Logs

Server logs provide extensive data about the state of the services when an error is encountered.

Log files are available for each service. The full logs can be found in the following directories:

AppsAnywhere 

From AppsAnywhere 2.9, these log files and are saved in:

/var/www/appsanywhere/logs

Customers can view these logs by logging into the AppsAnywhere appliance via the hypervisor with the 'setup' user (configured during first time configuration) and selecting View Log Files:

Legacy versions (AppsAnywhere 2.8 and older)

C:\Program Files (x86)\Zend\ZendServer\logs
C:\Program Files (x86)\Zend\Apache24\logs

Cloudpaging 

C:\Program Files (x86)\Numecent\Application Jukebox Server\core\logs

Parallels RAS

C:\ProgramData\Parallels\RASLogs

RAS Console 

Server Components

1. Change the Logging Level in Settings > Global Logging 
   
2. Click Retrieve and select all components to capture logs and to save them to a .zip file
   

Alternatively

1. Collect and send a RASAttachment.zip file 

Guest Agents

1. The Logging Level can be changed by right clicking Guest VM(s) > Troubleshooting > Logging > Configure
2. Retrieve – Allows logs to be saved locally to a .zip file.

Further information is available via Logging (parallels.com)