Linkar Suite 2.3.7

S0000        Error verifying install: {0}

S0001        Error setting Binding and / or Listening on the IP and Port of the EntryPoint\r\n{0}

S0002        Error in the IP and / or listening port of the EntryPoint\r\n{0}

S0003        Stopping EntryPoint: Error closing connections that are still open\r\n{0} EntryPoint {1} Status {2} from IP: {3} GUID: {4} Cmd {5}

S0004        Error starting EntryPoint main thread\r\n{0}

S0005        Stopping EntryPoint: error closing sockets\r\n{0} EntryPoint {1} Status {2}

S0006        SocketException in Accept Connections: {0} EntryPoint {1} Status {2}

S0007        Exception in Accept Connections: {0} EntryPoint {1} Status {2}

S0012        Processing connection: socket error receiving client package\r\n{0}

S0013        Data Length too large\r\n{0}

S0014        Closing connection: error closing the socket\r\n{0}

S0015        Command NOT valid in the indicated port. A wrong port is being used for the connection\r\n{0}

S0020        Not valid GUID

S0021        Error decrypting\r\n{0}

S0022        Error decrypting. Not valid PK

S0023        Not allowed working without ENCRYPTION DATA

S0030        Input format XML parsing error\r\n{0}

S0031        Input format XML parsing error\r\n{0}

S0032        Error rebuilding buffer Input in format XML\r\n{0}

S0040        Input format JSON parsing error\r\n{0}

S0041        Input format JSON parsing error\r\n{0}

S0042        Error rebuilding buffer Input in format JSON\r\n{0}

S0050        Profile {0} NOT FOUND

S0051        Unknown COMMAND TYPE

S0053        Unknown COMMAND for COMMAND TYPE DB

S0055        SENDCOMMAND Data parse error: {0}

S0056        Profile {0}, EntryPoint {1} NOT FOUND

S0057        Profile {0}, EntryPoint {1}, Session {2} NOT FOUND

S0060        Error sending response packet\r\n{0}

S0070        LITE: Only 30 HTTP Api operations allowed

S0100        ERROR RESPONSE LKLISTENING: {0}

S0103        NO DB LINES AVAILABLE

S0112        Operation CODE {0}, the database has not responded in the defined timeout time (Linkar Line ID {1} DB Line ID {2})

S0115        Linkar Line ID {0} (DB Line ID: {1}) is BROKEN. Internal ERROR MESSAGE: {2}        

S0116        ERROR: \"{0}\" executing PingPreOp in Linkar Line ID {1} (DB Line ID: {2}). The line has changed to a BROKEN status              

S0118        DB Lines Manager. Broken line resolution info:[%CR%][%LF%]{0}

S0120        LKPING Error: {0}

S0121        Special CHARS not received correctly. Verify Character Conversion From-To Database in EntryPoint.

S0130        ERROR closing DB connection Linkar Line ID {0} (DB Line ID {1}): {2}

S0140        Reset Common Blocks ERROR in Linkar Line ID {0} (DB Line ID {1}): {2}

S0160        Operation ABORTED by Admin

S0180        No response receive from some Reset Common Blocks commands

S0181        Other Reset Common Blocks commands are in execution

S0190        Error sending email: {0}

S0191        Error composing body email: {0}

S0202        QM ERROR {0}

S0210        Error connecting database QM using QMCLIENT: {0}

S0215        Error disconnecting database QM using QMCLIENT: {0}

S0250        D3(MVSP) Timeout waiting response from database (ms waiting: {0})

S0252        D3(MVSP) ERROR {0}

S0255        D3(MVSP) Error connecting database: {0}

S0256        D3(MVSP) Failed Login

S0257        D3(MVSP) Error disconnecting database: {0}

S0301        TERMINAL Connection Mode. SocketException: {0}

S0302        TERMINAL Connection Mode. Exception: {0}

S0310        TERMINAL Connection Mode. COMUNICATION ERROR: BAD Response header. NOT FOUND SUB.LKMAIN // + CfgServerParameters.LKLISTENING_CMD_LKMAIN},

