The following is a list of the partitioning error messages and suggestions on how some of the errors can be resolved.
|
|
|
|
-0 RQ_OK
|
|
|
-1 RQ_INF_TERMINATE
|
|
|
-2 RQ_INF_TERMINATE_THREAD
|
The thread itself is terminated.
|
|
-3 RQ_INF_RECONNECT_MAIN
|
|
|
-4 RQ INF RETRY
|
|
|
-5 RQ_INF_LOG_ACTIV
|
|
|
-6 RQ_INF_ALREADY_INITIALIZED
|
|
|
-10 RQGNRC_INF_NOWAIT
|
|
|
-11 RQGNRC INF NO RESULT
|
|
|
-32 RQMRG_INF_NO_REQUEST
|
Internal status code of the enterprise server.
|
|
-33 RQMRG_INF_IN_PROGRESS
|
|
-34 RQMRG_INF_CLOSE_APPSERV
|
|
-35 RQMRG_INF_WARNING_ERRS_ON_INIT
|
|
-40 RQMRB_INF_NO_PND_REQ
|
Internal status code of the broker.
|
|
-41 RQMRB_INF_APP_NOT_FOUND
|
|
-42 RQMRB_INF_APP_IN_USE
|
|
-43 RQMRB_INF_RT_NOT_TERM
|
|
-44 RQMRB_INF_ACK_SENT
|
|
-45 RQMRB_INF_CNCT_MAIN_REFUSED
|
|
-46 RQMRB_INF_CNCT_MAIN_NOT_RSPND
|
|
-47 RQMRB_INF_LICENSES_EXCEEDED
|
|
-50 MM_INF_LAST_BIGGER
|
Low-level status code of the memory tables, which are the foundation for broker resource management.
|
|
-51 MM_INF_LAST_SMALLER
|
|
-52 MM_INF_NO_REC
|
|
-53 MM_INF_EOF
|
|
-54 MM_INF_FILTER_LIMIT
|
|
-60 INF TIMEOUT
|
|
|
|
|
|
-102 ERR CNCT REFUSED MRB
|
The connection to the broker was refused. Verify that the broker was started on the port on the specified machine. Refer to its Mgrb.ini file.
|
|
-103 ERR APP NOT FOUND
|
|
|
-104 ERR APP IN USE
|
|
|
-105 ERR MRB NOT RSPND
|
|
|
-106 ERR RT NOT RSPND
|
|
|
-107 ERR CNCT RESET
|
|
|
-108 ERR INVALID REQ HDL
|
When the requester API is used, it may be related to a wrong argument that was passed to the API.
|
|
-109 ERR CNCT REFUSED RT
|
|
|
-110 ERR REQUEST TIMEOUT
|
The execution of the task was not completed during the Request Timeout interval. Increase the RequesterTimeout keyword (in the Mgreq.ini file for Internet or command line, or in the Magic.ini file for Call Remote).
|
|
-111 RQGNRC ERR NOT MRB
|
A requester tried to connect to a TCP/IP server that is not a Magic Broker.
|
|
-112 RQGNRC_WRN_ALT_MRB
|
Obsolete status code.
|
|
-113 RQGNRC ERR APPNAME REQUIRED
|
An application name was not specified in a Call Remote operation.
|
|
-114 RQGNRC ERR PRGNAME REQUIRED
|
A program name was not specified in a Call Remote operation.
|
|
-117 RQGNRC ERR MISMATCHED REQIDS
|
A requester sent a request to a Magic xpa server and received a response that was directed to another request.
Since version: 3.1 (In previous versions, error RQ_ERR_UNEXPECTED (-200) was returned in this scenario.)
|
|
-118 RQGNRC ERR TIME STAMP
|
A requester sent a request to the broker and received a response that was directed to another request.
|
|
-119 ERR LICENSES EXCEEDED
|
|
|
-120 ERR CONTEXTS EXCEEDED
|
Unable to find an available server because the maximum contexts was reached. Since version: 3.1
|
|
-128 ERR APP REJECTED
|
|
|
-130 ERR APP OPEN FAIL
|
The server engine could not open the application. Check that the application can be opened locally (for example, online). See also Error -130 and MySQL.
|
|
-131 ERR BAD PRG
|
|
|
-133 ERR ACCESS DENIED
|
|
|
-134 RQMRI ERR LIMITED LICENSE PART
|
License limited to only partitioning requests.
|
|
-135 RQMRI ERR LIMITED LICENSE HTTP
|
License limited to only Internet requests.
|
|
-136 ERR LIMITED LICENSE CS
|
|
|
-137 ERR REQ REJECTED
|
|
|
-138 ERR RT ERROR MSG
|
|
|
-139 ERR THREAD ABORTED
|
During the execution of a program, the program terminated abnormally. In the MAGIC_SPECIALS section, set the ExceptionMessageBoxDisplay flag to Yes, and use debugging techniques, such as WinDbg, to find the problem.
|
|
-140 RQTCP_ERR_NOT_INITIALIZED
|
This error has to do with the Winsock error 10093 WSANOTINITIALISED – Successful WSASTARTUP not yet performed.
|
|
-142 ERR BIND FAIL
|
A server module (e.g. broker or enterprise server) failed to bind to a local address, which might already be used.
|
|
-143 ERR CNCT REFUSED
|
A connection from a client module to a peer was refused. This can happen between almost any two modules. For example, from a requester to the broker or enterprise server, or from an enterprise server to the broker.
|
|
-144 ERR CNCT RESET
|
|
|
-146 ERR BIND HOST NOT FOUND
|
|
|
-147 ERR CNCT HOST NOT FOUND
|
|
|
-148 ERR CNCT CLOSED
|
|
|
-149 RQTCP ERR OUT OF SOCKETS
|
The current module reached the maximum number of opened sockets (the default is 1000). Increase this value using the keyword Handles=NNNN in the Mgreq.ini file.
|
|
-150 ERR CNCT REFUSED MRB
|
|
|
-151 ERR CNCT CLOSED BY REQ
|
|
|
-156 RQMRG ERR OUT OF SEQ MSG
|
|
|
-157 RQMRG ERR AUTHENTICATION
|
The credentials sent from a client could not be authenticated by the server, because of an unknown user, wrong password, etc.
|
|
-160 RQSPAWN_ERR_EXE_NOT_FOUND
|
Status code related to spawning executable files, usually by the broker. The executable file name may be wrong, the file may be damaged, the username or password may be wrong, etc.
|
|
-161 RQSPAWN_ERR_PATH_NOT_FOUND
|
|
-162 RQSPAWN_ERR_BAD_EXE
|
|
-163 RQSPAWN_ERR_BAD_LOGIN
|
|
-164 RQSPAWN_ERR_PRIVILEGE_NOT_HELD
|
|
-165 RQSPAWN_ERR_ARG_BIG
|
|
-166 RQSPAWN_ERR_MODE_EINVAL
|
|
-167 RQSPAWN_ERR_NOMEM
|
|
-168 RQSPAWN_ERR_NOPROCESS
|
|
-169 RQSPAWN_ERR_NET_UNREACHABLE
|
|
-170 MM_ERR_INV_SEG
|
Memory table status codes, relevant only during the broker’s processing. (The memory tables were originally developed to manage the broker resources.)
|
|
-171 MM_ERR_DUPLICATE
|
|
-172 MM_ERR_INV_OPER
|
|
-173 MM_ERR_INV_POS
|
|
-174 MM_ERR_NO_INIT
|
|
-175 MM_ERR_TARGET_EXISTS
|
|
-176 MM_ERR_OUT_OF_HDLS
|
|
-177 MM_ERR_KEY_DISABLED
|
|
-180 RQMRB WRN EXE NOT FOUND
|
The broker was requested to spawn an executable that is not listed in its [APPLICATIONS_LIST].
|
|
-181 RQMRB WRN RT NOT FOUND
|
The broker was requested to perform an operation on an engine that was not registered (host/port), for example to terminate an engine. If possible, reproduce the problem by setting the Log parameter to Enabled in the Mgreq.ini file.
|
|
-182 RQMRB WRN REQ NOT FOUND
|
The broker was requested to perform an operation on an unknown request, for example to modify its priority. If possible, reproduce the problem by setting the Log parameter to Enabled in the Mgreq.ini file.
|
|
-183 RQMRB WRN REQ NOT MATCH
|
The broker was requested to perform an operation on a request that does not match the requester application name. If possible, reproduce the problem by setting the Log parameter to Enabled in the Mgreq.ini file.
|
|
-185 RQMRB ERR REGISTER SERVICE
|
The broker failed during its initialization as a service. Reproduce the problem by setting the Log parameter in the Mgreq.ini file.
|
|
-186 RQMRB ERR REPORT SERVICE STATUS
|
The broker failed while reporting its status to the Service Control Manager of Windows. Reproduce the problem by setting the Log parameter in the Mgreq.ini file.
|
|
-187 RQMRB ERR CNCT REFUSED REMOTE MRB
|
The broker failed to connect a remote broker in order to start a remote executable ([REMOTE_APPLICATIONS_LIST]). Verify that the address of the remote broker is valid (host/port), and that a remote broker is bound to that address.
|
|
-188 RQMRB_ERR_RT_LOCK_FAILED
|
Internal status code of the broker.
|
|
-189 RQMRB_ERR_LICENSE_CONFLICT_FLOATING
|
The broker allows RIA floating licensing only for Magic xpa servers that are not specific to either desktop (MOBILE=N) or mobile (MOBILE=Y). Since version: 2.5
|
|
-197 ERR CTX NOT FOUND
|
|
|
-198 ERR QUE LIMIT
|
Queue limit reached. Increase the QueueMaxSize flag in the mgrb.ini file.
|
|
-200 ERR UNEXPECTED
|
Unexpected error. When accompanied by other error codes, please report to MSE's technical support.
|
|
-201 ERR NOT INITIALIZED
|
Code partitioning error. TCP/IP services were not installed. Install TCP/IP.
|
|
-202 ERR OPEN RESULT FILE
|
|
|
-203 RQLIB ERR INI FILE
|
An INI file could not be opened.
|
|
-204 RQCMDL ERR BAD ARGS
|
The command line requester could not parse its arguments. Use the help notes (displayed when activated without any argument).
|
|
-205 RQ ERR WRONG MSG SRVR
|
A query was requested on a middleware that does not support queries; for example, when starting the engine to serve requests from EJB.
|
|
-210 RQMRILOW ERR RECV FAIL
|
An internal error was caught while receiving a message from a peer. If possible, reproduce the problem by setting the Log parameter to Enabled in the Mgreq.ini file.
|
|
-211 RQMRILOW ERR NOT MRI
|
|
|
-212 RQMRILOW ERR OLD MRI
|
|
|
-260 RQHTTP ERR UPLOAD TOO BIG
|
The size of an uploaded file from a browser to the requester exceeded the maximal size. Increase the MaxUploadKB keyword in the Mgreq.ini file in the scripts directory.
|
|
-261 RQMRI_ERR_PRG_NOT_EXTERNAL
|
The program is not set as External. Since version: 2.3
|
|
-270 RQMRI_ERR_LIMITED_LICENSE
|
The license is limited – the current request type is prohibited. The Single user edition does not allow Browser Client programs. Since version: 2.3
|
|
-271 RQMRI_ERR_UNSYNCHRONIZED_METADATA
|
One or more files previously cached from the server to the client are out-dated. The client should be restarted once with the server accessible and available, and with the ConnectOnStartup execution property set to Y. Since version: 2.4
|
|
-272 RQMRI_ERR_CANNOT_EXECUTE_OFFLINE_RC_IN_ONLINE_MODE
|
An application that started without server access, cannot access a server running in Online deployment mode. Since version: 2.4
|
|
-274 RQMRI_ERR_CANNOT_EXECUTE_RC_WITH_ONLINE_MDI
|
Rich Client requests cannot be handled when the Online MDI is open. Since version: 2.3
|
|
-275 RQMRI_ERR_INCOMPATIBLE_RIACLIENT
|
The RIA Client version is not compatible with the server version. Since version: 2.4
|
|
-280 ERR_WRONG_SERVER_OR_SERVICE_NAME
|
Invalid server or service name. A client engine could not execute a ‘Call Remote’ due to an invalid server or service (as set in the Environment). Since version: 3.0
|
|
-281 ERR_FAILED_TO_CONNECT_SPACE
|
Failed to connect to the space. A client engine could not execute a ‘Call Remote’ since the required space was inaccessible. Since version: 3.0
|
|
-282 ERR_NO_RESPONSE
|
Request timed out without receiving a response from the space. A client inserted a request into the space (for example, by a ‘Call Remote’) and no matching response was inserted into the space (by any Magic xpa server). Since version: 3.0
|
Errors that are not listed in the documentation, such as -145, are best handled by using the log file from the Mgreq.ini file. For example, this log file can show problems that deal with resolving a host name, which is generally the cause of these errors.
It is important to distinguish between Web Server errors, which are not displayed in Magic xpa’s blue error page, and Magic xpa errors. Web Server errors might include a missing requester, insufficient rights, etc.
