Configuration error messages

A list of configuration error messages. For messages that are not self-explanatory, additional information is provided.

Table 1. Configuration error messages
Number	Description
GS-19001	`Unable to send data to a non connected remote task.` Internal error.
GS-19002	`Remote server unavailable.` Cannot connect to the remote host.
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 %1.` Error message and resolution should be self-explanatory.
GS-19100	`Host address and port pair must be unique: %1 host configuration has same host (%2) and port (%3)"` Error message and resolution should be self-explanatory.
GS-19101	`Connecting to '%1'`
GS-19102	`Connection failed: cannot connect to the Genero Studio Server` Error message and resolution should be self-explanatory.
GS-19103	`Connection failed: the Genero Studio Server uses a different protocol version` The versions of Genero Studio and Genero Studio Server do not match. See Remote environment software requirements.
GS-19104	`Client IP address has been converted from IPv6 to IPv4. Client IP address has been converted from IPv6 to IPv4. Client IP address is invalid. FGL runner may not manage to connect to GUI.` Error message and resolution should be self-explanatory.
GS-19105	`No mount point defined` Error message and resolution should be self-explanatory.
GS-19111	`Cannot write temporary file '%1` Error message and resolution should be self-explanatory.
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. If the issue is access permission, update the permissions on the file and/or the directory. If the file does not exist, you can retry the operation. If that does not fix the issue, you can delete the .gst hidden directory on both the client and the server, and then retry the operation. If that does not solve the issue, contact your local support.
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. 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. If the issue is access permission, update the permissions on the file and/or the directory. If the directory does not exist, you can retry the operation. If that does not solve the issue, contact your local support.
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. If the issue is access permission, update the permissions on the file and/or the directory. If the directory does not exist, you can retry the operation. If that does not solve the issue, contact your local support.
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.
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. Please contact your local support.
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. If the issue is access permission, update the permissions on the file and/or the directory. If the file does not exist, you can retry the operation. If that does not fix the issue, you can delete the .gst hidden directory on both the client and the server, and then retry the operation. If that does not solve the issue, contact your local support.
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. If the issue is access permission, update the permissions on the file and/or the directory. If the file does not exist, you can retry the operation. If that does not fix the issue, you can delete the .gst hidden directory on both the client and the server, and then retry the operation. If that does not solve the issue, contact your local support.
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.
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-19300	`<Choose a Genero Install>` Informational message.
GS-19301	`<Choose a Display Client>` Informational message.
GS-19302	`<Choose an Application Server Configuration>` Informational message.
GS-19303	`Fetching infos from GAS...` Informational message.
GS-19304	`GAS has refused to give informations. Verify your GAS settings` Failed to start GAS. This message will only be seen for GAS versions >= 2.40. Starting with 2.40, once the GAS version number is retrieved, Genero Studio tries to get the information about the application groups. This message appears when the retrieval of the GAS version number is successful, yet the retrieval of the application group information is not successful. To remedy the issue, verify that the GAS is started, and that the host and port values are correct. The GAS should also be configured to allow Genero Studio access to the GAS monitor. By default, the GAS monitor can only be accessed from the localhost, and Genero Studio/gsserver must be on the same machine as the GAS to access it.
GS-19400	`Path cannot be empty` Error message and resolution should be self-explanatory.
GS-19401	`Host IP address cannot be empty` Error message and resolution should be self-explanatory.
GS-19402	`Display client will not be accessible from other machines` Error message and resolution should be self-explanatory.
GS-19500	`Application group directory cannot be empty` Error message and resolution should be self-explanatory.
GS-19501	`Parent application cannot be empty` Error message and resolution should be self-explanatory.
GS-19502	`Application group cannot be empty` Error message and resolution should be self-explanatory.
GS-19503	`Start script path cannot be empty` Error message and resolution should be self-explanatory.
GS-19504	`Connector cannot contain only blanks` Error message and resolution should be self-explanatory.
GS-19505	`Web service group directory cannot be empty` Error message and resolution should be self-explanatory.
GS-19506	`Parent web service cannot be empty` Error message and resolution should be self-explanatory.
GS-19507	`Web service group cannot be empty` Error message and resolution should be self-explanatory.
GS-19600	`Incorrect environment variable '%1' 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...` Informational message.
GS-19707	`A network error occurred while checking GAS version (%1)` `%1` may be one of the following: `2`: The remote server closed the connection prematurely, before the entire reply was received and processed. `3`: The remote host name was not found (invalid hostname) . `4`: The connection to the remote server timed out. `5`: The operation was canceled via calls to abort() or close() before it was finished. `7`: The connection was broken due to disconnection from the network. However, the system has initiated roaming to another access point. The request should be resubmitted and will be processed as soon as the connection is re-established. `8`: The connection was broken due to disconnection from the network or failure to start the network. `9`: The background request is not currently allowed due to platform policy. `10`: While following redirects, the maximum limit was reached. The limit is set by default to 50. `11`: While following redirects, the network access API detected a redirect from a encrypted protocol (https) to an unencrypted one (http). `99`: An unknown network-related error was detected. `101`: The connection to the proxy server was refused (the proxy server is not accepting requests). `102`: The proxy server closed the connection prematurely, before the entire reply was received and processed. `103`: The proxy host name was not found (invalid proxy hostname). `104`: The connection to the proxy timed out, or the proxy did not reply in time to the request sent. `105`: The proxy requires authentication in order to honour the request but did not accept any credentials offered (if any). `199`: An unknown proxy-related error was detected. `201`: The access to the remote content was denied (similar to HTTP error 403). `202`: The operation requested on the remote content is not permitted. `203`: The remote content was not found at the server (similar to HTTP error 404). `204`: The remote server requires authentication to serve the content but the credentials provided (if any) were not accepted. `205`: The request needed to be sent again, but this failed. For example, failure might occur because the upload data could not be read a second time. `206`: The request could not be completed due to a conflict with the current state of the resource. `207`: The requested resource is no longer available at the server. `299`: An unknown error related to the remote content was detected. `301`: The Network Access API cannot honor the request because the protocol is not known. `302`: The requested operation is invalid for this protocol. `399`: A breakdown in protocol was detected (for example, parsing error, invalid or unexpected responses). `401`: The server encountered an unexpected condition which prevented it from fulfilling the request. `402`: The server does not support the functionality required to fulfill the request. `403`: The server is unable to handle the request at this time. `499`: An unknown error related to the server response was detected.