S0311        TERMINAL Connection Mode. COMUNICATION ERROR: The DB response does NOT have enough arguments or SUBS char NOT FOUND. Verify Character Conversion From-To Database in EntryPoint.

S0401        SOCKET Connection Mode. GENERAL COMUNICATION ERROR: {0}

S0402        SOCKET Connection Mode. GENERAL ERROR: {0}

S0403        SOCKET Connection Mode. COMMUNICATION ERROR: DB response has NOT enough arguments or SUBS char NOT FOUND.

S0500        BAD FORMATED HEADER FROM DB RESPONSE: LENGTH NOT NUMERIC

S0501        EOT MARK NOT FOUND IN DATA SECTION

S0503        Operation ABORTED by Admin

S0507        SOCKET Connection Mode. Wrong ID Header response

S0510        Timeout when establishing connection to DB

S0520        Error waiting response \"{0}\" from DB.\r\nLast received: {1}

S0521        Timeout waiting response \"{0}\" from DB.\r\nLast received: {1}

S0530        SocketException: TIMEOUT

S0531*        SocketException: {0}

S0540        Host: {0} Exception: {1}

S0541        Unable to resolve hostname or invalid IPv4: {0}

S0550        Timeout reading Telnet Client

S0560        Timeout writing Telnet Client

S0570        SOCKET Connection Mode. SocketException connecting to DB\r\n{0}

S0571        SOCKET Connection Mode. Exception connecting to DB: {0}}

S0600        The connection cannot be established. Telenet session Closed.

S0601        Error establishing Telnet connection: {0}

S0602        The connection cannot be established. SSH session Closed.

S0603        Error establishing SSH connection: {0}

S0606        Error in Telnet/SSH Read waiting contained text: \"{0}\"

S0607        Error in Telnet/SSH Read waiting ending text: \"{0}\"

S0608        Error in Telnet/SSH Read: \"{0}\"

S0609        Error in Telnet/SSH Write: \"{0}\"

S0610        Error Receiving Data: Telnet/SSH session is closed

S0611        EOT mark NOT FOUND in HEADER section ({0})

S0612        SOH mark NOT FOUND in HEADER section ({0})

S0613        NOT NUMERIC HEADER

S0614        EOT mark NOT FOUND in DATA section ({0})

S0615        STX mark NOT FOUND in DATA section ({0})

S0616        Error in received data. Expected length data: {0} Received data: {1}

S0620        Error Sending Data: Telnet/SSH session is closed

S0621        Error Sending HEADER: {0}

S0622        Error Sending DATA: {0}

S0623        TERMINAL Connection Mode. Wrong ID Header response

S0630        LoginString last command: \"{0}\" Result is \"{1}\"

S0631        LoginString last command EOT mark NOT FOUND: \"{0}\" Result is \"{1}\"

S0632        Error sending text in Executing LoginString {0}

S0633        Error receiving text in Executing LoginString {0}

S0634        Timeout Error received during the LoginString execution. Error: {0}

S0800        UNIOBJECTS ERROR. ErrorCode: {0} ErrorMessage: {1}

S0900        jBASE-jAgent. Timeout waiting response from DB

S0902        JBASE-jAgent. Exception executing operation: {0}

S0903        JBASE-jAgent. JSubroutineNotFoundException: {0}

S0910        jBASE-jAgent. Error connecting database: {0}

S0911        jBASE-jAgent. Error switching to account \"{0}\"

S0912        Error connecting to jBASE Agent. Check Authentication Mode

S0915        jBASE-jAgent. Error disconnecting: {0}

S3000        Login Time Expired

S3001        Invalid Session ID

S3010        Login: Entrypoint \"{0}\" NOT accessible in {1}:{2}

S3011        LITE version allow only 1 Client Connection

S3012        Login: PLUGIN not register

S3021        Logout: Entrypoint \"{0}\" NOT accessible in {1}:{2}

S3050        MISMATCH versions Linkar SERVER {0} / Linkar Client {1}

