PipeExec Component
Properties Methods Events Config Settings Errors
PipeExec provides an easy way to start and interact with a process over Stdin, Stdout, and Stderr.
Syntax
TiipPipeExec
Remarks
The PipeExec component provides a way to launch a process and then send/receive data to/from the process. To begin set ProcessFileName to the path of the process on disk. Optionally set ProcessArgs and ProcessWorkingDir.
Call StartProcess to start the process. Next call Send to send data to the process. Received data will be provided through the Stdout and Stderr events.
To terminate the process call StopProcess.
Example Code
Pipeexec exec = new Pipeexec();
exec.OnStdout += exec_OnStdout;
exec.ProcessFileName = @"C:\Windows\system32\cmd.exe";
exec.ProcessArgs = "/Q";
exec.StartProcess();
exec.Stdin = "dir" + System.Environment.NewLine;
while (true) //Wait for output
exec.DoEvents();
static void exec_OnStdout(object sender, PipeexecStdoutEventArgs e)
{
Console.WriteLine(e.Text);
}
Property List
The following is the full list of the properties of the component with short descriptions. Click on the links for further details.
AcceptData | Enables or disables data reception (the Stdout and Stderr events). |
BytesSent | The number of bytes actually sent after a call to the SendStdinText or SendStdinBytes method. |
EOL | This property is used to break the incoming data stream into chunks separated by EOL . |
ProcessArgs | The arguments to pass to the process. |
ProcessFileName | The path to the file on disk to execute. |
ProcessRunning | Whether the process is running. |
ProcessWorkingDir | The working directory of the process. |
SingleLineMode | This property includes a special mode for line-oriented protocols. |
Timeout | This property includes the timeout for the component. |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
Config | Sets or retrieves a configuration setting. |
DoEvents | This method processes events from the internal message queue. |
GetLine | This method gets a line of text from the server. |
Interrupt | This method interrupts the current action. |
Send | Sends data over the connected pipe. |
SendFile | Sends the file over the connected pipe. |
SendLine | This method sends a string followed by a newline. |
SendStdinBytes | This method sends binary data over the connected pipe. |
SendStdinText | This method sends text over the connected pipe. |
StartProcess | Starts the process. |
StopProcess | Stops the process. |
Event List
The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.
Error | Fired when information is available about errors during data delivery. |
ReadyToSend | Fired when the component is ready to send data. |
Stderr | Fired when data come in through stderr. |
Stdout | Fired when data come in through stdout. |
Config Settings
The following is a list of config settings for the component with short descriptions. Click on the links for further details.
LogonType | Specifies the logon type when starting a process as another user. |
Password | Specifies the password when starting a process as another user. |
ProcessId | Returns the Id of the process which was started. |
ProcessStartupFlags | Specifies the flags used when starting the process in Windows. |
ProcessWindowStyle | Specifies the window style when STARTF_USESHOWWINDOW is specified. |
User | Specifies the user when starting a process as another user. |
BuildInfo | Information about the product's build. |
CodePage | The system code page used for Unicode to Multibyte translations. |
LicenseInfo | Information about the current license. |
MaskSensitiveData | Whether sensitive data is masked in log messages. |
UseFIPSCompliantAPI | Tells the component whether or not to use FIPS certified APIs. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
AcceptData Property (PipeExec Component)
Enables or disables data reception (the Stdout and Stderr events).
Syntax
__property bool AcceptData = { read=FAcceptData, write=FSetAcceptData };
Default Value
True
Remarks
This property enables or disables data reception (the Stdout and Stderr events). Setting this property to False, temporarily disables data reception. Setting this property to True, re-enables data reception.
This property is not available at design time.
Data Type
Boolean
BytesSent Property (PipeExec Component)
The number of bytes actually sent after a call to the SendStdinText or SendStdinBytes method.
Syntax
__property int BytesSent = { read=FBytesSent };
Default Value
0
Remarks
This property indicates how many bytes were sent after the last call to SendStdinText or SendStdinBytes. Please check the SendStdinText or SendStdinBytes method for more information. Note: that BytesSent will always return 0 when the component is operating in synchronous mode (i.e., the Timeout property is set to a positive value.)
This property is read-only and not available at design time.
Data Type
Integer
EOL Property (PipeExec Component)
This property is used to break the incoming data stream into chunks separated by EOL .
Syntax
__property String EOL = { read=FEOL, write=FSetEOL }; __property DynamicArray<Byte> EOLB = { read=FEOLB, write=FSetEOLB };
Default Value
""
Remarks
This property is used to define boundaries in the input stream using the value of the property.
This property is especially useful with ASCII files. Setting it to CRLF ("\r\n") enables the incoming ASCII text stream to split into defined lines. In this case, one event is fired for each line received (as well as in packet boundaries). The CRLF ("\r\n") bytes are discarded.
This property is a binary string. Notably, this means that it can be more than one byte long, and it can contain NULL bytes.
Data Type
Byte Array
ProcessArgs Property (PipeExec Component)
The arguments to pass to the process.
Syntax
__property String ProcessArgs = { read=FProcessArgs, write=FSetProcessArgs };
Default Value
""
Remarks
This property specifies the arguments that will be passed to the process when it is started.
This property is not available at design time.
Data Type
String
ProcessFileName Property (PipeExec Component)
The path to the file on disk to execute.
Syntax
__property String ProcessFileName = { read=FProcessFileName, write=FSetProcessFileName };
Default Value
""
Remarks
This property specifies the path to the file on disk that will be executed. ProcessArgs optionally specifies the arguments that will be passed. ProcessWorkingDir optionally specifies the working directory in which the process will run.
This property is not available at design time.
Data Type
String
ProcessRunning Property (PipeExec Component)
Whether the process is running.
Syntax
__property bool ProcessRunning = { read=FProcessRunning };
Default Value
False
Remarks
This property indicates whether the process specified by ProcessFileName is running.
After calling StartProcess this property returns True. After calling StopProcess this property returns False.
This property is read-only and not available at design time.
Data Type
Boolean
ProcessWorkingDir Property (PipeExec Component)
The working directory of the process.
Syntax
__property String ProcessWorkingDir = { read=FProcessWorkingDir, write=FSetProcessWorkingDir };
Default Value
""
Remarks
This property optionally specifies the working directory in which the process will run.
This property is not available at design time.
Data Type
String
SingleLineMode Property (PipeExec Component)
This property includes a special mode for line-oriented protocols.
Syntax
__property bool SingleLineMode = { read=FSingleLineMode, write=FSetSingleLineMode };
Default Value
False
Remarks
When this property is set to True, the component treats the incoming data stream as lines separated by carriage return line feed (CRLF), CR, or LF. The EOL property is ignored.
When this property is set to True, AcceptData automatically will be set to False. Please refer to the GetLine method for more information.
This property is not available at design time.
Data Type
Boolean
Timeout Property (PipeExec Component)
This property includes the timeout for the component.
Syntax
__property int Timeout = { read=FTimeout, write=FSetTimeout };
Default Value
60
Remarks
If the Timeout property is set to 0, all operations return immediately, potentially failing with a WOULDBLOCK error if data cannot be sent immediately.
If Timeout is set to a positive value, data is sent in a blocking manner and the component will wait for the operation to complete before returning control. The component will handle any potential WOULDBLOCK errors internally and automatically retry the operation for a maximum of Timeout seconds.
The component will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.
If Timeout expires, and the operation is not yet complete, the component raises an exception.
Note: By default, all timeouts are inactivity timeouts, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.
The default value for the Timeout property is 60 seconds.
Data Type
Integer
Config Method (PipeExec Component)
Sets or retrieves a configuration setting.
Syntax
String __fastcall Config(String ConfigurationString);
Remarks
Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
DoEvents Method (PipeExec Component)
This method processes events from the internal message queue.
Syntax
void __fastcall DoEvents();
Remarks
When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.
GetLine Method (PipeExec Component)
This method gets a line of text from the server.
Syntax
String __fastcall GetLine();
Remarks
This method gets a line of text from the server. This method is an alternative method of receiving data for line-oriented protocols. The component will block if necessary and then will return the received line. AcceptData will be set automatically to True when the method is called, and then will be set to False after a line is received.
Please refer to the SingleLineMode property for more information.
Interrupt Method (PipeExec Component)
This method interrupts the current action.
Syntax
void __fastcall Interrupt();
Remarks
This method interrupts the current action. If you use SendFile to upload a file, the component will run synchronously until the upload is completed. This method will allow you to stop the file from uploading without disconnecting from the host.
Send Method (PipeExec Component)
Sends data over the connected pipe.
Syntax
void __fastcall Send(DynamicArray<Byte> Text);
Remarks
This method sends data to the server.
SendFile Method (PipeExec Component)
Sends the file over the connected pipe.
Syntax
void __fastcall SendFile(String FileName);
Remarks
This method sends the specified file to the server/process over the connected pipe.
Timeout must be set to a positive value so that the component will operate synchronously.
SendLine Method (PipeExec Component)
This method sends a string followed by a newline.
Syntax
void __fastcall SendLine(String Text);
Remarks
This method sends a string followed by a newline. This method is used to send data with line-oriented protocols. The line is followed by CRLF ("\r\n") .
Please refer to the GetLine method and SingleLineMode property for more information.
SendStdinBytes Method (PipeExec Component)
This method sends binary data over the connected pipe.
Syntax
void __fastcall SendStdinBytes(DynamicArray<Byte> Data);
Remarks
This method sends the specified binary data to the server over Stdin. To send text, use the SendStdinText method instead.
When Timeout is set to 0 the component will behave asynchronously. If you are sending data to the receiving process faster than it can process it, the outgoing queue might fill up. When this happens, the component raises the exception with errorcode 10035 and message "[10035] Operation would block" (WSAEWOULDBLOCK). You can handle this exception, and then try to send the data again. The BytesSent property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the ReadyToSend event before attempting to send data again. (However, please note that ReadyToSend is not fired when part of the data is successfully sent).
SendStdinText Method (PipeExec Component)
This method sends text over the connected pipe.
Syntax
void __fastcall SendStdinText(String Text);
Remarks
This method sends the specified text to the server over Stdin. To send binary data, use the SendStdinBytes method instead.
When Timeout is set to 0 the component will behave asynchronously. If you are sending data to the receiving process faster than it can process it, the outgoing queue might fill up. When this happens, the component raises the exception with errorcode 10035 and message "[10035] Operation would block" (WSAEWOULDBLOCK). You can handle this exception, and then try to send the data again. The BytesSent property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the ReadyToSend event before attempting to send data again. (However, please note that ReadyToSend is not fired when part of the data is successfully sent).
StartProcess Method (PipeExec Component)
Starts the process.
Syntax
void __fastcall StartProcess();
Remarks
This method starts the process specified by StartProcess. After starting the process data may be sent to the process by calling Send, SendLine, Send.
Data received from the process will be available from the Stdout and Stderr events.
The following properties are applicable when calling this method:
- ProcessFileName (required)
- ProcessArgs
- ProcessWorkingDir
StopProcess Method (PipeExec Component)
Stops the process.
Syntax
void __fastcall StopProcess();
Remarks
This method stops the process.
Error Event (PipeExec Component)
Fired when information is available about errors during data delivery.
Syntax
typedef struct { int ErrorCode; String Description; } TiipPipeExecErrorEventParams; typedef void __fastcall (__closure *TiipPipeExecErrorEvent)(System::TObject* Sender, TiipPipeExecErrorEventParams *e); __property TiipPipeExecErrorEvent OnError = { read=FOnError, write=FOnError };
Remarks
The Error event is fired in case of exceptional conditions during message processing. Normally the component raises an exception.
The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.
ReadyToSend Event (PipeExec Component)
Fired when the component is ready to send data.
Syntax
typedef struct { } TiipPipeExecReadyToSendEventParams; typedef void __fastcall (__closure *TiipPipeExecReadyToSendEvent)(System::TObject* Sender, TiipPipeExecReadyToSendEventParams *e); __property TiipPipeExecReadyToSendEvent OnReadyToSend = { read=FOnReadyToSend, write=FOnReadyToSend };
Remarks
The ReadyToSend event indicates that the underlying pipe is ready to accept data again after a failed send. The event is also fired immediately after a connection to the remote host is established.
Stderr Event (PipeExec Component)
Fired when data come in through stderr.
Syntax
typedef struct { String Text; DynamicArray<Byte> TextB; bool EOL; } TiipPipeExecStderrEventParams; typedef void __fastcall (__closure *TiipPipeExecStderrEvent)(System::TObject* Sender, TiipPipeExecStderrEventParams *e); __property TiipPipeExecStderrEvent OnStderr = { read=FOnStderr, write=FOnStderr };
Remarks
The Stderr event is fired every time the process outputs a line in its standard output. The incoming data is provided through the Text parameter.
Stdout Event (PipeExec Component)
Fired when data come in through stdout.
Syntax
typedef struct { String Text; DynamicArray<Byte> TextB; bool EOL; } TiipPipeExecStdoutEventParams; typedef void __fastcall (__closure *TiipPipeExecStdoutEvent)(System::TObject* Sender, TiipPipeExecStdoutEventParams *e); __property TiipPipeExecStdoutEvent OnStdout = { read=FOnStdout, write=FOnStdout };
Remarks
The Stdout event is fired every time the process outputs a line in its standard output. The incoming data is provided through the Text parameter.
EOL indicates whether or not the EOL string was found at the end of Text. If the EOL string was found, then EOL is True.
If Text is part of a data portion of length larger than MaxLineLength with no EOL strings in it, then EOL is False. Note: This means that one or more DataIn events with EOL set to False can be received during a connection.
If the EOL property is "" (empty string), then EOL can be disregarded (it is always True).
Config Settings (PipeExec Component)
The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.PipeExec Config Settings
2 | LOGON32_LOGON_INTERACTIVE |
3 | LOGON32_LOGON_NETWORK |
4 | LOGON32_LOGON_BATCH |
5 | LOGON32_LOGON_SERVICE |
7 | LOGON32_LOGON_UNLOCK |
8 | LOGON32_LOGON_NETWORK_CLEARTEXT |
9 | LOGON32_LOGON_NEW_CREDENTIALS |
This may be set to the binary 'OR' of one or more of the following values:
0x00000040 | STARTF_FORCEONFEEDBACK |
0x00000080 | STARTF_FORCEOFFFEEDBACK |
0x00002000 | STARTF_PREVENTPINNING |
0x00000020 | STARTF_RUNFULLSCREEN |
0x00001000 | STARTF_TITLEISAPPID |
0x00000800 | STARTF_TITLEISLINKNAME |
0x00000008 | STARTF_USECOUNTCHARS |
0x00000010 | STARTF_USEFILLATTRIBUTE |
0x00000200 | STARTF_USEHOTKEY |
0x00000004 | STARTF_USEPOSITION |
0x00000001 (default) | STARTF_USESHOWWINDOW |
0x00000002 | STARTF_USESIZE |
0x00000100 (default) | STARTF_USESTDHANDLES |
0 (default) | SW_HIDE |
1 | SW_SHOWNORMAL |
2 | SW_SHOWMINIMIZED |
3 | SW_SHOWMAXIMIZED |
4 | SW_SHOWNOACTIVATE |
5 | SW_SHOW |
6 | SW_MINIMIZE |
7 | SW_SHOWMINNOACTIVE |
8 | SW_SHOWNA |
9 | SW_RESTORE |
10 | SW_SHOWDEFAULT |
11 | SW_FORCEMINIMIZE |
Base Config Settings
The following is a list of valid code page identifiers:
Identifier | Name |
037 | IBM EBCDIC - U.S./Canada |
437 | OEM - United States |
500 | IBM EBCDIC - International |
708 | Arabic - ASMO 708 |
709 | Arabic - ASMO 449+, BCON V4 |
710 | Arabic - Transparent Arabic |
720 | Arabic - Transparent ASMO |
737 | OEM - Greek (formerly 437G) |
775 | OEM - Baltic |
850 | OEM - Multilingual Latin I |
852 | OEM - Latin II |
855 | OEM - Cyrillic (primarily Russian) |
857 | OEM - Turkish |
858 | OEM - Multilingual Latin I + Euro symbol |
860 | OEM - Portuguese |
861 | OEM - Icelandic |
862 | OEM - Hebrew |
863 | OEM - Canadian-French |
864 | OEM - Arabic |
865 | OEM - Nordic |
866 | OEM - Russian |
869 | OEM - Modern Greek |
870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
875 | IBM EBCDIC - Modern Greek |
932 | ANSI/OEM - Japanese, Shift-JIS |
936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
949 | ANSI/OEM - Korean (Unified Hangul Code) |
950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
1026 | IBM EBCDIC - Turkish (Latin-5) |
1047 | IBM EBCDIC - Latin 1/Open System |
1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
1147 | IBM EBCDIC - France (20297 + Euro symbol) |
1148 | IBM EBCDIC - International (500 + Euro symbol) |
1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
1201 | Unicode UCS-2 Big-Endian |
1250 | ANSI - Central European |
1251 | ANSI - Cyrillic |
1252 | ANSI - Latin I |
1253 | ANSI - Greek |
1254 | ANSI - Turkish |
1255 | ANSI - Hebrew |
1256 | ANSI - Arabic |
1257 | ANSI - Baltic |
1258 | ANSI/OEM - Vietnamese |
1361 | Korean (Johab) |
10000 | MAC - Roman |
10001 | MAC - Japanese |
10002 | MAC - Traditional Chinese (Big5) |
10003 | MAC - Korean |
10004 | MAC - Arabic |
10005 | MAC - Hebrew |
10006 | MAC - Greek I |
10007 | MAC - Cyrillic |
10008 | MAC - Simplified Chinese (GB 2312) |
10010 | MAC - Romania |
10017 | MAC - Ukraine |
10021 | MAC - Thai |
10029 | MAC - Latin II |
10079 | MAC - Icelandic |
10081 | MAC - Turkish |
10082 | MAC - Croatia |
12000 | Unicode UCS-4 Little-Endian |
12001 | Unicode UCS-4 Big-Endian |
20000 | CNS - Taiwan |
20001 | TCA - Taiwan |
20002 | Eten - Taiwan |
20003 | IBM5550 - Taiwan |
20004 | TeleText - Taiwan |
20005 | Wang - Taiwan |
20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
20106 | IA5 German (7-bit) |
20107 | IA5 Swedish (7-bit) |
20108 | IA5 Norwegian (7-bit) |
20127 | US-ASCII (7-bit) |
20261 | T.61 |
20269 | ISO 6937 Non-Spacing Accent |
20273 | IBM EBCDIC - Germany |
20277 | IBM EBCDIC - Denmark/Norway |
20278 | IBM EBCDIC - Finland/Sweden |
20280 | IBM EBCDIC - Italy |
20284 | IBM EBCDIC - Latin America/Spain |
20285 | IBM EBCDIC - United Kingdom |
20290 | IBM EBCDIC - Japanese Katakana Extended |
20297 | IBM EBCDIC - France |
20420 | IBM EBCDIC - Arabic |
20423 | IBM EBCDIC - Greek |
20424 | IBM EBCDIC - Hebrew |
20833 | IBM EBCDIC - Korean Extended |
20838 | IBM EBCDIC - Thai |
20866 | Russian - KOI8-R |
20871 | IBM EBCDIC - Icelandic |
20880 | IBM EBCDIC - Cyrillic (Russian) |
20905 | IBM EBCDIC - Turkish |
20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
20932 | JIS X 0208-1990 & 0121-1990 |
20936 | Simplified Chinese (GB2312) |
21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
21027 | Extended Alpha Lowercase |
21866 | Ukrainian (KOI8-U) |
28591 | ISO 8859-1 Latin I |
28592 | ISO 8859-2 Central Europe |
28593 | ISO 8859-3 Latin 3 |
28594 | ISO 8859-4 Baltic |
28595 | ISO 8859-5 Cyrillic |
28596 | ISO 8859-6 Arabic |
28597 | ISO 8859-7 Greek |
28598 | ISO 8859-8 Hebrew |
28599 | ISO 8859-9 Latin 5 |
28605 | ISO 8859-15 Latin 9 |
29001 | Europa 3 |
38598 | ISO 8859-8 Hebrew |
50220 | ISO 2022 Japanese with no halfwidth Katakana |
50221 | ISO 2022 Japanese with halfwidth Katakana |
50222 | ISO 2022 Japanese JIS X 0201-1989 |
50225 | ISO 2022 Korean |
50227 | ISO 2022 Simplified Chinese |
50229 | ISO 2022 Traditional Chinese |
50930 | Japanese (Katakana) Extended |
50931 | US/Canada and Japanese |
50933 | Korean Extended and Korean |
50935 | Simplified Chinese Extended and Simplified Chinese |
50936 | Simplified Chinese |
50937 | US/Canada and Traditional Chinese |
50939 | Japanese (Latin) Extended and Japanese |
51932 | EUC - Japanese |
51936 | EUC - Simplified Chinese |
51949 | EUC - Korean |
51950 | EUC - Traditional Chinese |
52936 | HZ-GB2312 Simplified Chinese |
54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
57002 | ISCII Devanagari |
57003 | ISCII Bengali |
57004 | ISCII Tamil |
57005 | ISCII Telugu |
57006 | ISCII Assamese |
57007 | ISCII Oriya |
57008 | ISCII Kannada |
57009 | ISCII Malayalam |
57010 | ISCII Gujarati |
57011 | ISCII Punjabi |
65000 | Unicode UTF-7 |
65001 | Unicode UTF-8 |
Identifier | Name |
1 | ASCII |
2 | NEXTSTEP |
3 | JapaneseEUC |
4 | UTF8 |
5 | ISOLatin1 |
6 | Symbol |
7 | NonLossyASCII |
8 | ShiftJIS |
9 | ISOLatin2 |
10 | Unicode |
11 | WindowsCP1251 |
12 | WindowsCP1252 |
13 | WindowsCP1253 |
14 | WindowsCP1254 |
15 | WindowsCP1250 |
21 | ISO2022JP |
30 | MacOSRoman |
10 | UTF16String |
0x90000100 | UTF16BigEndian |
0x94000100 | UTF16LittleEndian |
0x8c000100 | UTF32String |
0x98000100 | UTF32BigEndian |
0x9c000100 | UTF32LittleEndian |
65536 | Proprietary |
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
FIPS mode can be enabled by setting the UseFIPSCompliantAPI configuration setting to true. This is a static setting that applies to all instances of all components of the toolkit within the process. It is recommended to enable or disable this setting once before the component has been used to establish a connection. Enabling FIPS while an instance of the component is active and connected may result in unexpected behavior.
For more details, please see the FIPS 140-2 Compliance article.
Note: This setting is applicable only on Windows.
Note: Enabling FIPS compliance requires a special license; please contact sales@nsoftware.com for details.
Setting this configuration setting to true tells the component to use the internal implementation instead of using the system security libraries.
This setting is set to false by default on all platforms.
Trappable Errors (PipeExec Component)
PipeExec Errors
401 | Failed to create event. |
402 | Failed to create security descriptor. |
403 | Error creating named pipe. |
404 | Error connecting to named pipe. |
405 | Error disconnecting named pipe. |
408 | Error sending data. |
410 | Invalid MaxLineLength value. |
411 | Error reading data. |
412 | Error invoking RegisterWaitForSingleObject. |
413 | Operation would block. |
414 | Named pipe does not exist. |
415 | Named pipe is already connected. |
416 | Error connecting to named pipe. |
417 | Named pipe not connected. |
419 | Unsupported operation, see error message for details. |
420 | Failed to create named pipe for Stdin/Stdout/Stderr. |
421 | Failed to set handle information for Stdin/Stdout/Stderr. |
422 | Failed to create process. |
423 | Failed to terminate process. |