Administrator Guide : 5. Basic Troubleshooting and Tracing : Common Errors when Connecting to an Enterprise Access Server
 
Share this page                  
Common Errors when Connecting to an Enterprise Access Server
The following error messages are associated with connecting to an Enterprise Access server:
E_GC000B_RMT_LOGIN_FAIL
Remote login failure: invalid password/userid. If using installation passwords, please make sure all servers are 6.4/02 or newer and that they have been started by the installation owner.
Reason:
Caused by an incorrect username, password, or combination of both, or the remote Name server is not able to check passwords.
Action:
If remote server is a UNIX machine, see the Ingres Command Reference Guide for instructions on running mkvalidpw.
If remote server is on a Windows machine, ensure that the installation owner has the correct Advanced Operating System permissions (see the Getting Started for details).
E_GX0100
Error accessing Gateway System tables: Database not accessible by the gateway.
Reason:
Usually caused by missing Enterprise Access system catalogs or the user lacking appropriate access permissions.
Action:
Add the correct permissions (see DBMS Setup Requirements) and ensure that Enterprise Access catalogs have been generated correctly.
Ensure that the host database to which Enterprise Access is attempting to connect is accessible by the user attempting the connection and that queries may be issued. Use host DBMS tools to connect as the DBMS user that the alias definition uses; for example, for Oracle use sqlplus. Possible causes of problems are incorrect username/password/database name, host DBMS networking errors, insufficient DBMS permissions to the database (or to objects within the database).
Ensure that the Enterprise Access system catalogs were generated correctly; that is, ensure iigwcatxxx where xxx is the three-letter abbreviation for the server class, has been run. See Basic Troubleshooting and Tracing for more information on creating system catalogs.