GeneXus Server Troubleshooting

Official Content
This documentation is valid for:

When experiencing issues with GeneXus Server, a set of different logs can be examined to get more information about the possible errors. This article summarizes the various log files for GeneXus Server and in which situations they could be of help.

First of all, there are a couple of files which can be helpful when more information about the problem is needed:

GXSetup.log

The GXSetup.log records all the errors and actions taken during the installation process. This file is located in the GeneXus Server installation directory and can be of help when the setup process fails, or GeneXus Server does not operate in a correct manner just after installation.

GXServer.log

The GXServer.log records all the errors of the GeneXus Server business logic—not its web interface. This file is located in the GeneXus Server installation directory and can be of help in general. See Tracing GeneXus Server for further information.

client.log

The client.log records all the errors that occur in the GeneXus Server interface and GeneXus Access Manager. This file is located in the GeneXus Server installation directory and can be of help in general. This log can be activated by changing the <log4net threshold="OFF"> option to <log4net threshold="ALL"> in the web.config file located under C:\<GeneXus Server Dir>\Vdir folder.

Errors

  • IIS Error
========== Get versions started ==========
Contacting GeneXus Server at '<GeneXus Server Instance>'... done!
========== Commit started ==========
Contacting GeneXus Server at '<GeneXus Server Instance>'... done!
error: GeneXus Server: 500 - internal server error.
Commit Failed

Generally, when a 500 error occurs means that the problem is related to the IIS configuration.

In order to have more information about the cause of the problem choose one of the following options:

  •  Go to the Error Pages option of the IIS console:

GXServerTroubleshooting1

And select the Edit Feature Settings. 

GXServerTroubleshooting2

Verify that the 'Detailed Errors' option is selected in the Error Responses options:

  • Enable the GeneXus Server log (GXServer.log) as described before.

Retry the operation which caused the problem and verify that the GXServer.log contains the error's information. 

Contact Support Team including the GXServer.log file.


Was this page helpful?
What Is This?
Your feedback about this content is important. Let us know what you think.