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 The request can be continued.

101 The server has switched protocols in an upgrade header.

200 The request completed successfully.

201 The request has been fulfilled and resulted in the creation

of a new resource.

202 The request has been accepted for processing, but the

processing has not been completed.

203 The returned meta information in the entity-header is not

the definitive set available from the origin server.

204 The server has fulfilled the request, but there is no new

information to send back.

205 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.

206 The server has fulfilled the partial GET request for the

resource.

300 The server couldn't decide what to return.

301 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.

302 The requested resource resides temporarily under a

different URI (Uniform Resource Identifier).

303 The response to the request can be found under a different

URI (Uniform Resource Identifier) and should be retrieved

using a GET method on that resource.

304 The requested resource has not been modified.

305 The requested resource must be accessed through the

proxy given by the location field.

307 The redirected request keeps the same verb. HTTP/1.1

behaviour

400 The request could not be processed by the server due to

invalid syntax.

401 The requested resource requires user authentication.

402 Not currently implemented in the HTTP protocol

403 The server understood the request, but is refusing to fulfil

it

404 The server has not found anything matching the requested

URI (Uniform Resource Identifier).

405 The method used is not allowed.

406 No responses acceptable to the client were found.

407 Proxy authentication required.

408 The server timed out waiting for the request.

409 The request could not be completed due to a conflict with

the current state of the resource. The user should resubmit

with more information.

410 The requested resource is no longer available at the server,

and no forwarding address is known.

411 The server refuses to accept the request without a defined

content length.

412 The precondition given in one or more of the request

header fields evaluated to false when it was tested on the

server.

413 The server is refusing to process a request because the

request entity is larger than the server is willing or able to

process.

414 The server is refusing to service the request because the

request URI (Uniform Resource Identifier) is longer than

the server is willing to interpret.

415 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.

500 The server encountered an unexpected condition that

prevented it from fulfilling the request.

501 The server does not support the functionality required to

fulfil the request.

502 The server, while acting as a gateway or proxy, received

an invalid response from the upstream server it accessed in

attempting to fulfil the request.

503 The service is temporarily overloaded.

504 The request was timed out waiting for a gateway.

505 The server does not support, or refuses to support, the

HTTP protocol version that was used in the request

message.

12102 The method cannot be used after calling

IWinHttpRequest::Send;

12101 The method cannot be used before calling

IWinHttpRequest::Send

12100 The method cannot be used before calling

IWinHttpRequest::Open

12029 The attempt to connect to the server failed.

12044 The server is requesting client authentication.

12030 The connection with the server has been reset or

terminated.

12155 The header could not be added because it already exists.

12150 The requested header could not be located.

12019 The requested operation cannot be carried out because the

handle supplied is not in the correct state.

12018 The type of handle supplied is incorrect for this operation.

12004 An internal error has occurred.

12009 A request to WinHttpQueryOption or WinHttpSetOption

specified an invalid option value.

12154 The request made to WinHttpQueryHeaders is invalid.

12152 The server response could not be parsed.

12005 The URL is invalid.

12015 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.

12007 The server name could not be resolved.

12172 The initialization of the WinHTTP API has not occurred.

This indicates that a higher-level function, such as

WinHttpOpen, has not been called yet.

12017 The operation was cancelled, usually because the handle

on which the request was operating was closed before the

operation completed.

12011 The requested option cannot be set, only queried.

12001 No more handles could be generated at this time.

12156 The redirection failed because either the scheme changed

or all attempts made to redirect failed (default is five

attempts).

12032 The WinHTTP function failed. The desired function can

be retried on the same request handle.

12175 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.

12012 The WinHTTP function support is being shut down or

unloaded.

12002 The request has timed out.

12006 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 Firewall Error. Error description contains detailed

message.

143 Busy performing current action.

151 HTTP protocol error. The error message has the

server response.

152 No server specified in URL <HTTPS_p_URL.htm>

153 Specified URLScheme

<HTTPS_p_URLScheme.htm> is invalid.

156 Invalid cookie index (out of range).

301 Operation interrupted (or timeout).

302 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 Cannot load specified security library.

271 Cannot open certificate store.

