Iguana Error Messages

This page lists the most common Iguana errors, explains what they mean and identifies Actions to take.

This page is not definitive, to get the the best out of it you should use it as a guideline – or as a basis for your own list. You may have other errors that occur on your sites that you want to add to the list. Also you can customize Actions and Comments to meet your specific needs.

The list ErrorsOutShow.csv is available for you download and customize.

Please have a look at this FAQ on how to document error messages. It shows how to export errors from Iguana logs into a SQLite database. The errors on this page are generated using the code from this FAQ.

What do the fields in this table mean?

  • Message: this is the text of the error message.
  • Type: this is the type of error message.
    • debug: this is a development coding error (for a programmer).
    • Lua debug: this is a Lua coding error (for a programmer).
    • error: this a legitimate production error (for an administrator).
    • warning: production warning (for an administrator).
    • info: information message.
  • Status: this is used to decide which errors are shown in the filtered output (ErrorsOutShow.csv).
    • show: indicates to show in the ErrorsOutShow.csv file.
      • currently show is used to indicate unique messages.
    • Other codes like hide and duplicate are descriptive.
  • Source: where the error into the was sourced from, e.g.,
    • Interfaceware Log Export.
    • Interfaceware – manual entry.
  • Location: this is where the error is found in Iguana, e.g.,
    • Iguana Logs.
    • ServiceErrorLog.txt.
    • Iguana System.
  • Description: a brief/precise statement of what the error means.
  • Comment: use to describe the error.
    • longer brain dump of potential issues solutions etc etc…
  • Action: a brief/precise statement of the action to be taken when the error occurs.
    • You may require specific action(s) for your installation.

Note: *** is used when the exact meaning of an error is uncertain.

The list is divided into two parts. The first part General Errors does not contain any coding errors (Type = “Lua debug”). The second part Coding Errors contains a sample of (the potentially infinite number of) coding errors.

Part one: General Errors

