To debug and troubleshoot problems, you can view the Omnissa Access connector log files, which are stored on the connector server. The Directory Sync, User Auth, Kerberos Auth, and Virtual App services each have their own log files.
Connector Log Files
| Type of Log File | Log File Location | Description |
|---|---|---|
| Installation log file | ConnectorInstallerFolder\Access_Connector_Installer.log | Messages related to installation |
| User Auth service log files | INSTALL_DIR\Access Connector\User Auth Service\logs\eas-service.log | Messages related to authentication |
| Directory Sync service log files | INSTALL_DIR\Access Connector\Directory Sync Service\logs\eds-service.log | Messages related to directory sync |
| Kerberos Auth service log files | INSTALL_DIR\Access Connector\Kerberos Auth Service\logs\eks-service.log | Messages related to Kerberos authentication |
| Virtual App service log files | INSTALL_DIR\Access Connector\Virtual App Service\logs\eis-service.log | Messages related to virtual apps integration |
| Enterprise services vertex logs | INSTALL_DIR\Access Connector\User Auth Service\logs\eas-vertx-access.logINSTALL_DIR\Access Connector\Directory Sync Service\logs\eds-vertx-access.logINSTALL_DIR\Access Connector\Kerberos Auth Service\logs\eks-vertx-access.logINSTALL_DIR\Access Connector\Virtual App Service\logs\eis-vertx-access.log | Information about the API requests on the enterprise services. |
| Enterprise services process standard output logs | INSTALL_DIR\Access Connector\User Auth Service\logs\UserAuthService.out.log INSTALL_DIR\Access Connector\Directory Sync Service\logs\DirectorySyncService.out.logINSTALL_DIR\Access Connector\Kerberos Auth Service\logs\KerberosAuthService.out.logINSTALL_DIR\Access Connector\Virtual App Service\logs\VirtualAppService.out.log | Information about the process running the enterprise services. |
| Enterprise services process standard error logs | INSTALL_DIR\Access Connector\User Auth Service\logs\UserAuthService.err.logINSTALL_DIR\Access Connector\Directory Sync Service\logs\DirectorySyncService.err.log INSTALL_DIR\Access Connector\Kerberos Auth Service\logs\KerberosAuthService.err.logINSTALL_DIR\Access Connector\Virtual App Service\logs\VirtualAppService.err.log | Error information about the process running the enterprise services. |
| Enterprise services process wrapper logs | INSTALL_DIR\Access Connector\User Auth Service\logs\UserAuthService.wrapper.log INSTALL_DIR\Access Connector\Directory Sync Service\logs\DirectorySyncService.wrapper.log INSTALL_DIR\Access Connector\Kerberos Auth Service\logs\KerberosAuthService.wrapper.log INSTALL_DIR\Access Connector\Virtual App Service\logs\VirtualAppService.wrapper.log | Information about the process running the enterprise services such as Java options and process ID. |
Enabling DEBUG Mode for Connector Log Files
To help troubleshoot issues with your deployment, you can enable DEBUG mode for the servicename-service.log files. In DEBUG mode, debug messages are written to the log files and provide detailed information about issues.
Contact Support for information on how to turn on DEBUG mode.
Tailing Connector Log Files
You can tail log files to view the bottom n number of lines from a log file. You can also use the -wait option with the tail command to monitor the logs. With the -wait option, the specified number of lines are printed to the console every time the log is updated.
-
In the connector server, open Windows PowerShell.
-
Navigate to the folder that contains the log file.
-
Enter the following command:
Get-Content logFile -Tail numberOfLines –waitFor example:
Get-Content eds-service.log -Tail 2 –wait
Additional Information
For information about increasing the size and number of log files, see Increasing the Size and Number of Omnissa Access Connector Log Files.
Was this page helpful?