When setting up OutSystems on Microsoft Azure, the first step is to run the solution template wizard to deploy OutSystems infrastructure.
If an error occurs during this deployment phase, you will need the following information to troubleshoot the problem:
- OutSystems configuration files.
- The log files generated by the deployment process.
- The Azure Portal error stack.
This article shows you how to get this information.
Get OutSystems Configuration Files
For each OutSystems environment, you will find the following configuration files:
To get these configuration files, do the following:
- On your Azure Portal, go to the resource group of your OutSystems infrastructure and select the storage account associated to the environment where you got the error, which is <solution_identifier><environment>str<unique_suffix>. For example, if your solution identifier is “myid”, the storage account for the test environment is “myidteststr<unique_suffix>”.
- On the Storage account details page, click Files to access the storage account file service.
- Select share from the list of file shares.
- Select the directory corresponding to the virtual machine of the environment.
- You will find OutSystems configuration files in this directory: private.key and server.hsconf. To download each file, select the file name and click Download.
Get the Log Files Generated by the Deployment Process
For each OutSystems environment, the infrastructure deployment process generates the following log files:
To get these log files, do the following:
- Follow steps 1 to 4 from section Get OutSystems Configuration Files to go to the Directory corresponding to the virtual machine of the environment, inside the storage account file service. Then, select the logs directory.
- You will find the log files in this directory. To download each file, select the file name and click Download.
Get the Azure Portal Error Stack
To get the stack of the deployment error thrown in the Azure Portal, do the following:
- Go to the Resource group of your OutSystems infrastructure and choose Deployments from the menu to the left.
- Click on the failed deployment to expand the error and see the error stack.