Message Type Status Source LogSource Location Description Comment Action
‘PID’ member does not exist. Named members are MSH, NTE, PATIENT, ORDER. debug show Interfaceware – manual entry *** Iguana Logs PID segment not found in the parsed message The parsed message does not contain a PID segment. This can happen if you write code that expects ADT messages (works with ADT) but then a different message arrives (ORM for example) and the code breaks. But an ORM has a PID segment – aha but the VMD you are using only recognises ADT messages – therefore the PID segment in the ORM message is not parsed – therefore we get the error. There are several ways to handle this write code to IGNORE messages other than ADT – or if you want to process ORM message tehn write code to handle them (and probably change the VMD so you can parse them – though this is not mandatory as you can write code to handle them in Lua without VMD parsing).  Debug code and fix error – could be incorrect VMD also
ACK query response has been inactive for 1 minute. error show Interfaceware – log export ACK query response Iguana Logs no ACK response for 1 minute if this error occurs regularly it should be investigated manage – fix
CDA mapping has been inactive for 1 minute. error show Interfaceware – log export CDA mapping Iguana Logs CDA mapping has been inactive for 1 minute if this error occurs regularly it should be investigated manage – fix
Configuration errors were present:\r\n   * Directory into which error files are moved is invalid. It either does not exist, or the user Iguana is running under does not have sufficient permission to access it.\r\n   * Directory into which processed files are moved is invalid. It either does not exist, or the user Iguana is running under does not have sufficient permission to access it.\r\n   * Directory from which files are read is invalid. It either does not exist, or the user Iguana is running under does not have sufficient permission to access it.\r\nPlease edit the channel configuration to eliminate these errors.\r\n error show Interfaceware – log export Introduction – HL7 to DB – Txt Iguana Logs *** *** Create directory or fix permission issue
Couldn’t parse date ‘19580829000100.0-400’. Required format is YYYY-MM-DD or YYYY-MM-DD HH:MM:SS debug show Interfaceware – manual entry *** Iguana Logs Incorrectly date time format This error is caused by trying to map an incorrectly formatted date time. You can use the fuzzy data parser to fix this. It is very possible that this may be a “data error” as most values are correct – with a few in the wrong format. Correct the data time format (try fuzzy date time parser)
Created sub-directory ‘D:\logsindex’. info show Interfaceware – manual entry *** ServiceErrorLog.txt logs directory not found – created index directory was not found.  This is not a major concern because it will be rebuilt when it is not found.  However, if this is a system that has been up and running a while I would question why it was removed no action needed – you may want to investigate the cause
Created sub-directory ‘D:\logsmeta’. info show Interfaceware – manual entry *** ServiceErrorLog.txt meta directory not found – created meta directory was not found.  This is not a major concern because it will be rebuilt when it is not found.  However, if this is a system that has been up and running a while I would question why it was removed no action needed – you may want to investigate the cause
Email notification message could not be sent.\r\nReason: ERROR: Provided authentication rejected.\r\nResponse was:\r\n535 Login incorrect -ERR support@interfaceware.com password wrong or not a valid user\r\n error show Interfaceware – log export (Iguana Service) Iguana Logs email authentication user/password is wrong In Setting>Email Notification>Change choose the “Email Server Settings” tab under select the “Authentication” checkbox and enter the correct user and password. correct the user/password and confirm it works
Email notification message could not be sent.\r\nReason: ERROR: Received unexpected response code 250 in response to RCPT TO – expected 250\r\nCommand was: RCPT TO: <suppport@interfaceware.com>\r\n error show Interfaceware – log export (Iguana Service) Iguana Logs email connection/delivery issue it appears that there was an SMTP error (though 250 = success) – if it recurs then investigate and fix manage – fix
Email notification message could not be sent.\r\nReason: Failed to read SMTP response – got error code -2 from NTBsocket::read() error show Interfaceware – log export (Iguana Service) Iguana Logs *** *** manage – fix
Error (0)nSQLite error occurred while fetching row.\r\nSQLite: test.sqlite\r\nPrepared SQL statement: DELETE FROM patient\r\n\r\nno such table: patient debug show Interfaceware – log export Test2 Iguana Logs table does not exist trying to use a table that does not exist in the database – this is probably something for a programmer to fix debug
Error (0)nSQLite error occurred while opening file.\r\nSQLite: test.sqlite\r\n\r\nunable to open database file debug show Interfaceware – log export Test2 Iguana Logs cannot read existing database file this means the file exists but cannot be read, probably some other process is locking the file NOTE: it is not a MISSING – if the file did not exist SQLite would just create another debug
Error (1049)nAttempted connection to MySQL database failed.\r\nMySQL Error Message:\r\nUnknown database ‘scheduler’ error show Interfaceware – log export Scheduler Iguana Logs Database does not exist  could be caused by a network error making the database temporarily unavailble. Could occur during setup/install if you forgot to install the database. Need to identify why the DB is unavailable and fix. manage – fix
Error encountered while filtering message: Translator error occurred in module “main”, line 10: attempt to call global ‘Template’ (a nil value) error show Interfaceware – manual entry *** Iguana Logs No main() function Tried to run a channel with no main() function defined. Probably forgot to commit a first milestone for the channel. Solution: create a milestone. If main() is really missing you need to create that and then a milestone. Probably commit 1st milestone (create main 1st if it does not exist)
Error encountered while trying to save configuration file. Attempt to remove ‘C:\Program Files\iNTERFACEWARE\Iguana\IguanaConfiguration.xml’ failed. Permission denied. Please check to see if Iguana is running under a user account that has the permissions required to execute this operation. error show Interfaceware – manual entry *** Iguana System cannot access config file IguanaConfiguration.xml For some reason access was denied to a vital file the IguanaConfiguration.xml.  Most often when we see this it means that something else is locking it up.  I would try to move to another part of the app to see if it is working.  If not then restart service, if still not i would kill all network connections to the server momentarily and then retry.  If it still fails you may have to recover from a backup copy.   need to unlock IguanaConfiguration.xml – try: restarting Iguana, killing all network connections, or restore from backup.
Error occurred at: Friday, December 2nd, 2011 @ 08:59:10 AM\r\nThe log index commit system has failed. Possible reasons:\r\n – The disk has run out of space.\r\n – An external process (such as antivirus or backup software) is locking files in the log system, or has changed the file permissions.\r\n – Some other unknown I/O error occurred, please provide this error to iNTERFACEWARE.\r\n\r\nAdditional Information: \r\nSQLite error occurred while executing SQL statement.\r\nSQLite: logsindex20111202_log_index.db\r\nPrepared SQL statement: BEGIN IMMEDIATE\r\n\r\ndatabase or disk is full error show Interfaceware – log export (Iguana Service) Iguana Logs low disk space – or log files locked low disk space then you need to add or free up some space (you may want to move the logs to a dedicated drive/spidle/LUN on a busy server) – also can be a backup or virus checking program locking the log files (if this is the case you need to investigate and fix, check in the wiki for details) free up disk space – or prevent locking of log files
Error occurred at: Friday, December 2nd, 2011 @ 08:59:10 AM\r\nThe log index commit system has failed. Possible reasons:\r\n – The disk has run out of space.\r\n – An external process (such as antivirus or backup software) is locking files in the log system, or has changed the file permissions.\r\n – Some other unknown I/O error occurred, please provide this error to iNTERFACEWARE.\r\n\r\nAdditional Information: \r\nSQLite error occurred while executing SQL statement.\r\nSQLite: logsindex20111202_log_index.db\r\nPrepared SQL statement: BEGIN IMMEDIATE\r\n\r\ndatabase or disk is full  Stopping all channels. error show Interfaceware – log export (Iguana Service) Iguana Logs low disk space – or log files locked low disk space then you need to add or free up some space (you may want to move the logs to a dedicated drive/spidle/LUN on a busy server) – also can be a backup or virus checking program locking the log files (if this is the case you need to investigate and fix, check in the wiki for details) free up disk space – or prevent locking of log files
Errors occurred while setting up HTTPS channel server SSL context. HTTPS channel server not started.\r\nCertificate file does not exist: ”\r\n error show Interfaceware – log export (Iguana Service) Iguana Logs cannot find certificate file cannot find the cetificate file specified in Settings>Web Server, probably just means there is no cetificate file specified. To specify go to Settings>Web Server and edit the setting selct the “Use HTTPS” checkbox and enter or correct the Certificate file(s). Could mean the settings are referring to the wrong file name (typo), need to change the settings. Also the file could be missing need to find/create/add. fix settings to refer to correct file – or add/create the file
Executing Log Purge for logs before 2011/11/04 (YYYY/MM/DD):\r\n\r\nFiles between 2011/11/04 and 2011/11/05 were not deleted because they are in use: \r\nDate       | In Use By\r\n2011/11/04 | From DB\r\n\r\nNo files were deleted.\r\n\r\n error show Interfaceware – log export (Iguana Service) Iguana Logs logs locked – cannot be purged this is probably caused by a backup or a virus checker running at the same time as Iguana is set to purge the logs. Either reschedule the log purge time – or rescedule the virus checker or backup process. reschedule log purge or backup/antivirus
Failed login attempt by user “UserOnly” from IP 127.0.0.1:\r\nInvalid password.\r\n error show Interfaceware – log export (Iguana Service) Iguana Logs login failure could be an attempt to hack server – if you see multiple attempts on one use you should check security and ensure that the password is VERY secure (particularly for an admin user) check security if multiple login failures for one user
Failed to connect to localhost:5145 (retry 60 of 60).\r\nA connection could not be established.  Ensure that there is an LLP server listening at the target host and port.\r\nReached specified maximum number of reconnection attempts. This LLP Client component will stop. error show Interfaceware – log export Sender (deleted) Iguana Logs LLP listener not running the LLP listener for this server is not running – could be another channel – or a different app – depends on circumstances – need to investigate and fix start the LLP Listener
Failed to connect to localhost:6000 (retry 10 of 10). A connection could not be established.  Ensure that there is an LLP server listening at the target host and port. Reached specified maximum number of reconnection attempts. This LLP Client component will stop.  error show Interfaceware – manual entry *** Iguana Logs could not connect to LLP listener Failed to connect to outbound LLP connection.  You can try to restart the channel.  If it continues then you will have to contact the receiving side to figure out why they are not open and listening for a message to be sent restart channel – or contact receiver to see if they have issues
Failed to connect to localhost:6000 (retry 9 of 60). A connection could not be established.  Ensure that there is an LLP server listening at the target host and port. Will attempt to reconnect in 10000 milliseconds. warning show Interfaceware – manual entry *** Iguana Logs could not connect to LLP listener where localhost and port number are will be whatever you are trying to connect to.  This is letting you know that it could not connect to the Outbound IP and Port.  This is not a major concern sometimes connections drop and it will continue to retry.  If it does not connect it will Error out. no action needed – you may want to investigate the cause
Iguana encountered an error when it was last run. nn                  Because the error may have been caused by starting channels, channels configured to automatically start have not been started. error show Interfaceware – log export (Iguana Service) Iguana Logs Iguana service crashed – channels not started Because it could have been a channel that caused the crash channels are not automatically started when Iguana resumed – need to investigate and restart channels manaually investigate crash – restart channels manually
Iguana service has started. info show Interfaceware – manual entry *** ServiceErrorLog.txt Iguana service started This just means that the service has started none
Iguana spent 100 milliseconds retrying its file I/O operations, possibly reducing overall performance.\r\nThis is usually caused by antivirus and/or backup software running on the same drive as Iguana’s log files.\r\nConsider changing the scanning software to omit the log directory. error show Interfaceware – log export (Iguana Service) Iguana Logs manage – fix
Main iguana service has shut down. info show Interfaceware – manual entry *** ServiceErrorLog.txt Iguana service stopped Iguana Service was stopped none
No main function is defined. This is required as the main entry point for the script. Please edit and save the script to correct the error. error show Interfaceware – log export Introduction – HL7 to DB – LLP Iguana Logs probably no milestone this probably means there is no milestone for the channel – or you are trying to run a milestone that does not have a main() function – fix the code issue and create a milestone create milestone
Plugin Communication Server could not be started because the port is already in use. error show Interfaceware – log export (Iguana Service) Iguana Logs Default plugin port already used The default plugin port is being used by something else – if you have multiple Iguana installations on the same machine then it is probably another Iguana Server – usually you would change this server to use a different port – but you could change the other application to use a different port… Change plugin port in Iguana Program Settings
Plugin connection attempt failed.\r\nThe connection to the plugin was reset abruptly, likely due to abnormal plugin termination. error show Interfaceware – log export (Iguana Service) Iguana Logs *** *** manage – fix
Project with guid 5568… has no milestones. error show Interfaceware – manual entry *** Iguana Logs no milestone This means that the system cannot find the saved milestone for Iguana. This could mean that either the folder with that guid in the “C:\Program Files\interfaceware\Iguana\edit\admin”  or that the vcs_repo.sqlite [located in “C:\Program Files\interfaceware\iguana” from is missing or corrupted.  You could try to restore from most recent backup. It is also possible no milestone has been created yet. Create a first milestone, or revert to previous valid milestone, or recover vcs_repo.sqlite from backup
Project with guid 7F9D97325CFC0E36CF86A122F27E368C has no milestones. debug show Interfaceware – log export Database In (deleted) Iguana Logs project has no milestone project has no milestone(s) need to create at least one before you can run the channel create milestone
Queue index file ‘D:\logs\indexqueue_index.db’ does not exist, and will be rebuilt. info show Interfaceware – manual entry *** ServiceErrorLog.txt log index not valid – rebuilt Index was not built for all of the logs so it will create the index.  It will have to do this for new logs and logs that may have been transferred over for viewing purposes. no action needed – you may want to investigate the cause
Some warnings detected while loading configuration\r\nWarning:  “use_https” is an unknown attribute.\r\nWarning:  “serve_files” is an unknown attribute.\r\nWarning:  “file_serve_directory” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\nWarning:  “ack_style” is an unknown attribute.\r\n warning show Interfaceware – log export (Iguana Service) Iguana Logs *** *** manage – fix
Stopped log heart beat thread.  Last action will be to flush this log. info show Interfaceware – manual entry *** Iguana Logs channel stopping This occurs when the service is being stopped and it is informing you that the channel is just being stopped none
The file ‘logs20111127.log’ does not appear to be a valid queue file, and has been renamed to ‘logs20111127.log.invalid’. error show Interfaceware – log export (Iguana Service) Iguana Logs corrupt log file renamed Basically this is caused by a disk write error and the log file was not written correctly = corrupted. This could happen after Iguana crashed for some reason, or there was a disk write failure of some kind. Usually no action is required, though it does mean that any logged messages in this file are unavailable. If log messages are CRITICAL it may be possible to edit the file to recover messages. usually no action
There is not a function main defined in the script.  This is required as the main entry point. error show Interfaceware – manual entry *** Iguana Logs No main() function Tried to run a channel with no main() function defined. Probably forgot to commit a first milestone for the channel. Solution: create a milestone. If main() is really missing you need to create that and then a milestone. Probably commit 1st milestone (create main 1st if it does not exist)
Translator error occurred in module “dbc”, line 10:nTimed out – script took longer than 20 seconds to stop. error show Interfaceware – log export Test2 Iguana Logs probably a database timeout the dbc uses protected call to run database queries (Lua pcall), this is an error returned by pcall. If this error recurs you will need to refr it to a programmer if tis error recurs it will need to be debugged
Translator error occurred in module “main”, line 12:nSQLite error occurred while preparing SQL statement.\r\nSQLite: sqlite_db\r\nPrepared SQL statement: INSERT INTO patient(LastName) VALUES(“Smith”,”ZZZ”)\r\n\r\n2 values for 1 columns debug show Interfaceware – log export Database in Iguana Logs Lua code error refer to programmer debug
Translator error occurred in module “main”, line 147:nCould not resolve host: mail.interfaceware.com; No data record of requested type error show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs mail configuration issue it seems the mail host could not be identified. Could be network connectivity, or host may not exist (e.g., typo). Check that the “Outgoing Mail Server” in Settings>Email Notification is set correctly. manage – fix
Translator error occurred in module “main”, line 147:nSSL connection timeout error show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs *** *** manage – fix
Translator error occurred in module “main”, line 153:nserver response timeout debug show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs code error refer to programmer debug
Translator error occurred in module “main”, line 26:nSQLite error occurred while preparing SQL statement.\r\nSQLite: test.sqlite\r\nPrepared SQL statement: DELETE FROM patient\r\n\r\nno such table: patient debug show Interfaceware – log export Test2 Iguana Logs table does not exist trying to use a table that does not exist in the database – this is probably something for a programmer to fix debug
Translator error occurred in module “main”, line 6: debug show Interfaceware – manual entry *** Iguana Logs error in main() at line nn This error is produced due to some new data being sent that the system could not handle.  It is informing you of the exact location.  You can view an audit trail for this error to see what message was causing the issue.  Usually this will need to be corrected by the original integration analyst that built the channel debug
Translator error occurred in module “main”, line 78:nattempt to index local ‘MSH’ (a nil value) debug show Interfaceware – log export Exercise – Web Result (deleted) Iguana Logs no MSH segment probably a coding error (forgot to assign the MSH segment to a variable?) – or a broken HL7 message (with no MSH segment?) – or you might be trying to parse a message that is not HL7 at all… fix Lua code
Unable to connect warning show Interfaceware – manual entry *** Iguana System Iguana uanavailable – either not running or no network connection You may see this if you are monitoring more than one instance of iguana.  It would be listed in the Server section at the bottom of the dashboard.  This means that this machine cannot connect through the network to the other Iguana instance.  Either that instance is down, the service is down or the network is disconnected restart remote server, or check network connection
Unexpected code from server: 503 response: The remote Iguana HTTPS channel ‘<channel name>’ is not running. error show Interfaceware – manual entry *** Iguana Logs remote channel not running Pretty self explanatory the HTTPS channel you are trying to access is not running – needs to be started on the remote server start channel on remote Iguana server

Part two: Coding Errors

The second part contains a sample of (the potentially infinite number of) coding errors.

Message Type Status Source LogSource Location Description Comment Action
‘)’ expected near ‘=’ Lua debug show Interfaceware – manual entry *** Iguana Logs Missing last ‘)’ bracket in function call – often means you used ‘()’ when you should use ‘{}’ This is a common error (for me anway 🙂 when you are calling a function that expects a single table {} parameter – like myfunc({a=’a’,b=’b’}) if you do myfunc(a=’a’,b=’b’) you get the error. NOTE: myfunc{a=’a’,b=’b’} works as shorthand for ‘({})’ with the ‘()’ omitted. Debug code and fix error
…D3AD855E7482D16F13CAC750CB2F_558sharedcheckmsg.lua:235: attempt to perform arithmetic on local ‘Cnt’ (a nil value) Lua debug show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs invalid arithmetic operation probably did not initialize the variable fix Lua code
Error encountered while filtering message:\r\nTranslator error occurred in module “main”, line 23:nCopy of HL7 message does not match the original Lua debug show Interfaceware – log export Sender (deleted) Iguana Logs Lua code error this is an error raised in Lua code – refer to a programmer. This is probably something new/unexpected in the  message data that needs some added rule/processing fix Lua code
This is a leaf node without children. Lua debug show Interfaceware – manual entry *** Iguana Logs Attempt to access a child of a leaf node (= no children) – often :S() function not defined Basically any action that tries to access children of a leaf node will cause this error. Frequently this is caused because the :S() function is not define – just add require ‘node’ to fix this. Another example would be trying to to access PID[1][1] when it does not exist (PID[1] is a leaf node). Debug code and fix error
Translator error occurred in module “main”, line 112:nattempt to compare nil with string Lua debug show Interfaceware – log export Exercise – Web Result (deleted) Iguana Logs Lua code error refer to programmer fix Lua code
Translator error occurred in module “main”, line 123:nattempt to concatenate field ‘?’ (a nil value) Lua debug show Interfaceware – log export _Exercise – Web Result (deleted) Iguana Logs Lua code error refer to programmer fix Lua code
Translator error occurred in module “main”, line 147:nattempt to call method ‘S’ (a nil value) Lua debug show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs :S() function not defined probably just need to include the “node” module (require ‘node’) – unless you prefer to define the :S() function somewhere else define :S() function
Translator error occurred in module “main”, line 147:nattempt to concatenate local ‘smtp’ (a table value) Lua debug show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs Lua code error refer to programmer fix Lua code
Translator error occurred in module “main”, line 29:nbad argument #1 to ‘sub’ (number expected, got nil) Lua debug show Interfaceware – log export _Exercise – Web Result (deleted) Iguana Logs Lua code error refer to programmer fix Lua code
Translator error occurred in module “main”, line 328:nattempt to perform arithmetic on a nil value Lua debug show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs invalid arithmetic operation probably just forgot to assign a value to a variable – cannot do arithmetic on a nil value – need to assign a value fix Lua code
Translator error occurred in module “main”, line 432:nattempt to compare two nil values Lua debug show Interfaceware – log export _MarkCertAssignment (deleted) Iguana Logs invalid arithmetic operation probably just forgot to assign value to a variables – cannot do arithmetic on a nil value – need to assign values fix Lua code
attempt to call method ‘<function name>’ (a nil value) Lua debug show Interfaceware – manual entry *** Iguana Logs function not defined Code is trying to call a function that has not been defined. Often this is a missing library function – so just add the library to the project and the require ‘<module name>’ to the code. define function – often this is a missing require ‘<module name>’
attempt to index global ‘<variable name>’ (a nil value) Lua debug show Interfaceware – manual entry *** Iguana Logs trying to index a variable that is not a table This often happens when you change (refactor) code and forget to change a variable name. Just check that code and fix the issue. Debug code and fix error
end’ expected (to close ‘function’ at line <line no> near ‘<eof>’ Lua debug show Interfaceware – manual entry *** Iguana Logs Missing last ‘)’ bracket in last function definition (near <eof> = end of file = last function) Fairly obvious you forgot to add the ‘)’ to close off the last function… Add the ‘)’ to close the function

Leave A Comment?