Below is a list of common issues related to the installation and execution of GeneXus Next Desktop.
To determine which version you are running, open the docker-compose.yml file included in the zip file of GeneXus Next that you downloaded from the GeneXus website.
Strings like "GXWEB_IDE_VERSION:-0.0.566" and "GXWEB_BL_VERSION:-bl-182121-services1.0.681" are the ones that identify the version; that is, the ones you should copy and include in any report to the Support team.
Another way to find out the version is to look in the Docker Desktop application. To do so, open it and click on the corresponding container (gxms-1 or gxweb-1). Once inside the selected container, you can see the version under the title, in the version link after the slash ('/').
Detailed logs are generated in the Docker containers. Typically, the container named "gxms-1" runs the backend services and business logic of GeneXus and has the stack trace or exception you need to send to the Support team.
1. Copy the gxlogging.config file to the GeneXus directory. For example:
docker cp C:\User\username\Downloads\gxlogging.config genexus-gxms-1:/app/gxlogging.config
2. Restart the container gxms-1 and refresh the web IDE.
3. Carry out the steps that are failing.
4. Copy the GXBL.log file to a local directory. For example:
docker cp genexus-gxms-1:/app/GXBL.log c:\Temp\GXBL.log
5. Look at the log file (c:\Temp\GXBL.log).
To execute a PowerShell script, it is required to have unrestricted execution policies. Otherwise, it will give this error:
PS C:\genexus\gxnext> ./dup.ps1
./dup.ps1 : File C:\genexus\gxnext\dup.ps1 cannot be loaded because running scripts is disabled on this system. For more
information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ ./dup.ps1
+ 05/02/24 08:15 PM[[User:user1]] 05/02/24 08:15 PM
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
PS C:\genexus\gxnext> Set-ExecutionPolicy Unrestricted
You will get something similar to the following:
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"): Y
PS C:\genexus\gxnext> ./dup.ps1
[+] Running 29/18
✔ gxweb 11 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 0B/0B Pulled 127.5s
✔ gxms 11 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 0B/0B Pulled 172.0s
✔ sql 4 layers [⣿⣿⣿⣿] 0B/0B Pulled 200.5s
Do not unzip the GeneXusNextDesktop*.zip or *.tar.gz in the Program Files folder to avoid being denied access.
Otherwise, when executing:
PS C:\Program Files (x86)\gxnext> ./dup.ps1
An access denied error will be displayed.
Unzip it inside a folder with a simple name.
When downloading the zip file, it may get blocked. If that happens, this error is displayed:
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run C:\GeneXusNextRUN\dup.ps1?
[D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"):
Type 'R'.
When executing the dup.sh script, the following error may be displayed:
permission denied: ./dup.sh
You have to assign running permissions to the dup.sh script, so that it can be executed from the terminal. To do so, write:
chmod +x ./dup.sh
After that, execute the script:
./dup.sh
When executing the dup.ps1 script, the following error may be displayed:
✘ gxms Error context canceled
✘ gxweb Error context canceled
- sql Pulling
no matching manifest for windows/amd64 10.0.22631 in the manifest list entries
You have to switch to Linux Containers. (ref.)
When running the dup.ps1 script, the following error may appear:
failed to read expected number of bytes: unexpected EOF
This error typically occurs when the download of the required images is interrupted before completion.
It indicates that the end of the file (EOF) was reached unexpectedly, and the script attempted to read more data than was available due to the incomplete download.
This is a temporary error. Run the dup.ps1 script again.
This usually occurs when one of the required ports is already in use by another process.
Ports used by GeneXus Next:
- gxweb: 3000
- gxms-1: 4200, 8001, 8080, 8082
- genexus-sql-1: 1433
- genexus-android: 8022
- genexus-pgsql-1: 5432
Check if the port is in use and stop the process.
On Windows
Run:
netstat -ano | findstr <PORT>
Then, to stop the process:
taskkill /PID <PID> /F
On macOS
Run
lsof -i :<PORT>
Then, to stop the process:
kill <PID>
Once the port is free, run ./dup.ps1 again.
This error message is displayed when the GeneXus Module version installed on the KB being used doesn't match the GeneXus Module version provided by the GeneXus version being run. To solve this situation, proceed as follows:
-
Close GeneXus Next Desktop.
-
Stop the containers (in Rancher/Docker, or shut down Rancher/Docker directly).
-
Remove the SQL container. To do so, execute:
docker stop gxms_shared-sql-1
docker rm gxms_shared-sql-1
docker volume rm gxmodules_repository
Note: With the default configuration of GeneXus Next Desktop, Knowledge Bases are not lost when removing the containers and the volume, as they are stored on the host. For more information, see
Where are Knowledge Bases stored?.
GeneXus Next Desktop - Setup and Troubleshooting Guide for Running Native Mobile Apps