url_response, Winsock, e2e and controller error/return codes The error code Variable in messages The $code number

is returned from the http-server. The $description depends on if NT authentication is used or not. If NT authentication used, the description is as described in the table below (if NT authentication is NOT used, the codes are as described further down below this table): URL_RESPONSE CURLE_OK (0) All fine. Proceed as usual. CURLE_UNSUPPORTED_PROTOCOL (1) The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you didn't use, it can be a misspelled protocol string or just a protocol libcurl has no code for. CURLE_FAILED_INIT (2) Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental couldn't get done at init time. CURLE_URL_MALFORMAT (3) The URL was not properly formatted. CURLE_NOT_BUILT_IN (4) A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt libcurl. CURLE_COULDNT_RESOLVE_PROXY (5) Couldn't resolve proxy. The given proxy host could not be resolved. CURLE_COULDNT_RESOLVE_HOST (6) Couldn't resolve host. The given remote host was not resolved.

CURLE_COULDNT_CONNECT (7) Failed to connect() to host or proxy. CURLE_FTP_WEIRD_SERVER_REPLY (8) After connecting to a FTP server, libcurl expects to get a certain reply back. This error code implies that it got a strange or bad reply. The given remote server is probably not an OK FTP server. CURLE_REMOTE_ACCESS_DENIED (9) We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory. CURLE_FTP_ACCEPT_FAILED (10) While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar. CURLE_FTP_WEIRD_PASS_REPLY (11) After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected code was returned. CURLE_FTP_ACCEPT_TIMEOUT (12) During an active FTP session while waiting for the server to connect, the CURLOPT_ACCEPTTIMOUT_MS (or the internal default) timeout expired. CURLE_FTP_WEIRD_PASV_REPLY (13) libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. The server is flawed. CURLE_FTP_WEIRD_227_FORMAT (14) FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line, this return code is passed back. CURLE_FTP_CANT_GET_HOST (15) An internal failure to lookup the host used for the new connection. CURLE_FTP_COULDNT_SET_TYPE (17)

Received an error when trying to set the transfer mode to binary or ASCII. CURLE_PARTIAL_FILE (18) A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously given size. CURLE_FTP_COULDNT_RETR_FILE (19) This was either a weird reply to a 'RETR' command or a zero byte transfer complete. CURLE_QUOTE_ERROR (21) When sending custom "QUOTE" commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command. CURLE_HTTP_RETURNED_ERROR (22) This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400. CURLE_WRITE_ERROR (23) An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback. CURLE_UPLOAD_FAILED (25) Failed starting the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server's explanation for this. CURLE_READ_ERROR (26) There was a problem reading a local file or an error returned by the read callback. CURLE_OUT_OF_MEMORY (27) A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs. CURLE_OPERATION_TIMEDOUT (28) Operation timeout. The specified time-out period was reached according to the conditions. CURLE_FTP_PORT_FAILED (30)

The FTP PORT command returned error. This mostly happens when you haven't specified a good enough address for libcurl to use. See CURLOPT_FTPPORT. CURLE_FTP_COULDNT_USE_REST (31) The FTP REST command returned error. This should never happen if the server is sane. CURLE_RANGE_ERROR (33) The server does not support or accept range requests. CURLE_HTTP_POST_ERROR (34) This is an odd error that mainly occurs due to internal confusion. CURLE_SSL_CONNECT_ERROR (35) A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others. CURLE_BAD_DOWNLOAD_RESUME (36) The download could not be resumed because the specified offset was out of the file boundary. CURLE_FILE_COULDNT_READ_FILE (37) A file given with FILE:// couldn't be opened. Most likely because the file path doesn't identify an existing file. Did you check file permissions? CURLE_LDAP_CANNOT_BIND (38) LDAP cannot bind. LDAP bind operation failed. CURLE_LDAP_SEARCH_FAILED (39) LDAP search failed. CURLE_FUNCTION_NOT_FOUND (41) Function not found. A required zlib function was not found. CURLE_ABORTED_BY_CALLBACK (42) Aborted by callback. A callback returned "abort" to libcurl.