272 Cannot find specified certificate.

273 Cannot acquire security credentials.

274 Cannot find certificate chain.

275 Cannot verify certificate chain.

276 Error during handshake.

280 Error verifying certificate.

281 Could not find client certificate.

282 Could not find server certificate.

283 Error encrypting data.

284 Error decrypting data.

WINSOCK ERRORS

The error message descriptions show the corresponding Winsock error number.

See also http://msdn.microsoft.com/en-

us/library/windows/desktop/ms740668%28v=vs.85%29.aspx

10004 Interrupted system call.

10009 Bad file number.

10013 Access denied.

10014 Bad address.

10022 Invalid argument.

10024 Too many open files.

10035 Operation would block.

10036 Operation now in progress.

10037 Operation already in progress.

10038 Socket operation on non-socket.

10039 Destination address required.

10040 Message too long.

10041 Protocol wrong type for socket.

10042 Bad protocol option.

10043 Protocol not supported.

10044 Socket type not supported.

10045 Operation not supported on socket.

10046 Protocol family not supported.

10047 Address family not supported by protocol family.

10048 Address already in use.

10049 Can't assign requested address.

10050 Network is down.

10051 Network is unreachable.

10052 Net dropped connection or reset.

10053 Software caused connection abort.

10054 Connection reset by peer.

10055 No buffer space available.

10056 Socket is already connected.

10057 Socket is not connected.

10058 Can't send after socket shutdown.

10059 Too many references, can't splice.

10060 Connection timed out.

10061 Connection refused.

10062 Too many levels of symbolic links.

10063 File name too long.

10064 Host is down.

10065 No route to host.

10066 Directory not empty

10067 Too many processes.

10068 Too many users.

10069 Disc Quota Exceeded.

10070 Stale NFS file handle.

10071 Too many levels of remote in path.

10091 Network subsystem is unavailable.

10092 WINSOCK DLL Version out of range.

10093 Winsock not loaded yet.

11001 Host not found.

11002 Non-authoritative 'Host not found' (try again or

check DNS setup).

11003 Non-recoverable errors: FORMERR, REFUSED,

NOTIMP.

11004 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 An HTTP error prevents the specified page to load

-404,-405 Usual HTTP error codes

-14 Invalid character for WriteHTML - use instead WriteHTMLPaste function

-12 Download timeout

-11 Internal error

-8 HTML Element not found

-7 Index too big

-5 Page has not finished to load within the timeout

-4 Browser lost

-3 Bad HTML descriptor

-3 Browser not recognized (Only for StartBrowser function when its first parameter

is different from "IE")

-2 Page not found

-1 Impossible to capture or invalid range (Capture Web functions)

-1 No browser in use (no UsePage or StartBrowser before)

-1 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 Index too big when running NimRecorder Excel functions (the array is smaller

than the number of cells)

-1 ColeDispatch Exception : Error returned by Excel when an invalid operation is

attempted by NimRecorder Excel functions

1 File empty

2 File not found

3 Path not found

4 Too many files open

5 Path empty

6 Directory already exists

7 File already exists

8 Not enough memory

9 File or path not found (TaskExec could not find if it's the file or the path which is

not found)

10 Incorrect disk

11 Error in current directory

12 Write protected

13 Unable to copy files

14 Unable to delete files

15 Unable to name files

16 Unable to move directory

17 Unable to create directory

18 Unable to delete directory

19 Unable to change directory

20 Unable to write (or save)

21 Directory full

22 Bad sector

23 Error IO

24 Violation error

25 Disk full

26 Unable to create file

27 Unable to open file

28 Unable to readi file

29 Invalid file

30 Unable to close file

31 Invalid length

32 Unable to change attributes

90 Internal XML COM error

99 Invalid parameters

110 Invalid XML path

111 Invalid XML attribute or XML attribute not found

112 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 DDE failure

35 No association

36 Access denied

37 DLL not found

38 Sharing violation

39 Empty Shell name

40 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 File or path does not exist

80 The file already exists

550 Requested action not taken. File unavailable (e.g., file not found, no access)

553 Requested action not taken. File name not allowed

