When the Installer execution has completed, logs will be in the Installation directory. This is the case for both successful and unsuccessful executions.
Intensive logging is generated with Studio Manager Worker Installer execution. The logs ensure that vital information for all scenarios is retained. One log file is generated; it contains detailed information about each step performed. A new file is generated for every execution.
Example: Evolve_Worker_20.0100.2010.14001_MODIFY_10142020_182857.log Evolve_Worker_20.0100.2010.14001_REPAIR_10142020_183057.log
This file will be available at this location: InstallationDir\ Logs\InstallationLogs
Log is added in case of error while fetching connection string from Evolve server. Error details are logged in the installation log file.
Note: Queues which are created with the machine name are created by the application. If you delete these queues, they are automatically recreated after resetting the IIS.
Evolve/Studio Manager Cloud configurations
Below will be our recommendation for Evolve Server & Worker VMs/Cloud database(Azure SQL
Managed Instance/AWS RDS) configurations: 56
- Evolve Server VM and worker VM should be in the same data center as of Azure SQL Managed Instance or AWS RDS. Both VMs and database instance should be as close as possible.
- Network latency among Evolve/Worker Server VMs and Cloud database instances should be minimal.
Skip SAPUI Check
Below command can be used to skip SAPGUI check in case of installation and is applicable only using command line.
Launch GUI issue 'sapgui start failed' troubleshooting steps