CURLE_BAD_FUNCTION_ARGUMENT (43) Internal error. A function was called with a bad parameter. CURLE_INTERFACE_FAILED (45) Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections' source IP address with CURLOPT_INTERFACE. CURLE_TOO_MANY_REDIRECTS (47) Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS. CURLE_UNKNOWN_OPTION (48) An option passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem in the program that uses libcurl. The error buffer might contain more specific information about which exact option it concerns. CURLE_TELNET_OPTION_SYNTAX (49) A telnet option string was Illegally formatted. CURLE_PEER_FAILED_VERIFICATION (51) The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK. CURLE_GOT_NOTHING (52) Nothing was returned from the server, and under the circumstances, getting nothing is considered an error. CURLE_SSL_ENGINE_NOTFOUND (53) The specified crypto engine wasn't found. CURLE_SSL_ENGINE_SETFAILED (54) Failed setting the selected SSL crypto engine as default! CURLE_SEND_ERROR (55) Failed sending network data. CURLE_RECV_ERROR (56)

Failure with receiving network data. CURLE_SSL_CERTPROBLEM (58) problem with the local client certificate. CURLE_SSL_CIPHER (59) Couldn't use specified cipher. CURLE_SSL_CACERT (60) Peer certificate cannot be authenticated with known CA certificates. CURLE_BAD_CONTENT_ENCODING (61) Unrecognized transfer encoding. CURLE_LDAP_INVALID_URL (62) Invalid LDAP URL. CURLE_FILESIZE_EXCEEDED (63) Maximum file size exceeded. CURLE_USE_SSL_FAILED (64) Requested FTP SSL level failed. CURLE_SEND_FAIL_REWIND (65) When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation failed. CURLE_SSL_ENGINE_INITFAILED (66) Initiating the SSL Engine failed. CURLE_LOGIN_DENIED (67) The remote server denied curl to login (Added in 7.13.1) CURLE_TFTP_NOTFOUND (68) File not found on TFTP server.

CURLE_TFTP_PERM (69) Permission problem on TFTP server. CURLE_REMOTE_DISK_FULL (70) Out of disk space on the server. CURLE_TFTP_ILLEGAL (71) Illegal TFTP operation. CURLE_TFTP_UNKNOWNID (72) Unknown TFTP transfer ID. CURLE_REMOTE_FILE_EXISTS (73) File already exists and will not be overwritten. CURLE_TFTP_NOSUCHUSER (74) This error should never be returned by a properly functioning TFTP server. CURLE_CONV_FAILED (75) Character conversion failed. CURLE_CONV_REQD (76) Caller must register conversion callbacks. CURLE_SSL_CACERT_BADFILE (77) Problem with reading the SSL CA cert (path? access rights?) CURLE_REMOTE_FILE_NOT_FOUND (78) The resource referenced in the URL does not exist. CURLE_SSH (79) An unspecified error occurred during the SSH session. CURLE_SSL_SHUTDOWN_FAILED (80)

Failed to shut down the SSL connection. CURLE_AGAIN (81) Socket is not ready for send/recv wait till it's ready and try again. This return code is only returned from curl_easy_recv(3) and curl_easy_send(3) (Added in 7.18.2) CURLE_SSL_CRL_BADFILE (82) Failed to load CRL file (Added in 7.19.0) CURLE_SSL_ISSUER_ERROR (83) Issuer check failed (Added in 7.19.0) CURLE_FTP_PRET_FAILED (84) The FTP server does not understand the PRET command at all or does not support the given argument. Be careful when using CURLOPT_CUSTOMREQUEST, a custom LIST command will be sent with PRET CMD before PASV as well. (Added in 7.20.0) CURLE_RTSP_CSEQ_ERROR (85) Mismatch of RTSP CSeq numbers. CURLE_RTSP_SESSION_ERROR (86) Mismatch of RTSP Session Identifiers. CURLE_FTP_BAD_FILE_LIST (87) Unable to parse FTP file list (during FTP wildcard downloading). CURLE_CHUNK_FAILED (88) Chunk callback reported error. CURLE_OBSOLETE* These error codes will never be returned. They were used in an old libcurl version and are currently unused.

CURLMcode
This is the generic return code used by functions in the libcurl multi interface. Also consider curl_multi_strerror(3).