S3051        MISMATCH versions Linkar SERVER {0} / MV Accounts {1}

S3060        Session GUID not found

S3070        Error getting password from \"{0}\" service: {1}

S4010        Entrypoint \"{0}\" NOT accessible in {1}:{2}

S4011        PLUGIN not register in Direct Operation

S6000        Profile DB type not valid

S6001        EntryPoint \"{0}\" is not started: \"{1}\"

S6002        Error Updating Entrypoint \"{0}\" (Profile \"{0}\")

S6003        Error STARTING DB LINES in EntryPoint \"{0}\" (Profile: \"{1}\") : {2}

S8000        CMD MANAGER. DECRYPT ERROR: {0}

S8001        CMD MANAGER. Error calculating SID\r\n{0}

S8002        CMD MANAGER. Error writing config.xml\r\n{0}

S8003        CMD MANAGER. Error downloading config.xml\r\n{0}

S8004        CMD MANAGER. Error getting NIC list\r\n{0}

S8005        CMD MANAGER. Error getting NIC list. NIC list empty

S8006        CMD MANAGER. Error calculating activation

S8010        Wrong Activation Data

S8011        Wrong Plugin Activation Data

S8012        Plugin can't be activated in Lite Version

S8020        CMD MANAGER. Error Starting Profile. See Error File Logs in LinkarServer

S8021        CMD MANAGER. Error Starting EntryPoint. See Error File Logs in LinkarServer

S8025        CMD MANAGER. Session ID {0} not found

S8030        CMD MANAGER. Can not START Entrypoint \"{0}\" in Profile \"{1}\"

S8049        CMD MANAGER. Unkwon MANAGER command

S8050        CMD MANAGER ({0}) Profile \"{1}\" NOT FOUND

S8051        CMD MANAGER ({0}) Entrypoint \"{1}\" NOT FOUND in Profile \"{2}\"

S8052        CMD MANAGER. Command bad formated. {0}

S8053        CMD MANAGER. General exception performing DATA BASE TEST CONNECTION: \"{0}\"

S8096        Lite Version in Docker not allowed.

S8097        Pro Version: Maximun {0} lines opened simultaneously

S8098        Lite Version: Only 1 Database Line Running Allowed

S8099        Lite Version: Only 1 Entrypoint Running Allowed

S8100        Incorrect password

S8101        Not Authorizated to EntryPoint \"{0}\"

S8102        User \"{0}\" does not exist

S8103        NULL User List

S8104        User \"{0}\" is DISABLED

S9000        Command incorrectly formed. Missing argument/s

S9001        Command incorrectly formed. Extra Argument/s

S9002        Error Reloading Config Data: {0}

S9020        Error in LkSchemas Info DESERIALIZATION : {0}

S9100        Error in Statistics Module: {0}

S9101        Error in Statistics Module management EntryPoint Dictionaries Counters: {0}

S9102        Error in Statistics Service Web: {0}

S9999        Unhandled exception: {0}

C0001        Session ID NOT VALID

C0002        Socket Exception        (only COM Library)

C0003        Linkar Exception        (errors from Linkar SERVER)

C0004        Exception                (only COM Library)

C0005        IP or Host NOT valid

C0009        CHECKSUM ERROR

Error code C0003 refers to errors originated in Linkar Server. In the LkException InternalCode and InternalMessage properties you can check Linkar SERVER error codes (see Linkar SERVER error table above)

No exceptions are raised in the COM assembly functions. Exceptions are captured internally and error messages are copied to the LkError property of the LkData class objects

A0001        Error reading config file from API Key %1

A0002        The API Key %1 is inactive

A0003        The API Key %1 is expired

A0004        The Client IP %1 is not allowed

A0005        The Operation %1 is not allowed

A0007        Linkar SERVER is offline

A0008        The API Key %1 data has errors

A0009        The API Key %1 does not exist

A0010        The EntryPoint is not assigned

A0011        The Profile %1 does not exist

