Type search words and press enter
Seamless e-invoicing is now at your fingertips. Check out our self-help videos.
https://help.tallysolutions.com/docs/td9rel54/td9/troubleshooting/td9_troubleshooting.htm

Tally.Developer 9 - Troubleshooting

This topic lists common error or warning messages and their corresponding solutions.

Errors

Error Code

Error Message

Possible Reason(s) for Failure

Possible Solution(s)

0001

Could not find the file '%s'

This error occurs when an included TDL file is not found or doesn't exist.

Include the correct file with correct folder path. To include files, use the feature Include Existing File or Include New File available on Tally.Developer 9 window right click.

0003

File '%s' is loaded already.

This error occurs when a TDL file is included more than once as a part of another TDL file.

Remove the repeated inclusions of the file.

0004

The description type is empty.

This error occurs when a definition is described without a definition type.

Add the required description type.

0005

The description name is empty.

This error occurs when a definition is defined without a definition name.

Add the required definition name.

0006

The description type is misspelt or incorrect.

This error occurs when a definition is described with incorrect definition type.

Correct the definition type.

0007

The description name contains invalid characters.

This error occurs when a definition is described with a name containing invalid characters.

Definition names must abide by the rules.

0008

Could not find the original description of %s: %s.

This error occurs when definition is modified with # but the original description of it, doesn't exist.

Ensure that the original description exists.

0009

%s: %s is a duplicate description already defined in %s(%d) .

This error occurs when a defined description is already exists in the code.

Rename the duplicate description or remove it to avoid the error.

0010

Could not modify the fixed description %s : %s.

This error occurs when the developer is trying to modify an internal description.

Use the internal descriptions  in your customisations, do not try to modify.

0011

The system description type '%s' is invalid.

This error occurs when an invalid system description type is specified.

Correct the description type to a valid description type.

0012

Could not understand the attribute '%s'. Attribute name is empty.

This error occurs when the attribute name is empty in the definition.

Add the required attribute name.

0013

Could not understand the attribute '%s' for a modifier.

This error occurs when an incorrect attribute is used along with modifiers like Add, Delete, replace, in a definition.

Check for spelling mistakes and use the correct attribute.

0014

The attribute '%s' is not valid for the description '%s'.

This error occurs when an invalid attribute is used in a definition.

Check for spelling mistakes and use the correct attribute.

0015

The description type '%s' is not valid for the dynamic modifier Local.

This error occurs when the description type specified in local modifier is not a valid one.

Check for spelling mistakes and use the right description type for the right definition.

0016

The description name is mandatory for the dynamic modifier Local.

This error occurs when no description name is given in local modifier.

Ensure that all statements used in the code are completed.

0017

Empty or invalid attribute for the dynamic modifier Local.

This error occurs when a local definition is incomplete without specifying any attribute to be modified/added/deleted.

Ensure that all statements are completed.

0018

Function: %s - Mandatory parameter %d is missing.

This error occurs when a function is called without passing its mandatory parameter.

Ensure that mandatory parameters are passed in the function call, or set a default value for the parameter to avoid such errors.

0019

The attribute '%s' is not valid for the description '%s' in a dynamic modifier Local.

This error occurs when the attribute specified for a local modifier is not valid for the description.

In the Local modifier,use the attributes to be changed as the attributes of the description type specified.

0021

Cannot mark a system description as optional(!).

This error occurs when a system description is marked as optional.

Do not mark the system descriptions as optional.

0023

The attribute value for '%s' is empty within the modifier.

This error occurs when the attribute value for a modifier is empty.

Ensure that the modifiers have appropriate attribute values.

0025

Could not use the description %s: %s referred from %s in the attribute Use.

This error occurs when a description is used with 'Use' attribute in another, and it does not exist.

Ensure that the description used with the attribute Use is already available. Check for spelling mistakes, if any.

0027

The attribute definition started without a valid description.

This error occurs when an attribute or line of code does not fall within a description.

Correct the code with proper definition or check if certain characters are written by mistake.

0028

Unable to load the file '%s'. Invalid file format .

This error occurs when a binary file is included in the TDL file.

Ensure that the file for inclusion is a .txt file or .tdl file.

0029

Could not find the description %s %s - '%s' referred from %s %s - '%s' in the attribute - %s.

This error occurs when a description is used referred in another does not exist.

Ensure that any referred description is already available. Check for spelling mistakes, if any.

0030

Duplicate label %s in procedural block.

This error occurs when a duplicate labels are present in a function.

Use labels with a margin of 5 points, like 000, 005, 010, so that any intermediate labels when introduced can have a label with number in between.

0031

The value of system %s '%s' is empty.

This error occurs when value for the system description is not given.

Ensure the system definitions are complete.

0033

No action specified for system event.