CURLM_CALL_MULTI_PERFORM (-1) This is not really an error. It means you should call curl_multi_perform(3) again without doing select() or similar in between. CURLM_OK (0) Things are fine. CURLM_BAD_HANDLE (1) The passed-in handle is not a valid CURLM handle. CURLM_BAD_EASY_HANDLE (2) An easy handle was not good/valid. It could mean that it isn't an easy handle at all, or possibly that the handle already is in used by this or another multi handle. CURLM_OUT_OF_MEMORY (3) You are doomed. CURLM_INTERNAL_ERROR (4) This can only be returned if libcurl bugs. Please report it to us! CURLM_BAD_SOCKET (5) The passed-in socket is not a valid one that libcurl already knows about. (Added in 7.15.4) CURLM_UNKNOWN_OPTION (6) curl_multi_setopt() with unsupported option (Added in 7.15.4)

CURLSHcode
The "share" interface will return a CURLSHcode to indicate when an error has occurred. Also consider curl_share_strerror(3). CURLSHE_OK (0) All fine. Proceed as usual. CURLSHE_BAD_OPTION (1) An invalid option was passed to the function.

CURLSHE_IN_USE (2) The share object is currently in use. CURLSHE_INVALID (3) An invalid share object was passed to the function. CURLSHE_NOMEM (4) Not enough memory was available. (Added in 7.12.0) CURLSHE_NOT_BUILT_IN (5) The requested sharing could not be done because the library you use don't have that particular feature enabled. (Added in 7.23.0)

100 101 200 201 202 203 204 205

206 300 301

302 303

The request can be continued. The server has switched protocols in an upgrade header. The request completed successfully. The request has been fulfilled and resulted in the creation of a new resource. The request has been accepted for processing, but the processing has not been completed. The returned meta information in the entity-header is not the definitive set available from the origin server. The server has fulfilled the request, but there is no new information to send back. The request has been completed, and the client program should reset the document view that caused the request to be sent to allow the user to easily initiate another input action. The server has fulfilled the partial GET request for the resource. The server couldn't decide what to return. The requested resource has been assigned to a new permanent URI (Uniform Resource Identifier), and any future references to this resource should be done using one of the returned URIs. The requested resource resides temporarily under a different URI (Uniform Resource Identifier). The response to the request can be found under a different URI (Uniform Resource Identifier) and should be retrieved

304 305 307 400 401 402 403 404 405 406 407 408 409

410 411 412

413

414

415

500

using a GET method on that resource. The requested resource has not been modified. The requested resource must be accessed through the proxy given by the location field. The redirected request keeps the same verb. HTTP/1.1 behaviour The request could not be processed by the server due to invalid syntax. The requested resource requires user authentication. Not currently implemented in the HTTP protocol The server understood the request, but is refusing to fulfil it The server has not found anything matching the requested URI (Uniform Resource Identifier). The method used is not allowed. No responses acceptable to the client were found. Proxy authentication required. The server timed out waiting for the request. The request could not be completed due to a conflict with the current state of the resource. The user should resubmit with more information. The requested resource is no longer available at the server, and no forwarding address is known. The server refuses to accept the request without a defined content length. The precondition given in one or more of the request header fields evaluated to false when it was tested on the server. The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server is refusing to service the request because the request URI (Uniform Resource Identifier) is longer than the server is willing to interpret. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. The server encountered an unexpected condition that prevented it from fulfilling the request.

501 502

The server does not support the functionality required to fulfil the request. The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in

503 504 505

12102 12101 12100 12029 12044 12030 12155 12150 12019 12018 12004 12009 12154 12152 12005 12015

12007 12172

12017

12011 12001 12156

12032

attempting to fulfil the request. The service is temporarily overloaded. The request was timed out waiting for a gateway. The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The method cannot be used after calling IWinHttpRequest::Send; The method cannot be used before calling IWinHttpRequest::Send The method cannot be used before calling IWinHttpRequest::Open The attempt to connect to the server failed. The server is requesting client authentication. The connection with the server has been reset or terminated. The header could not be added because it already exists. The requested header could not be located. The requested operation cannot be carried out because the handle supplied is not in the correct state. The type of handle supplied is incorrect for this operation. An internal error has occurred. A request to WinHttpQueryOption or WinHttpSetOption specified an invalid option value. The request made to WinHttpQueryHeaders is invalid. The server response could not be parsed. The URL is invalid. The login attempt failed. When this error is encountered, the request handle should be closed with WinHttpCloseHandle. A new request handle must be created before retrying the function that originally produced this error. The server name could not be resolved. The initialization of the WinHTTP API has not occurred. This indicates that a higher-level function, such as WinHttpOpen, has not been called yet. The operation was cancelled, usually because the handle on which the request was operating was closed before the operation completed. The requested option cannot be set, only queried. No more handles could be generated at this time. The redirection failed because either the scheme changed or all attempts made to redirect failed (default is five attempts). The WinHTTP function failed. The desired function can