A0012        The EntryPoint %1 does not exist

A0013        Must specify an API Key in the header of the request

  M0001        You can not delete your own session

  M0002        ERROR processing response of CMD GetSessionIds:\r\n{0}

  M0003        ERROR processing response of CMD GetStatus:\r\n{0}

  M0400        NIC list empty

100        Session does not exist

101        There is no user in the Session

102        Data account does not exist

103        It is not being executed in the Data Account %1. Error from %2

110        Method %1 does not exist

111        Inconsistency between Record Separation Marks

119        File %1 must exist in Data Account

120        File %1 does not exist

121        Record %1 does not exist

122        Operation Cancelled. Record %1 modified by another user

123        Operation Cancelled. Record %1 already exists

124        Invalid RecordID %1

125        Operation Cancelled. Empty RecordID

126        More than one option is indicated to create the RecordID

127        Operation Cancelled. No RecordID for the writing

128        More than one option to recover the RecordID is indicated

129        Wrong separator. %1

130        Wrong Dictionaries in DictClause: %1

131        Dict %1 is Calculated. The Calculated Option must be activated.

140        Main Control Custom Error. %1

141        NewRecoverRecordID Custom Errror. %1

150        Exception %1.%2

151        Trigger Error %1%2

152        Status Error. %1, %2

153        Index error

180        Wrongly defined page number

181        Wrongly defined records per page

182        Query Error %1

190        Wrong Conversion

191        Wrong Conversion type

192        Wrong Format Specification

201        Subroutine name is not indicated

202        Subroutine %1 does not exist or it is not catalogued

203        Inconsistency in the number of arguments of the subroutine %1

204        La subrutina %1 no está compilada en FlashBasic

212        Input/Output format must be %1

213        Not Available in this Version. %1

214        SchemaType value is wrong

215        Expired Evaluation Time

216        No %1 label found in %2 buffer

217        The %1 label is not valid

230        Invalid Parameter %1. %2

231        Schema %1 already exists

232        Schema %1 does not exist

233        Property %1 already exists

234        Wrong Data Type %1. STRING, BOOL, INTEGER, DECIMAL, DATE, TIME, DATETIME

240        Validation Error. Equal To. Wrong Format

241        Validation Error. Field MV Number Requires Field Number greater than 0

242        Validation Error. Field MV Number must be greater than 0

243        Validation Error. Field MV Number, MV or SV Table Name are not valid

244        Validation Error. Field SV Number Requires Field Number greater than 0

245        Validation Error. Field SV Number must be greater than 0

246        Validation Error. Field SV Number, MV or SV Table Name are not valid

247        Validation Error. If it Is Key, it cannot be Calculated

248        Validation Error. If it Is Key, Field Number must be 0

249        Validation Error. If it Is Key, it is not Equal To

250        Validation Error. If it Is Key, it is not MV or SV

251        Validation Error. Calculated Property. Any Field Number is valid

252        Validation Error. Calculated Property. cannot be Key

253        Validation Error. Calculated Property. cannot be Required

254        Validation Error. Calculated Property. The Dictionary must exist.

255        Validation Error. SV Table requires a MV Table Name

256        Validation Error. Max Range must be greater than the Min Range

257        Validation Error. Decimal Data Type. No number of decimals defined

259        Validation Error. Max Length must be greater than 0

260        Validation Error. Inconsistency between Options and Options Label

261        Validation Error in %1. This is mandatory

262        Validation Error in %1. Must be Numeric

263        Validation Error in %1. Must be Boolean

264        Validation Error in %1. Only letters or numbers

You can customize the error messages in other languages by creating new records and adding the language's original extension to the code.

In the Client Login Function there is an argument called Language. This argument is used to make the admin know the language of the final user, and the Linkar components use this argument forced to capital letters to locate the error in this language in the errors list. If the error doesnot exist, the message by default in English will be used

For instance, the same list in Spanish:

100.ES        No existe Sesión

101.ES        No existe usuario en la Sesión

102.ES        No existe Cuenta de Datos

............