Configuration error messages
A list of configuration error messages. For messages that are not self-explanatory, additional information is provided.
Number | Description |
---|---|
GS-19001 | File 'file'
already exists. Error message and resolution should be self-explanatory. |
GS-19002 | Remote server unavailable. Cannot connect to the remote host. |
GS-19003 | Unable to send data to a non
connected remote task. Internal error. |
GS-19004 | Remote processing error. Internal error. |
GS-19005 | Incompatible server protocol. The protocol versions in the client and the server are not the same. See Remote environment software requirements. |
GS-19006 | A server is listening on the given port, but it isn't
a Studio Server. Error message and resolution should be self-explanatory. |
GS-19007 | Studio Server is listening on the given port, but it
doesn't use the same protocol version.
Error message and resolution should be self-explanatory. |
GS-19008 | Disconnection has been forced by the client. Error message and resolution should be self-explanatory. |
GS-19009 | The server disconnected. Error message and resolution should be self-explanatory. |
GS-19010 | Internal socket error.
Internal error. |
GS-19011 | Request aborted.
Internal error. |
GS-19012 | Server is not reachable or doesn't listen on given
port. Error message and resolution should be self-explanatory. |
GS-19013 | Connected to 'value'.
Error message and resolution should be self-explanatory. |
GS-19111 | Cannot write temporary file
'file' Error message and resolution should be self-explanatory. |
GS-19112 | Application group
'group' is not present on the Application Server The application group selected in the active configuration is not found in the GAS. |
GS-19113 | The directory for application
group 'group' doesn't match the Application Server one The directory of the application group selected in the active configuration does not match the directory defined in the GAS. |
GS-19200 | Synchronization failed: Cannot read 'timestamp.info'
file. When synchronization directories are used in to create a remote configuration for Genero Studio, a hidden directory (.gst) is created in the local directory. A timestamp.info file is written to this directory to store the time of the last synchronization. This
error occurs when the file cannot be read. Either the file does not exist, or
there is an access permission issue.
|
GS-19201 | Synchronization failed: Cannot write 'timestamp.info'
file. When synchronization directories are used in to create a remote configuration for Genero Studio, a hidden directory (.gst) is created in the local directory. A timestamp.info file is written to this directory to store the time of the last synchronization. |
GS-19202 | Synchronization failed: Cannot write 'excluded.info'
file. When synchronization directories are used in to create a remote configuration for Genero Studio, a hidden directory (.gst) is created in the local directory. A excluded.info file is written to this directory to list all files that will not be synchronized, to include files that have been modified since synchronization to the server, and therefore should not be synchronized back from the server. See Define synchronization directories for more information on excluding files from synchronization. This error occurs when the file cannot be created or written
to. Possible issues could be that the .gst directory no longer exists, or
access rights (write permission) have not been granted.
|
GS-19203 | Synchronization failed: Timestamp is not in the correct
format. The timestamp.info file is not in the correct format. In practice, this error should not occur. If you receive this error, delete the timestamp.info file and restart the synchronization operation. |
GS-19204 | Synchronization failed: Synchronization directory is
invalid. The synchronization directory is invalid. In practice, this error should not occur. If you receive this error, contact your local support center. |
GS-19205 | Synchronization failed: An error occurred during the locking
request. Locking of the remote directory has failed. This error can indicate a network issue or a file writing issue. Check your network connections and check your file-writing permissions on the remote directory. |
GS-19206 | Synchronization failed: Connection to server is in
progress. Connection is still in progress when trying to lock the remote directory. This error is not expected in practice. Contact your local support center. |
GS-19207 | Synchronization failed: Task has been aborted by
user. The user has aborted the task, from either the Task Manager or by switching configurations. There is no additional action to take, as the task was aborted by the user. |
GS-19208 | Synchronization failed: Cannot read 'dirid.info'
file. When synchronization directories are used in to create a remote configuration for Genero Studio, a hidden directory (.gst) is created in the local directory. A dirid.info file is written to this directory to store a unique identifier for the directory. This
error occurs when the file cannot be read. Either the file does not exist, or
there is an access permission issue.
|
GS-19209 | Synchronization failed: Cannot write 'dirid.info'
file. When synchronization directories are used in to create a remote configuration for Genero Studio, a hidden directory (.gst) is created in the local directory. A dirid.info file is written to this directory to store a unique identifier for the directory. This
error occurs when the file cannot be read. Either the file does not exist, or
there is an access permission issue.
|
GS-19210 | Synchronization failed: Invalid hash
string. Before doing synchronization, The local directory and the remote directory hashed identifiers are compared. If they do not match, this error is raised. This error occurs when the client directory is not associated with the remote directory. Verify your configuration. If your configuration is verified, then contact your local support center. |
GS-19211 | Synchronization failed: 'dirid.info' not a client
file. When synchronization directories are used in to create a remote configuration for Genero Studio, a hidden directory (.gst) is created in the local directory. A dirid.info file is written to this directory to store a unique identifier for the directory. The dirid.info file format differs between the client (local) and remote directories. If the client directory has a dirid.info file that uses the remote format, this error is raised. This error occurs when the server directory has been used as a client directory. You must specify a different directory as the client directory, as a directory can either be a client directory or a server directory, but it cannot be both. |
GS-19600 | Incorrect environment variable
'variable' value Error message and resolution should be self-explanatory. |
GS-19601 | Put one and only one Genero Mobile for Android
package in $(GMADIR) Error message and resolution should be self-explanatory. |
GS-19602 | Display Client type should be 'iOS' or 'iOS
Simulator' Error message and resolution should be self-explanatory. |
GS-19603 | Debug server connection error, check if the mobile
app is running on the device
Error message and resolution should be self-explanatory. |
GS-19604 | Starting display client...
Error message and resolution should be self-explanatory. |
GS-19701 | Invalid GAS startup
path. The path of the GAS startup script is wrong. |
GS-19702 | GAS has failed to
start. The GAS startup script finished with an error. |
GS-19704 | GAS has been successfully
started. Error message and resolution should be self-explanatory. |
GS-19705 | GAS is not started. Starting
it. The GAS was not found running and will be started using the GAS startup script. |
GS-19706 | A GAS is currently running on
port 'port' Error message and resolution should be self-explanatory. |
GS-19707 | A network error occurred while
checking GAS version (value) value may be one of the
following:
|
GS-19708 | SSL handshake has failed. Verify
that you have a valid certificate. An SSL error occurred while trying to start the GAS. |