12175

12012 12002 12006

be retried on the same request handle. One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server. To determine what type of error was encountered, check for a WINHTTP_CALLBACK_STATUS_SECURE_FAILURE notification in a status callback function. The WinHTTP function support is being shut down or unloaded. The request has timed out. The URL scheme could not be recognized, or is not supported.

If NT authentication is NOT used, the codes are as described below: HTTP Errors 118 143 151 152 153 156 301 302 Firewall Error. Error description contains detailed message. Busy performing current action. HTTP protocol error. The error message has the server response. No server specified in URL <HTTPS_p_URL.htm> Specified URLScheme <HTTPS_p_URLScheme.htm> is invalid. Invalid cookie index (out of range). Operation interrupted (or timeout). Can't open AttachedFile <HTTPS_p_AttachedFile.htm>.

SSL Errors The class may also return a one or more of the following SSL-specific errors. The messages below are generalized descriptions of the corresponding error codes. Actual error messages will include additional information and extended error codes depending on the situation. 270 271 272 273 274 275 276 280 281 Cannot load specified security library. Cannot open certificate store. Cannot find specified certificate. Cannot acquire security credentials. Cannot find certificate chain. Cannot verify certificate chain. Error during handshake. Error verifying certificate. Could not find client certificate.

282 283 284

Could not find server certificate. Error encrypting data. Error decrypting data.

WINSOCK ERRORS The error message descriptions show the corresponding Winsock error number. See also http://msdn.microsoft.com/enus/library/windows/desktop/ms740668%28v=vs.85%29.aspx 10004 10009 10013 10014 10022 10024 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 Interrupted system call. Bad file number. Access denied. Bad address. Invalid argument. Too many open files. Operation would block. Operation now in progress. Operation already in progress. Socket operation on non-socket. Destination address required. Message too long. Protocol wrong type for socket. Bad protocol option. Protocol not supported. Socket type not supported. Operation not supported on socket. Protocol family not supported. Address family not supported by protocol family. Address already in use. Can't assign requested address. Network is down. Network is unreachable. Net dropped connection or reset. Software caused connection abort. Connection reset by peer. No buffer space available. Socket is already connected. Socket is not connected. Can't send after socket shutdown. Too many references, can't splice. Connection timed out. Connection refused. Too many levels of symbolic links. File name too long. Host is down. No route to host.

10066 10067 10068 10069 10070 10071 10091 10092 10093 11001 11002 11003 11004

Directory not empty Too many processes. Too many users. Disc Quota Exceeded. Stale NFS file handle. Too many levels of remote in path. Network subsystem is unavailable. WINSOCK DLL Version out of range. Winsock not loaded yet. Host not found. Non-authoritative 'Host not found' (try again or check DNS setup). Non-recoverable errors: FORMERR, REFUSED, NOTIMP. Valid name, no data record (check DNS setup).

E2E ERROR/RETURN CODES (e2e_appmon_dev) Error codes issued by the probe itself (not related to a aspecific function): -3 A -3 return code is a general failure code, so it is difficult to say anything specific about the cause of this. One possibility is the access rights for the user setup to run the script in the e2e_appmon probe. Another is that the probe is looking in the wrong directory for either the task executor binary or the script file. Note that with proper error handling it is possible to see which line of the script is failing when it is run by the probe. -4 A -4 error code means that the script was killed before execution completed. In this case you would also get an alarm telling you that the script did not complete on time and had to be killed. -5 A return code of -5 means "Page has not finished to load within the timeout 1. Verify that there's currently only one user logged on 2. Verify that there's only one e2e_starter.exe running When e2e_appmon starts, it sets a registry key for all users which makes e2e_starter.exe run on every login. e2e_starter should close when it detects that there's already an e2e_starter running,

but in some cases, this check may fail - this'll mostly cause profiles to be run on interactive session (or in parallel). Logs of interest would be the e2e_starter.log found in the probe directory.

Error codes for Web functions