12001 No more handles could be generated at this time

12002 The request has timed out

12003 An extended error was returned from the server

12004 An internal error has occurred

12005 The URL is invalid

12006 The URL scheme could not be recognized or is not supported

12007 The server name could not be resolved

12008 The requested protocol could not be located

12012 Internet function support is being shut down or unloaded

12013 The request to connect and log on to an FTP server could not be completed

because the supplied user name is incorrect

12014 The request to connect and log on to an FTP server could not be completed

because the supplied password is incorrect

12015 The request to connect to and log on to an FTP server failed

12016 The requested operation is invalid

12017 The operation was canceled

12020 The request cannot be made via a proxy

12021 A required registry value could not be located

12022 A required registry value was located but is an incorrect type or has an invalid

value

12023 Direct network access cannot be made at this time

12026 The required operation could not be completed because one or more requests are

pending

12028 The requested item could not be located

12029 The attempt to connect to the server failed

12030 The connection with the server has been terminated

12037 SSL certificate date that was received from the server is bad. The certificate is

expired

12038 SSL certificate common name (host name field) is incorrect

12039 The application is moving from a non-SSL to an SSL connection because of a

redirect

12040 The application is moving from an SSL to an non-SSL connection because of a

redirect

12110 The requested operation cannot be made on the FTP session handle because an

operation is already in progress

12111 The FTP operation was not completed because the session was aborted

12156 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 Close the record set first

-4 Connection cancelled

-3 No numeric field

-2 No connection available

-1 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 An HTTP error prevents the specified page to load

-404,-405 Usual HTTP error codes

-14 Invalid character for WriteHTML - use instead WriteHTMLPaste function

-12 Download timeout

-11 Internal error

-8 HTML Element not found

-7 Index too big

-5 Page has not finished to load within the timeout

-4 Browser lost

-3 Bad HTML descriptor

-3 Browser not recognized (Only for StartBrowser function when its first parameter

is different from "IE")

-2 Page not found

-1 Impossible to capture or invalid range (Capture Web functions)

-1 No browser in use (no UsePage or StartBrowser before)

-1 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 Window not found (or window handle not found)

42 Window name empty

43 No window specified

44 Impossible to move the window

45 Impossible to resize the window

46 Focus change error

48 Impossible to find Edit box

49 Impossible to find Combobox

50 Impossible to attach to Combobox

51 Impossible to find Listbox control

52 Impossible to find Combobox control

53 Impossible to find Listview control

54 Impossible to find Treeview control

55 Impossible to find button

56 Impossible to find checkbox

57 Impossible to find radiobutton

58 Impossible to find Tab

59 Invalid scrollbar

60 Impossible to create the msgframe

61 New coordinates for window are out of the screen

62 Impossible to read window size

64 Out of screen

65 Item not found

75 Empty menu name

76 Menu not found

77 Menu attach error

78 Menu item not found

90 Internal error

95 Invalid instance number

98 Error in key list inside instruction SendKeys

99 Invalid parameter

105 Invalid UI command (the User Interface is not available when running a non-

interactive task via Scheduler)

106 Invalid toolbar

108 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) OK

nime_ERROR (1) General error

nime_COMERR (2) Communication error – usually a timeout

nime_INVAL (3) Invalid argument

nime_NOENT (4) Not found

nime_ISENT (5) Already defined

nime_ACCESS (6) Permission denied

nime_AGAIN (7) Temporarily out of resources (ie. try again)

nime_NOMEM (8) Out of resources

nime_NOSPC (9) No space left

nime_EPIPE (10) Broken pipe/connection

nime_NOCMD (11) Command not found

nime_LOGIN (12) Login failed

nime_SIDEXP (13) SID expired

nime_ILLMAC (14) Illegal MAC

nime_ILLSID (15) Illegal SID

nime_SIDSESS (16) Session id for hub is invalid

nime_EXPIRED (17) Expired

nime_NOLIC (18) No license

nime_INVLIC (19) Invalid license

nime_ILLLIC (20) Illegal license

nime_INVOP (21) Invalid operation

nime_SSLREQ (22) SSL connection required

nime_USER (100) User error from this value and up