This error occurs when the required action is not specified for a system event.

Specify the required action for the System Event.

0034

Attribute '%s' is not allowed within the modifier '%s'.

This error occurs when an invalid attribute is used inside a modifier (Add/Delete/Replace).

Use the valid attribute in the modifier.

0035

The event '%s' is invalid or not valid at %s scope.

This error occurs when an incorrect event specified at definition level or the event is not a valid event for the scope.

Ensure that the spelling for the event is correct and the event is a valid event.

0036

Menu item '%s' does not have an action parameter.

This error occurs when action parameter is not specified for a menu item.

Add the appropriate action parameter.

0037

Location keyword '%s' is not supported for the modifier '%s'.

This error occurs when location keywords before, after, at beginning, at end are used along with modifier Replace or Delete.

Do not use location keywords with modifiers Replace and Delete .

0041

Invalid TDL expression - %s.

This error occurs when a given TDL expression is not understandable or invalid.

Write a valid TDL expression.

0042

Action '%s' - mandatory parameter %d is missing.

This error occurs when a mandatory parameter for the action is missing.

Give mandatory parameters when necessary.

0045

Description %s: %s is not available in the target version.

This error occurs when a description used in customisation is not available in the target version, while performing version compatibility check.

Add the required description to the customisation from the base release default code. Rename the description and use it.

0046

System description %s: %s is not available in the target version.

This error occurs when a system description used in customisation is not available in the target version, while performing version compatibility check.

Add the required description to the customisation from the base release default code. Rename the description and use it.

0047

Invalid keyword '%s'. The type of keyword expected is '%s'.

This error occurs when an invalid keyword is used for an attribute.

Provide the appropriate keyword.

Warnings

Code

Message

Possible Reason(s) for Warning

Possible Solution(s)

0005

The value of the attribute '%s' is empty in the modifier Local.

This warning occurs when an attribute value is not given in a local modifier.

Provide an appropriate value for the attribute.

0010

The value of the attribute '%s' is empty.

This warning occurs when attribute value is not specified where the value specification is not mandatory.

Provide the sub-attributes or remove the line of code, if not required

0012

Repeat flag is not supported for the UDF '%s'.

This warning occurs when Repeat flag which was earlier supported is used during UDF creation.

Remove the repeat flag.

0013

The mandatory second value of '%s' is not given.

This warning occurs when second sub-attribute of an attribute is mandatory and is not specified.

Set the variable to a value.

0014

The mandatory third value of '%s' is not given.

This warning occurs when third sub- attribute of an attribute is mandatory and is not specified.

Provide the third attribute.

0015

Ignored Modifier(#), Reinitializer(*), and Const(@) that are not allowed for system description type '%s'.

This warning occurs when Modifier(#), Reinitializer(*), or Const (@) is specified in a system definition.

Remove the reinitializer.

0016

Duplicate description name %s %s - %s is overridden. \n%s(%d) : was the previous declaration.

This warning occurs when a system description is overridden due to duplicate declaration.

Rename the event if same name was used by mistake

or

Remove the declaration if you need to execute the previous declaration.

0017

Original description is not found for %s: %s(Reinitialization allowed).

This warning occurs when a definition is re-initialized without having an original description.

Remove the re-initialization, if the definition is the original description.

0020

In the function '%s', the mandatory parameter %s is specified after optional parameter.

This warning appears when a mandatory parameter is mentioned in a function definition after a optional parameter

Make sure optional parameter is always mentioned at the end of the parameter list

0021

The function '%s' does not take any parameter.

This warning occurs when a function with no parameters is called by passing parameters.

Make sure to pass parameter only when parameter is required by the function. Either remove the parameter passed or specify 'parameter' inside the function as applicable.

0022

The UDF number %ld used for '%s' is not in the allowed range.

This warning occurs when the number specified for the UDF is not within the range allowed.

Ensure the UDF is defined using the allowed range.

0023

Unused description %s %s - %s.

This warning occurs when the definition is not used in the code.

Remove the code if it is not going to be used as part of code clean up. If the definition is used dynamically in the project specify the same with the help of preprocessor directive InUse.

0026

The description %s: %s is modified in the target version.

This warning occurs when the default description used in the customisation is modified in the target version, while performing version compatibility check.

Check the modification done in the definitions and see how it affects the functionality/execution of the code.

0027

The default description of type %s is modified in the target version. It may affect the description %s: %s.

This warning occurs when the default description type used in the customisation is modified in the target version, while performing version compatibility check.

Check the modification done in the definitions and see how it affects the functionality/execution of the code.

0028

The system description %s: %s is modified in the target version.

This warning occurs when the system description used in the customisation is modified in the target version, while performing version compatibility check .

Check the modification done in the definitions and see how it affects the functionality/execution of the code.