The table below lists the possible error codes for the NimRecorder Web functions, for the errors stopping script execution (unless #IgnoreErrors=1). -2146697211 -404,-405 -14 -12 -11 -8 -7 -5 -4 -3 -3 -2 -1 -1 -1 An HTTP error prevents the specified page to load Usual HTTP error codes Invalid character for WriteHTML - use instead WriteHTMLPaste function Download timeout Internal error HTML Element not found Index too big Page has not finished to load within the timeout Browser lost Bad HTML descriptor Browser not recognized (Only for StartBrowser function when its first parameter is different from "IE") Page not found Impossible to capture or invalid range (Capture Web functions) No browser in use (no UsePage or StartBrowser before) Extraction cannot be done (ExtractLink function)

Error codes for File management functions

The table below lists the possible error codes for the NimRecorder File management functions, for the errors stopping script execution (unless #IgnoreErrors=1). -2 -1 1 2 3 4 5 Index too big when running NimRecorder Excel functions (the array is smaller than the number of cells) ColeDispatch Exception : Error returned by Excel when an invalid operation is attempted by NimRecorder Excel functions File empty File not found Path not found Too many files open Path empty

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 90 99 110 111 112

Directory already exists File already exists Not enough memory File or path not found (TaskExec could not find if it's the file or the path which is not found) Incorrect disk Error in current directory Write protected Unable to copy files Unable to delete files Unable to name files Unable to move directory Unable to create directory Unable to delete directory Unable to change directory Unable to write (or save) Directory full Bad sector Error IO Violation error Disk full Unable to create file Unable to open file Unable to readi file Invalid file Unable to close file Invalid length Unable to change attributes Internal XML COM error Invalid parameters Invalid XML path Invalid XML attribute or XML attribute not found Index too big (return code only for the XML functions)

Error codes for Flow control functions

The table below lists the possible error codes for the NimRecorder Flow control functions, for the errors stopping script execution (unless #IgnoreErrors=1). Only the Shell or the Run function return such error codes. 34 35 36 37 38 39 40 DDE failure No association Access denied DLL not found Sharing violation Empty Shell name Empty Run name

Error codes for FTP functions

The table below lists the possible error codes for the NimRecorder FTP functions, for the errors stopping script execution (unless #IgnoreErrors=1). 9 80 550 553 12001 12002 12003 12004 12005 12006 12007 12008 12012 12013 12014 12015 12016 12017 File or path does not exist The file already exists Requested action not taken. File unavailable (e.g., file not found, no access) Requested action not taken. File name not allowed No more handles could be generated at this time The request has timed out An extended error was returned from the server An internal error has occurred The URL is invalid The URL scheme could not be recognized or is not supported The server name could not be resolved The requested protocol could not be located Internet function support is being shut down or unloaded The request to connect and log on to an FTP server could not be completed because the supplied user name is incorrect The request to connect and log on to an FTP server could not be completed because the supplied password is incorrect The request to connect to and log on to an FTP server failed The requested operation is invalid The operation was canceled

12020 12021 12022 12023 12026 12028 12029 12030 12037 12038 12039 12040 12110 12111 12156

The request cannot be made via a proxy A required registry value could not be located A required registry value was located but is an incorrect type or has an invalid value Direct network access cannot be made at this time The required operation could not be completed because one or more requests are pending The requested item could not be located The attempt to connect to the server failed The connection with the server has been terminated SSL certificate date that was received from the server is bad. The certificate is expired SSL certificate common name (host name field) is incorrect The application is moving from a non-SSL to an SSL connection because of a redirect The application is moving from an SSL to an non-SSL connection because of a redirect The requested operation cannot be made on the FTP session handle because an operation is already in progress The FTP operation was not completed because the session was aborted The redirection failed because either the scheme changed (for example, HTTP to FTP) or all attempts made to redirect failed (default is five attempts)

Error codes for ODBC functions

The table below lists the possible error codes for the NimRecorder ODBC functions, for the errors stopping script execution (unless #IgnoreErrors=1). -5 -4 -3 -2 -1 Close the record set first Connection cancelled No numeric field No connection available No record set

Error codes for Synchronization functions

There are no error codes for Synchronization functions. At execution, if an error prevents even the PauseFalse block to be executed, an error message is displayed and execution stops. You have to correct the code and then replay.

Error codes for User dialog functions

There are no error codes for User dialog functions. At execution, the function returns an empty string in case of an error.

Error codes for Web functions

The table below lists the possible error codes for the NimRecorder Web functions, for the errors stopping script execution (unless #IgnoreErrors=1). -2146697211 -404,-405 -14 -12 -11 -8 -7 -5 -4 -3 -3 -2 -1 -1 -1 An HTTP error prevents the specified page to load Usual HTTP error codes Invalid character for WriteHTML - use instead WriteHTMLPaste function Download timeout Internal error HTML Element not found Index too big Page has not finished to load within the timeout Browser lost Bad HTML descriptor Browser not recognized (Only for StartBrowser function when its first parameter is different from "IE") Page not found Impossible to capture or invalid range (Capture Web functions) No browser in use (no UsePage or StartBrowser before) Extraction cannot be done (ExtractLink function)

Error codes for Windows management functions

The table below lists the possible error codes for the NimRecorder Windows management functions, for the errors stopping script execution (unless #IgnoreErrors=1). 41 42 43 44 45 46 48 Window not found (or window handle not found) Window name empty No window specified Impossible to move the window Impossible to resize the window Focus change error Impossible to find Edit box

49 50 51 52 53 54 55 56 57 58 59 60 61 62 64 65 75 76 77 78 90 95 98 99 105 106 108

Impossible to find Combobox Impossible to attach to Combobox Impossible to find Listbox control Impossible to find Combobox control Impossible to find Listview control Impossible to find Treeview control Impossible to find button Impossible to find checkbox Impossible to find radiobutton Impossible to find Tab Invalid scrollbar Impossible to create the msgframe New coordinates for window are out of the screen Impossible to read window size Out of screen Item not found Empty menu name Menu not found Menu attach error Menu item not found Internal error Invalid instance number Error in key list inside instruction SendKeys Invalid parameter Invalid UI command (the User Interface is not available when running a noninteractive task via Scheduler) Invalid toolbar Invalid Regular Expression

Scheduler, error codes

These codes are found in the Windows system application log (event viewer) for the WTScheduler service. When a scheduled task has failed, in Last run result column, the error code is reported. If error code is 21, it means that the .ROB script has ended with errors. It's possible to see the full error message and the line which failed clicking Application log button. It opens Event viewer, double-click Application on the right pane and open the WTScheduler line for the script which failed.

1 Can't create SchLogon process 2 Can't create/write to SchLogon pipe 3 Bad registry entries for SchLogon location 4 Bad username 5 LogonUser function failed 6 Grant access to SchLogon failed 7 Failed to open Winsta0 8 Failed to open input desktop 9 Failed to create new desktop 10 Failed to switch desktop 11 Failed to grant access to WSD 12 Failed to create SchLogon process 13 The SchLogon process has died unexpectedly 14 Couldn't load user profile 15 Couldn't open user token 16 Couldn't logoff user 17 There is a protected screen saver 18 Couldn't find logon window 19 Scheduler Indicator process not present (near clock) 20 Non interactive script has requested an UI command 21 Error in script (the Wintask script raised an error before its end) 22 error when trying to send the user information to the password dialog on w2k

101 Can't open SchedSrv process 102 Can't duplicate pipe handle 103 Error reading pipe 104 First timeout expired Schlogon errors (during logon) 105 TerminateProcess called 106 Bad registry entries 107 Create task process failed 108 Open window station WinSta0 failed 109 Assign WinSta0 failed 110 Create desktop failed 111 Switch desktop failed 112 Can't force new session 113 Can't create user shell (Explorer)

CONTROLLER ERROR CODES nime_OK (0) nime_ERROR (1) nime_COMERR (2) nime_INVAL (3) nime_NOENT (4) nime_ISENT (5) nime_ACCESS (6) nime_AGAIN (7) nime_NOMEM (8) nime_NOSPC (9) nime_EPIPE (10) nime_NOCMD (11) nime_LOGIN (12) nime_SIDEXP (13) nime_ILLMAC (14) nime_ILLSID (15) nime_SIDSESS (16) nime_EXPIRED (17) nime_NOLIC (18) nime_INVLIC (19) nime_ILLLIC (20) nime_INVOP (21) nime_SSLREQ (22) nime_USER (100) OK General error Communication error usually a timeout Invalid argument Not found Already defined Permission denied Temporarily out of resources (ie. try again) Out of resources No space left Broken pipe/connection Command not found Login failed SID expired Illegal MAC Illegal SID Session id for hub is invalid Expired No license Invalid license Illegal license Invalid operation SSL connection required User error from this value and up