1. Unrecoverable error occurred while executing the Web application routine
In your browser, when executing your web page, you get an error message similar to the following displayed:
Provided the application is running in your IDE, then the cause is almost certainly a missing table. Make sure that all the tables that your application requires are in the Repository List. If that still does not fix it then you will need to enable tracing on the target system in order to identify the cause.
2. No table data is displayed in your browser
There are many issues that might cause this, but when the web page is displayed but not the data, it is because the application server cannot be reached. And this might be caused by an incorrect web-alias or a duplicate web-alias.
Use Windows Explorer to locate the file <root>\run\conf\lansaweb.conf. Find the value of web-alias. Check that it is the value being used in the URL. For example, if the URL you used is: http://localhost:8081/shopping/dem/xdtools.html?Page=HandTools
then check that the web-alias is 'shopping'
3. GitDeployHub output indicates the deployment failed when installing the package
If the application has not yet been deployed successfully, then check that the user NT Authority\System (LocalSystem) has the correct rights to the database to create tables.
Firstly, check that it is in the db_owner role as shown here:
And secondly, check that the user's login has been granted the securityadmin role as shown here:
4. NT AUTHORITY\SYSTEM must not be given the permissions described in (3)
Your organisation may have a site policy not to grant these permissions or your database server may not be local to this machine.
You must provide a user who has these permissions to the database and database server. So allocate one. This user must then be the Identity which the Hub website uses. Open IIS and navigate to the Application Pools. Right click on the Hub website and choose Advanced Settings. The dialog is show here:
Locate the Identity line and click on the ellipses to change the Identity to the user you have chosen to use for the deployment.
This user will also need to be and administrator of the machine to gain access to the application's website directory.
Also ensure that the user or administrators have access to the SSH key you are using.
Note that there is a script to set these permissions for LocalSystem which is easily modified for a different user. See <installation root>\Tools\gitdeployhub\Install\setdbauthority.ps1
5. Smoke Test fails
The log file on the Git Deploy Hub fails and is highlighted in red. The log contains a message similar to this:
[email protected]:lansa/yourname-v14-dem.git (fetch)
[email protected]:lansa/yourname-v14-dem.git (push)
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
git fetch returned 128
Check HOME environment variable is set correctly for the current user - see top of log output.
The machine must be rebooted in order to propagate environment variable changes to the svchost.exe process which hosts iis (w3wp.exe).
There are several things to check:
a. IIS is using the wrong Identity
What is the UserID displayed in the Parameters section of the Git Deploy Hub interface? Is this correct? If not then the Identity of the Application Pool needs to be changed. to the correct user id.
b. The HOME environment variable is not set to the location of the SSH file.
The value of the HOME environment variable that this user is using is displayed near the top of the log. The LocalMachine setting of the HOME environment variable is usually used. If the System settings indicate that HOME is correctly set, then reboot the machine so that svchost.exe receives the update. If HOME is not correct, change it and reboot.
c. You specified an incorrect GitHub repository URL
Check the remote origin's URL in the smoke test log is correct. (The first two lines in the example.)
d. The ssh key is not authorized to access the repository in GitHub.
Go to GitHub and check that the user associated with the SSH key has permission to read the git repository and that the SSH key matches the user.