This page summarizes some of the errors relative to the GeneXus Access Manager that may be encountered through the various stages (during the build or in runtime), and explains the causes of such errors and how to solve them.
Detailed error:
error: Cannot connect with GAM repository with the given Administrator or Connection user.
error: GAM(): Connection not found.
error: GAM(): Repository connection failed for user .
Integrated Security Initialization Failed
error: Build cancelled.
error: Operation Canceled by the user
Run Developer Menu Failed
Cause: Must specify information on Administrator User Name Property, Administrator User Password Property, Connection User Name Property, or Connection User Password Property.
This may happen when the GAM’s DB already exists and the GAM’s corresponding Administrator user and Connection user were not specified in the properties.
In the case of a KB with an environment ('Env1') with enabled GAM (Enable Integrated Security property= true), if a new environment ('Env2') is created.
If the setting of the GAM’s datastore of Env2 is the same as that of the datastore of Env1 (for example, when the database name of the main datastore of Env2 setting is equal to the database name of environment Env1, and if default values are always taken, then the database of the GAM datastore of Env2 will be the same as that of Env1).
Another case is the creation of a KB where the GAM’s datastore (database name) is set up pointing to a DB that already contains a GAM repository.
When F5 is executed without previously assigning Administrator User Name Property, Administrator User Password Property, Connection User Name Property, Connection User Password Property, then the error mentioned will occur.
Detailed error:
error: Cannot connect with GAM repository with the given Administrator or Connection user.
error: GAM(): Repository password failed for user testreg1.testreg1.
Integrated Security Initialization Failed
error: Build cancelled.
error: Operation Canceled by the user
Run Developer Menu Failed
Cause: Connection User Password Property wrongly set up.
Detailed error:
error: Cannot connect with GAM repository with the given Administrator or Connection user.
error: GAM(): Connection not found.
error: GAM(): Repository connection failed for user testreg1.testreg.
Integrated Security Initialization Failed
error: Build cancelled.
error: Operation Canceled by the user
Run Developer Menu Failed
Causes:
• Setting of Connection User Name Property, or Connection User Password Property wrong or does not exist for that DB in the GAM.
• Wrong setting of the GAM’s Repository ID Environment property.
Detailed error:
error: Cannot connect with GAM repository with the given Administrator or Connection user.
error: GAM(): User password incorrect.
Integrated Security Initialization Failed
error: Build cancelled.
error: Operation Canceled by the user
Run Developer Menu Failed
Cause: Administrator User Password Property wrongly set up.
Detailed error:
error: Cannot connect with GAM repository with the given Administrator or Connection user.
error: GAM(): User unknown.
Integrated Security Initialization Failed
error: Build cancelled.
error: Operation Canceled by the user
Run Developer Menu Failed
Cause: Administrator User Password Property wrongly set up, does not exist. Note that the Administrator user is created only when the GAM’s DB is created; if the DB already exists, then the user specified in the corresponding property must exist in the DB.
GAM Permissions Creation
Reading KB Applications ...
Application environment not found. (GAM133)
Cause:
GAM Permissions are generated in association with each GAM Application. This error may occur if, upon generating permits, the GAM does not find an application in the GAM’s DB that is identified by the value set in the Application Id Property. The value of this property is auto-assigned when a KB is created and the GAM is enabled. It is editable to allow a KB to point to an existing DB in the GAM and use an existing application.
Registering 'Dashboard1'...Your password has expired, please change it now. (GAM24)
error: Cannot register the application in GAM repository.
error: GAM(): Your password has expired, please change it now.
Failed
Cause: The password of administrator user shown in the Administrator User Name Property has expired. We must go through the GAM Web Backoffice to change the password and then assign that value to the Administrator User Password Property.
========== Retrieve GAM Version From Database started ==========
error: Unable to load DLL 'libmySQL.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Current GAM version:
Retrieve GAM Version From Database Success
Cause: GAM processes executing in the GeneXus IDE use csharp and ADO Net to connect to the GAM’s DB (detect GAM version in the DB, record applications, generate permits).
This is why the ADO Net client corresponding to the DBMS used is required; for the case of Mysql download it from here. You need to install the driver for 32 bits because the processes inside GX IDE use 32 bits, so the 32bit libmysql.dll has to be copied to the c:\windows\syswow64 folder. In runtime, you can use the driver for 64 bits.
error CS0006: Metadata file 'bin\Artech.Security.dll' could not be found
Compiling gamsdlogin_gamlogin_section_general...failed ( error code=1)
Microsoft (R) Visual C# 2008 Compiler version 3.5.30729.5420 for Microsoft (R) .NET Framework version 3.5
Copyright (C) Microsoft Corporation. All rights reserved.
Solution: Must be enabled GAM in the model when consolidating objects that refer to the GAM’s external objects. Also, in NET models, Compiler Flags must be set with value /r:bin\Artech.Security.API.Common.dll.
A failure upon verifying the Repository Connection.
The connection.gam file is not correct according to the connections defined in that repository.
connection.gam not found in the web application.
application.gam file not found.
The information on the connection.gam does not match the information on the GAM’s Repository table. Verify that the connection.gam located in the application’s directory is the right one.
Cause: the connection.gam is not in accordance with the Repository Connections. Specifically, there is a difference in the connection password for the user.
Probably, one of the following is happening:
- The password of the connection user has changed, and you haven't changed it in the "Connection User Password property" accordingly.
By default, the password is <name of the KB>123, see Connection User Password property.
If it has been changed, you need to know the new password. If not, you have to generate a new Repository Connection.
- The connection.gam is not correct or is not updated. In this case, you can remove it from the web folder so it can be generated again by the rebuild all.
For additional information see this link.
Go to How to debug errors when using Authentication Type through external web services and the GAM.
Using Custom Authentication Type the error is thrown when the authentication type is misconfigured.
In case that the external Procedure is called "gamwslogin", the error is thrown when the class name is set to gamwslogin, instead of agamwslogin.
If the application authenticates using Facebook, and you get the following error:
Http 1.00 - Connection has been shutdown: javax.net.ssl.SSLHandshakeException:sun.security.validator.validatorException:PKIX path building failed:sun.security.provider.certpath:SunCertPathBuilderException: unable to find valid certification path to request target - StatusCode:0
Check that Java 1.7 or upper is installed on the application server. See GAM Facebook Authentication Type (Software Requirements).
Sometimes this error could appear. The problem is related to the decrypt algorithm when trying to decrypt the GAM User. See this SAC for further information.
When using Iseries, take into account that the date data type fields in GAM tables are created as char data types, so the Date Data Type definition property must be set to Char, not to Date.
Otherwise, the application throws the exception: java.sql.DataTruncation: Data truncation. For more information see SAC 36455.
Deploying to a server details the GAM111 error when executing the GAMRepository.GetOuthAccessToken method. Verify that the machine Timezone configuration is consistent. Otherwise please check the SAC #45012: GAM111 - Application Client Revoked notes.
1. The selected database does not have a GAM database schema.
Cause: it may happen if the file Template.client.exe.config is not under the folder of the GAM platform (for example C:\Program Files (x86)\Artech\GeneXus\GAM Deploy Tool\Resources\Platforms\NetSQL\NetSQL) or the access to the file client.exe.config under the same directory is denied. Check the log generated under the temp directory to see information about the error.
2. The user or password is incorrect. (GAM18)
Cause: The GAM deploy tool requires entering using the gamadmin credentials (by default gamadmin/gamadmin123).
As since GeneXus 15 upgrade 4, to generate a trace for the processes that run within the IDE, do the following:
- Activate the NET or Java log (depending on the environment)
- If you indicate a relative path to the log, it's generated under <data model>\Library\GAM
For older versions of GeneXus:
Edit the file <GeneXus>\library\gam\gamclient.exe.config.template and modify: <log4net threshold="All">.
The log file generated is located in the model directory (specifically at <data model>\Library\GAM\gamclient.log)
HowTo: Generate GAM trace
HowTo: Generate trace of GAM Deploy Tool
Error Codes and Messages for GAM