Error Messages

This section contains a detailed description of each error message (including cause and action). The errors are divided into various groups.

An error message consists of an error code (in square brackets - []) that is shown at the beginning of the error message and of the message's text below the error code. The error code is a combination of letters and numbers. The letters represent the error group, the numbers serve to identify the messages within an error group. The error messages are listed in alphabetical order according to groups and in ascending order of their number inside each group. The numbering is not necessarily continuous.

To resolve errors close the window containing the error message by clicking on the OK button or by pressing the "Enter" key and then performing the actions described under "Action".

aactdbd

[aactdbd-01]

	Description
Message:	Error when trying to read the workstation configuration:The configuration key is invalid!
Cause:	Maybe the configuration key or the file containing it is defect.
Action:	Correct the possible causes and try it again.

[aactdbd-02]

	Description
Message:	Error when generating the database activation key!
Cause:	Maybe the file where the activation key should be written in is write-protected or it was deleted.
Action:	Correct the possible causes and try it again.

[aactdbd-03]

	Description
Message:	Error when generating the log file!
Cause:	The log file couldn't be generated maybe the data storage medium specified is either write-protected or full.
Action:	Remove the write-protection from the data storage medium or create some new space or assign a valid file name and restart the generation.

aacquiui

[aacquiui-02]

Message:	The acquisition module HOMER could not be started. Maybe HOMER has not been installed correctly.
Cause:	The file "acqui.dat" in the ADOxxinstallation directory does not contain a valid path for HOMER or HOMER was not installed in due form respectively.
Action:	Make sure that HOMER is installed properly (e.g.try to start HOMER via the "Start" menu of the operating system). If HOMER starts without error that way, the acquisition module is installed properly (If this produces an error too, the installation procedure was faulty and has to be repeated). Correct the call path for "homer.exe" in the file "acqui.dat". The path defined in "acqui.dat" is a path relative to the HOMER program file "homer.exe", starting from the HOMER program directory. The path of the HOMER program directory is defined in the system variable HOMERDIR, which is set automatically during the HOMER installation. If the system variable HOMERDIR is not found, ADOxx tries to start the path defined in "acqui.dat" relative to the current working directory (that is the ADOxx installation directory).

aactana

[aactana-01]

Message:	Fatal error during activity analysis! Delete the simulation cache and restart the simulation.
Cause:	A fatal error has occurred from which the system cannot automatically recover.
Action:	Try to run the simulation again. If the same error re-occurs, then export your models to an ADL file and contact your ADOxx consultant.

aadlui

[aadlui-02]

Message:	The import is not possible as currently a simulation resp. analytic evaluation is performed!
Cause:	A model which should be overwritten by the import is used by a simulation or an analytic evaluation at the moment.
Action:	Close all windows of the simulation or analytical evaluation and try the import again.

aadma

[aadma-02]

	Description
Message:	The initialisation of ADOxx failed. Login cancelled.
Cause:	Possibly, the connection with the ADOxx database server was aborted.
Action:	Repeat the login process. Should the error re-occur, please contact your database or system administrator.

[aadma-04]

	Description
Message:	"<"%name">" (<(%type)>) could not be deleted, because it is currently locked by user < %user!> !
Cause:	The model listed is currently being edited by the ADOxx user specified and thus cannot be deleted.
Action:	The user specified above should stop the editing of the model and close this model so that it can then be deleted. (You can also send an appropriate messsage to the user via ADOxx-Mail (Menu "Extras", menu item "Messages").)

[aadma-05]

	Description
Message	"<"%name">" (<(%type)>) has the access state "read access" and cannot be deleted!
Cause:	The model listed is loaded as read-only and thus can neither be changed or deleted.
Action:	Close the model specified and then attempt to delete it again.

[aadma-06]

	Description
Message:	An error occurred when deleting in the database!
Cause:	It is possible that your connection to the database server has been aborted or the database server is overloaded.
Action:	Repeat the deletion. Should the error re-occur, either try again later or else contact your database or system administrator.

[aadma-07]

	Description
Message:	The library "<library name>" could not be loaded! Quit ADOxx.
Cause:	The model and model group list belonging to the library could not be loaded .
Action:	Quit ADOxx and the restart ADOxx. If the error occurs again, contact your ADOxx administrator.

[aadma-08]

	Description
Message:	The configuration file "<file name>" could not be written. There are probably no access rights for the write access to the file. (The configuration change has only been carried out in the database and thus is not complete.) Contact your system administrator and then carry out the configuration change again.
Cause:	When trying to change the configuration, the specified configuration file could not be opened.
Action:	Verifiy whether you possess enough write access rights in the target directory and if enough hard disk memory is available. If the file already exists, check whether the file is write protected or already opened.

[aadma-09]

	Description
Message:	The file "<file name>" specified after the parameter -e cannot be opened!
Cause:	The file name for the parameter -e to execute an AdoScript is not valid.
Action:	Please check the path and name of the file and enter a valid file name.

[aadma-10]

	Description
Message:	ADOxx can't be used with the desired language <language> since the licence number is not configured for this language. The login process will be aborted.
Cause:	The access rights defined in the licence number do not allow a login in the selected language.
Action:	Contact your ADOxx administrator.

aalkwins

[aalkwins-01]

	Description
Message:	Invalid file name.
Cause:	An invalid file name, the name of a write-protected file or a directory that does not exist has been specified for the import file.
Action:	Enter a valid name of a file that is not write-protected in an existing directory.

[aalkwins-02]

	Description
Message:	Specify a file name.
Cause:	You have not specified a file name for the file to be exported.
Action:	Enter the file name of the file to be exported.

[aalkwins-08]

	Description
Message:	The models contained in the application model "<model name>" have been deleted. Therefore this application model is no longer valid.
Cause:	The application model you have specified for export no longer contains any models.
Action:	Specify a different application model which contains the models you require.

[aalkwins-10]

	Description
Message:	Username must be at least three characters!
Cause:	When renaming a username during UDL import, a name of less than three characters was specified.
Action:	Please enter a new username which is at least three characters long.

[aalkwins-11]

	Description
Message:	An unknown model type has been used!
Cause:	For the export using AdoScript an unknown model type was provided. The export of models of this type is not possible.
Action:	Use the name of an existing model type in the AdoScript.

[aalkwins-12]

	Description
Message:	Specify a file name for the protocol file.
Cause:	You have not specified a file name for the protocol file to be generated.
Action:	Enter the file name of the protocol file to be generated.

aanabrw

[aanabrw-01]

Message:	Error during the copy: All values could not be pasted!
Cause:	An error has occurred when pasting in the ADOxx browser. This is why the pasting process has been cancelled.
Action:	Verify whether the area to be pasted is not to large and whether the attribute types go together. Also check whether it is allowed to be pasted in the selected area.

[aanabrw-02]

Message:	Error during the copy: No value could be pasted!
Cause:	An error has occurred when pasting in the ADOxx browser. This is why the pasting process has been cancelled.
Action:	Verify whether the area to be pasted is not to large and whether the attribute types go together. Also check whether it is allowed to be pasted in the selected area.

[aanabrw-03]

Message:	The action could not be performed, as the concerned model was deleted in the meantime!Refresh the query result by pressing the refresh icon.
Cause:	You tried to perform an action for a previously deleted model.
Action:	Refresh your query result before you continue.

[aanabrw-04]

Message:	The action could not be performed, as the concerned object was deleted in the meantime!Refresh the query result by pressing the refresh icon.
Cause:	You tried to perform an action for a previously deleted object.
Action:	Refresh your query result before you continue.

aanactrl

[aanactrl-02]

Message:	The AQL expression is syntactically not correct!
Cause:	The AQL expression you have entered does not correspond with the defined AQL syntax.
Action:	Enter a syntactically correct AQL expression.

aanadlg

[aanadlg-04]

	Description
Message:	The models to be analysed must be defined on the same application library.
Cause:	The models selected for analysis are based on different application libraries.
Action:	Select a number of models to be analysed which are based on the same application library.

[aanadlg-05]

	Description
Message:	An error has occurred during the storage!
Cause:	An error has occurred during the storage of the model information of the models analysed. The data medium is probably write-protected.
Action:	Check the access state of the target storage medium.

[aanadlg-06]

	Description
Message:	The entered value "<value>" is not valid! <Format> is expected.
Cause:	While creating a standardised query, you have entered a value which is not compatible with the selected attribute.
Action:	Enter a value compatible with the entry type.

aanaeval

[aanaeval-01]

Message:	The input parameters for the analytic evaluation are corrupt. The evaluation cannot continue.
Cause:	There is a problem with the sim mapping specifications.
Action:	Contact your ADOxx administrator. The sim mapping specified within the application library contains errors. This can be corrected within the library management component of the ADOxx Development Toolkit.

[aanaeval-02]

Message:	Enter valid values in all fields of the group "Filter".
Cause:	An invalid value exists in at least one field of the group "Filter".
Action:	Enter a valid value or else deactivate the group "Filter".

[aanaeval-03]

Message:	The given filter doesn't apply to any one object.Change the "Filter" settings.
Cause:	The required action cannot be carried out as no object (Activity) can be found to match the filter settings.
Action:	Enter a valid value or else deactivate the group "Filter".

[aanaeval-04]

Message:	Either no simresult mapping is defined or the mapping defined is invalid. Adopting the evaluation results is therefore not possible.
Cause:	Simresult mapping is either invalid or not defined.
Action:	Contact your ADOxx administrator. The "simresult mapping" must be corrected in the Development Toolkit.

[aanaeval-05]

Message:	There are no input parameter defined. The analytic evaluation cannot be carried out. Define an input parameter configuration in ADOxxDevelopment Toolkit or contact your ADOxx administrator.
Cause:	The Sim-Mapping is deficient or not defined.
Action:	Contact your ADOxx administrator. The Sim-Mapping defined in the ADOxx Development Toolkit must be corrected.

[aanaeval-06]

Message:	The model contains no object, for which results can be calculated.
Cause:	The analytic evaluation has been carried out with a model which contains no object of the class Activity.
Action:	Carry out the analytic evaluation with a model which contains at least one object of the class Activity.

[aanaeval-07]

Message:	Some of the models to be evaluated are loaded with a write protection. The automatic transfer of the evaluation results to the models would lead to inconsistencies because of the mix of results and therefore is not possible. The evaluation will be cancelled.
Cause:	The analytic evaluation has been started via an AdoScript. Then the option of the automatic storage of the evaluation results to the models has been activated.(Note: The option has been possibly activated automatically.) When this option is activated, it must be possible to load all the models to be evaluated (main or submodels) with write access. If this is not the case, the evaluation cannot be continued.
Action:	Make sure that all models to be evaluated can be loaded with write access. For instance, you can manually load the models with write access before starting the evaluation.

aanaud

[aanaud-01]

	Description
Message:	Error in application library.
Cause:	The query definitions in your application library contain errors.
Action:	Contact your ADOxx administrator or your ADOxx consultant.

[aanaud-03]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Unknown model type ("<model type name>")!
Cause:	An unknown model type has been used in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-04]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Invalid context!
Cause:	A key word has been used in a wrong context in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-05]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Unknown key word ("<Name>")!
Cause:	An unknown key word has been used in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-06]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Invalid menu item!
Cause:	The menu item is missing in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-07]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Invalid query!
Cause:	The query text is missing in the query in the above-mentioned library attribute .
Action:	Contact your ADOxx administrator.

[aanaud-08]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Invalid AQL expression!
Cause:	A syntactical invalid AQL expression is used in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-09]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Unknown class ("<class name>") in the <context>!
Cause:	An unknown class is used in the query in the above-mentioned library attribute. The context can be the input fields or the result attributes.
Action:	Contact your ADOxx administrator.

[aanaud-10]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Unknown attribute ("<attribute name>") in the <context>!
Cause:	An unknown attribute is used in the query in the above-mentioned library attribute. The context can be the input fields or the result attributes.
Action:	Contact your ADOxx administrator.

[aanaud-11]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Key word missing("<Name>")!
Cause:	The named key word is missing in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-12]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Context missing!
Cause:	A required context is missing in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-13]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Input field empty!
Cause:	The input elements are missing in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-14]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: AQL expressions empty!
Cause:	The AQL expressions are missing in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-15]

	Description
Message:	The entered value "<Value>" is invalid! Expected is <Format>.
Cause:	While carrying out a predefined query, you have entered a value, which does not match to the defined input type.
Action:	Enter a value which suits the input type.

[aanaud-16]

	Description
Message:	Error in library attribute "<attribute name>": <Number>. query: Result attribute empty!
Cause:	A plan without result attributes has been defined in the query in the above-mentioned library attribute.
Action:	Contact your ADOxx administrator.

[aanaud-17]

	Description
Message:	Error in library attribute "<attribute name>": The length of the attribute value exceeds the maximum allowed length of 32.000 characters!
Cause:	The definition for the mentioned query attribute exceeds 32.000 characters and therefore can not be saved.
Action:	Reduce the attribute value by deleting not used parts of the text.

aap

[aap-01]

	Description
Message:	The attribute possesses no facet of the type "<Type name>".
Cause:	The attribute possesses no facet with the names "AttributeProfileRefDomain" and so cannot be used.
Action:	Contact your ADOxx administrator.

[aap-02]

	Description
Message:	The expression is faulty: "<LEO error message>"
Cause:	The value of the facet "AttributeProfileRefDomain" is faulty. The LEO expression entered contains a syntactical error. Note the appropriate [aleo] error message.
Action:	Rectify the value of the facet "AttributeProfileRefDomain" and take into account the specified [aleo] error message or contact your ADOxx administrator.

[aap-03]

	Description
Message:	The LEO expression is empty.
Cause:	The facet "AttributeProfileRefDomain" is empty.
Action:	Rectify the value of the facet "AttributeProfileRefDomain" or contact your ADOxx administrator.

[aap-04]

	Description
Message:	The key word "APREF" is missing.
Cause:	The LEO expression in the facet "AttributeProfileRefDomain" does not contain the required key word "APREF".
Action:	Correct the value of the facet "AttributeProfileRefDomain" by adding the key word "APREF" or contact your ADOxx administrator.

[aap-05]

	Description
Message:	The parameter "c" of the key word "APREF" is missing.
Cause:	The parameter "c" of the key word "APREF" is required but has not been found.
Action:	Rectify the value of the facet "AttributeProfileRefDomain" by adding the parameter "c" to the key word "APREF" or contact your ADOxx administrator.

[aap-06]

	Description
Message:	The parameter "c" of the key word "APREF" contains an unknown class name.
Cause:	The class entered in the parameter "c" does not exist.
Action:	Rectify the value of the facet "AttributeProfileRefDomain" by adding a valid class name or contact your ADOxx administrator.

[aap-07]

	Description
Message:	The specified class in the parameter "c" of the key word "APREF" is not an attribute profile class.
Cause:	The specified class in the parameter "c" is not the name of an attribute profile class but the name of another ADOxx class.
Action:	Rectify the value of the facet "AttributeProfileRefDomain" by inserting a valid attribute profile class name or contact your ADOxx administrator.

[aap-08]

	Description
Message:	The specified class in the parameter "c" of the key word "APREF" is not instanceable.
Cause:	The class specified in the parameter "c" may be an attribute profile class, but it has been defined as "abstract" and so cannot be instanced.
Action:	Rectify the value of the facet "AttributeProfileRefDomain" by inserting a valid attribute profile class name or set the referenced class on "not abstract" or contact your ADOxx administrator.

[aap-09]

	Description
Message:	The LEO expression contains too many key words.
Cause:	The facet "AttributeProfileRefDomain" can only reference one attribute profile class.
Action:	Rectify the value of the facet "AttributeProfileRefDomain" by referencing only one attribute profile class or contact your ADOxx administrator.

[aap-10]

	Description
Message:	The LEO expression can contain a maximum of one reference.
Cause:	An attribute value refers to more than one attribute profile.
Action:	Change the attribute value by referencing only one attribute profile or contact your ADOxx administrator.

[aap-11]

	Description
Message:	The key word "REF" is missing.
Cause:	The attribute value is faulty because the key word "REF" is missing.
Action:	Change the attribute value by inserting the key word "REF" or contact your ADOxx administrator.

[aap-12]

	Description
Message:	The parameter "i" of the key word "REF" is missing.
Cause:	The attribute value is faulty because the parameter "i" of the key word "APREF" is not available.
Action:	Change the attribute value by adding the parameter "i" to the key word "REF" or contact your ADOxx administrator.

[aap-14]

	Description
Message:	The specified instance in the parameter "i" of the key word "REF" is invalid.
Cause:	The referenced attribute profile has not been found.
Action:	Change the attribute value so that a valid attribute profile is shown or contact your ADOxx administrator.

[aap-15]

	Description
Message:	The specified instance in the parameter "i" of the key word "REF" does not have the suitable class.
Cause:	The referenced attribute profile is not from the class specified in the facet "AttributeProfileRefDomain".
Action:	Change the attribute value so that a valid attribute profile is shown or contact your ADOxx administrator.

aapedit

[aapedit-01]

	Description
Message:	The entry "<entry text>" is not authorised for the attribute "<attribute name>"! <Additional error text> Would you like to further edit the attribute?
Cause:	During the editing of attribute profiles, an invalid attribute value has been entered.
Action:	Enter a valid value for this attribute.

[aapedit-02]

	Description
Message:	The name "<object name>" is already assigned to another object of the class "<Class name>" ! <Additional error text> Would you like to further edit the attribute?
Cause:	When changing the name of an object in the Attribute Profile Management, you have selected a name which is already given for this class .
Action:	Select another name for the object.

[aapedit-03]

	Description
Message:	Not all values could be inserted successfully!
Cause:	When pasting in the ADOxx browser, an error has occurred. This cancelled the pasting.
Action:	Check if the area to be pasted is not too large and if the attributes go together. Then verify if it is allowed to paste in the area you have selected.

aappmod

[aappmod-03]

Message:	The application model <application model name> already exists. Please use another name.
Cause:	Application models are identified by their names.Therefore each application model must have a unique name.
Action:	Enter a different name for the required application model.

[aappmod-10]

Message:	The application model <model name> could not be deleted. Please refresh the model lists and try again.
Cause:	Possibly an error with the connection to the ADOxxdatabase occurred or - if you are working in a client/server environment - the application model may already have been deleted by another ADOxx user.
Action:	Refresh the model lists by clicking on the "Refresh" button. If the error re-occurs, then exit ADOxxand restart the application. If the error re-re-occurs, please contact your ADOxx administrator.

[aappmod-11]

Message:	The application model <model name> could not be created. Refresh the model lists and try again.
Cause:	Possibly an error occurred with your connection to the ADOxx database or - if you are working in a client/server environment - it is possible that one of the models you have selected was already deleted by another ADOxx user.
Action:	Refresh the model lists by clicking on the "Refresh" button. If the error re-occurs, then exit ADOxx and restart the application. If the error re-occurs, then please contact your ADOxx administrator.

[aappmod-12]

Message:	The application model <model name> could not be changed. Please refresh the application model list and try again.
Cause:	Possibly a problem occurred with your connection to the ADOxx database or - if you are working in a client/server environment - one of your selected models may already have been deleted by another ADOxx user.
Action:	Refresh the model lists by clicking on the "Refresh" button. If the error re-occurs, exit from ADOxxand restart the application. If the error re-occurs, then please contact your ADOxx administrator.

[aappmod-13]

Message:	The models contained in the application model "<model name>" have been deleted. This is why the application model is no longer valid. Delete the application model "<model name>" and then actualise the model lists.
Cause:	You have tried to open or change a no longer existing model.
Action:	Redefine the application library after having updated the model lists .

aapqury

[aapqury-01]

	Description
Message:	The AQL expression is syntactically not correct!
Cause:	The AQL expression you have entered does not correspond with the AQL syntax defined.
Action:	Enter a syntactically correct AQL expression.

[aapqury-02]

	Description
Message:	"<Attribute profile name>" is already being edited by another ADOxx user and thus can not be changed!
Cause:	The specified attribute profile cannot be changed as it is already being edited by another ADOxx user.
Action:	Carry out the changes later.

[aapqury-03]

	Description
Message:	Error during the copy: Not all values could be inserted!
Cause:	During the insertion in the ADOxx browser, an error has occurred. The pasting has been cancelled.
Action:	Check if the area to be pasted is not too large and if the attribute types go together. Then check if it is possible to paste in the area you have selected.

[aapqury-04]

	Description
Message:	Error during the copy: No value could be inserted!
Cause:	During the insertion in the ADOxx browser, none of the values to be inserted could be assigned.
Action:	Check if the area to be pasted is not to large and if the attribute types go together. Then check if it possible to paste in the area you have selected.

aapview

[aapview-01]

	Description
Message:	Error when following an attribute profile reference: "<Model name>" (<model type>) could not be opened. The referenced model has meanwhile possibly been deleted.
Cause:	The original model of the attribute profile reference cannot be opened, because it has been meanwhile deleted by another ADOxx user or your access right to this model has been withdrawn by the ADOxx administrator.
Action:	Speak with other ADOxx users or with your ADOxx administrator.

abmpsup

[abmpsup-01]

	Description
Message:	File "<filename>" cannot be opened!
Cause:	One of the specified files cannot be opened with write access. Possibly an incorrect path has been entered or there may be too little space available in the directory or disk on which the file should be stored.
Action:	Please check that the file and path were specified correctly and check the space available on the data medium on which the file should be stored.

[abmpsup-02]

	Description
Message:	No file name specified!
Cause:	You wish to save the generated graphic in a file, but have not specified a filename.
Action:	Please enter a filename in which the graphic should be stored.

abrsimpl

[abrsimpl-06]

	Description
Message:	The column width must be of a number greater than 0 and smaller than 200!
Cause:	You have entered no number or a number outside the valid area (between 0 and 200, excluding limits).
Action:	Enter a valid column width.

[abrsimpl-07]

	Description
Message:	Error while following an inter-model reference: <modelname> <modeltype> could not be opened!Probably the referenced model has been deleted or renamed in the meantimeand the inter-model references have to be updated first.
Cause:	Probably the referenced model has been deleted or renamed in the meantime.
Action:	Refresh the inter-model references.

[abrsimpl-08]

	Description
Message:	Error while following an inter-model reference:The referenced object <objectname> <classname> in model <modelname> <modeltype> could not be found!Probably the referenced object has been deleted or renamed in the meantime.
Cause:	Probably the referenced object has been deleted or renamed in the meantime.
Action:	Refresh the inter-model references.

acaledit

[acaledit-01]

Message:	Invalid entry of the start time (format hh:mm)!
Cause:	The start time has been entered in an invalid format.
Action:	Enter the start time in format hh:mm (hours:minutes).

[acaledit-02]

Message:	Invalid entry of the end time (format hh:mm)!
Cause:	The end time has been entered in an invalid format.
Action:	Enter the end time in format hh:mm (hours:minutes).

[acaledit-03]

Message:	The starting time must be before the ending time!
Cause:	The start time you have entered is after the input end time.
Action:	Define the start and end times so that the start time is earlier than the end time.

[acaledit-04]

Message:	Invalid initialising value!
Cause:	The internal value for the calendar is invalid, since it contains an unknown distribution (only uniform or exponential distribution are allowed).
Action:	Correct the calendar value.

acalui

[acalui-01]

	Description
Message:	The day profile <day profile name> cannot be deleted because it is still being used.Please click on the search button to identify the assigned days.
Cause:	You are attempting to delete a day profile which is still assigned to a number of days in the calendar. A day profile can only be deleted when it is no longer assigned to any days.
Action:	If you really want to delete the selected day profile, then you must first ensure that it is no longer assigned to any days in the calendar. Using the "Search" button, you can identify the days to which this day profile is still assigned. Using the "Assign" button you can assign a day profile to a number of different days.Alternatively, by double-clicking on a day directly within the calendar, you can change the assigned day profile.

[acalui-02]

	Description
Message:	Please enter a name for the new day profile.
Cause:	You have not specified a name for the day profile you are trying to create. As day profiles are identified by their names, it is essential to enter a unique name.
Action:	Enter a valid name for the day profile.

[acalui-03]

	Description
Message:	The day profile name <day profile name> is not allowed. Either a day profile with this name already exists or the name specified contains restricted characters.Please use a different name.
Cause:	An invalid name has been entered for the day profile.Either a day profile with this name already exists or the name specified contains the character "@".
Action:	Enter a valid name for the new day profile which does not contain the character "@".

[acalui-04]

	Description
Message:	The maximum number of day profiles has been reached.Before defining a new day profile, please delete at least one.
Cause:	There is a maximum permitted number of day profile (approx. 50). This number has been reached.
Action:	Delete at least one of the existing day profiles in order to define a new one.

[acalui-05]

	Description
Message:	Please select a day profile.
Cause:	You have clicked on a button (Change, Delete, Assign or Search) which requires a day profile to be specified before the relevant action can be carried out.
Action:	Select a day profile from the list and click on the button again.

[acalui-06]

	Description
Message:	The input in the start field is not time.
Cause:	You have entered a value into the Start field which is not in the correct time format. Note that the required format is "hh:mm:ss", where "hh" is a number between "00" and "23", and both "mm" and "ss" require a number between "00" and "59". A valid value is for example "08:00:00".
Action:	Enter a time as described in "Cause" above.

[acalui-07]

	Description
Message:	The input in the End field is not time.
Cause:	You have entered a value into the End field which is not in the correct time format. Note that the required format is "hh:mm:ss", where "hh" is a number between "00" and "23", and both "mm" and "ss" require a number between "00" and "59". A valid value is for example "17:00:00".
Action:	Enter a time as described in "Cause" above.

[acalui-08]

	Description
Message:	The start time cannot be later than the end time.
Cause:	When defining time intervals, the start time must be earlier than the end time. Please note that the time intervals within a day must be between "00:00:00" and "23:59:59".
Action:	Enter values in the Start and End fields which make up a valid time interval.

[acalui-09]

	Description
Message:	There are intersections with intervals that are already defined in the day profile.
Cause:	You have attempted to define a new time interval which overlaps with existing intervals. The time intervals within a day profile must be distinct - i.e.they cannot overlap with any other time intervals.
Action:	Enter a valid time interval which doesn't overlap with any other time intervals. If necessary, delete or change existing time intervals.

[acalui-10]

	Description
Message:	Please select an interval.
Cause:	You have clicked on a button (Change or Delete) which requires a time interval on which to work.
Action:	Select the time interval on which you want to carry out the action, and then click on the relevant button again.

[acalui-13]

	Description
Message:	Please consider that the start date must be before the end date.
Cause:	You have entered start and end dates which don't define a time interval. Please note that the time interval must lie within a single year (January - December).
Action:	Enter a start and end date which define a valid time interval.

[acalui-14]

	Description
Message:	The days set is empty. Please activate at least one input type.
Cause:	You have not selected an input type ("Day" or "Time interval"). This means that no dates can be selected to which a day profile can be assigned.
Action:	Activate at least one input type (by clicking) and then define the days to which the day profile should be assigned.

[acalui-15]

	Description
Message:	The calendar is too large. Therefore it cannot be stored in the database. Please delete some day profiles.
Cause:	There is an internal limit defined for the complexity of the calendar. When a very high number of day profiles are defined (>50) the calendar can become so complex that it can no longer be saved.
Action:	Delete any unnecessary day profiles - i.e.day profiles which are not assigned to any days.

[acalui-16]

	Description
Message:	The distribution is not correct.
Cause:	You have entered a value into the input field which does not meet the conventions of the distribution.
Action:	Once you select your required distribution type, the syntax is shown in the 'Distribution' field. When using uniform distribution, please be careful that the minimum and maximum bounds are in the correct time format.

[acalui-17]

	Description
Message:	The maximum number of day profiles has been defined.Before copying a day profile, please delete at least one.
Cause:	A limit exists for the maximum number of day profiles which can be defined (approx. 50).
Action:	Delete at least one day profile.

[acalui-18]

	Description
Message:	Please specify the reference object and select at least one day profile.
Cause:	In order to copy a day profile into the current calendar, you must first specify the model from which you want to copy, the reference object which contains the day profile you want to copy and finally the actual day profile itself.
Action:	Select the reference object and the day profile.

[acalui-19]

	Description
Message:	A day profile named<day profile name> already exists. Therefore it cannot be copied.
Cause:	Day profiles must have a unique name within a calendar.Therefore if a day profile with the same name already exists in the calendar to which you are attempting to copy, the system will not allow the new profile to be copied.
Action:	If you are sure that you want to copy the new day profile into your calendar, you must first delete the existing day profile with the same name.

[acalui-20]

	Description
Message:	The calendar has the wrong format. Therefore the day profiles cannot be copied.
Cause:	If the calendar of the selected reference object has an invalid format, then no day profiles can be copied.
Action:	Select a different reference object. In order to correct the invalid calendar of the reference object, you should open the ADOxx notebook of that object - the calendar will then automatically be corrected to contain standard values.

acard

[acard-02]

	Description
Message:	"<Object>": A maximum of <number> connectors is allowed (<direction>). Should the verification of the cardinalities be continued?
Cause:	The verification of the cardinalities of the model has determined that the maximum number of allowed connectors in the specified object is too high . The possibly shown direction ("incoming", "outgoing" or "all together") indicates whether the maximum number of incoming or outgoing connectors has been reached or if the number of connectors in general is too high.
Action:	According to the defined cardinality restrictions, only a certain number of connectors is allowed. To adhere to these restrictions, you have to delete connectors which start from or end in the specified object.

[acard-03]

	Description
Message:	"<source>": A maximum of <number> connectors of the type "<relation class>" is allowed (<direction>). Should the verification of the cardinalities be continued?
Cause:	The verification of the cardinalities of the model has determined that the maximum number of allowed connectors of the specified relation type in the specified source is too high. The source is about a concrete object, an object of the class displayed a relation between a concrete object and objects of the specified class or about the relation between objects of the class shown and a concrete object.The possibly shown direction ("incoming", "outgoing" or "all together") indicates whether the maximum number of incoming or outgoing connectors has been reached or if the number of connectors in general is too high.
Action:	According to the cardinality restrictions, only a certain number of connectors of the specified relation class are permitted. To adhere to these restrictions, you have to delete connectors which start from or end in the specified object.

[acard-04]

	Description
Message:	Unexpected value in the attribute "<attribute>" ("<class>"): "<error expression>" is not a valid value. "<correct expression>" is expected.
Cause:	The specified attribute of the specified class contains an invalid value. The valid expression listed is expected instead.
Action:	Contact your ADOxx administrator. The Development Toolkit should be used to correct the invalid value.

[acard-05]

	Description
Message:	The model contains<number> objects of the class "<class name>". A maximum of <number> objects are allowed. Should the verification of the cardinalities be continued?
Cause:	The verification of a model has determined that the maximumnumber of allowed objects of the specific class is too high.
Action:	According to the defined cardinality restrictions, only a certain number of objects of the specified class is allowed. To fulfill these restrictions, you must delete the appropriate number of objects of this class.

[acard-06]

	Description
Message:	The model contains<number> objects of the class "<class name>". <At least number> object(s) is/are required. Should the verification of the cardinalities be continued?
Cause:	The verification of a model has determined that theminimum number of required connectors of the specific class has not been reached.
Action:	According to the defined cardinality restrictions, a minimum number of objects of the specified class is required.To fulfill these restrictions, you must create the corresponding number of objects of this class.

[acard-07]

	Description
Message:	<Object or class name>:At least <number> connector(s) is/are required (<direction>). Should the verification of the cardinalities be continued?
Cause:	The verification of a model has determined that the minimal number of required connectors has not been reached. The possibly shown direction ("incoming", "outgoing" or "all together") indicates whether the minimum number of incoming or outgoing connectors has not been reached or if the number of connectors in general is too low.
Action:	According to the defined cardinality restrictions, a minimum number of connectors is required. To fulfill these restrictions, you must create additional connectors, which start from or end in the specified object.

[acard-08]

	Description
Message:	<Object or class name>: At least<number> connector(s) of the type "<relation class name>" is/are required (<direction>). Should the verification of the cardinalities be continued?
Cause:	The verification of a model has determined that for the minimum number of required connectors of the specified class for the specified object has not been reached. The possibly shown direction ("incoming", "outgoing" or "all together") indicates whether the minimum number of incoming or outgoing connectors has not been reached or if the number of connectors in general is too low.
Action:	According to the defined cardinality restrictions, a minimum number of connectors of the specified relation class is required. To fulfill these restrictions, you must create additional connectors of the relation class, which start from or end in the specified object.

[acard-09]

	Description
Message:	Error in the assignment of the attribute "<attribute name>" ("<class name>"): "<expression>" is not applicable to the relation class "<relation class name>"!
Cause:	The specified cardinality restriction is not meaningful. This message will be delivered for instance if the number of incoming connectors are restricted to a class, although the corresponding connectors of this class can only be outgoing (and not incoming).
Action:	Remove this restriction.

acase40

[acase40-01]

Message:	Error while following the selected reference!
Cause:	The referenced object in case/4/0 has been deleted or case/4/0 could not be started
Action:	Delete or change the reference or install case/4/0 correctly

[acase40-02]

Message:	An error has occurred during the new creation of a reference!!
Cause:	This is a serious error on the part of case/4/0.Possibly case/4/0 is not correctly installed.
Action:	Install case/4/0 or check the existing case/4/0 installation.

[acase40-03]

Message:	An error has occurred while attempting to change the selected reference!
Cause:	This is a serious error on the part of case/4/0.Possibly case/4/0 is not correctly installed.
Action:	Install case/4/0 or check the existing case/4/0 installation.

[acase40-04]

Message:	An error has occurred while deleting a reference!
Cause:	This is a serious error on the part of case/4/0.Possibly case/4/0 is not correctly installed.
Action:	Install case/4/0 or check the existing case/4/0 installation.

acccber

[acccber-01]

Message:	The quantity is 0 in at least one model of the application model!
Cause:	The 'Quantity' attribute in a 'Process start' object is 0 for at least one of the business process models belonging to the application model.
Action:	Check the business processes in the application model and specify a 'Quantity' greater than 0 for each 'Process start' object.

[acccber-02]

Message:	The cost driver quantity is 0 in at least one model of the application model!
Cause:	The attribute 'Cost driver quantity' in objects of the class 'Process start' is 0 in at least one of the business process models belonging to the application model.
Action:	Check the business processes in the application model and specify a 'Cost driver quantity' greater than 0 for each 'Process start' object.

acccdlg

[acccdlg-01]

Message:	Internal error "Internal error number" while processing the application model "application model name"!
Cause:	An internal error occurred while processing this application model.
Action:	Please contact your ADOxx administrator.

[acccdlg-02]

Message:	The input parameters are not defined correctly.Please contact ADOxx customer support.
Cause:	The input parameters specified for the ADOxx-3c simulation are not consistent with the class and attribute definitions of the application library.
Action:	Correct the "sim mapping" definition in the Development Toolkit or contact your ADOxx consultant.

[acccdlg-03]

Message:	There is no quantity defined in at least one model of the application model!. <Model name>
Cause:	The 'Quantity' attribute in a 'Process start' object is 0 for at least one of the business process models belonging to the application model.
Action:	Check the business processes in the application model and specify a 'Quantity' greater than 0 for each 'Process start' object.

acccinit

[acccinit-01]

Message:	At least one performer is not assigned to a cost centre!
Cause:	At least one of the performers from the working environment model specified as part of the application model is not assigned to a cost centre.
Action:	A performer must belong to exactly one cost centre.Connect the performer through the relation "Is charged to" with the corresponding cost centre.

[acccinit-02]

Message:	At least one performer is assigned to more than one cost centre!
Cause:	At least one of the performers from the working environment model specified as part of the application library is assigned to more than one cost centre.
Action:	A performer must be assigned to exactly one cost centre.Delete the incorrect relations from the model.

[acccinit-03]

Message:	At least one cost centre has more than one manager!
Cause:	At least one cost centre in the working environment model is connected to more than one performer with the relation "Is cost centre manager".
Action:	Each cost centre must have at most one manager - so delete the unnecessary relations.

[acccinit-04]

Message:	The attribute <attribute name> is not defined!
Cause:	The attribute specified is not defined in the application library.
Action:	Please contact your ADOxx consultant.

[acccinit-05]

Message:	The class<class name> is not defined in the application library!
Cause:	The class specified is not defined in the application library.
Action:	Please contact your ADOxx consultant.

acnumchk

[acnumchk-01]

	Description
Message:	The key word "DOMAIN" is missing.
Cause:	The LEO expression in the facet "AttributeNumericDomain" does not contain the required key word "DOMAIN".
Action:	Rectify the value of the facet "AttributeNumericDomain", by adding the key word "DOMAIN" or contact your ADOxx administrator.

[acnumchk-02]

	Description
Message:	The parameter "message" of the key word "DOMAIN" is missing.
Cause:	The LEO expression in the facet "AttributeNumericDomain" does not contain the required parameter "message" for the key word "DOMAIN".
Action:	Rectify the value of the facet "AttributeNumericDomain", by adding the parameter "message" to the key word "DOMAIN" or contact your ADOxx administrator.

[acnumchk-03]

	Description
Message:	After the key word "DOMAIN", only the key word "INTERVAL" is authorised.
Cause:	The LEO expression in the facet "AttributeNumericDomain" contains an invalid key word.After the key word "DOMAIN", only the key word "INTERVAL" is allowed.
Action:	Rectify the value of the facet "AttributeNumericDomain", by also using the key word "INTERVAL" after the key word "DOMAIN" or contact your ADOxx administrator.

[acnumchk-04]

	Description
Message:	The parameter "lowerbound" of the key word "INTERVAL" is missing.
Cause:	The LEO expression in the facet "AttributeNumericDomain" does not contain the required parameter "lowerbound" for the key word "INTERVAL".
Action:	Rectify the value of the facet "AttributeNumericDomain", by adding the parameter "lowerbound' to the key word "INTERVAL" or contact your ADOxx administrator.

[acnumchk-05]

	Description
Message:	The parameter "upperbound" of the key word "INTERVAL" is missing.
Cause:	The LEO expression in the facet "AttributeNumericDomain" does not contain the required parameter "upperbound" for the key word "INTERVAL".
Action:	Rectify the value of the facet "AttributeNumericDomain", by adding the parameter "upperbound" to the key word "INTERVAL" or contact your ADOxx administrator.

[acnumchk-06]

	Description
Message:	The value of the parameter "upperbound" is smaller than the value of the parameter "lowerbound".
Cause:	The value of the parameter "upperbound" of the key word "INTERVAL" is smaller than the value of the parameter "lowerbound" of the same key word.
Action:	Change the value of the parameter "lowerbound" and "upperbound" so that the value of the parameter "upperbound" is greater than or equal to the value of the parameter "lowerbound" or contact your ADOxx administrator.

[acnumchk-07]

	Description
Message:	The value is not in one of the specified intervals.
Cause:	The specified value is not within the area valid for the attribute.
Action:	Change the value so that it is in an interval specified in the facet "AttributeNumericDomain".

acoexhan

[acoexhan-01]

	Description
Message:	No expression!
Cause:	The value of the edited EXPRESSION attribute does not contain any expression, i.e. no formula or possible constant. This way no result can be calculated for the EXPRESSION attribute.
Action:	Specify an expression for the calculation of the result.

[acoexhan-02]

	Description
Message:	The result of the expression is not of the type specified in the attribute definition! Expected type:"<result type1>" Delivered type:"<result type2>".
Cause:	The expression of the EXPRESSION attribute delivers a result, which is of another type than the one specified in the attribute definition. This is why you cannot use the result.
Action:	Specify an expression which delivers a result matching to the type. If necessary, insert a conversion operator (VAL/STR) in this formula .

[acoexhan-03]

	Description
Message:	The calculated value is too long/big to save in the database!
Cause:	The result of an EXPRESSION attribute returned a value which is too long/big to save in the database.
Action:	Define an expression resulting in a shorter/smaller value.

[acoexhan-04]

	Description
Message:	The expression is too long to store in the database!
Cause:	The EXPRESSION is too long and therefore cannot be saved into the database.
Action:	Define a shorter expression to calculate the result.

acoexman

[acoexman-01]

	Description
Message:	The syntax definition is EXPR type:<ResultType>[expr: [fixed:]<expression>, however the attribute value is "<attribute value>"!
Cause:	The value defined for the EXPRESSION attribute is syntactically wrong.
Action:	Change the value so that the syntax instructions come up.

acoexpar

[acoexpar-01]

	Description
Message:	Internal error!
Cause:	An unexpected error code has been delivered in the EXPRESSION attribute during the call of a core function.This can occur when a number which is not an ID is given instead of an ID.
Action:	Verify and correct the formula.

[acoexpar-02]

	Description
Message:	Attribute "<attribute name>" (<Class name>) does not exist!
Cause:	In the EXPRESSION attribute, a string, whose value is not an attribute name in the specified class, has been assigned during the call of a function, which expects an attribute name as a parameter.
Action:	Verify and correct the formula.

[acoexpar-03]

	Description
Message:	The attribute "<attribute name>" (<class name>) cannot be accessed because of its types in the expressions!
Cause:	You are trying to sort an attribute of the type RECORD or PROFILEREF.
Action:	Verify and correct the formula.

[acoexpar-04]

	Description
Message:	Error in the referenced attribute "<attribute name>" of the objects "<object name>" (<class name>) in "<model name>" (<model type>)!
Cause:	The EXPRESSION attribute accesses to another EXPRESSION attribute, in which an error is delivered instead of a value.
Action:	Verify and correct the formula of the referenced EXPRESSION attribute specified in the error message.

[acoexpar-05]

	Description
Message:	At the moment, the object "<Object name>" (<class name>) in "<model name>" (<model type>) cannot be accessed!
Cause:	The EXPRESSION attribute attempts to access an object which is not in the memory yet. This conflict can only occur during the loading of a model and will disappear itself after the loading process.
Action:	No action required or action is done automatically.

[acoexpar-06]

	Description
Message:	No object "<object name>" (<class name>) exists in "<model name>" (<model type>)!
Cause:	In the EXPRESSION attribute, a string, with a value which is not the name of an object of the specified class, has been assigned during the call of a function, which has an object name as parameter.
Action:	Verify and correct the formula.

[acoexpar-07]

	Description
Message:	In the model type "<model type>", there is no class "<class name>"!
Cause:	In the EXPRESSION attribute, a string whose value is not the name of a class in the specified model type, has been assigned during the call of a function, which expects a class name as a parameter.
Action:	Verify and correct the formula.

[acoexpar-08]

	Description
Message:	Access to the specific attribute "<attribute name>" is not authorised!
Cause:	In the EXPRESSION attribute, you have attempted to sort this attribute, which leads to an endless recursion.
Action:	Verify and correct the formula.

[acoexpar-09]

	Description
Message:	The attribute "<attribute name>" (<class name>) is not of numerical type!
Cause:	In the EXPRESSION attribute, you have attempted to calculate an arithmetical aggregate function via a non numerical attribute.
Action:	Verify and correct the formula.

[acoexpar-10]

	Description
Message:	The ID list is faulty!
Cause:	In the EXPRESSION attribute, a string, which contains no or not only IDs, is assigned to a function, which expects a string with a list of IDs as parameter.
Action:	Verify and correct the formula.

[acoexpar-11]

	Description
Message:	<Function name> cannot be evaluated without access to the Modelling Component!
Cause:	In the EXPRESSION attribute, you have attempted to access the "modelling" message port, which is not available.
Action:	None. This error does not occur in the ModellingToolkit.

[acoexpar-12]

	Description
Message:	No column "<column name> exists in the record attribute "<attribute name>" (<class name>)!
Cause:	In the EXPRESSION attribute, a string, whose value is not the name of a column of the specified RECORD attribute, is assigned during the call of a function, which expects as a column name of a RECORD attribute as parameter.
Action:	Verify and correct the formula.

[acoexpar-13]

	Description
Message:	The column "<column name>" of the record attribute "<attribute name>" (<class name>) is not of numerical type!
Cause:	In the EXPRESSION attribute, you have attempted to calculate an arithmetical aggregate function using a non numerical attribute.
Action:	Verify and correct the formula.

[acoexpar-14]

	Description
Message:	The column "<column name>" of the record attribute "<attribute name>" (<class name>) is not of the type <type name>!
Cause:	In the EXPRESSION attribute, a RECORD column is accessed, whose attribute type is different from the attribute type expected.
Action:	Verify and correct the formula.

[acoexpar-15]

	Description
Message:	Syntactical error in the AQL expression!
Cause:	In the EXPRESSION attribute, a function is called, which expects an AQL expression with a string as parameter.The value assigned is not a syntactically correct AQL expression.
Action:	Verify and correct the formula.

[acoexpar-16]

	Description
Message:	Missing reference in object "<Object name>" (<class name>), record attribute "<attribute name>", column "<column name>" [<column index name>]!
Cause:	In the EXPRESSION attribute, an INTERREF attribute, which must contain a valid reference, is accessed.However the INTERREF attribute contains either no reference or no valid reference.
Action:	Change the specified INTERREF attribute, so that it contains a valid reference.

[acoexpar-17]

	Description
Message:	The attribute "<attribute name>" (<class name>) is neither of numerical nor of time type!
Cause:	In the EXPRESSION attribute, you have attempted to calculate an arithmetical aggregate function via a non numerical and non time attribute.
Action:	Verify and correct the formula.

[acoexpar-19]

	Description
Message:	The AQL expression cannot be evaluated!
Cause:	In the EXPRESSION attribute, you have attempted to evaluate an AQL expression, without having the message port required for it available.
Action:	None. This error does not occur in the ModellingToolkit.

[acoexpar-20]

	Description
Message:	Cyclic dependence when accessing to the attribute "<attribute name>" of the object "<object name>" (<class name>) in "<model name>" (<model type>)!
Cause:	Several EXPRESSION attributes cyclically access another, so that an endless recursion appears.
Action:	Verify and correct the formulas of the concerned EXPRESSION attribute.

[acoexpar-21]

	Description
Message:	In the model type <model type> there is no relation type "<class name>"!
Cause:	In the EXPRESSION attribute, a string, which is not the name of a relation type, is assigned to a function, which expects the name of a relation type as parameter.
Action:	Verify and correct the formula.

[acoexpar-22]

	Description
Message:	The ID list when calling the <function name> is empty!
Cause:	In the EXPRESSION attribute, an empty string is assigned to a function which expects a non-empty ID list as a parameter. The reason can be, that an INTERREF attribute is accessed in which no valid reference is contained.
Action:	Verify and correct the formula and the included INTERREF attributes.

[acoexpar-23]

	Description
Message:	The attribute "<attribute name>" (<class name>) is not of the type <type name>!
Cause:	In the EXPRESSION attribute, an attribute which is different from the expected attribute type, is being accessed using a function.
Action:	Verify and correct the formula.

[acoexpar-24]

	Description
Message:	At least one object is referenced by the INTERREF attribute "<attribute name>" of the object "<object name>" (<class name>) and you cannot access this object as "<model name>" (<model type>) is not loaded!
Cause:	In the EXPRESSION attribute, you have attempted to find IDs referenced objects, without having opened the target model.
Action:	Open the target model. If the expression could be correctly calculated once, the last valid result will be delivered instead of this error.

[acoexpar-25]

	Description
Message:	An object "<object name>" (<class name>) is referenced by the INTERREF attribute "<attribute name>" of the object "<object name>" (<class name>) and this object does not exist in "<model name>" (<model type>)!
Cause:	In the EXPRESSION attribute, you have attempted to find IDs referencing, no longer existing objects.
Action:	Edit the INTERREF attribute concerned or create new objects, so that the INTERREF attribute contain valid references again.

[acoexpar-26]

	Description
Message:	The INTERREF attribute "<attribute name>" of the object "<object name>" (<class name>) contains errors!
Cause:	In the EXPRESSION attribute, you have accessed an INTERREF attribute, which contains an invalid value.This means that the database is corrupt.
Action:	The ADOxx database may be recreated.

[acoexpar-27]

	Description
Message:	The call of the <function name> can not be evaluated, as "<model name>" (<model type>) is not loaded!
Cause:	In the EXPRESSION attribute, you have attempted to sort information from a model which is not opened.
Action:	Open the specified model. If the expression could be correctly calculated once, the last valid result will be delivered instead of this error.

[acoexpar-28]

	Description
Message:	The call of the <function name> can not be evaluated, as there is no scope or referenced model!
Cause:	You have attempted to evaluate an object-related expression without having specified the scope. This can occur during the call of EVAL_EXPRESSION, when functions have been called, which refer to a specific object id and the parameter object has not been specified.
Action:	Specify the object id when calling EVAL_EXPRESSION.

[acoexpar-29]

	Description
Message:	The record attribute "<attribute name>" (<class name>) contains no row with index <row number>!
Cause:	In the EXPRESSION attribute, you have attempted to access a RECORD row which does not exist.
Action:	Verify and correct the formula or edit the specified RECORD attribute.

[acoexpar-30]

	Description
Message:	The attribute profile referenced by "<attribute name>" (<class name>) does not exist!
Cause:	In the EXPRESSION attribute, you have attempted to access to a referenced attribute profile, which has broken the attribute profile reference .
Action:	Verify and correct the formula or the attribute profile reference specified in the error message.

acompare

[acompare-01]

Message:	Please specify a filename.
Cause:	No filename has been specified.
Action:	Please enter the filename to which you wish to write.

[acompare-02]

Message:	Invalid filename.
Cause:	An invalid filename has been specified for the result file.
Action:	Enter a valid filename.

[acompare-03]

Message:	Error while opening the result file.
Cause:	The result file could not be opened - perhaps no access is currently possible to the location where file is stored (e.g. an external data storage medium).
Action:	Check the data medium or location and begin again.

[acompare-04]

Message:	Error while reading the result file.
Cause:	The specified result file was not in the expected ACR format.
Action:	While saving this file, a serious error must have occurred. Use a different result file.

[acompare-07]

Message:	A representation is not possible because there are no common values available.
Cause:	The selected results have no value in common.Therefore a comparable representation is not possible.
Action:	Select different results to be compared.

[acompare-13]

Message:	The result <result name> does not exist.
Cause:	You have selected a non-existent result.
Action:	Enter the name of an existing result.

[acompare-14]

Message:	Error while writing to file.
Cause:	An error occurred while saving information on the result comparison to a file.
Action:	Possibly there is not enough space on the data medium.Please check the space available on the location to which you are saving the file and then try again.

acomps

[acomps-01]

Message:	No control component specified!
Cause:	A fatal error has occurred.
Action:	If this error re-occurs after attempting simulation again, export your models to an ADL file and contact your ADOxx consultant.

aconfui

[aconfui-05]

	Description
Message:	Cannot load current configuration!
Cause:	An error occurred while the current configuration was read from the ADOxx database.
Action:	Quit ADOxx and re-start it. Should this error re-occur, contact your system administrator.

[aconfui-10]

	Description
Message:	Licence number does not correspond with customer number!
Cause:	The licence number entered cannot be used for configuring components when combined with the customer number listed.
Action:	Check the licence number entered. Should this error still occur, contact your system administrator or your ADOxx consultant.

[aconfui-12]

	Description
Message:	No licence number entered!
Cause:	You did not enter a licence number.
Action:	Enter the licence number for the new configuration of components of the ADOxx Modelling Toolkit.

[aconfui-13]

	Description
Message:	New configuration could not be saved in database.
Cause:	An error occurred when the new configuration was to be saved in the ADOxx database.
Action:	Quit ADOxx and re-start it. Should this error re-occur, contact your database or system administrator.

[aconfui-20]

	Description
Message:	The new licence number could not be saved in the database!Currently <number> users are created, but the new licence number only allows at most <number> users.In order to use the new licence number, at least one user has to be deleted first.
Cause:	The maximum number of user allready exists that's why you can't use the licence.
Action:	Delete one user to create a new one.

acregchk

[acregchk-01]

	Description
Message:	The key word "REGEXP" is missing.
Cause:	The LEO expression in the facet "AttributeRegularExpression" doesn't contain the required key word "REGEXP".
Action:	Rectify the value of the facet "AttributeRegularExpression", by adding the key word "REGEXP" or contact your ADOxx administrator.

[acregchk-02]

	Description
Message:	The parameter "expression" of the key word "REGEXP" is missing.
Cause:	The LEO expression in the facet "AttributeRegularExpression" does not contain the required parameter "expression" for the key word "REGEXP". In the parameter "expression", you must have the regular expression, which the attribute values must meet.
Action:	Correct the value of the facet "AttributeRegularExpression", by adding the parameter "expression" to the key word "REGEXP", or contact your ADOxx administrator.

[acregchk-03]

	Description
Message:	The parameter "message" of the key word "REGEXP" is missing.
Cause:	The LEO expression in the facet "AttributeRegularExpression" does not contain the parameter "message" required for the key word "REGEXP". In the parameter "message", you must have the description text for the regular expression, which the attribute values must meet.
Action:	Correct the value of the facet "AttributeRegularExpression", by adding the parameter "message" to the key word "REGEXP" or contact your ADOxx administrator.

[acregchk-04]

	Description
Message:	The regular expression in the parameter "expression" is invalid.
Cause:	The parameter "expression" in the facet "AttributeRegularExpression" contains an invalid regular expression.
Action:	Rectify the value of the facet "AttributeRegularExpression", by giving a valid regular expression as value to the parameter "expression" of the key word "REGEXP" or contact your ADOxx administrator.

[acregchk-05]

	Description
Message:	The expression does not meet the regular expression in the parameter "expression".
Cause:	You have attempted to assign a value, which doesn't correspond to the defined regular expression.
Action:	Change the value in such a way, that it meets the regular expression. If necessary, have a look at the help text of the corresponding attribute to find out if there is a description of the possible values.

adbacc

[adbacc-01]

	Description
Message:	<Database error message> Class:ADBACC, Stmt handle:<Handle>, Function:<Function Name>
Cause:	A general database error occurred. The error message gives information about the cause of the error and contains the database error-code, which can be used to gain further information from the database error documentation.
Action:	Exit ADOxx and start it again. If the error re-occurs, please write down the <Database error message>, <Handle> and <Function Name> and contact your system administrator.

adbadm

[adbadm-01]

	Description
Message:	<Database error message> Class:ADBADM, Stmt handle:<Handle>, Function:<Function Name>
Cause:	A general database error occurred. The error message gives information about the cause of the error and contains the database error-code, which can be used to gain further information from the database error documentation.
Action:	Quit ADOxx and start it again. If the error still occurs, please write down the <Database error message>, <Handle> and <Function Name> and contact your system administrator.

adbback

[adbback-01]

Message:	Database error occurred: SQLCODE: <Database error code><parameter, which caused the error>.
Cause:	A general database error occurred. SQLCODE indicates a database-specific error code, which can be looked up in the database documentation.
Action:	Find the cause for the error within the database documentation (e.g. look up the DB2 error code "-1124" in the DB2 documentation under "SQL1124N") and ask your database administrator to carry out the necessary actions described in the documentation to fix the problem.

[adbback-02]

Message:	User name, password and database name must be entered.
Cause:	At least one necessary parameter has not been entered.
Action:	Enter the user name, password and database name.

[adbback-03]

Message:	Alias name of database not found.
Cause:	The ADOxx database name entered does not exist.
Action:	Enter the correct name of the ADOxx database to be saved.

[adbback-04]

Message:	User name/password not valid.
Cause:	The user name and/or password have not been entered correctly.
Action:	Enter the user name and password correctly.

[adbback-05]

Message:	Path not found or invalid.
Cause:	The path entered cannot be found or accessed, or is invalid.
Action:	Enter an existing path or a path, where you have access rights. If necessary, create a new path using "mkdir" and run "ADBBACK" again.

[adbback-06]

Message:	Database in use. All users must close their connections before database backup can be run.
Cause:	The ADOxx database to be saved is being used by one or more ADOxx users. You can only run the backup when all connections to the ADOxx database are terminated.
Action:	All ADOxx users must terminate their connections to the ADOxx database so that it can be saved.

[adbback-07]

Message:	Database manager has not been started.
Cause:	The database manager or the database instance is not active.
Action:	Start the database manager or the database.

[adbback-08]

Message:	User name does not exist or has insufficient privileges.
Cause:	The user name entered does not exist or has not got sufficient rights.
Action:	Enter the user name correctly. If the message occurs again, create the user and/or allocate the necessary rights. This can only be done by the database administrator.

adbinst

[adbinst-01]

Message:	Database error: SQLCODE: <Database error code><Parameter, which caused the error>.
Cause:	A general database error occurred. SQLCODE indicates a database-specific error code, which can be looked up in the database documentation.
Action:	Find the cause for the error within the database documentation (e.g. look up the DB2 error code "-1124" in the DB2 documentation under "SQL1124N") and ask your database administrator to carry out the necessary actions described in the documentation to fix the problem.

[adbinst-02]

Message:	Syntax error for database name: [<node>:]<database name>.
Cause:	You did not fill in the input field 'database name' correctly. The correct syntax is [<node>:]<database name>.
Action:	Enter the database name according to the correct syntax.

[adbinst-03]

Message:	User name and password must be entered.
Cause:	At least one of the values for the fields 'SYSADM/SYSCTRL user' and 'password' is missing.
Action:	Enter the missing value(s).

[adbinst-04]

Message:	Invalid database name.
Cause:	The name of the ADOxx database is either too short or long, or consists of invalid characters.
Action:	Enter a name consisting of three to eight alpha-numeric characters.

[adbinst-05]

Message:	It is not possible to create a database from this node.
Cause:	This message occurs, when only the client-enabler is installed on the local machine and the user tries to create a new database on a remote server without entering the name of the node.
Action:	You can't install an ADOxx database on your computer with the current client/server configuration of your database system, please contact your system administrator.

[adbinst-06]

Message:	Database name exists already.
Cause:	An ADOxx database with this name exists already .
Action:	Enter a different name for the new ADOxx database.

[adbinst-07]

Message:	User name does not exist or has insufficient privileges.
Cause:	The user name entered either does not exist or has not sufficient rights to create databases.
Action:	Ensure that the user name was entered correctly.If that is the case, please contact your database administrator.

[adbinst-08]

Message:	Unsuccessful login.
Cause:	You entered an incorrect user name or password.
Action:	Ensure, that the user name and password were entered correctly. If that is the case, please contact your database administrator.

[adbinst-09]

Message:	Command line error. Calling convention:adbinst [-u<user>] [-p<password>] [-d[<node>:]<database name>] [-l<licence number>] [-s<database system>] [-c[+|-]]
Cause:	The syntax used in the command line is not correct.
Action:	Enter the command line parameters in the syntactically correct form.

[adbinst-10]

Message:	'ADOxx' user does not exist or has insufficient privileges.
Cause:	The default user 'ADOxx' has not been created on the computer or doesn't have database creation privileges.
Action:	Create the user 'ADOxx' in the user profile administration and/or grant him database creation privileges. This can only be done by your system administrator.

[adbinst-11]

Message:	Unsuccessful login of user 'ADOxx'.
Cause:	The login attempt of the user 'ADOxx' could not be successfully executed. This might be caused by a changed password of the standard user 'ADOxx'.
Action:	Please contact your system administrator.

[adbinst-12]

Message:	Error while creating tables.
Cause:	A database error occurred when generating the database tables. This is caused either by lack of database rights for the standard user 'ADOxx' or by a database error which cannot be localised (e.g. network error, system break down, connection break down).
Action:	Make sure, that the standard user 'ADOxx' has been created correctly and is assigned with the necessary database rights and that the network connection (as described in the DBMS-specific documentation) has been correctly configured.

[adbinst-13]

Message:	Error while creating base classes.
Cause:	An error occurred during the creation of the ADOxx base classes. This is most likely caused by a system error (network error, connection breakdown).
Action:	Try to install your ADOxx database again. Please check the system settings on your computer (e.g. path settings, network) if the error reoccurs.

[adbinst-14]

Message:	Error while creating meta model/standard AL.
Cause:	When generating the meta model or the standard application library an error occurred. The error is most likely caused by a system error (network error, connection break down).
Action:	Try to install your ADOxx database again.If the error re-occurs, please check the system settings on your computer (e.g. path settings, network).

[adbinst-15]

Message:	Database manager has not been started.
Cause:	The database manager or the database instance is not active.
Action:	Start the database manager or the database instance.

[adbinst-16]

Message:	Incorrect licence number or licence file not found.
Cause:	You entered an invalid licence number.
Action:	Make sure that the licence number was entered correctly (capital/small letters!). If the error re-occurs, please contact your ADOxx consultant.

[adbinst-17]

Message:	Error while generating database statistics. Please contact your database administrator.However, the created database can be used anyway.
Cause:	You have just created a new database. During the creation of the catalogue statistics for the new database a non-critical error occurred.
Action:	No troubleshooting is necessary, as the database is functional anyway. However, contact your database administrator for tracking down the reason for this error.

[adbinst-18]

Message:	The selected database does not exist or has not yet been catalogued.
Cause:	The database has not been set-up on the database server or the network connection has not been configured on the client.
Action:	Setup the database and the network connection according to the guidelines in your "Installation and database administration manual".

[adbinst-19]

Message:	Personal Oracle is not installed.
Cause:	You tried to create an ADOxx database for "Personal Oracle", without having installed the database system "Personal Oracle" on your computer.
Action:	Install "Personal Oracle", using your Oracle installation-package. If you are using an Oracle server version (also as a stand-alone version), please select the entry "ORACLE" (and not "PersonalORACLE") in the list-box "Database system" of the program window.

[adbinst-20]

Message:	File <file name> could not be found.
Cause:	The file needed, could not be found. This might be due to an error during the installation of ADOxx or due to the fact, that the file has been deleted.
Action:	Re-start the ADOxx installation program.

[adbinst-21]

Message:	Import of the standard application library failed.
Cause:	1. The file "adostd.abl" could not be found. 2. The file "adostd.abl" does not include the standard application library. 3. The ABL file containing the standard application library is invalid.
Action:	Please contact your ADOxx consultant.

adbrest

[adbrest-01]

Message:	Database error: SQLCODE: <database error code> <parameter, causing the error>.
Cause:	A database error occurred. SQLCODE indicates a database-specific error code that can be looked up in the database documentation.
Action:	Find the cause for the error within the database documentation (e.g. look up the DB2 error code "-1124" in the DB2 documentation under "SQL1124N") and ask your database administrator to carry out the necessary actions described in the documentation to fix the problem.

[adbrest-02]

Message:	User name, password, database name and timestamp must be entered.
Cause:	You did not enter one or more necessary parameters.
Action:	Enter all of the following: user name, password, ADOxx database name and timestamp.

[adbrest-03]

Message:	User name does not exist or has insufficient privileges.
Cause:	The user name entered does not exist or has not sufficient rights.
Action:	Make sure that the user name had been entered correctly.If the message re-occurs, create the user and/or assign the necessary rights to the user. This has to be done by the database administrator.

[adbrest-04]

Message:	User name/password not valid.
Cause:	You entered the user name and/or password incorrectly.
Action:	Enter a valid user name and the valid password.

[adbrest-05]

Message:	Path not found or invalid.
Cause:	The path entered does not exist or cannot be accessed.
Action:	Enter the path to which the ADOxx database had been saved with ADBBACK.

[adbrest-06]

Message:	Database in use. All users must close their connections before database can be restored.
Cause:	The ADOxx database to be restored is being used by one or more ADOxx users. It can only be restored, when all connections to the ADOxx database have been terminated.
Action:	All ADOxx users must terminate their connections with the ADOxx database to be restored.

[adbrest-07]

Message:	Timestamp entered is invalid
Cause:	The syntax of the parameter "timestamp" is not correct.
Action:	The timestamp is derived from the date and time at which the backup was made and is represented by a number consisting of 14 digits (Example: A back-up from the 3rd of July 1998 at 13 hours 05 minutes and 27 seconds has the timestamp "19980703130527").

[adbrest-08]

Message:	Timestamp or database alias name could not be found.
Cause:	The timestamp or the name of the ADOxx database could not be found.
Action:	Make sure that the ADOxx database name and the timestamp were entered correctly.

[adbrest-09]

Message:	Database manager has not been started.
Cause:	The database manager or the database instance is not active.
Action:	Start the database manager or the database instance.

adbsess

[adbsess-01]

	Description
Message:	The network or database system is not available at the moment. The database connection has been aborted. In the current session, no further database access is possible. It is recommended to start the application again.
Cause:	An error has occurred in the network connection.
Action:	Try to start the application again. Should this error appear again, contact your system administrator.

[adbsess-02]

	Description
Message:	Because of an unexpected database message, the connection with the database has been aborted. In the current session, no further database access is possible. It is recommended to start the application again.
Cause:	Demands to the database system have been rejected by an error message.
Action:	Click on the button "Show database message" and note the displayed error message and contact a system administrator or an ADOxx administrator. Further access to the database is only possible once you have restarted the application.

adelmod

[adelmod-02]

Message:	The model <modelname> <modeltype> can not be deleted as it is currently used within a simulation or analytical evaluation!
Cause:	The model you wanted to delete is currently used in a simulation or an analytical evaluation.
Action:	Close the simulation result or analytical evaluation result first and than try again.

[adelmod-03]

Message:	The following models can not be deleted as they are currently used within a simulation or analytical evaluation! <list with models>
Cause:	The models you wanted to delete are currently used in a simulation or an analytical evaluation.
Action:	Close the simulation result or analytical evaluation result first and than try again.

adistrib

[adistrib-01]

	Description
Message:	Enter a numeric value for the expected valueperiod;
Cause:	No number has been entered for the expected value in a normal distribution.
Action:	Enter a numeric value for the expectation.

[adistrib-02]

	Description
Message:	Enter a number greater than 0 for the standard deviation.
Cause:	Either no number or a number less than or equal to 0 has been entered for the standard deviation value of the normal distribution.
Action:	Enter a positive number for the standard deviation.

[adistrib-04]

	Description
Message:	Enter a number greater than 0,00000001 for the expected value.
Cause:	Either no number or a number less than or equal to 0.00000001 has been entered for the expected value in the exponential distribution.
Action:	Enter an authorised number (i.e. greater than 0.00000001) for the expected value.

[adistrib-05]

	Description
Message:	Enter a number for both the lower and upper bounds.
Cause:	No number has been entered for either the lower or upper bound of the uniform distribution.
Action:	Enter a numeric value for the lower and upper bounds.

[adistrib-06]

	Description
Message:	The lower bound cannot be greater than the upper bound.
Cause:	A smaller value has been entered for the upper bound of a uniform distribution compared to that entered for the lower bound.
Action:	Enter numeric values for the upper and lower bounds such that the upper bound is greater than the lower bound.

[adistrib-08]

	Description
Message:	The sum of the probabilities must add up to 1.
Cause:	You have entered probability values for the discrete distribution where the sum of all probabilities is not 1.
Action:	Specify the probabilities such that they add up to 1.

[adistrib-09]

	Description
Message:	Enter a valid symbol name.
Cause:	An invalid symbol name has been specified for the discrete distribution (i.e. one which contains invalid characters such as @ or is completely numeric.
Action:	Enter an alphanumeric value for the symbol.

[adistrib-10]

	Description
Message:	Enter a unique symbol name.
Cause:	You have entered a symbol name which you have already used within this discrete distribution.
Action:	Each symbol name within a discrete distribution must be unique - select a different symbol name.

[adistrib-11]

	Description
Message:	Enter a value between 0 and 1. Please note that format is "0,n" or "0.n" - NOT ".n".
Cause:	Either no number, or a number less than zero or greater than 1 has been entered for the probability value in the discrete distribution.
Action:	Please enter a number between 0 and 1. (Format 0,n or 0.n).

[adistrib-13]

	Description
Message:	Syntax error.
Cause:	The distribution defined is not correct.
Action:	Check the correct syntax for the distribution type.

[adistrib-14]

	Description
Message:	Invalid number.
Cause:	A non-numeric value has been entered as part of the distribution instead of a numeric value.
Action:	Enter a numeric value.

[adistrib-15]

	Description
Message:	Invalid symbol.
Cause:	An invalid symbol name has been specified for the discrete distribution (i.e. one which contains invalid characters such as @ or is completely numeric.
Action:	Enter an alphanumeric value for the symbol.

[adistrib-16]

	Description
Message:	Ambiguous symbol.
Cause:	A symbol name which is not unique within this discrete distribution has been entered.
Action:	Ensure that every symbol name is unique within a discrete distribution.

[adistrib-17]

	Description
Message:	No object selected!
Cause:	No object was selected in resource assignment.
Action:	Select the object(s) to be assigned to the resource.

[adistrib-19]

	Description
Message:	Expression is syntactically incorrect!
Cause:	The AQL expression for resource assignment is syntactically incorrect.
Action:	Correct the AQL expression or use the input support to create an AQL expression with the correct syntax.

[adistrib-20]

	Description
Message:	The current performer can only be selected alone.
Cause:	You have attempted to use the expression "current performer" with other objects.
Action:	Either select "current performer" or the other objects.

[adistrib-23]

	Description
Message:	Expression syntactically incorrect!
Cause:	The AQL expression in the "Performer" field is syntactically incorrect.
Action:	Check the AQL syntax or re-enter the performer required using the input support.

[adistrib-28]

	Description
Message:	Invalid value. Times must be entered in the format yy:ddd:hh:mm:ss.
Cause:	You have entered a time value in an invalid format.
Action:	Enter a time value in the correct format (yy:ddd:hh:mm:ss).

[adistrib-29]

	Description
Message:	Invalid value. The year may not be higher than 999999.
Cause:	Too high a value has been entered for the year.
Action:	Enter value less than or equal to 999999 for the year.

[adistrib-30]

	Description
Message:	Error while creating a new inter-reference: The maximum number of references for this attribute to model type <model type> is <number>.
Cause:	The maximum number of references for this attribute to models of the specified type has been exceeded.
Action:	Delete another reference or contact your ADOxx administrator or consultant if you would like to increase this maximum number.

[adistrib-31]

	Description
Message:	Error while creating a new inter-reference:! The maximum number of references for this attribute to objects of class<class name> in model type <model type> is <number>.
Cause:	The maximum number of object references from this attribute has been exceeded.
Action:	Delete any unnecessary object references or contact your ADOxx consultant.

[adistrib-34]

	Description
Message:	Error when creating a new inter model reference: The maximum number of references authorised for this attribute is <number>!
Cause:	You have attempted to create a new inter model reference, although the INTERREF attribute already contains the maximum number of references authorised for this attribute.
Action:	If there is an unnecessary reference in this INTERREF attribute, you must delete it first.

[adistrib-35]

	Description
Message:	The transition condition contains errors: Unknown comparison operator! Hint: Names of variables must not contain blanks.
Cause:	The transition condition is syntactically not correct.
Action:	Correct the error.

[adistrib-36]

	Description
Message:	The value for the process time contains errors: The expected format is YY:DDD:HH:MM:SS!
Cause:	The format of the process time in comparison within the transition condition is not correct.
Action:	Enter a process time in ADOxx time format YY:DDD:HH:MM:SS.

[adistrib-37]

	Description
Message:	The value for the day time contains errors: The expected format is hh:mm:ss!
Cause:	The format of the day time in comparison within the transition condition is not correct.
Action:	Enter a day time in format hh:mm:ss.

[adistrib-38]

	Description
Message:	The value for "Date-time" is invalid. The value must be in format "YYYY:MM:DD hh:mm:ss" and you must keep within the following value range: Year: 0001 - 9999, month: 01 - 12, day:01 - 31 Hour: 00 - 23, minute: 00 - 59, second: 00 - 59.
Cause:	You have entered an invalid value in an attribute of the type "Date-time" (i.e. invalid format or outside the authorised value range .
Action:	Enter the value using the format "YYYY:MM:DD hh:mm:ss" and observe the above described value range.

[adistrib-39]

	Description
Message:	The value for "Year" is too big. Values between 0001 and 9999 are authorised.
Cause:	In an attribute of type "Date-time", you have entered a value for "Year", which is outside the authorised value range.
Action:	Enter a value between 0001 and 9999 for the year.

[adistrib-40]

	Description
Message:	The value for "Date" is invalid. The value must be in format "YYYY:MM:DD" and you must keep to the following value range: Year: 0001 - 9999, month: 01 - 12, day: 01 - 31.
Cause:	You have entered an invalid value for the date in an attribute of type "Datum" (DATE) (i.e. invalid format or outside the authorised value range.
Action:	Enter the value in format "YYYY:MM:DD" and observe the above described value range.

[adistrib-41]

	Description
Message:	The value for "Days" is too big. The maximum allowed value is 364 days.
Cause:	In an attribute of type "Time", you have entered a value for "Days", which is outside the valid range.
Action:	Enter a value between 0 and 364 for the days.

[adistrib-42]

	Description
Message:	The value for "Hours" is too big. The maximum allowed value is 23 hours.
Cause:	In an attribute of type "Time", you have entered a value for "Hours", which is outside the valid range.
Action:	Enter a value between 0 and 23 for the hours.

[adistrib-43]

	Description
Message:	The value for "Minutes" is too big. The maximum allowed value is 59 minutes.
Cause:	In an attribute of type "Time", you have entered a value for "Minutes", which is outside the valid range.
Action:	Enter a value between 0 and 59 for the minutes.

[adistrib-44]

	Description
Message:	The value for "Seconds" is too big. The maximum allowed value is 59 seconds.
Cause:	In an attribute of type "Time", you have entered a value for "Seconds", which is outside the valid range.
Action:	Enter a value between 0 and 59 for the seconds.

adocase

[adocase-01]

Message:	Error initialising Case/4/0. Check the following information: <error-specific description>
Cause:	A system error occurred while trying to start the case/4/0 interface or to initialise case/4/0.Possibly your system does not fulfill the software requirments.
Action:	Note the error description. Check that your system fulfills all software requirements.

adynattr

[adynattr-01]

Message:	Error with access to a dynamic attribute!
Cause:	A fatal error has occurred.
Action:	If this error re-occurs on starting simulation again, please export your models to an ADL file and contact your ADOxx consultant.

[adynattr-02]

Message:	Illegal type for dynamic attribute!
Cause:	A fatal error has occurred.
Action:	If this error re-occurs on starting simulation again, please export your models to an ADL file and contact your ADOxx consultant.

[adynattr-03]

Message:	Error during the access to internal representation of a dynamic attribute!
Cause:	A fatal error has occurred.
Action:	If this error re-occurs on starting simulation again, please export your models to an ADL file and contact your ADOxx consultant.

adynpred

[adynpred-01]

Message:	Activity was not yet executed! <Activityclass name>:<object name> Model:<model name>
Cause:	In the specified activity, the attribute "Performer" contains an AQL expression which references "performer of" another activity. However the activity referenced here has not yet been executed and so the performer cannot be evaluated.
Action:	Correct the entry in the "Performer" attribute of the specified activity.

aeadsply

[aeadsply-01]

Message:	The diagram cannot be displayed, the names of the columns and rows are not unique. The following names are not unique. <terms>
Cause:	The names of the columns and rows are not unique.
Action:	Update the entries so that the names of the columns and rows are unique.

[aeadsply-04]

Message:	A result with this name already exists. You may not use duplicate names for results.
Cause:	You have specified a name for a result function which is not unique within this agent.
Action:	Enter a different name for the result.

[aeadsply-05]

Message:	This is not a valid filename. Please select another file name.
Cause:	An invalid filename was entered for the result.
Action:	Enter a valid filename or deactivate the calculation of this result.

[aeadsply-06]

Message:	The result history cannot be displayed.
Cause:	You want to show the development of the agents results graphically. An error occurred while building this graphic.
Action:	Contact your ADOxx consultant. If you know in which file the results are saved, then also send this file to your ADOxx consultant.

[aeadsply-07]

Message:	Please enter a valid time string. Time values have to be entered in the following format: yy:ddd:hh:mm:ss where "yy" specifies the number of years, "ddd" specifies the number of days, "hh" the number of hours, "mm" the number of minutes and "ss" the number of seconds.
Cause:	You have entered a time value in an invalid format.
Action:	Please enter the time in a valid format.

[aeadsply-08]

Message:	The name of a result that should be animated has changed. Please select the result again.
Cause:	You have specified a result function for animation within this agent. However following the creation of this agent, the function has been changed or deleted.
Action:	Select the result functions which should be animated.

[aeadsply-09]

Message:	Please select an object class or remove the result "<result name>" from this agent.
Cause:	You must select a class for the result function.
Action:	Select a class or delete the result function.

[aeadsply-10]

Message:	The name of this agent is not unique. Please select another name.
Cause:	You are attempting to define two agents with the same name within your model.
Action:	Select a different name for this agent.

[aeadsply-11]

Message:	You have not selected any objects to be observed yet.
Cause:	You have not selected any objects to be observed for this agent.
Action:	Select the register "Basic configuration" and select the objects which you would like this agent to observe.

[aeadsply-12]

Message:	You have to select at least one result and at least one object.
Cause:	You have selected no results or no objects.Therefore no diagram can be shown.
Action:	Select at least one object and at least one result.

[aeadsply-13]

Message:	"<result term>". Syntax error in the specified formula.
Cause:	There is a syntax error in the specified formula.
Action:	Correct the formula.

[aeadsply-14]

Message:	"<result term>". The specified formula contains an invalid result name
Cause:	An invalid result formula was entered or the result formula was changed after it was specified.
Action:	Correct the formula.

[aeadsply-16]

Message:	No agents may be created in this model.
Cause:	You have attempted to create agents in a model which cannot be simulated.
Action:	Insure that the active model window refers to a model that can be simulated.

[aeadsply-17]

Message:	Error in agent customising: The keyword AGENT must be followed by the name of the defined agent type.
Cause:	A predefined agent contains errors.
Action:	Contact your ADOxx administrator. The agent definition must be corrected in the library management component of the ADOxx Development Toolkit.

[aeadsply-19]

Message:	A maximum of 50 graphs can be displayed at the same time. Any surplus graphs will be ignored.
Cause:	The animation of agent results and the presentation of the result history is in the form of function graphs.A maximum of 50 graphs can be displayed at the same time.However under the current conditions, more than 50 graphs are required to be displayed.
Action:	End the simulation and open the configuration window of the relevant agent. Decrease the detail grade of the result functions which should be displayed.

[aeadsply-20]

Message:	Agent could not be copied.
Cause:	The selected agent could not be copied.
Action:	Export the model in which the Agent is specified to ADL and then contact your ADOxx consultant.

[aeadsply-21]

Message:	The agent could not be inserted.
Cause:	Insertion of a previously copied agent is not possible.
Action:	Save the model from which the agent was copied and the model in which you want to insert the agent to an ADL file, note the name of the agent and contact your ADOxxconsultant.

[aeadsply-23]

Message:	Please select an attribute or remove the result function "<result>" from this agent.
Cause:	You must select an attribute for the agent specified.
Action:	Select an attribute or delete the agent.

aeagents

[aeagents-02]

	Description
Message:	Error in a combining function of an agent.
Cause:	A result function of type "Animation" or "Special formula" could not be initialised. The agent concerned is configured incorrectly. Perhaps the agent was imported from an ADL file which contained errors.
Action:	Cancel the simulation, open the start window of the simulation again and click on the button "Agents".Open the configuration window of each agent marked here as incorrect and correct the configuration errors. As soon as you close the configuration windows again you will be informed if you have overlooked possible configuration errors. Correct these and start the simulation again.Note: To avoid similar problems in the long run, you should export the models simulated to an ADL file and inform your ADOxx consultant.

[aeagents-05]

	Description
Message:	All specified result functions of the current agent could not be saved. (Too many functions have been specified). The configuration window of the current agent will show you which functions were saved successfully.
Cause:	You tried to assign too many result functions to an agent. On average, about 15 functions can be assigned to an agent. Note: The exact number depends on both the types of result functions assigned and the manner in which result functions, which were already assigned, were configured. There is no fixed upper limit for the number of possible result functions in an agent.)
Action:	Check which result functions had been assigned successfully and which were not by using the tab cards in the configuration window of the agent and those which were not. Remove unnecessary result functions.

[aeagents-06]

	Description
Message:	The result names of the following agent are not unique:"<Agent name>"
Cause:	An agent is configured incorrectly. Perhaps the agent was imported from an invalid ADL file or you used a predefined agent, the definition of which is incorrect.
Action:	Open this agent's configuration window and change the result name of all result functions so that all result names are unambiguous.

[aeagents-07]

	Description
Message:	The following result will not be generated: "<Name of the result function concerned>:<Name of the result not generated>"
Cause:	A result, which serves as basis for the result function listed, cannot be generated. The result function may have been configured incorrectly.
Action:	Cancel the simulation and then open the start window of the simulation again. Click on the button "Agents".and correct the configuration of all the agents marked as incorrect in the window "Agents overview".

[aeagents-08]

	Description
Message:	The configuration string of an agent could not be decoded. The following result type was not recognised:"<Unknown result type>"
Cause:	An agent is configured incorrectly. Perhaps the agent was imported from an invalid ADL file or you used a predefined agent, the definition of which is incorrect.
Action:	Correct the configuration of all the agents marked here as incorrect in the window "Agents Overview" (menu "Edit" - option**"Agents"**).

[aeagents-09]

	Description
Message:	An agent result cannot be determined due to one of the following reasons: the agent is located in a recursively called process, the agent is located in a subprocess which was called in a parallel way within the execution of one and the same main process. Result: "<Result name>" (Process: "<Process name>")
Cause:	The model structure simulated cannot be evaluated by one of the agents created. There are two possible reasons for this: 1. the model in which the agent was created is called recursively. That is, the model calls itself again (maybe via other subprocesses). 2. the agent was created in a subprocess and this subprocess is called from a super ordinated process in a parallel way. To put it in a more general context this means that two (or more) instances of a (sub)process which orginate from the same main process instance, are executed simultaneously.
Action:	Avoid recursive model structures or change your model structures accordingly. Avoid calling subprocesses in a parallel way within a model structure.One way to avoid a parallel structure is to move the agent from the subprocess, which is called in a parallel way, to the directly super ordinated process and assign the subprocess call objects as observed objects to the agent.

[aeagents-10]

	Description
Message:	Error when evaluating the simulation through an agent.The generation of the following result has been deactivated to avoid further error messages: "<Result name>"
Cause:	An unexpected error occurred while the result listed was calculated. Generation of this result has been cancelled.
Action:	Note the result name listed, export the models simulated to an ADL file and inform your ADOxxconsultant.

aeagnrl

[aeagnrl-01]

Message:	An error has occurred. Please contact your ADOxx consultant.
Cause:	An unexpected error occurred in the agent function.
Action:	Please note under which circumstances the error occurred and inform your ADOxx consultant.

[aeagnrl-02]

Message:	A result function could not be identified.
Cause:	The configuration data of an agent is incorrect.
Action:	Open the window "Agent overview" and correct the configuration of all the agents maked as incorrect.

[aeagnrl-04]

Message:	Agent specific settings could not be decoded.
Cause:	An agent is configured incorrectly.
Action:	Open the window "Agent Overview" and correct the configuration of all the agents marked as incorrect here.

[aeagnrl-06]

Message:	The evaluation calendar of the agent is corrupt.
Cause:	An agent is configured incorrectly. Perhaps the agent was imported from an invalid ADL file or you use a predefined agent, the definition of which is incorrect.
Action:	Open the window "Agent Overview" and correct the configuration of all the agents marked as incorrect here. Hint: To avoid this error in the future, you should inform your ADOxx consultant. The agent definition in the ADOxx Development Toolkit is probably incorrect and must be corrected.

[aeagnrl-08]

Message:	No simulation results are available.
Cause:	The agent selected did not calculate results.
Action:	You have probably already received other error messages concerning this agent. Correct these errors.As soon as all errors are corrected, the agent will calculate results again.

[aeagnrl-11]

Message:	All result functions could not be applied to the agent.
Cause:	You tried to assign further result functions to an agent. Not all the result functions selected could really be assigned. Perhaps you tried to assign too many result functions to the agent.
Action:	Check which of the result functions were assigned successfully and which were not by using the tab cards in the agent's configuration window. Should you have assigned a large number of result functions to an agent, consider whether you can remove some of them. Only assign those result functions which are really needed to the agent.

[aeagnrl-13]

Message:	This model was loaded in read-only mode. This is why the action cannot be carried out. Load the model with write access.
Cause:	You loaded the model concerned in read-only mode.You can only execute the action if you have read-write access to the model.
Action:	Close the model and then reload it with read-write access. Then repeat the action.

[aeagnrl-14]

Message:	The configuration values of this agent are corrupt.
Cause:	The agent you are currently editing is configured incorrectly.
Action:	Should you have just tried to create a predefined agent, please contact your ADOxx administrator.The agent definition is incorrect and must be corrected in the Library Management of the ADOxx Development Toolkit. If this is not the case, open this agent's configuration window and check the configuration. As soon as you close the window again, you will be informed about possible configuration errors.

[aeagnrl-15]

Message:	The definition of an agent's observed objects is invalid.
Cause:	An agent is configured incorrectly. Perhaps the agent was imported from a corrupt ADL file or you are use a predefined agent, the definition of which is incorrect
Action:	Cancel the simulation, re-open the start window of the simulation and click on the button "Agents". In the window "Agent Overview", assign new objects to be observed to all agents marked as incorrect. Start the simulation again.

[aeagnrl-18]

Message:	There are too many settings for this agent. Select fewer objects to be evaluated or results to be created. You can also distribute the tasks to several agents.
Cause:	The agent has been assigned too many reference objects and/or tasks. The configuration of the agent therefore is too extensive and cannot be saved.
Action:	Assign less tasks to the agent. Distribute/split the tasks among several agents.

aearslt

[aearslt-01]

Message:	The following file could not be opened with write access: "<filename>"
Cause:	An agent was instructed to record the result history of one of its results. The agent could not open the file in which the result history should be saved. This could be due to one of the following reasons: 1.The file exists already and is write-protected. 2. The filename is incorrect. 3.The disk is full or has not been inserted.
Action:	Depending on the cause, act according to one of the following recommendations: 1. Remove the write-protection from the existing file. (Attention:This means the file can be over-written any number of times in the future!) 2. Correct the filename in the configuration window of the agent concerned. 3.Clear some storage space on the disk or insert a disk. Hint: If you close the error message and do not correct the error, the result history will not be recorded.

[aearslt-02]

Message:	Error when writing the file "<filename>".The disk may be full.
Cause:	An agent was instructed to record the result history of one of its results. An error occurred during the simulation, while the result history was being saved.The disk is either full or was removed. Note:In the case of very large models and long simulation duration the file containing the result history can also become very large. Even if you thought prior to the simulation that there was enough empty space on the disk, this may have been utilised already.
Action:	Cancel the simulation and then empty some storage space for the result history file. **Note:**If you close the error message and don't correct the error, the result history will not be recorded.

[aearslt-03]

Message:	Error reading the file "<filename>".
Cause:	During the simulation an agent recorded the result history of one of its results in the file listed. Now this result history is to be displayed graphically.For this reason it is being read in again from the file.An error occurred, while the file was read in. Perhaps the disk on which the result history was saved has been removed.
Action:	Insert the disk again and restart the display of the result history.

aeasubag

[aeasubag-02]

	Description
Message:	The following result generating function of an agent has not been configured completely and is thus deactivated:"<result name>"
Cause:	You use a predefined agent. This agent's definition is incorrect
Action:	Cancel the simulation, then open the start window of the simulation again and click on the button "Agents".The window "Agent overview" opens up. Correct the configuration of all agents marked as incorrect here.

Hint: To avoid this error in the future, you should note down the result name listed (and the agent type concerned, if you know it) and inform your ADOxx consultant. The agent definition in the Library Management of the ADOxxDevelopment Toolkit is probably incorrect and must be corrected.

[aeasubag-03]

	Description
Message:	The initialisation of an agent failed. The result "<result name>" cannot be initialised because "<name>" is not a valid name. Please contact your ADOxx administrator.
Cause:	You are using a predefined agent. An invalid name was used within the definition of this agent.
Action:	Note down the result and the name listed (and also the agent type concerned, if you know it) and inform your ADOxx consultant. The agent definition in the Library Management of the ADOxx Development Toolkit must be corrected.

[aeasubag-04]

	Description
Message:	The following result cannot be generated because not all results on which this result is based are available: "<Name of the Result Function Concerned>"
Cause:	The calculation formula in the result function listed is incorrect. It references other result functions which do not exist
Action:	Open the configuration window of the concerned Result Function and correct the calculation formula.

[aeasubag-05]

	Description
Message:	The following result cannot be generated because of a syntax error in the required formula: "<Result function name>"
Cause:	The calculation formula for the result function listed is incorrect. It contains a syntax error.
Action:	Open the configuration window of the agent concerned and correct the calculation formula.

[aeasubag-06]

	Description
Message:	Some specified calendars are too complex. The following result cannot be generated: "<Result name>"
Cause:	The calendars of performers, resources and/or agents in the models simulated are too complex. The result listed( which is always of the type "Workload") therefore cannot be calculated
Action:	Use a smaller number of different day profiles in the calendars.

[aeasubag-07]

	Description
Message:	"<Result name>" This result cannot be generated. (Possibly other results which are required for the generation are not available under the current settings.)
Cause:	An agent's result could not be generated. This may be for one of the following reasons: 1.The result listed could not be initialised. In this case, you already received an appropriate error message at the beginning of the simulation. 2. The result was calculated based on other results. One or more of these other results is not available. Either an error occurred while the result not available was being calculated (in this case, you already received an appropriate error message at the beginning of the simulation), or the result not available cannot be displayed under the current settings of the result representation (That is the most probable cause.)
Action:	Depending on the cause: 1. Correct the error that was originally reported. 2.Change the settings concerning the result representation. Please note that some results can only be represented "per <time period>" (such as "per year"). As long as the option "per process" is selected, these results will not be available. Then display the results of the agent concerned again.

[aeasubag-08]

	Description
Message:	The formula for the result "<result name>" contains too many different result names. The formula cannot be evaluated.
Cause:	A calculation formula may contain at most 26 different results. This upper limit was exceeded by the calculation formula of the result function listed.
Action:	Simplify the calculation formula.

aevalrel

[aevalrel-02]

Message:	Wrong value at the from object.
Cause:	You have entered a non-numeric value as the filter for the from-object in the relation table for a numeric attribute.
Action:	Enter a number.

[aevalrel-03]

Message:	Wrong value at the to-object.
Cause:	You have entered a non-numeric value as the filter for the to-object in the relation table for a numeric attribute.
Action:	Enter a number.

[aevalrel-04]

Message:	Wrong value at the relation.
Cause:	You have entered a non-numeric value as the filter for the relation in the relation table for a numeric attribute.
Action:	Enter a number.

[aevalrel-05]

Message:	Error in application library.
Cause:	The definition of the selected relation table contains errors in the application library.
Action:	Contact your ADOxx administrator or your ADOxx consultant.

aevkres

[aevkres-01]

Message:	Error in audit trail (line <line number>): The process "<process name>" was not found.
Cause:	An error occurred while reading the audit trail.An unknown process was referenced.
Action:	Replace the invalid process with a valid one in the audit trail.

[aevkres-02]

Message:	Error in audit trail (row <line number>): The process instance "<instance name>" was not found.
Cause:	An error occurred while reading the audit trail.An unknown instance was referenced.
Action:	Replace the invalid instance name with a valid one in the audit trail.

[aevkres-03]

Message:	Error in audit trail (line <line number>): The activity "<activity name>" could not be found.
Cause:	An error occurred while reading the audit trail.An unknown activity was referenced.
Action:	Replace the invalid activity name with a valid one in the audit trail.

[aevkres-04]

Message:	Error in audit trail (line <line number>): The activity instance "<instance name>" could not be found.
Cause:	An error occurred while reading the audit trail.An unknown activity instance was referenced.
Action:	Replace the invalid instance name with a valid one in the audit trail.

[aevkres-05]

Message:	Error in audit trail (line <line number>): The file is not a valid audit trail.
Cause:	A syntax error occurred while reading the audit trail.
Action:	Correct the syntax in the specified line of the audit trail.

[aevkres-06]

Message:	Error in audit trail (line <line number>): This line is too long. A maximum of 1023 characters is allowed.
Cause:	The audit trail contains a line with more than 1023 characters.
Action:	Check the specified line and reduce it.

aexinst

[aexinst-01]

Message:	Parameter not satisfactory. The syntax:<file to create><new file> <ADOxx Excel file 1> <ADOxxExcel file 2> {<Excel path>}
Cause:	An error has occurred during the installation.
Action:	Contact your ADOxx administrator.

aexpappl

[aexpappl-01]

	Description
Message:	The attribute "Documentation configuration" contains errors (row <no:>)! The format model has been ignored, since a required attribute is missing: <attribute name>
Cause:	The content of the library attribute "Documentation configuration" is faulty: An attribute of the class "__LibraryMetaData__" of the D library is referenced but does not exist.
Action:	Contact your ADOxx administrator.

[aexpappl-06]

	Description
Message:	Error during the creation of the help file.
Cause:	These temporary files are created in the current directory or in the directory at which the enviroment variable TEMP is pointing.
Action:	Ensure that the enviroment variable TEMP exists and points to a directory in which enough memory space is available and in which you are allowed to create files.

[aexpappl-08]

	Description
Message:	The file <File name> does not exist!
Cause:	During the ADOxx customising, it was determined that one or more files (e.g. graphic logo files) should be copied from the installation directory to the target directory. The file specified in the error message could not be opened.
Action:	Verify your ADOxx installation using the file list and create or complete if necessary missing or damaged files.

Hint: The documentation process will continue despite this error but the generated documentation contents will not contain data related to the damaged or missing files e.g. a logo.

[aexpappl-10]

	Description
Message:	The attribute "documentation configuration" is faulty! The name of the format model is missing, the format model has been ignored.
Cause:	In the attribute "documentation configuration", no name was specified during the definition of a format model (using a FORMAT or an EXPORT element).
Action:	Correct this error using the Development Toolkit or contact your ADOxx administrator.

[aexpappl-13]

	Description
Message:	The attribute "documentation configuration" contains errors (row <no:>)! The element "<element name>" is faulty.
Cause:	In the attribute "Documentation configuration", an invalid name was entered.
Action:	Correct the spelling of the element name or delete the invalid element using the Development Toolkit or contact your ADOxx administrator.

[aexpappl-14]

	Description
Message:	The attribute "Documentation configuration" contains errors (row <no:>)! SOURCE elements must always be inside an EXPORT element.
Cause:	In the attribute "documentation configuration", an element was entered at the wrong position.
Action:	Correct the error using the Development Toolkit or contact your ADOxx administrator.

[aexpappl-15]

	Description
Message:	The attribute "Documentation configuration" contains errors (row <no:>)! The SOURCE element "<element name>" does not exist.
Cause:	In the attribute "Documentation configuration", an invalid element name was given to a SOURCE element.
Action:	Correct the element name using the Development Toolkit or contact your ADOxx administrator.

[aexpappl-16]

	Description
Message:	The attribute "Documentation configuration" contains errors (row <no:>)! LIBRARY elements must be inside SOURCE "Model" elements.
Cause:	In the attribute "Documentation configuration", an element was entered at the wrong position.
Action:	Correct the error using the Development Toolkit or contact your ADOxx administrator.

[aexpappl-17]

	Description
Message:	Error in the attribute "Documentation configuration". The attribute "<attribute name>" does not exist.
Cause:	The content of the library attribute "Documentation configuration" is faulty: An attribute from the class "__LibraryMetaData__" of the D library is referenced but does not exist.
Action:	Contact your ADOxx administrator.

[aexpappl-18]

	Description
Message:	Error in the attribute "Documentation configuration". Characteristics <Characteristics name>.The attribute <attribute name> has the wrong type.
Cause:	In the library attribute "Documentation configuration", an attribute of the class "__LibraryMetaData__" of the D library is referenced but has the wrong type.
Action:	Contact your ADOxx administrator.

[aexpappl-19]

	Description
Message:	Error in the attribute "Documentation configuration". Characteristics <characteristics name>. The value "<value denomination>" is not allowed in the attribute "<attribute name>". Valid values are: <value area>
Cause:	In the library attribute "Documentation configuration", an enumeration attribute of the class "__LibraryMetaData__" of the D library is referenced but its value area contains invalid values.
Action:	Contact your ADOxx administrator.

[aexpappl-20]

	Description
Message:	Error in the attribute "Documentation configuration". The value "<value denomination>" is not allowed in the attribute "<attribute name>. Valid values are: <value area>
Cause:	In the library attribute "Documentation configuration", an enumeration attribute of the class "__LibraryMetaData__" of the D library is referenced but its value is not in the valid area.
Action:	Contact your ADOxx administrator.

[aexpappl-21]

	Description
Message:	Error in the attribute "Documentation configuration". Characteristics <characteristics name>. The attribute "<attribute name>" is not a class attribute.
Cause:	The content of the attribute "Documentation configuration" is faulty: An attribute from the class "__LibraryMetaData__" of the D library is referenced but is not a class attribute.
Action:	Contact your ADOxx administrator.

[aexpappl-22]

	Description
Message:	The file "<file name>" could not be opened!
Cause:	A file required for the documentation generation could not be opened.
Action:	Verify your ADOxx installation using the file list and replace or complete if necessary missing or damaged files.

[aexpappl-23]

	Description
Message:	The file "<file name>" could not be overwritten! Make sure that the directory to which the file should be written does exist and that you own the required write access rights.
Cause:	The target file specified for the documentation could not be opened with write access.
Action:	Verify the write access to the target directory, in which the file will be generated. You can create documentation only in directories for which you own write access. Then verify, if a file with the specified name exists already in the target directory and delete this file if necessary.

[aexpappl-25]

	Description
Message:	Invalid Value: The value "<Value>" could not be saved.
Cause:	The configuration of the documentation generation is faulty.
Action:	Contact your ADOxx administrator.

[aexpappl-26]

	Description
Message:	Error in the application library: No documentation export was defined for the menu item "<name>".
Cause:	No format model exists in the attribute "Documentation configuration" for the menu item called (using a FORMAT or EXPORT element).
Action:	Control the spelling of the menu items called and if necessary correct errors or adapt the attribute "documentation configuration" using the Development Toolkit or contact your ADOxx administrator.

[aexpappl-27]

	Description
Message:	The class "__LibraryMetaData__" does not exist.
Cause:	The class "__LibraryMetaData__" required for the documentation generation does not exist in the Dlibrary .
Action:	Contact your ADOxx administrator.

[aexpappl-28]

	Description
Message:	The user settings could not be saved to the database, since the user profile exceeds the maximum length.
Cause:	The database attribute to save the user-specific settings is not large enough to store all settings.
Action:	The user settings could not be saved to the database.

Hint: The settings carried out for the documentation are lost after you close ADOxx. But the settings are valid for the documentation which will be immediately generated.

[aexpappl-29]

	Description
Message:	An error has occurred during the conversion of the library attribute "Documentation configuration": The attribute "<attribute name>" could not be created in the class "_Library MetaData_".
Cause:	An attribute with the specified name already exists in the class "_Library MetaData_".
Action:	Contact your ADOxx administrator.

[aexpappl-30]

	Description
Message:	Error in the command "EXEC_ACFILTER"! The attribute "<attribute name>" does not exist within the class "_Library MetaData_".
Cause:	The specified attribute is referenced within the AdoScript command EXEC_ACFILTER, but does not exist.
Action:	Contact your ADOxx administrator.

[aexpappl-31]

	Description
Message:	The converted library attribute "Documentation configuration" could not be saved to the database as it is too long.
Cause:	The configuration of the Documentation Component is too big to be converted.
Action:	Carry out a manual conversion of the library attribute or simplify the configuration by deleting single menu items.

[aexpappl-32]

	Description
Message:	Error in the application library: No settings dialogue has been defined.
Cause:	No format model (using the DIALOG element) exists in the attribute "documentation configuration" for the called menu item.
Action:	Correct the error if necessary (adapt the attribute "documentation configuration" using the Development Toolkit) or contact your ADOxx administrator.

[aexpappl-33]

	Description
Message:	The settings for the attribute- and class filter could not be saved, as the length of the settings exceeds the maximum length allowed for the attribute "<Attribute name>" of the class "__LibraryMetaData__".
Cause:	The settings you have defined in the attribute and class filter cannot be saved to the ADOxx database, because of their size.
Action:	When carrying out the settings in the attribute and class filter, use the predefined mode (button "Load mode") to reduce the complexity and therefore the size.

[aexpappl-34]

	Description
Message:	Error in the attribute "documentation configuration", Characteristics "<characteristics>". The value "<value>" of the attribute "<attribute name1>" has not been defined in the attribute "<attribute name2>".
Cause:	The specified value can also be the name of an attribute (attribute name2) which contains the domain.
Action:	Define the value in the domain or change the value of the attribute to a value from the domain.

[aexpappl-35]

	Description
Message:	The target directory "<directory name>" is not a valid directory.
Cause:	The specified directory name is invalid.
Action:	Specify a valid directory name. (The characters / \ : * ? < > and **|**are not allowed in directory names.)

[aexpappl-36]

	Description
Message:	No LOG file could be created! Documentation generation will continue.
Cause:	The creation of the LOG file is wrong.
Action:	Verify if a file with this name exists already and if it is write-protected or already opened. If necessary, verify if you possess write rights on the target directory and if there is enough memory available in the hard disc.

[aexpappl-37]

	Description
Message:	The file "<file name>" is referenced in the "documentation configuration" with "copy", but has not been specified in the "requirefile" area. Contact your ADOxx administrator.
Cause:	The specified file has been listed in the library attribute "documentation configuration" as a copy parameter and not as a "requirefile" parameter.
Action:	In the ADOxx Development Toolkit, define the specified file in the library attribute "documentation configuration" as a "requirefile" parameter or contact your ADOxx administrator.

[aexpappl-38]

	Description
Message:	The ADOxx installation directory cannot be used as a target directory.
Cause:	You have selected the ADOxx installation directory as the target directory for the documentation generation or the export. This is not allowed for security reasons.
Action:	Select another target directory. If you have write access rights only on the ADOxx installation directory, create a sub directory in it and select a file as target file in this sub directory.

[aexpappl-39]

	Description
Message:	The format of the font table "<file name>" is not valid. The default font table will be used.
Cause:	A codepage conversion table you wanted to use contains an error and is thus invalid.
Action:	Contact your ADOxx administrator.

aexpdlg

[aexpdlg-01]

Message:	The user specific settings are inconsistent. Standard values will be loaded.
Cause:	The user profile is in an inconsistent state.This can happen e.g., if a user is assigned to a new application library.
Action:	Close the error message, standard values will be loaded and carry out the settings in the attribute and class filter again.

aexplore

[aexplore-01]

Message:	Error while moving a model group! "<Model group>" can not be moved to "<target model group>".
Cause:	Either the target model group is write-protected or a subgroup of the group to be moved.
Action:	Move model groups only into other groups where you have write-access to and which are no sub groups of the group to be moved.

[aexplore-02]

Message:	Error while copying a model group! "<Model group>" can not be copied to "<target model group>".
Cause:	Either the target model group is write-protected or a subgroup of the group to be copied.
Action:	Copy model groups only into other groups where you have write-access to and which are no sub groups of the group to be copied.

[aexplore-03]

Message:	Error while copying model groups! Just disjoint model groups can be copied in one go.
Cause:	When copying a model group, all sub groups are automatically copied with it. Thus when selecting model groups for copying, it is neither allowed nor expedient to select sub groups.
Action:	Adjust your model group selection accordingly.

[aexplore-04]

Message:	Error while creating a new model group! Access permissions to the parent model group may have been changed or the parent model group may have been deleted by another user. Refresh the model explorer, then try again.
Cause:	Creating a new model group is not possible, as your selected parent group is no longer accessible. Either this group was deleted in the meantime by another user or the access rights were changed by the ADOxx administrator.
Action:	Refresh the model group view before creating new model groups.

[aexplore-05]

Message:	Error while moving a model group! Model group 1 is already contained in Model group 2. Therefore it cannot be moved to that model group.
Cause:	The model group was moved to the same model group it was contained in originally.
Action:	Make sure you selected the right model groups.

[aexplore-06]

Message:	Error while moving a model group! The target model group Model group 2 already contains a model group with name Model group 1.
Cause:	The model group selected was moved to a different model group which already contains another model group with the same name. Therefore the action has been cancelled.
Action:	Rename one of the two model groups before trying to move it again. Alternatively only move the content of the model group and subsequently delete the then empty group.

aexport

[aexport-01]

	Description
Message:	Unable to open export file.
Cause:	The file to be exported could not be created, since the data storage medium specified is either write-protected or full.
Action:	Remove the write-protection from the data carrier/medium or create some new space or assign a valid file name and restart the export.

[aexport-05]

	Description
Message:	No models were exported.
Cause:	Due to errors during the loading process no models were exported.
Action:	Quit ADOxx and restart it. If the error message re-occurs during the next attempt, please inform your database administrator.

[aexport-06]

	Description
Message:	Unknown model type.
Cause:	An unknown model type was encountered during the export process. Possibly, the connection to the ADOxxdatabase was aborted.
Action:	Quit ADOxx and re-start it. If the error message re-occurs during the next attempt, please inform your database administrator.

[aexport-07]

	Description
Message:	Unknown library type.
Cause:	An unknown library type was encountered during the export process. Possibly, the connection to the ADOxx database was aborted.
Action:	Quit ADOxx and re-start it. If the error message re-occurs during the next attempt, please inform your database administrator.

[aexport-08]

	Description
Message:	Error in export:<Error>
Cause:	The error listed occurred during the export process.Possibly, the connection to the ADOxx database has been aborted.
Action:	Quit ADOxx and re-start it. If the error message re-occurs during the next attempt, please inform your database administrator.

[aexport-10]

	Description
Message:	Error writing to file "<filename>".
Cause:	During the export process an error occurred while writing to the file specified.
Action:	There is possibly not enough space left on the data carrier/medium. If there is still enough space, start the export process again.

[aexport-11]

	Description
Message:	Error in library "<library name>". Do you want to continue anyway?
Cause:	During the export process an error occurred either while a library was about to be loaded or while determining the libraries assigned.
Action:	Cancel the export process and re-start it. If you continue the export process, the ADL file will not contain the relevant model groups access information.

[aexport-12]

	Description
Message:	Error when exporting files belonging to the library!
Cause:	When loading a file belonging to the library from the ADOxx database, a serious error has occurred.The connection to the database may be aborted.
Action:	Close ADOxx, start it again and repeat the export.Should the message appear again, contact your database administrator.

[aexport-13]

	Description
Message:	Error while reading data from the database. The connection to the database may be broken. Please restart product name. If the error occurs again afterwards, please contact your product name customer support.
Cause:	The connection to the database may be broken.
Action:	Restart product name. Should the problem occur again, contact your product name customer support.

[aexport-14]

	Description
Message:	The export has been aborted. The user "Admin" must not be exported. Repeat the export without the user "Admin".
Cause:	The user "Admin" must not be exported.
Action:	Repeat the export without the user "Admin".

aexpsort

[aexpsort-01]

Message:	Class <class name> The attribute specified as sort criteria <Attribute name> does not exist. The default value will be used. Should this message be shown again in the future?
Cause:	Your application library contains errors.
Action:	Contact your ADOxx administrator.

[aexpsort-02]

Message:	Class <class name> The attribute specified as sorting criteria <attribute name> is of an invalid type. The default value will be used. Should thus message be shown again in the future?
Cause:	Your application library contains errors.
Action:	Contact your ADOxx administrator.

[aexpsort-03]

Message:	Class <class name>: The attribute specified as a duplicate criterion "<attribute name>" does not exist. The default value will be used. Should this message be shown again in the future?
Cause:	Your application library contains errors.
Action:	Contact your ADOxx consultant.

[aexpsort-04]

Message:	Class <class name>: The attribute specified as a duplicate criterion "<attribute name>" is of an invalid type. The default value will be used. Should this message be shown again in the future?
Cause:	An attribute of an invalid type is defined as duplicate criterion in your application library.
Action:	Contact your ADOxx consultant.

afile

[afile-01]

	Description
Message:	The file <file name> could not be opened with read access.
Cause:	An error occurred, when attempting to open the specified file with read access.
Action:	Verify, whether the specified directory as well as the specified file exist and whether you possess the required access rights to this file.

[afile-02]

	Description
Message:	The file <file name> could not be opened with write access. The file may be used by another program.
Cause:	An error occurred, when attempting to open the specified file with write access.
Action:	Verify, whether the specified file is currently opened, whether the specified directory as well as the specified file exist and whether you possess the required access rights for this file.

[afile-03]

	Description
Message:	Error when reading the file "<file name>".
Cause:	An error occurred when reading the specified file.
Action:	Repeat the process. Should the error appear again, manually copy the specified file to the target directory. If successful, verify your ADOxxinstallation using the file list. If necessary, reinstall ADOxx.

[afile-04]

	Description
Message:	Error when reading the file "<file name>".
Cause:	An error occurred when writing the specified file to the target directory.
Action:	Verify if there is enough memory space available in the target directory. If the target directory is a network drive, check if there is still a connection.Then repeat the process.

[afile-05]

	Description
Message:	The file "<file name>" could not be deleted.
Cause:	An error has occurred when deleting the specified file.
Action:	Verify, if the specified directory and/or the specified file exist, if you have the required rights to delete this file and if the file is already opened.

[afile-06]

	Description
Message:	The file "<file name>" does not exist.
Cause:	The specified file could not be found.
Action:	Verify if the specified directory and/or the specified file exist and whether you have the required rights to access this file.

[afile-07]

	Description
Message:	The file "<file name>" exists already.
Cause:	You have attempted to create or copy the specified file.
Action:	The file will be created only if the already existing file has been renamed or deleted.

[afile-08]

	Description
Message:	The file "<file name>" cannot be closed.
Cause:	An error has occurred when trying to close the specified file.
Action:	Repeat the process or contact your ADOxx administrator.

[afile-09]

	Description
Message:	No temporary file could be created.
Cause:	An error has occurred when trying to create a temporary file in the temporary folder.
Action:	Verify if enough memory space is available in the hard disk, if the system variable "TEMP" is set and if you have the required access rights for the directory specified in the system variable "TEMP".

[afile-10]

	Description
Message:	The file name "<file name>" is invalid.
Cause:	The specified file name is not in a correct format or contains invalid characters.
Action:	When entering file names, make sure that total length of paths and file names does not exceed 120 figures and no more than seven directories are contained in the path.Moreover, the characters / \ : * ? < > and **|**are not valid.

[afile-11]

	Description
Message:	The file "<file name>" could not be renamed.
Cause:	An error has occurred when attempting to rename the specified file.
Action:	Verify if a file with the same name already exists. If necessary assign another file name.

[afile-12]

	Description
Message:	The file "<file name>" could not be moved.
Cause:	An error has occurred when attempting to move the specified file.
Action:	Verify if the specified directory exists and if a file with the same name is contained in this directory.

[afile-13]

	Description
Message:	The specified database directory is invalid.
Cause:	The database directory you have specified could not be found.
Action:	Verify the specified database directory and correct your entry accordingly.

[afile-14]

	Description
Message:	The file "<file name>" could not be accessed, since it is not open!
Cause:	You have tried to access a file which is not open.
Action:	Open the file before you access it.

[afile-16]

	Description
Message:	The file "<file name>" already exists for the library "<library name>".
Cause:	You have tried to import or to copy the specified file to the folder of the specified application library.
Action:	The file can only be imported or copied with the specified name once the file already existing in the folder of the application library has been renamed or deleted.

[afile-17]

	Description
Message:	The name of the file "<file name>" is too long.
Cause:	The file <file name> could not be stored in the database because the name of the file is too long.
Action:	Adjust the length of the file name accordingly.Note that the length of the external file name within the library (including the file extension) and the length of the library name must not exceed 249 characters.

afilemgt

[afilemgt-01]

	Description
Message:	No file name has been entered!
Cause:	You have not specified a file name for the export file.
Action:	Enter the name of the export file.

[afilemgt-02]

	Description
Message:	The specified directory name is invalid!
Cause:	For the export of a file, you have specified a path which does not exist.
Action:	Enter a valid (=existing) path for the export.

[afilemgt-03]

	Description
Message:	The file <file name> does not exist!
Cause:	The specified path and/or file name for the import does not exist.
Action:	Enter the correct file name and/or path of an existing file.

[afilemgt-04]

	Description
Message:	An error has occurred when importing the file "<file name>" to the database. The import will be aborted.
Cause:	During the import, a database or a network error has occurred.
Action:	If a database error message has also previously suddenly been shown, note the error information and contact a system administrator. Restart the application and repeat the process.

[afilemgt-05]

	Description
Message:	An error has occurred during the export of the file "<file name>" from the database. The export will be aborted.
Cause:	During the export, a database or a network error has occurred.
Action:	If a database error message has also previously suddenly been shown, note the error information and contact a system administrator. Restart the application.

[afilemgt-06]

	Description
Message:	An error has occurred when renaming the file "<file name>". The file has not been renamed.
Cause:	When renaming the file, a database or network error has occurred.
Action:	If a database error message has also previously suddenly been shown, note the error information and contact a system administrator. Restart the application and repeat the process.

agdt

[agdt-01]

	Description
Message:	An error has occurred when sorting the start model!
Cause:	The model could not be sorted. Connectors are possibly missing in the model to be arranged.
Action:	Check the model to be arranged for missing connectors and repeat the process. Should the error appear again, close ADOxx and start it again. If the error is not corrected, contact your ADOxx administrator.

[agdt-02]

	Description
Message:	Positions could not be assigned!
Cause:	An error occurred, while positions were being assigned
Action:	Quit ADOxx and start it again. Should this error re-occur, contact your ADOxx administrator.

[agdt-03]

	Description
Message:	Bend-points could not be inserted!
Cause:	An error occurred while the bend-points were being inserted.
Action:	Should this error re-occur, align the connectors without inserting bend-points or contact your ADOxx administrator.

[agdt-04]

	Description
Message:	Positions could not be assigned with bend-points!
Cause:	An error occurred while positions with bend-points were being assigned.
Action:	Quit ADOxx and start it again. Should this error re-occur, contact your ADOxx administrator.

[agdt-05]

	Description
Message:	Method median-down could not be applied!
Cause:	An error occurred while the median-down method was being applied.
Action:	Quit ADOxx and start it again. Should this error re-occur, align the connectors without applying the median-down method or contact your ADOxx administrator.

[agdt-06]

	Description
Message:	Median-up method could not be applied!
Cause:	An error occurred while the median-up method was being applied.
Action:	Quit ADOxx and start it again. Should this error re-occur, align the connectors without applying the median-up method or contact your ADOxx administrator.

[agdt-07]

	Description
Message:	Pairwise exchange could not be applied!
Cause:	An error occurred while pair wise exchange was being applied.
Action:	Quit ADOxx and start it again. Should this error re-occur, align the connectors without applying pairwise exchange or contact your ADOxx administrator.

[agdt-08]

	Description
Message:	Pendulum-down method could not be applied.
Cause:	An error occurred while the pendulum-down method was being applied.
Action:	Quit ADOxx and restart it. Should this error re-occur, align the connectors without applying the pendulum-down method or contact your ADOxx administrator.

[agdt-09]

	Description
Message:	Pendulum-up method could not be applied!
Cause:	An error occurred while the pendulum-up method was being applied.
Action:	Quit ADOxx and start it again. Should this error re-occur, align the connectors without applying the pendulum-up method or contact your ADOxx administrator.

[agdt-10]

	Description
Message:	Horizontal mirror could not be applied!
Cause:	An error occurred while applying the horizontal mirror.
Action:	Quit ADOxx and start it again. Should this error re-occur, contact your ADOxx administrator.

[agdt-11]

	Description
Message:	Vertical mirror could not be applied!
Cause:	An error occurred while applying the vertical mirror.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-12]

	Description
Message:	It was not possible to arrange downwards!
Cause:	An error occurred while arranging downwards.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-13]

	Description
Message:	It was not possible to arrange upwards!
Cause:	An error occurred while arranging downwards.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-14]

	Description
Message:	It was not possible to arrange to the right!
Cause:	An error occurred while arranging to the right.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-15]

	Description
Message:	It was not possible to arrange to the left!
Cause:	An error occurred while arranging to the left.
Action:	Quit ADOxx and start it again, contact your ADOxx administrator.

[agdt-16]

	Description
Message:	The rubber band method could not be applied!
Cause:	An error occurred while applying the rubber band method.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-18]

	Description
Message:	Cycle minimisation could not be applied!
Cause:	An error occurred while applying cycle minimisation.
Action:	The model contains too many cycles and therefore may not be arranged in the current form. Try to simplify the model and to reduce the number of cycles.

[agdt-19]

	Description
Message:	New model could not be written!
Cause:	An error occurred while the newly arranged model was about to be transferred.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-20]

	Description
Message:	At least one relation couldn't be inverted according to the parameter value!
Cause:	An error occured while attempting to turn the relations of the model according to the parameter value.
Action:	Change the parameter values of the alignment function or contact your ADOxx administrator.

[agdt-22]

	Description
Message:	Process-hierarchy could not be generated because two objects would have the same name!
Cause:	An attempt was made to create an object with a name currently assigned to an existing object.
Action:	Delete the model, into which the process hierarchy was to be generated and then start generating the process hierarchy again.

[agdt-23]

	Description
Message:	Could not position one object of the model to be arranged!
Cause:	An error occurred while positioning the object.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-24]

	Description
Message:	Could not number the objects of the model!
Cause:	An error occurred, while the model objects were being numbered.
Action:	Quit and restart ADOxx. Should this error re-occur, contact your ADOxx administrator.

[agdt-26]

	Description
Message:	The selected model contains no model object to be arranged! No arrangement could be carried out.
Cause:	The arrangement function has been used on a model which contains no object and therefore has been closed.
Action:	Use the arrangement function only on models with objects you want to re-place.

[agdt-27]

	Description
Message:	The selected model contains no model references to be displayed as a process-hierarchy!
Cause:	You selected a model without model references for generating a graphical process hierarchy.
Action:	Insert the necessary model references or select a different model.

[agdt-28]

	Description
Message:	The selected model involves no objects for numbering! Cannot number objects.
Cause:	You selected a model which does not contain any objects or objects which are not defined for numbering when attempting to number the objects.
Action:	Model the object to be numbered or select a different model.

[agdt-29]

	Description
Message:	Name missing after the key word "<profile>"!
Cause:	In the configuration of the arrangement function, a profile and a name have been defined. The profile is either an arrangement profile PROFILE, a hierarchy profile HIERPROFILE or an enumeration profile ENUMPROFILE.
Action:	Once you have specified a profile in the configuration of the arrangement function, you need to give a name to the profile. Specify the name between double quotation marks or if necessary contact your ADOxx administrator.

[agdt-30]

	Description
Message:	Faulty initialising with expression for the key word "<element>"!
Cause:	The specified element could not be initialised.The error appears, when an element of the same name has already been defined, when a previous definition refers to the same model type/the same class, relation etc. or when the specified model type/the specified class/relation class does not exist. Element is one of the following syntax elements: PROFILE, CLASSPAIRPAR, HIERPROFILE,HIERmodel type, ENUMPROFILE, ENUMmodel type, ENUMCLASS or ENUMREL.
Action:	Verify the configuration of the arrangement function and if necessary contact your ADOxx administrator.

[agdt-31]

	Description
Message:	Wrong key word "<key word>"!
Cause:	The specified key word is not authorised in this context or makes no sense here.
Action:	Verify the configuration of the arrangement function and if necessary contact your ADOxx administrator.

[agdt-32]

	Description
Message:	Faulty value after the key word "<key word>"!
Cause:	This error appears for one of the following reasons: The name of the model type has not been specified or is invalid (for HIERmodel type, ENUMmodel type, CLASSmodel type, DEFmodel typeor CLASSPAIRmodel type). The name of the attribute, the class or the relation is missing or is invalid (for CLASSPAR, CLASSPAIRPAR,HIERATTRIB, HIERCLASS, HIERUSECLASS,HIERUSEREL, HIERUSEATTRIB, ENUMCLASS or ENUMREL). The parameter dist: for DOUBLEDPhas not been specified. The parameter **vertdist:**for CHNGSIZE has not been specified. The parameter use: for HIERPROFILEor usetype: for HIERmodel typehas not been specified, the profile or the model type does not exist.
Action:	Check/complete the configuration of the application function and if necessary contact your ADOxx administrator.

agenpar

[agenpar-01]

Message:	Syntactical error! '(' expected!
Cause:	An opening bracket is expected for the parse of a random generator.
Action:	Check if an opening bracket is missing in the expression you have specified and if necessary insert it.The second row of the error message indicates where in ADOxx a bracket is expected.

[agenpar-02]

Message:	Syntax error! ')' expected!
Cause:	When translating a random generator, a closing bracket was expected.
Action:	Check that the syntax of your given expression is correct and insert the required closing bracket. The second line of the error message gives you an idea of where in ADOxx a bracket is expected.

[agenpar-03]

Message:	The argument for an exponential distribution cannot be 0!
Cause:	You have entered 0 as the argument for an exponential distribution. This value is not permitted.
Action:	Replace the 0 with another value.

[agenpar-04]

Message:	The first argument of a uniform distribution must be smaller than the second!
Cause:	The first argument which you have entered for a uniform distribution is smaller than the second.
Action:	Check that you have entered the arguments in the correct order.

[agenpar-05]

Message:	Syntax error! Character string or ' expected!
Cause:	When translating a random generator, a single quotation mark or a character string was expected.
Action:	Check if you are missing a character string or quotation mark from your expression and add in whatever is missing. The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-06]

Message:	Syntax error! ' expected!
Cause:	During translation of a random generator a quotation mark was missing.
Action:	Check if you are missing a quotation mark from your expression and add it in where necessary. The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-07]

Message:	Syntax error! Constant, variable or distribution expected!
Cause:	When checking a random generator, a constant, variable or distribution was expected.
Action:	Check if you have left out a constant, a variable or a random generator from your expression. The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-08]

Message:	Syntax error! Multiplication or division are not defined for character strings!
Cause:	You are attempting to multiply or divide variables or constants which are characters within the expression you have entered.
Action:	Change the type of the variable referenced by the expression, replace the constants with numerical constants or replace the multiplication or division operator with one which is valid for character strings (e.g. +).

[agenpar-09]

Message:	Syntax error! Addition or subtraction of two terms of different types!
Cause:	The expression you have entered attempts to add or subtract two variables or constants of different types.
Action:	Change the type in the variable referenced by this expression so that the operation can be carried out.

[agenpar-10]

Message:	Syntax error! Subtraction is not defined for character strings!
Cause:	You are attempting to subtract variables or constants which are strings within the expression you have defined.
Action:	Change the type in the variable referenced by this expression or change the constant to a numeric constant or change the operator to one which is permitted for character strings in order that the operation can be carried out.

[agenpar-11]

Message:	Syntax error! Semicolon or end expected!
Cause:	ADOxx expects an end to your expression or a semicolon as a divider between two expressions.
Action:	If you wish to specify more than one expression in your random generator, specify these by semicolons. If this is not required, check that you have not forgotten to enter an operator between two terms. The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-12]

Message:	Syntax error! Numeric parameter expected!
Cause:	ADOxx expected a numeric parameter as an argument for the distribution.
Action:	Replace the specified argument with a numeric constant.Variables or constants are not permitted in this case.The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-13]

Message:	Syntax error! Semicolon expected!
Cause:	When translating a random generator, a semicolon was expected.
Action:	Check where you are missing a semicolon from your expression and add it in where necessary. The second line of the error message gives you an idea of where in ADOxx this is expected. A semicolon can also be used to separate a number of expressions in a random generator.

[agenpar-14]

Message:	Syntax error! Character string expected!
Cause:	ADOxx expected a character string as parameter to the distribution.
Action:	Replace the appropriate argument with a character string. Variables or constants which begin with a figure are not permitted in this case. The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-15]

Message:	Syntax error! Probability expected!
Cause:	ADOxx expected a probability as argument to the distribution.
Action:	Replace the appropriate argument with a probability.Variables or characters are not allowed in this case.The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-16]

Message:	A probability must be between 0 and 1!
Cause:	You have entered a probability which is smaller than 0 or greater than 1.
Action:	Replace the probability with a valid value.Please note that probability must be entered as 0.n or 0,n. The second line of the error message gives you an idea of where in ADOxx this is expected.

[agenpar-17]

Message:	The sum of the probabilities must be 1!
Cause:	The sum of the probabilities of a discrete distribution must be exactly 1.
Action:	Change the probabilities of the created symbols of the discrete distribution so that they sum to 1.

[agenpar-18]

Message:	The arrival time cannot be negative.
Cause:	If a uniform distribution is used then the lower bound must not be smaller than 0.
Action:	When using a uniform distribution to determine the arrival times, the arguments used must be positive.

[agenpar-19]

Message:	The upper bound must be greater than 0!
Cause:	When using a uniform distribution to specify arrival frequency, then upper bound must be greater than 0.
Action:	Increase the value of the upper bound (second argument) so that it is greater than 0.

aglochan

[aglochan-01]

Message:	No objects matching the criteria were found.
Cause:	The evaluation of the predefined or user-defined criteria did not find any result objects.
Action:	Formulate the selection criteria so that at least one object is found.

[aglochan-02]

Message:	Select at least one attribute.
Cause:	No attribute to be changed was selected from that attribute list.
Action:	Select at least one attribute so that the change can be executed.

[aglochan-04]

Message:	Attributes could not be changed.
Cause:	An error occurred while trying to update the attributes.
Action:	Close the model and open it again. Try to update the attributes once more. If the error re-occurs contact your system administrator.

[aglochan-05]

Message:	The selection contains objects or connectors of different types or relations. Please change criteria to select only objects or connectors of the same type.
Cause:	The selection criteria contains objects of different types. The global change is only possible for attribute of objects of a class or connectors of a relation class.
Action:	Change the selection criteria so that only objects of one type or connectors of one relation class are selected.

[aglochan-06]

Message:	Invalid input for attribute<attribute name>:<attribute value>
Cause:	An invalid value was entered for the attribute given - e.g. a value of the wrong type.
Action:	Enter a valid value.

[aglochan-08]

Message:	The selected attribute combination is not allowed.Please select an attribute combination with at least one activated change mode.
Cause:	The selected attributes have no possible changes in common.
Action:	Select only attributes which have at least one change mode in common.

[aglochan-09]

Message:	Please select one attribute which should be changed.
Cause:	When "Taking over" an attribute, the attribute to which the value should be copied has not been specified.
Action:	Please select an attribute to which the input attribute should be "taken over".

[aglochan-11]

Message:	The AQL expression is syntactically incorrect!
Cause:	The AQL expression to find the objects to be changed is syntactically incorrect.
Action:	Enter a syntactically correct AQL expression.

[aglochan-12]

Message:	There are no changeable attributes!
Cause:	The class of the object to be changed contains no attributes. A change is therefore not possible.
Action:	Select other objects.

[aglochan-13]

Message:	Wrong floating point value!
Cause:	The entered value is not a valid floating point.
Action:	Enter a valid floating point value.

[aglochan-14]

Message:	Wrong time value!
Cause:	The entered time value does not correspond with the ADOxx time format (yy:ddd:hh:mm:ss).
Action:	Enter a value in ADOxx time format.

[aglochan-15]

Message:	The value 0 is not allowed for the division!
Cause:	A division by 0 is not possible.
Action:	Enter a value for the divisor which is not 0.

agogo

[agogo-01]

	Description
Message:	At first the keyword "GRAPHREP" has to appear,but the attribute value starts with "<Text>"!
Cause:	The specified attribute contains errors.
Action:	This error can be fixed in the ADOxx Development Toolkit or please contact your ADOxx administrator.

[agogo-02]

	Description
Message:	"<Text>" is not a keyword!
Cause:	The value assigned to the specified attribute during customising contains errors.
Action:	This error can be fixed in the ADOxx Development Toolkit or please contact your ADOxx administrator.

[agogo-03]

	Description
Message:	"<Text>" is not the name of an attribute!
Cause:	The value assigned to the specified attribute during customising contains errors.
Action:	This error can be fixed in the ADOxx Development Toolkit or please contact your ADOxx administrator.

[agogo-04]

	Description
Message:	"<Keyword>" cannot be used together with COMPOUND!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. Only LINE, POLYLINE and CURVE can be used together with COMPOUND.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-05]

	Description
Message:	Illegal numeric parameter in _<keyword>_element! An integer value > 0 has to be specified.
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. The number of points in the case of POLYLINE / POLYGON must be greater than 0.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-06]

	Description
Message:	<Keyword> without IF!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. ELSIF, ELSE or ENDIF used without previous IF.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-07]

	Description
Message:	IF without ENDIF!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-08]

	Description
Message:	<keyword> is just defined for relations!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. EDGE, START, MIDDLE or END in the definition of the graphic representation of a class.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-10]

	Description
Message:	IF with multiple ELSE branches!
Cause:	The customised attribute value contains the syntax/semantics error described. A defined IF sequence contains more than one ELSE branches. While multiple ELSIF statements are possible, only one ELSE condition is allowed.
Action:	Fix the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-11]

	Description
Message:	<Keyword> without block - element sequence enclosed in curly braces is missing!
Cause:	The customised attribute value contains the syntax/semantics error described. FOR or WHILE loops without element sequence in curly braces ("{ .. }").
Action:	Fix the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-12]

	Description
Message:	<Keyword> without WHILE!
Cause:	The customised attribute value contains the syntax/semantics error described. ENDWHILEwas used without preceeding WHILE statement.
Action:	Fix the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agogo-13]

	Description
Message:	"<Name>" is not the name of a model type group!
Cause:	The customised attribute value contains the syntax/semantics error described. The model type group name specified in the HOTSPOT definition of the Method Diagram does not comply with any existing name of a model type group.
Action:	Fix the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

agolam

[agolam-01]

Message:	The arrangement algorithm <Algorithmname> cannot be aplied on <Modelname> because the model already contains swimlanes!
Cause:	The model has already been arranged with swimlanes.
Action:	Arrange the model without swimlanes first and then arrange it with swimlanes again.

[agolam-02]

Message:	Missing parameter: <parametername>!
Cause:	The paramater was not defined.
Action:	Use an appropriate parameter.

[agolam-03]

Message:	<Classname> is not a swimlane class' name!
Cause:	The used classname is not a swimlane class' name.
Action:	Use an appropriate classname.

[agolam-04]

Message:	<Attributename> is not a object reference's class name!
Cause:	The used attribute is not a object reference's class name!
Action:	Use an appropriate objectname.

[agolam-05]

Message:	<Modeltypename> is not a model type name!
Cause:	The used modeltypename is not a model type name!
Action:	Use an appropriate modeltypename.

[agolam-06]

Message:	_<Variantname>_is not a variant name!
Cause:	The used variantname is not a variant name!
Action:	Use an appropriate variantname.

[agolam-07]

Message:	<Algorithmuname> is not a layout algorithm name!
Cause:	The used algorithmname is not a layout algorithm name.
Action:	Use an appropriate algorithmname.

agolay

[agolay-03]

	Description
Message:	"<Text>" is not a keyword!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agolay-04]

	Description
Message:	Missing layout for "<keyword>"!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. HEAD, BITMAP, PAGE or FOOT, without having previously introduced LAYOUT.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agolay-05]

	Description
Message:	Region "<keyword>" defined twice!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. HEAD, BITMAP, PAGE or FOOT definition twice in LAYOUT.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agolay-06]

	Description
Message:	Missing region for "<keyword>"!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. TEXT, ATTR or FONT, without having previously introduced a region (HEAD, ...).
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agolay-07]

	Description
Message:	Necessary region "PAGE" is missing in layout "<Name>"!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. A layout must always contain a PAGE definition.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[agolay-08]

	Description
Message:	At layout "<name of layout>" specified attribute_"<attribute name>"_ is not existing or is of the wrong type!
Cause:	The customised attribute value contains the syntax/semantics error described. In the page layout definition <name of layout> the GraphRep attribute <attribute name> was specified. However, this attribute does not exist in the class "__ModelTypeMetaData__".
Action:	Fix the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

agraph

[agraph-01]

Message:	Print-Error: Unable to connect to printer.
Cause:	The operating system could not establish a connection to the printer.
Action:	Check the connection to the printer or the printer itself. Contact your system administrator if necessary.

[agraph-02]

Message:	All attribute and result values selected for the representation are 0. A diagram with such values can not be displayed.
Cause:	All attribute and result values selected for the representation are 0. A diagram with such values can not be displayed.
Action:	At least one of the attribute or result values to be represented must be greater than 0. Select a set which contains at least one attribute or result value greater than 0 from the sets of results to be represented.

[agraph-03]

Message:	Error while copying the graphic to the clipboard:There is not enough available memory.
Cause:	There is not enough memory available to copy the graphic to the clipboard.
Action:	Exit some other programs and try again.

[agraph-04]

Message:	An error has occurred when writing the file "<file name>". The file name is possibly not allowed or the data carrier is full.
Cause:	An error has occurred when writing on the specified file. The cause is either there is not enough memory in the target drive or an error when accessing to the file or a faulty target medium.
Action:	Verify the file name and make sure that there is enough memory space available in the target drive (you need at least, depending on the output format, from 100KB to 10MB).Make some free space in memory or check if a not write- protected medium is enclosed in the target drive as long as you are dealing with an interchangeable data medium.

ahaconv

[ahaconv-01]

	Description
Message:	"<Token ()>" is not a key word!
Cause:	There is a syntactical error in a class attribute "__Conversion__", which is required for the transformation of objects to another class.
Action:	Verify and correct the "__Conversion__" attribute.

[ahaconv-02]

	Description
Message:	"<Name>" is not the name of class that can be instanced!
Cause:	A not existing class is specified in a class attribute "__Conversion__", which is required for the transformation of objects to another class.
Action:	Verify and correct the "__Conversion__" attribute.

[ahaconv-03]

	Description
Message:	The attribute "<attribute name>" (<class name>) does not exist!
Cause:	A not existing attribute is specified in a class attribute "__Conversion__", which is required for the transformation of objects to another class.
Action:	Verify and correct the "__Conversion__" attribute.

[ahaconv-04]

	Description
Message:	The attribute "<attribute name 1>" (<class name 1>) and "<attribute name 2>" (<class name 2>) are not of the same type!
Cause:	A conversion indication, which is not realisable, is specified in a class attribute "__Conversion__", which is required for the transformation of objects to another class.
Action:	Verify and correct the "__Conversion__" attribute.

[ahaconv-05]

	Description
Message:	The attributes are not based on the same record class: "<Attribute name 1>" (<Class name 1>): "<Record class 1>" "<Attribute name 2>" (<Class name 2>): "<Record class 2>"
Cause:	In the class attribute "__Conversion__", used for converting objects from one class to another, a statement has been made which cannot be executed.
Action:	Check and correct the "__Conversion__" attribute.

[ahaconv-06]

	Description
Message:	The attributes are not based on the same attribute profile class: "<Attribute name 1>" (<Class name 1>): "<Attribute profile class 1>" "<Attribute name 2>" (<Class name 2>): "<Attribute profile class 2>"
Cause:	In the class attribute "__Conversion__", used for converting objects from one class to another, a statement has been made which cannot be executed.
Action:	Check and correct the "__Conversion__" attribute.

[ahaconv-07]

	Description
Message:	The following attribute cannot be converted as not all enumeration values are defined in the target attribute: From "<Attribute name 1>" (<Class name 1>) to "<Attribute name 2>" (<Class name 2>)
Cause:	In the class attribute "__Conversion__", used for converting objects from one class to another, a statement has been made which cannot be executed.
Action:	Check and correct the "__Conversion__" attribute.

[ahaconv-08]

	Description
Message:	The following attribute cannot be converted as the name of the target attribute is already assigned to another object: From "<Attribute name 1>" (<Class name 1>) to "<Attribute name 2>" (<Class name 2>)
Cause:	In the class attribute "__Conversion__", used for converting objects from one class to another, a statement has been made which cannot be executed. The name used for the instance to be converted cannot be assigned as this name has already been assigned to an object of this class in the model.
Action:	Check and correct the "__Conversion__" attribute.

ahagrob

[ahagrob-01]

	Description
Message:	"<text>" is not a keyword!
Cause:	In the class attribute "Allowed objects" of a swimlane class an unknown keyword is defined.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahagrob-02]

	Description
Message:	"<class name>" is not the name of a class!
Cause:	In the class attribute "Allowed objects" of a swimlane class the name of a undefined class is used with the INCL or EXCL keyword.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahagrob-03]

	Description
Message:	Objects of class "<class name>" may be placed over multiple swimlanes. Therefore class "<class name>" cannot be excluded from swimlane class "<class name of swimlane>"!
Cause:	In the class attribute "Allowed objects" of the specified swimlane class the specified class is excluded although this class can be placed above several swimlanes.Because of the invalid combination (exclusion in the swimlane class - class allowed to be placed above several swimlanes) the exclusion is ignored.
Action:	Correct the class attribute "Allowed objects" in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

ahamot

[ahamot-01]

	Description
Message:	Error in the value of attribute "<attribute name>" (<context>): "<text>" is not a keyword!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahamot-02]

	Description
Message:	Error in the value of attribute "<attribute name>" (<context>): Missing model type for "<keyword>"!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. INCL, EXCL, OR_ASSIGN,AND_ASSIGNor MODE, without having previously introduced model type.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahamot-03]

	Description
Message:	Error in the value of attribute "<attribute name>" (<context>): Name for "<keyword>" is missing!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. Name missing after model type, MODE,OR_ASSIGNor AND_ASSIGN.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahamot-04]

	Description
Message:	Error in the value of attribute "<attribute name>" (<context>): Base model type "<name>" is not defined!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. The model type (name after from:,OR_ASSIGNor AND_ASSIGN) was not defined.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahamot-05]

	Description
Message:	Error in the value of attribute "<attribute name>" (<context>): Base mode "<name>" is not defined!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. The mode (name after from:, OR_ASSIGNor AND_ASSIGN) was not defined.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahamot-06]

	Description
Message:	Error in the value of attribute "<attribute name>" (<context>): "<name>" is not the name of a class or relation class that can be instanced!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified. The name after INCL or EXCL is not a class or relation name. Common mistake:Trying to include or exclude a class which does not belong to the model type at all, while a mode is defined.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahamot-08]

	Description
Message:	The file "<file name>" could not be found!
Cause:	The Bitmap file assigned to a model type does not exist.
Action:	Create the appropriate file or correct the file name.

ahanote

[ahanote-01]

	Description
Message:	Error in the value of attribute "<attribute name>" (<context>): "<text>" is not a keyword!
Cause:	The value defined during customising of the attribute listed contains the syntax error specified.
Action:	Correct the error in the Library Management of the ADOxx Development Toolkit or contact your ADOxx administrator.

[ahanote-02]

	Description
Message:	"<attribute name>" is not the name of an attribute of this class!
Cause:	The specified attribute is contained in the class attribute "AttrRep", but it is not defined for this class.
Action:	Enter in the class attribute "AttrRep" only the attribute, which is also defined in this class.

[ahanote-04]

	Description
Message:	The attribute "<attribute name>" is contained several times!
Cause:	In the class attribute "AttrRep" for the assembly of the ADOxx notebook, the mentioned attribute is defined more than once. In the ADOxx notebook, an attribute cannot be displayed more than once.
Action:	Delete in the class attribute "AttrRep" the concerned ATTR elements, so that the specified attribute appears only once.

[ahanote-05]

	Description
Message:	The user "<User name>" has no access rights for the notebook!
Cause:	You have not sufficient rights to access the ADOxxnotebook of the object/relation.
Action:	Contact your ADOxx administrator.

aicondef

[aicondef-01]

	Description
Message:	Cannot load icon configuration!
Cause:	Possibly the connection to the ADOxx database server has been aborted.
Action:	Repeat the action. Should the error re-occur, please contact your database or system administrator.

[aicondef-02]

	Description
Message:	Cannot save icon configuration!
Cause:	Possibly the connection to the ADOxx database server has been aborted.
Action:	Repeat the action. Should the error re-occur, please contact your database or system administrator.

[aicondef-03]

	Description
Message:	Unknown user!
Cause:	Possibly the connection to the ADOxx database server has been aborted.
Action:	Repeat the action. Should the error re-occur, please contact your database or system administrator.

[aicondef-04]

	Description
Message:	Cannot load quick-access bar configuration from application library!
Cause:	Possibly the application library is defective.
Action:	Repeat the action. Should the error re-occur, please contact your ADOxx administrator.

aimport

[aimport-01]

	Description
Message:	Unable to open import file.
Cause:	The import file could not be opened as the data storage medium specified could not be accessed.
Action:	Check the medium and re-start the import.

[aimport-02]

	Description
Message:	Import of file <path+file name>: error in line <#: <semantic/syntax error> The import process will be aborted.
Cause:	During the import, the specified file contains a semantically or syntactically incorrect definition.This might be due to a default in the specified file or to manual changes within the file.
Action:	The content of the file cannot be imported. If necessary contact your ADOxx consultant.

[aimport-03]

	Description
Message:	Import of file <path+file name>:contains libraries which are not allowed.
Cause:	The ADL-file contains library definitions, which are not allowed.
Action:	The models included in the file cannot be imported.

[aimport-04]

	Description
Message:	A serious error occurred while deleting the erroneous library. Possibly the connection to the database has been aborted. Please exit ADOxx.
Cause:	An error occurred during deletion of an erroneous library.
Action:	Exit ADOxx and inform your database administrator.

[aimport-05]

	Description
Message:	A serious error occurred while deleting the erroneous model. Possibly the connection to the database has been aborted. Please exit ADOxx.
Cause:	A serious error occurred during the deletion of an erroneous model.
Action:	Exit ADOxx, re-start it and redo the import. If the error re-occurs, please contact your database administrator.

[aimport-06]

	Description
Message:	A serious error occurred while loading the old model.Possibly the connection to the database has been aborted.Please exit ADOxx.
Cause:	After an error occurred during the model import (option "Paste into existing models"), the attempt to reload the old model led to a serious error.
Action:	Exit ADOxx, re-start it and redo the import. If the error re-occurs, please contact your database administrator.

[aimport-07]

	Description
Message:	A serious error occurred while restoring the old model.Possibly the connection to the database has been aborted.Please exit ADOxx.
Cause:	After an error occurred during the model import (option "Overwrite existing models"), the attempt to restore the model to be overwritten led to a serious error.
Action:	Exit ADOxx, re-start it and redo the import. If the error re-occurs, please contact your database administrator.

[aimport-08]

	Description
Message:	Import of file<file name>:File contains models which are not allowed.
Cause:	The ABL file contains model definitions, which are not allowed.
Action:	The libraries included in the file cannot be imported.

[aimport-09]

	Description
Message:	Import of file <file name>:invalid format.
Cause:	You tried to import an ADOxx library or an ADL file which is not compatible with your ADOxx version.ADOxx libraries are not directly exchangeable within different ADOxx versions and/or different operating systems.
Action:	Please contact your ADOxx consultant.

[aimport-10]

	Description
Message:	Import of file <file name>: The read-only model <model name> cannot be changed by import.
Cause:	You tried to change a read-only model via model import (option "Overwrite existing models" or "Paste into existing models").
Action:	If the model was loaded read-only, please close it and import the model again. If you have read-only access for the model, please contact your ADOxx administrator.

[aimport-11]

	Description
Message:	No application libraries are defined in the database.Therefore user import is impossible.
Cause:	You tried to import users, without previously importing an application library.
Action:	Import the application library needed and re-start the user import.

[aimport-12]

	Description
Message:	Error when opening the protocol file!
Cause:	An error has occurred when opening the protocol file.The data storage medium specified is possibly write-protected.
Action:	Re-check the protocol file name and/or control the access state of the data medium.

[aimport-13]

	Description
Message:	Error when writing the protocol file "<file name>"!
Cause:	When creating the import protocol file an error has occurred.
Action:	The data medium is possibly full.

[aimport-14]

	Description
Message:	The model group "<model group name>" does not exist! Would you like to skip the setting of the corresponding access right and continue the import?
Cause:	The model group referenced for the UDL import does not exist, i.e. in the UDL file, the access right defined to the specified model group cannot be set.
Action:	Click on the "Yes" button to skip the setting of the access rights of the specified model group and continue the import. Click on the "All" button to skip the setting of the access rights of all non existing model groups and continue the UDL import. If you click on the "No" button, the UDL import will be aborted.

[aimport-15]

	Description
Message:	The libraries contain no classes! An import is therefore not possible.
Cause:	The libraries of the imported ABL file contain no classes.
Action:	Select another ABL file.

[aimport-16]

	Description
Message:	Import of the file<file name>: The user has no access to the model "<model name>"! This cannot be changed by the import.
Cause:	You have attempted to change a model you can not access by ADL import into the data base. This is not permitted.
Action:	Select another import option (e.g.rename) or do not import the specified model.

[aimport-17]

	Description
Message:	Unknown target library! The connection to the database is possibly aborted. Exit ADOxx.
Cause:	When searching for information in the library, into which the ADL file should be imported, a serious error has occurred.
Action:	Exit ADOxx, restart it and repeat the import.Should the message re-appear, contact your database administrator.

[aimport-18]

	Description
Message:	The ADL file is possibly from a versioned library. The import of such a file to a non-versioned library is only possible by explicitly specifying the option 'import-versioned-file'.
Cause:	You have tried to import an ADL file from a versioned library to a non versioned library. In the silent mode of the ADL import via an AdoScript, this is only possible by explicitly specifying the option 'import-versioned-file'.
Action:	Insert the option 'import-versioned-file' to the AdoScript.

[aimport-19]

	Description
Message:	The ADL file is possibly from a versioned library. The import of such a file with the option 'Transfer version number to the model name' is only possible by explicitly specifying the option 'import-versioned-file'.
Cause:	When searching for information of the library to which the ADL file should be imported, a serious error has occurred.
Action:	Insert the additional option 'import-versioned-file' to the AdoScript.

[aimport-20]

	Description
Message:	Invalid target model group!
Cause:	A target model group must be specified for the ADL import via an AdoScript in silent mode, when models or model groups should be imported. You have specified either no or invalid target model groups.
Action:	Specify a valid target model group.

[aimport-22]

	Description
Message:	Invalid target attribute profile group!
Cause:	A target attribute profile group must be specified for the ADL import via an AdoScript in silent mode, when attribute profile groups should be imported. You have specified either no or an invalid target attribute profile group.
Action:	Enter a valid target attribute profile group.

[aimport-24]

	Description
Message:	A serious error has occurred when re-creating the old attribute profile. The connection with the database is possibly aborted. Exit ADOxx.
Cause:	After an error in the attribute profile import (option "Overwrite attribute profiles") you have tried to re-create the overwritten attribute profile, which has led to a serious error.
Action:	Exit ADOxx, restart it and repeat the import.If the message appears again, inform your database administrator.

[aimport-25]

	Description
Message:	A serious error has occurred when deleting the faulty attribute profile. The connection with the database is possibly aborted. Exit ADOxx.
Cause:	After an error in the attribute profile import, you have tried to delete the faulty attribute profile, which has led to a serious error.
Action:	Exit ADOxx, restart it and repeat the import.If the message appears again, inform your database administrator.

[aimport-26]

	Description
Message:	Import of the file <ABL file name>: Error when saving the file belonging to the library "<file name>"!
Cause:	A serious error has occurred during the library import when saving the specified file to the ADOxx database.
Action:	Exit ADOxx, restart it and repeat the import.Note that the length of the external file name within the library (including the file extension) and the length of the library name must not exceed 249 characters in total. If the message appears again, inform your database administrator.

[aimport-27]

	Description
Message:	System user administration could not be initialised!
Cause:	You have been trying to import system users into an ADOxx database with Single-Sign-on functionality, but the operating system does not support Single-Sign-on.
Action:	To import system users into a ADOxx database use an operating system supporting Single-Sign-on (i.e.Windows XP/2000). Please pay attention to the software pre-requisites for Single-Sign-on within the ADOxx installation manual.

[aimport-28]

	Description
Message:	File <file name> cannot be imported! The file cannot be imported, because it was created by an older version of ADOxx. Please contact your ADOxx consultant.
Cause:	You have tried to import an encrypted file (e.g. an application library) into a ADOxx database. The obligatory check revealed that the file comes from an older ADOxx version, but the encryption was changed afterwards. For security reasons, ADOxx does not accept such files.
Action:	The encryption algorithm has to stay the same if the file shall be re-imported. Contact your ADOxx consultant.

[aimport-29]

	Description
Message:	The import is not possible as currently a simulation resp. analytical evaluation is performed!
Cause:	A model which should be overwritten by the import is used by a simulation or an analytic evaluation at the moment.
Action:	Close all windows of the simulation or analytical evaluation and try the import again.

airdom

[airdom-01]

	Description
Message:	The LEO expression is faulty: "<LEO error message>"
Cause:	The LEO expression in the facet "AttributeInterRefDomain" does not correspond with the LEO syntax. Pay attention to the LEO error message.
Action:	Rectify the value of the facet "AttributeInterRefDomain" by adapting theLEO expression or contact your ADOxx administrator.

[airdom-02]

	Description
Message:	The LEO expression must contain at last one domain definition.
Cause:	The LEO expression contains no domain definition.At least one domain definition is always required.
Action:	Rectify the value of the facet "AttributeInterRefDomain", by adapting the LEO expression or contact your ADOxx administrator.

[airdom-03]

	Description
Message:	Only "MODREF" and "OBJREF" are valid keywords.
Cause:	An invalid key word has been specified. Valid key words are "MODREF" and "OBJREF".
Action:	Rectify the value of the facet "AttributeInterRefDomain" by adapting the LEO expression, so that it contains only the key words "MODREF" and "OBJREF" or contact your ADOxx administrator.

[airdom-04]

	Description
Message:	Model references and object references cannot be mixed.
Cause:	The key words "MODREF" and "OBJREF" cannot be used mixed within an attribute.
Action:	Rectify the value of the facet "AttributeInterRefDomain" by adapting the LEO expression, so that the key words "MODREF" and "OBJREF" don't appear together or contact your ADOxx administrator.

[airdom-05]

	Description
Message:	Internal core error.
Cause:	An internal error has occured.
Action:	Contact your ADOxx administrator.

[airdom-06]

	Description
Message:	The specified class does not exist.
Cause:	The specified class name is not valid in the library.
Action:	Rectify the value of the facet "AttributeInterRefDomain" by adapting the LEO expression so that it contains a valid class name or contact your ADOxx administrator.

[airdom-07]

	Description
Message:	The specified model type does not exist.
Cause:	The specified model type is unknown in the current library.
Action:	Rectify the value of the facet "AttributeInterRefDomain" by adapting the LEO expression, so that it contains a valid model type name or contact your ADOxx administrator.

[airdom-08]

	Description
Message:	The specified class does not exist in the specified model type.
Cause:	The specified class does exist, but is not visible in the specified model type.
Action:	Rectify the value of the facet "AttributeInterRefDomain" by adapting the LEO expression, so that it contains a valid class name or contact your ADOxx administrator.

[airdom-09]

	Description
Message:	The maximum number of referenced is not valid.
Cause:	The parameter "max" contains an invalid value.Valid values must be greater than 0.
Action:	Rectify the value of the facet "AttributeInterRefDomain" by adapting the LEO expression or contact your ADOxx administrator.

aleo

[aleo-01]

	Description
Message:	Character expected after backslash '\'! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-02]

	Description
Message:	Closing quotation mark " is missing! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-03]

	Description
Message:	Invalid character:<character>. key word (next element) or Name (next attribute) expected! <Context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-04]

	Description
Message:	<figure> ':' expected! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-05]

	Description
Message:	Value expected after ':' ! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-06]

	Description
Message:	<Text>: Measure unknown! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-08]

	Description
Message:	<Text> is not a keyword! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-09]

	Description
Message:	Unauthorised figure after closing quotation marks '"'! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-10]

	Description
Message:	Unauthorised figure after a bracket closing an expression ')'! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-13]

	Description
Message:	Operand expected! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-14]

	Description
Message:	Closing bracket ')' is missing! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-15]

	Description
Message:	Operator expected! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-16]

	Description
Message:	Closing bracket ')' without opening bracket '('! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-17]

	Description
Message:	Unauthorised figure! <context>
Cause:	The attribute listed (context) was changed during customising (or in the ADL file) and contains the syntax error described
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-18]

	Description
Message:	Division by 0! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-19]

	Description
Message:	Over flow! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-21]

	Description
Message:	Type incompatibility! <function call> <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-22]

	Description
Message:	<Text>: Unknown function! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-23]

	Description
Message:	Wrong number of parameters! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-24]

	Description
Message:	<Text>:Unknown operator! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-25]

	Description
Message:	<Text>: Lower-case letters in a key word! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-26]

	Description
Message:	Under flow when accessing to string! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-27]

	Description
Message:	Over flow when accessing to string! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-28]

	Description
Message:	<figure>: unauthorised figure after a key word! <context>
Cause:	The attribute listed (context) was changed during customisation (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-29]

	Description
Message:	Unauthorised figure after an attribute name! <context>
Cause:	The attribute listed (context) was changed during customisation (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-30]

	Description
Message:	Unauthorised figure after an attribute value! <context>
Cause:	The attribute listed (context) was changed during customisation (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-31]

	Description
Message:	The target of a value assignment must be a variable! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-32]

	Description
Message:	Call of the function error()! <context>
Cause:	The described runtime error has occurred during the evaluation of an expression, which is contained in the value of the specified attribute.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-34]

	Description
Message:	Closing bracket '}' is missing! <context>
Cause:	The attribute listed (context) was changed during customisation (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-35]

	Description
Message:	Closing bracket '}' without opening bracket '{'! <context>
Cause:	The attribute listed (context) was changed during customisation (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-36]

	Description
Message:	The value for <attribute name> is missing or is of the wrong type! Expected: <Attribute type1>, found: <Attribute type2>. <context>
Cause:	The attribute listed (context) was changed during customisation (or in the ADL file) and contains the syntax error described.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-37]

	Description
Message:	Over flow when concatenating two strings! The maximum possible length of a string contains 65529 characters.
Cause:	The string made from the concatenation is too long to be saved to a string variable.
Action:	Change the concerned command or expression, so that the created string will not be too long.

[aleo-38]

	Description
Message:	Overflow while calculating an expression! The expression is too complex and cannot be calculated.
Cause:	The expression has a nesting depth and/or a number of operands greater than 250.
Action:	Simplify the expression or contact your ADOxx administrator.

[aleo-39]

	Description
Message:	<Name of variable>: is not initialised! <Name of function>
Cause:	Calling the function <Name of function> changes an array (areplace, aappend). However the variable <Name of variable> is not defined as an array.
Action:	Initialize the variable listed as an array before the function call or contact your ADOxx administrator.

[aleo-40]

	Description
Message:	Parameter list without function!
Cause:	A part of the expression is interpreted as a parameter list without a function name in front of it.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-41]

Message:	<Text>:Unknown directive!
Cause:	An unknown directive is used. A directive is a keyword with @ in front of it.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-42]

Message:	<Typ>.<Property>:Unknown property!
Cause:	Trying to access a not existing object property with an point-operator.
Action:	Correct the error described or contact your ADOxx administrator.

[aleo-43]

Message:	@INCLUDE:<Filename> could not be opened!
Cause:	Possible reasons why this error occurs: the file doesn't exist or the file can't be read because of missing user rights.
Action:	Correct the error described or contact your ADOxx administrator.

alib2sgm

[alib2sgm-01]

	Description
Message:	The file could not be opened.
Cause:	The file specified for the storage of browser contents could not be opened.
Action:	The data carrier may be write protected. Delete the write protection and try to save the browser contents again. If necessary contact your system administrator.

[alib2sgm-02]

	Description
Message:	No file name has been entered!
Cause:	You have not specified a file name for the export file of a library.
Action:	Enter the name of an export file.

[alib2sgm-03]

	Description
Message:	The directory name entered is invalid!
Cause:	You have entered a not existing path for the export of a library.
Action:	Enter a valid (=existing) path for the export.

alibchk

[alibchk-01]

	Description
Message:	The facet "<facet name>" is faulty!
Cause:	A facet, which should immediately be assigned a value, is empty.
Action:	Contact your ADOxx administrator.

[alibchk-02]

	Description
Message:	unknown type of the facet "<facet name>":<TypNr>.
Cause:	A facet contained in the library has an invalid type.
Action:	Note the facet name and type and contact your ADOxx administrator.

[alibchk-03]

	Description
Message:	Attribute values of type STRING cannot contain more than 3699 characters.
Cause:	The value of a STRING attribute is too long.
Action:	Reduce the value entered.

[alibchk-04]

	Description
Message:	Attribute values of type LONGSTRING cannot contain more than 32000 characters.
Cause:	The value of a LONGSTRING attribute is too long.
Action:	Reduce the value entered.

[alibchk-05]

	Description
Message:	Attribute values of type INTEGER must be integer.
Cause:	The value of an INTEGER attribute is not integer.
Action:	Verify the value and correct typing errors.

[alibchk-06]

	Description
Message:	Attribute values of type DOUBLE can only be floats.
Cause:	The value of a DOUBLE attribute is not in the valid format.
Action:	Verify the value and correct typing errors .

[alibchk-07]

	Description
Message:	Attribute values of type TIME must have the following format: YY:DDD:HH:MM:SS (Year:day:hours:minutes:seconds)
Cause:	The value of a TIME attribute is not in the valid format.
Action:	Correct the attribute value.

[alibchk-08]

	Description
Message:	The facet "<facet name>" is not assigned a value. It must be assigned with a name of a record class.
Cause:	The specified facet is not assigned with a valid value.
Action:	Contact your ADOxx administrator.

[alibchk-09]

	Description
Message:	The name "<record name>" of the facet "<facet name>" does not correspond with any existing record class.
Cause:	The specified facet is not assigned a valid value.
Action:	Contact your ADOxx administrator.

[alibchk-10]

	Description
Message:	The facet "<facet name>" must be assigned with a positive integer value.
Cause:	The specified facet is not assigned a valid value.
Action:	Contact your ADOxx administrator.

[alibchk-11]

	Description
Message:	The value (<value>) of the attribute "<attribute name>" is not in the valid value area.
Cause:	The specified attribute value is not in the authorised value area.
Action:	Correct the attribute value, so that it is in the valid value area.

[alibchk-12]

	Description
Message:	The attribute "<attribute name>" of the record class or attribute profile class "<name>" is not valid.
Cause:	No valid notebook string has been specified for the specified record.
Action:	Contact your ADOxx administrator.

[alibchk-13]

	Description
Message:	The attribute "<attribute name>" referenced via the submodel pointer does not exist in the class "<class name>" !
Cause:	The attribute referenced via the submodel pointer doesn't exist.
Action:	Contact your ADOxx administrator.

[alibchk-14]

	Description
Message:	In the class "<class name>", the attribute "<Attributname>" referenced via the submodel pointer is not of the type INTERREF!
Cause:	In the specified class, the attribute referenced via the submodel pointer is not of the type INTERREF!
Action:	Contact your ADOxx administrator.

[alibchk-15]

	Description
Message:	There is no attribute "<attribute name>" defined in the class "<class name>" !
Cause:	A required class attribute is not defined.
Action:	Contact your ADOxx administrator.

[alibchk-16]

	Description
Message:	The value of the facet "<facet name>" is too long ("<n>" characters)! Facet values cannot be longer than "<m>" characters.
Cause:	The value of a facet is too long.
Action:	Contact your ADOxx administrator.

[alibchk-17]

	Description
Message:	Error in library attribute "Relation evaluations": <Error>.
Cause:	The specified error has been discovered in the library attribute "Relation evaluations".
Action:	Contact your ADOxx administrator.

[alibchk-18]

	Description
Message:	Error in library attribute "Sim result-mapping": <Error>.
Cause:	The specified error has been discovered in the library attribute "Sim result-mapping".
Action:	Contact your ADOxx administrator.

[alibchk-19]

	Description
Message:	Attribute values of type EXPRESSION cannot contain more than 3600 characters.
Cause:	The value of an EXPRESSION attribute is too long.
Action:	Reduce the value entered.

[alibchk-23]

	Description
Message:	The entry "<entry>" is contained several times in the facet "<facet name>".
Cause:	The entry displayed cannot appear more than one time in the specified facet and this entry is contained more than once.
Action:	Correct the specified facet accordingly.

[alibchk-26]

	Description
Message:	The item "<item>" is not allowed in the facet "<facet name>".
Cause:	The entered enumeration values include a semicolon ";". This is not allowed.
Action:	Correct the specified item accordingly.

alibload

[alibload-01]

	Description
Message:	The library "<library name>"could not be loaded. Possibly the connection to the database was lost.
Cause:	The library listed could not be loaded from the database.
Action:	Repeat the action. Should the error re-occur, close/quit ADOxx, re-start it and repeat the action again. Should the error still continue to occur, please contact your system administrator.

[alibload-02]

	Description
Message:	Initialisation of the application library "<library name>" has failed for the following reasons: <Number of error message> <Error description> <Number of error message> <Error description>...
Cause:	The attributes of the library contain errors.
Action:	Please check the attributes of the libraries shown. Within the message window further error codes (Number of an error message) will be shown specifying the type of error (Error description).

[alibload-03]

	Description
Message:	The library "<library name>" is currently being edited by the user "<user name>" and therefore cannot be loaded.
Cause:	Another ADOxx administrator is editing the mentioned library at the same time.
Action:	Wait until the library is released or speak with the other ADOxx administrator about it. (You can also send an appropriate message to the specified user via the ADOxx mail (menu "Extras", menu item "Messages").)

alibmgt

[alibmgt-01]

	Description
Message:	One imported library could not be saved in the database! Please quit ADOxx.
Cause:	An error occurred while the library imported was about to be saved. It may be a problem with the network.
Action:	Quit ADOxx, restart it and repeat the library import.Should the message appear again, please contact your system administrator.

[alibmgt-05]

	Description
Message:	This library is the standard application library.You cannot delete it!
Cause:	You have attempted to delete the standard application library. The standard application library cannot be deleted.
Action:	The standard application library cannot be deleted.

[alibmgt-07]

	Description
Message:	No file name was entered!
Cause:	You did not enter a file name for the export file of a library.
Action:	Enter the name of the export file.

[alibmgt-08]

	Description
Message:	The directory name entered is invalid!
Cause:	You entered a path that does not exist for exporting a library.
Action:	Enter a valid (= existing) path for the export.

[alibmgt-15]

	Description
Message:	The file <file name> does not exist!
Cause:	The path entered and/or the file name of the ABL file for the import does not exist.
Action:	Enter the file name and/or the path of an existing ABL file.

[alibmgt-17]

	Description
Message:	The library <library name> is assigned to the following users:<user name_1, .., user name_n>!
Cause:	You tried to delete the application library listed which is assigned to the ADOxx users listed.
Action:	Change the settings of the ADOxx users listed in the User Management component. You can either assign a different application library to these users or delete them from the user list.

[alibmgt-19]

	Description
Message:	There are (application) models based on the library <library>!
Cause:	You tried to delete the application library listed.However, models which are based on this application library still exist.
Action:	Delete the models based on the application library listed before you delete the application library. If you wish to re-use the models later, export them as well as the application library prior to the deletion.

[alibmgt-23]

	Description
Message:	The library could not be saved!
Cause:	The connection to the ADOxx database server may have been lost or the server may have broken down.
Action:	Quit ADOxx and restart it. Should the message appear again, please contact your database administrator.

[alibmgt-24]

	Description
Message:	Invalid input for attribute <attribute name>:<value>!
Cause:	You entered the value listed into the ADOxxnotebook but it does not match the type of the attribute listed.
Action:	Please enter a valid value.

[alibmgt-26]

	Description
Message:	The class attributes of the library "<library name>" contain errors!
Cause:	The notebook definitions of the library listed are invalid. This may cause run-time errors when the library is used in the ADOxx Modelling Toolkit.
Action:	Close the window containing the error message by clicking on the "OK" button and save the error protocol then shown. Contact your ADOxx consultant and give him the error protocol so that the errors in the notebook definitions can be fixed.

[alibmgt-28]

	Description
Message:	The attributes of the library <library name> contain errors! This may produce runtime errors in the ADOxx Modelling Toolkit.Please pay attention to the following information.
Cause:	The attributes in the library listed contain invalid values.
Action:	Close the window containing the error message by clicking on the "OK" button and save the error protocol which will then be shown.Correct the library attributes (the syntax of which is described in the ADOxx Administration. if necessary contact your ADOxx consultant and give him the error protocol so that the errors in the attribute definitions can be fixed.

[alibmgt-29]

	Description
Message:	The file <file name> does not exist!
Cause:	An invalid name was entered for the import file.
Action:	Please enter a valid file name.

[alibmgt-31]

	Description
Message:	The application library <library name> cannot be deleted because of one or more defined model groups!
Cause:	One or more model groups could not be deleted automatically.
Action:	Repeat deleting the application library listed.Should the message appear again, delete the model groups in the Model Management component or contact your ADOxx administrator.

[alibmgt-32]

	Description
Message:	The application library <library name> cannot be deleted!
Cause:	An internal error occurred while you tried to delete the application library.
Action:	Please contact your ADOxx consultant.

[alibmgt-33]

	Description
Message:	The dynamic library <library name> cannot be deleted!
Cause:	A severe internal error occurred while you tried to delete the dynamic library.
Action:	Please contact your ADOxx consultant.

[alibmgt-34]

	Description
Message:	The Static library <library name> could not be deleted since the user <user name> is currently logged in!
Cause:	The Static library could not be deleted since it is currently being edited by the specified user.
Action:	Delete the specified library once the specified user has finished to edit this library. (You can also send an appropriate message to the specified user via the ADOxx mail (menu "Extras", menu item "Messages").)

[alibmgt-36]

	Description
Message:	The application library "<library name>" could not be deleted!
Cause:	When attempting, to delete the application library, a serious internal error has occurred.
Action:	Contact your ADOxx administrator.

[alibmgt-37]

	Description
Message:	The library "<library name>" could not be deleted, because there are still files in the database assigned to this library!
Cause:	Deleting the library specified is currently not possible, as there still exists external files assigned to this library.
Action:	Delete the external files using the file management before deleting the application library or activate the option "Delete external files" when deleting the application library.

[alibmgt-38]

	Description
Message:	Cannot delete application library "<library name>" because the model "<model name>" is locked by the user "<user name>"!
Cause:	Deleting the library specified is currently not possible, as the model mentioned - which is based on that library - is currently in use by the user specifed and thus locked.
Action:	Repeat the procedure later, after the user closed the model.

alibren

[alibren-01]

	Description
Message:	The library "<current library name>" could not be renamed because the new name "<new library name>" is not unique!
Cause:	The name you selected for renaming cannot be used because another library in the same database already bears this name.
Action:	Choose another name for one of the two libraries.

alic

[alic-01]

Message:	Error while writing licence file "<file name>".
Cause:	For being able to change the customer number or licence number, certain access permissions are necessary. In this case write-access to the ADOxx installation directory is missing.
Action:	Establish write-access to the ADOxx installation directory or contact your system administrator.

[alic-02]

Message:	Invalid customer number or licence number! Maybe the licence number you have entered belongs to a previous version of ADOxx and is no longer valid. Please contact your ADOxx customer support
Cause:	You have tried to enter an invalid combination of user name and licence key. Either the customer number contains a typing error or your licence key is outdated.
Action:	Check the customer number for typing errors or contact your ADOxx consultant.

alogin

[alogin-05]

	Description
Message:	Data base "<database name>" does not exist!
Cause:	A database of the name you entered has not been catalogued on your computer.
Action:	Check the database name entered or apply to your database administrator to have the respective database catalogued.

[alogin-06]

	Description
Message:	ADOxx could not connect to the database! Please try again.
Cause:	The connection to the ADOxx database server may have been lost or the server may have broken down.
Action:	Repeat the action. Should the error occur again, please contact your system administrator.

[alogin-09]

	Description
Message:	The user <user name> is already logged into ADOxx! The login process was stopped.
Cause:	A user may not be logged in more than once. A user of the user name you entered is already logged in.
Action:	Login using a different user name or wait until the user logged in logs out of ADOxx.

[alogin-10]

	Description
Message:	Login impossible - a user name must be specified!
Cause:	You did not enter a user name into the field 'Login'.
Action:	Please enter a user name.

[alogin-11]

	Description
Message:	Login impossible - a password must be specified!
Cause:	You did not enter a password into the field 'Password'.
Action:	Please enter the user's password.

[alogin-12]

	Description
Message:	Login impossible - a database name must be specified!
Cause:	You did not enter a database name into the field 'database Name'.
Action:	Please enter a database name.

[alogin-13]

	Description
Message:	Wrong password specified for user < user name> of database <database name>!
Cause:	The password you entered is not the correct one for the user and database listed.
Action:	Please enter the correct password.

[alogin-14]

	Description
Message:	In the database <database name>, there is no user <user name>!
Cause:	The user name you entered is not part of the list of possible users for the database listed.
Action:	Please enter a user name that is permitted for the database listed or ask the ADOxx administrator to enter the user name you used before into the user list of the ADOxx database.

[alogin-15]

	Description
Message:	The user <user name> has no execution access for the Modelling Toolkit!
Cause:	The user of the user name you entered has no execution access for the Modelling Toolkit.
Action:	Enter the user name of an ADOxx user who has execution access or ask your ADOxx administrator to grant you execution access.

[alogin-16]

	Description
Message:	The user <user name> has no execution access for the Development Toolkit!
Cause:	The user of the user name you entered has no execution access for the Development Toolkit.
Action:	Enter the user name of an ADOxx user who has execution access or ask your ADOxx administrator to grant you execution access.

[alogin-17]

	Description
Message:	The database system is not valid!
Cause:	The database system you entered does not exist.
Action:	Enter one of the database systems permitted (parameter -sDB2, -sORACLE, -sINFORMIX or -sSQLSERVER).

[alogin-18]

	Description
Message:	ADOxx could not connect to the database - task stopped! Please contact your system administrator.
Cause:	The connection to the ADOxx database server may have been lost or the ADOxx database server may have broken down.
Action:	Repeat the action. Should the message occur again, please contact your system administrator.

[alogin-19]

	Description
Message:	At the moment the maximum number of <number> users is logged in to the ADOxx database <data base name>.Do you want to log into another ADOxx database?
Cause:	You tried to log into an ADOxx database which had the maximum number of users permitted already logged in.
Action:	Click on the "Yes" button to log into another ADOxx database or the "No" button to cancel.

[alogin-20]

	Description
Message:	The ADOxx database <database name> is configured for single user mode and a user is already logged in at the moment! Do you want to log into another ADOxxdatabase?
Cause:	You tried to log into an ADOxx database which is configured for single user mode (maximum number of users permitted: 1).
Action:	Click on the "Yes" button to log into another ADOxx database or the "No" button to cancel the ADOxx message.

[alogin-21]

	Description
Message:	With this ADOxx version the selected database cannot be accessed. The database <database name> was created with another ADOxx version <version number1> You currently use <version number2>. Note: You may migrate your models using the import/export tool. Do you want to login to another ADOxx database?
Cause:	You tried to log into a database which was not generated by your current ADOxx version (version number2).
Action:	Generate a new database using your current ADOxx version. Then migrate the models and libraries from the database with the help of the ADOxx version listed (version number1). If necessary contact your ADOxx administrator.

[alogin-22]

	Description
Message:	A character set error has been detected with the selected database! Please contact your ADOxx administrator. Do you want to login to another ADOxx database?
Cause:	The database system and your ADOxx client use different character sets. Note: If the database system is "Microsoft SQL Server", then there are probably different ODBC settings regarding the option "Transform OEM into ANSI" on the various clients.
Action:	Contact your ADOxx administrator. Hint: When the database system "Microsoft SQL Server" is used, the option "Transform OEM into ANSI" (program "ODBC32" in the Windows system directory "Settings") must be set to the same value for all clients with ADOxx applications.This value must also agree with the one on that client from which the ADOxx database was installed.

[alogin-23]

	Description
Message:	The operating system could not authenticate the user "<user name>".
Cause:	You have tried to login as system user with a user name unknown in the active domain.
Action:	Check the user name for typing errors, check if this user is really a system user and no ADOxx user or choose a different user name for login.

[alogin-24]

	Description
Message:	You tried to log on to the specified ADOxx database as system user. This is not supported by the specified ADOxx database. Do you want to logon as ADOxx user to the specified database "<database name>" or to some other ADOxx database?
Cause:	Not all databases support single sign-on and in this course logging on as system user. You have chosen such a database for login.
Action:	Try to logon to this database as ADOxx user or enter the name of a single sign-on-able ADOxx database.

[alogin-25]

	Description
Message:	With this ADOxx version the selected database cannot be accessed, because the licence key in the database seems to be incorrect. Maybe the database was created with a more recent version of ADOxx. Try to use a newer version of ADOxx or contact your ADOxx customer support..
Cause:	You have tried to login to a ADOxx database that is not suitable for your ADOxx version because it was created with a newer ADOxx version than the one you are using.
Action:	Login to an older ADOxx database, use a newer ADOxx version or contact your ADOxx consultant.

[alogin-26]

	Description
Message:	The user <username> could not log on to the database_<databasename>_ from this workstation!Logging on to this database is only possible from the workstation with the system ID <ID>.Contact your ADOxx administrator.
Cause:	You can only log on to your workstation with your user account.
Action:	Login to your workstation or contact your ADOxx administrator.

Hint: If you want to change the workstation contact your ADOxx administrator to update your ADOxx licence.

[alogin-27]

	Description
Message:	The user <username> could not log on to the database <databasename>!The workstation key necessary for this could not be retrieved.Possibly the windows service "Windows Management Instrumentation (WMI)" is not running.
Cause:	Possibly WMI is not active on your workstation.
Action:	Contact your system administrator.

[alogin-28]

	Description
Message:	The user <username> could not log on to the database <databasename> from this workstation!Loggging on to this database is only possible from the workstation with the system ID <ID>.Do you want to create a new configuration key resp. activate the database for this workstation?
Cause:	You can only login to an activated workstation.
Action:	Login to your workstation or contact your ADOxx administrator.

[alogin-30]

	Description
Message:	The configuration key for the workstation could not be written to the file <filename>!
Cause:	Maybe the file is write-protected.
Action:	Correct the possible causes and try again.

[alogin-31]

	Description
Message:	Error when trying to activate the database <databasename>:The activation key is invalid!
Cause:	Maybe the file can't be read or it contains no activation key.
Action:	Correct the possible causes and try again. If the problem occurs again contact your ADOxx consultant.

[alogin-32]

	Description
Message:	Error when trying to activate the database <databasename>:The activation key is not valid for this workstation!
Cause:	Maybe the file can't be read or it contains no activation key.
Action:	Correct the possible causes and try again. If the problem occurs again contact your ADOxx consultant.

amessg

[amessg-01]

Message:	The message by user <user name> (Subject: <subject>) can not be read, because it was deleted in the meantime!
Cause:	The message was deleted in the meantime.
Action:	A deleted mesage can not be read. If necessary, ask the sender to send the message again.

[amessg-02]

Message:	The message by user <user name> (Subject: <subject>) can not be replied to, because it was deleted in the meantime!
Cause:	The message was deleted in the meantime.
Action:	A deleted mesage can not be replied to.

[amessg-03]

Message:	The message by user <user name> (Subject: <subject>) can not be forwarded, because it was deleted in the meantime!
Cause:	The message was deleted in the meantime.
Action:	A deleted mesage can not be forwarded.

[amessg-04]

Message:	Send message failed!
Cause:	The message could not be delivered because of unexpected reasons.
Action:	Please try to resolve the problem as follows: - Send the message again. - Reduce the text of the message and reduce the length of the subject of the message. Send the message again. - Quit ADOxx and restart it again. Send the message again. - If the delivery of the message still fails, contact your ADOxx consultant.

[amessg-05]

Message:	Send message failed, because the message text is too long!
Cause:	The message text is too long.
Action:	Reduce the text of the message and try again.

amigrat

[amigrat-03]

	Description
Message:	An error occurred during import of a user group/user.
Cause:	The UDL file to be imported is incorrect.
Action:	Please contact your ADOxx administrator.

ammcp

[ammcp-01]

Message:	Error while moving a reference originating from the object <object name (class name)> in model <model name (model type)>! The model <model name (model type)> is write-protected and can therefore not be changed. Do you want to skip moving this reference?
Cause:	You have tried to move an inter-model reference to a different target object. However, as the source model of one reference is write-protected for you, this action could not be performed.
Action:	Click "Yes" to skip the write-protected reference and continue with the next reference. Click "Yes, all" to skip this and all further write-protected references. Click "Cancel" to terminate the process and undo all previous changes. If necessary, contact your ADOxx administrator for extended access permissions.

[ammcp-02]

Message:	Error while moving a reference originating from the object <object name (class name)> in model <model name (model type)>! The model <model name (model type)> is currently locked by the user <user name> and can therefore not be changed. Do you want to skip moving this reference?
Cause:	You have tried to move an inter-model reference to a different target object. However, as the source model of one reference is currently in use by another user, this action could not be performed.
Action:	Click "Yes" to skip the locked reference and continue with the next reference. Click "Yes, all" to skip this and all further currently locked references. Click "Cancel" to terminate the process and undo all previous changes. If necessary, contact your ADOxx administrator for extended access permissions. Try again later, maybe.

amoddiff

[amoddiff-02]

Message:	No further information available!
Cause:	You have selected a cell in the table in which there is no further information.
Action:	Select the attribute you would like to compare in the column 'In both models'.

[amoddiff-08]

Message:	The model <model name > could not be loaded. Please refresh the models list and try again.
Cause:	An error occurred while attempting to load the specified model. It is possible that this model was deleted by another ADOxx user.
Action:	Refresh the model list and select a different model.

[amoddiff-09]

Message:	An error occurred while evaluating attributes.
Cause:	An error occurred while evaluating attributes.
Action:	Try again or select a different object whose attributes you would like to compare.

[amoddiff-10]

Message:	The models to be compared must have the same model type.
Cause:	You have selected two models for comparison of different model types. Only models of the same type can be compared.
Action:	Select two models of the same model type.

[amoddiff-11]

Message:	The action could not be performed, as the concerned model was deleted in the meantime!
Cause:	You tried to perform an action for a previously deleted model.
Action:	Close your result window and execute the model comparation again.

[amoddiff-12]

Message:	The action could not be performed, as the concerned object was deleted in the meantime!
Cause:	You tried to perform an action for a previously deleted object.
Action:	Close your result window and execute the model comparation again.

amodlru

[amodlru-01]

Message:	Model <model name>, Instance <instance name> The reference model does not exist. The process is continued. Should future messages of this type be displayed?
Cause:	The specified instance refers to a model which does not exist in the database.
Action:	Check whether the model exists and correct/recreate the model reference if necessary.

[amodlru-02]

Message:	Internal error<error number>
Cause:	An unexpected error has occurred.
Action:	Quit ADOxx, restart it and try this again.If the error re-occurs, contact your ADOxx consultant.

[amodlru-03]

Message:	Model <Model name>, Instance <Instance name> The referenced model could not be loaded. The process is continued. Should future messages of this type be displayed?
Cause:	An unexpected error occurred.
Action:	Exit ADOxx, restart it and repeat the task.Should the error occur again please contact your ADOxxconsultant.

[amodlru-04]

Message:	Model <Model name>, Instance <Instance name> The referenced model could not be loaded as you do not have sufficient access rights. The process is continued. Should future messages of this type be displayed?
Cause:	The instance points to a model in a model group in which you do not have the required access rights(read access).
Action:	Contact your ADOxx administrator in order to obtain sufficient access rights.

amodmgt

[amodmgt-10]

	Description
Message:	The user-specific configuration could not be loaded.
Cause:	An error occurred while the user-specific configuration was about to be loaded.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your ADOxx administrator.

[amodmgt-11]

	Description
Message:	Error in the value of the attribute "<attribute name>" (<class name>): "<Value>" is not an instance attribute name of the same class!
Cause:	The class attribute of the class listed is filled with an illegal value. The value must be the name of an (instance) attribute of the same class.
Action:	Please inform your ADOxx administrator

[amodmgt-12]

	Description
Message:	There are no classes defined in the library "<library name>".
Cause:	No classes are defined in the specified library.
Action:	Inform your ADOxx administrator.

[amodmgt-13]

	Description
Message:	The D library of the application library "<library name>" is defective!
Cause:	Your application library is defective.
Action:	Inform your ADOxx administrator.

[amodmgt-14]

	Description
Message:	The S library of the application library "<library name>" is defective!
Cause:	Your application library is defective.
Action:	Inform your ADOxx administrator.

amodraw

[amodraw-02]

Message:	The input "<input text>" is invalid for the attribute "<attribute name>"! <Information about valid inputs>
Cause:	The input text cannot be converted into a value valid for this attribute.
Action:	Correct your input accordingly. Consider the given information while doing this.

[amodraw-03]

Message:	Clipboard error: Not enough free memory!
Cause:	The selected objects and connectors could not be copied onto the clipboard as there is not enough free memory.
Action:	Attempt to increase the space available by closing applications and model windows. Then try to copy to the clipboard again.

[amodraw-04]

Message:	Error on creating a new relation: A relation of type <relation type> from object "<object name>" (<class name>) to object "<object name>" (<class name>) already exists !
Cause:	You have attempted to link two objects by a connector when they are already connected by a relation of the same type.
Action:	Only one connector of the given type can exist between two objects.

[amodraw-05]

Message:	Error on creating a new relation: A relation of type "<relation type>" from object "<object name>" (<class name>) to object "<object name>" (<class name>) is not allowed! < Information on what relations are possible between the two selected objects and which objects can be linked by the selected relation is also provided here.>
Cause:	You are attempting to create a relation between two objects which cannot be linked by the relation chosen.
Action:	If another relation can be used to link the two objects, then join the objects using this relation instead.

[amodraw-08]

Message:	Error while writing file "<filename>"! The filename may be invalid or the disk is full or write protected or currently being used by another application.
Cause:	The file cannot be created because the filename you have entered is invalid or there is not enough space to create the file or the disk is write-protected or or currently being used by another application.
Action:	Check the filename selected and the space available.Close the file in the other application or close the application blocking the access to the file

[amodraw-09]

Message:	Error in the value of attribute "<attribute name>" (<model name>): "<Text>" is not a keyword!
Cause:	The value of the specified model attribute was possibly altered in the ADL file and now contains an invalid value.
Action:	Correct the ADL file or contact your ADOxxconsultant.

[amodraw-10]

Message:	No value specified in attribute "<attribute name>"!
Cause:	Ctrl and double-click cannot be used to bring the referenced model to the foreground in this case as no value was specified in the attribute.
Action:	Close the error message and then select that model to which you would like to link this reference attribute.

[amodraw-11]

Message:	Error while following an inter-reference! "<model name>" (<model type>) could not be opened. Probably the referenced model has been deleted or renamed and the inter-references need to be updated.
Cause:	You have attempted to follow a model inter-reference where the model referenced no longer exists 1.the model was altered by another ADOxx user in the meantime or 2. the model was deleted by another ADOxx user.
Action:	1. Refresh the inter-model references with at the window "Outgoing inter-model references" (menu "Model" - menu items**"Inter-model references - Outgoing from active model"**). 2.Recreate the deleted model or delete the reference.

[amodraw-12]

Message:	Error while following an inter-model reference: The referenced object "<object name>" (<class name> in model "<model name>" (<model type>) could not be found!. The referenced model has probably been deleted or renamed and the inter-references need to be updated.
or
Message:	Error while following an inter-model reference: The referenced object with ID "<object ID>" in model "<model name>" (<model type>) could not be found!. The referenced model has probably been deleted or renamed and the inter-references need to be updated.
Cause:	You have attempted to follow a model inter-reference where the model referenced no longer exists. It has probably been altered or deleted by another ADOxx user.
Action:	Recreate the model or delete the reference.

[amodraw-13]

Message:	No model pointer is specified for class "<class name>"!
Cause:	It is not possible to link to the referenced model through ctrl and double-click as the class attribute "Model pointer" must first be updated to hold the correct model description.
Action:	Define the model pointer in the ADOxxDevelopment Toolkit or contact your ADOxx administrator.

[amodraw-14]

Message:	The name "<object name>" is already assigned to another object of class "<class name>"!
Cause:	You have attempted to give a name to an object which is the same as the name already given to an object of the same class in the same model.
Action:	Enter a name which is unique within the model for this object.

[amodraw-15]

Message:	Error while creating graphics: Not enough free memory!
Cause:	For large graphics (greater than 1000x1000 pixel) the space available may not sufficient especially when the colour settings are very high on the local computer (e.g.16 mill. colours).
Action:	Set the colour resolution to 256 colours or produce the graphic with fewer colours or smaller proportions.

[amodraw-16]

Message:	Error when following the model pointer: "<model name>" (<model type>) does not exist!
Cause:	The specified model has since been deleted or there is a spelling mistake.
Action:	Re-create the model and correct the model name accordingly.

[amodraw-17]

Message:	None of the copied objects (initial model type: "<model type1>") can be pasted into the models of type "<model type2>"!
Cause:	The models which you want to copy from one model cannot be pasted into a model of another model type. Either the class of the models is not defined in the target model or the target model is not based on the same library (BP or WE library) as the starting model.
Action:	It is not possible to copy these objects.

[amodraw-18]

Message:	Error when reconnecting a relation: A relation of the type <relation type> of object "<object name>" (<class name>) to object "<object name>" (<class name>) already exists!
Cause:	You have attempted to put a relation between two objects, for which there is already an appropriate connector.
Action:	Only a connector of the same type is possible between two objects.

[amodraw-19]

Message:	Error when reconnecting a relation: A relation of the type <relation type> of object "<object name>" (<class name>) to object "<object name>" (<class name>) is not authorised! <Information concerning which relation is possible between the selected objects and between which classes the selected relation is authorised.>
Cause:	The created connector is missing since the underlying relation is, according to its definition, not possible between the classes of the selected objects.
Action:	If there is another relation authorised between the objects, you can use this relation to connect them with each other.

[amodraw-20]

Message:	Error when following an inter model reference! "<model name>" (<model type>) could not be opened because of an inappropriate version number. The referenced model may have been deleted in the meanwhile or the inter model references must only be updated once the referenced model has been updated.
Cause:	You have attempted to follow an inter model reference, but the referenced model no longer exists as a result of it possibly being deleted in the meantime by another ADOxxuser.
Action:	Update the inter model references (menu "Edit" - entry**"inter model references"** - button "Update") and repeat the action. Should the error re-occur, restore the deleted model and delete the reference.

[amodraw-21]

Message:	The object cannot be renamed as it is referenced by at least one model you do not have access to.
Cause:	You have tried to rename an object which is referenced by another model you do not have access to.
Action:	Update the model list and try again. Should the error re-occur then contact your ADOxx administrator in order to gain access to the referenced models. A list of all models referencing the target object can be obtained using the dialogue "Show incoming references".

[amodraw-22]

Message:	The input "Connector number" is invalid for the connector mark! Enter a positive numeric value.
Cause:	You have tried to rename a connector mark and assigned an invalid value.
Action:	Enter an integer value greater than zero in order to rename the connector mark or click on the button Cancel to exit the renaming.

[amodraw-23]

Message:	The Connector number provided is not valid for the connector mark! Please provide an index consisting of no more than three characters using characters A-Z.
Cause:	You have tried to rename a connector mark and assigned an invalid value.
Action:	Enter a valid name for the connector mark: valid values are strings consisting of characters from A to Z and having no more than three characters(A, AB, ABC).

[amodraw-24]

Message:	None of the copied objects can be pasted, because that would lead to at least one violation of a cardinality condition!
Cause:	You have tried to paste objects into a model. Among these objects at least one could not be pasted due to the current cardinality conditions. As the cardinality rules are already checked during modelling in the application library used, ADOxx prevented the pasting action.
Action:	Check again which objects you have copied beforehand and adjust the selection according to the cardinality conditions.

[amodraw-25]

Message:	Error while moving the incoming references of the object <object name (class name)> in the model <model name (model type)>!
Cause:	You have tried to move the incoming inter-model references from the object < object name> to a different object. This was not possible because the models containing the starting point of the references could not be loaded. You either have only write access on these models or these models are currently in use by other users. Another possibility could be that the connection to the database is interrupted.
Action:	Check your access permissions on the from-models of the references. If you have write-access, but the models are locked by other users, try again later. If you do not have access to the database at all, then restart ADOxx.

[amodraw-26]

Message:	Error while creating a swimlane of class <Class name>!Inserting the new swimlane would enlarge the drawing area over its maximum size of 50m x 50m.
Cause:	With the creation of a swimlane the drawing area will be enlarged. The maximum size of the drawing area is 50m x 50m. A new swimlane can not be created because the drawing area would overflow the maximum size.
Action:	Reduce the size of the drawing area, e.g. with resizing another swimlane.

[amodraw-27]

Message:	Error while pasting a swimlane!Pasting would enlarge the drawing area over its maximum size of 50m x 50m.
Cause:	Pasting a swimlane enlarges the drawing area. The maximum size of the drawing area is 50m x 50m. A swimlane can not be pasted because the drawing area would overflow the maximum size.
Action:	Reduce the size of the drawing area, e.g. with resizing another swimlane.

[amodraw-28]

Message:	Not all of the selected connectors could be included into the active variant! Including of a connector is only possible, when both of the related objects have been selected as well or are already contained in the active variant.
Cause:	Connector can only be included in an active variant, when both their related objects have been selected or are already contained in the active variant.
Action:	Select all the related objects and include them into the active variant.

[amodraw-29]

Message:	Activating of variant name of variant in modell name is only possible with write access! Some objects in that variant do not yet have a position, so activating that variant would change the model. The model is opened write-protected.
Cause:	Some objects in that variant do not yet have a position, so activating that variant would change the model. The model is opened write-protected.
Action:	Open the model with write access to perform activation of the desired variant.

amodtab

[amodtab-01]

Message:	The input "<input text>" is not valid for the attribute "<attribute name>" <additional error information> Would you like to work further on this attribute?
Cause:	An invalid value was added via the modelling tabular view.
Action:	Enter a valid value.

[amodtab-02]

Message:	The name "<object name>" is already assigned to another object of class "<class name>"! <additional error text> Would you like to continue working on this attribute?
Cause:	When changing an objects name in the tabular modelling view, a name was given to one object which had already been assigned to another object of the same class.
Action:	Select a different name for the object.

[amodtab-03]

Message:	Not all values could be pasted!
Cause:	When pasting to the ADOxx browser, an error has occurred. Therefore not all values could be inserted.
Action:	Check if the area to be pasted is not too large and if the attribute types go together. Then check if the pasting is allowed for the area you have selected.You should also pay attention to the uniqueness of the object names during the pasting.

[amodtab-04]

Message:	No values could be pasted!
Cause:	When pasting to the ADOxx browser, an error has occurred. Therefore no values could be inserted.
Action:	Check if the area to be pasted is not too large and if the attribute types go together. Then check if the pasting is allowed for the area you have selected.You should also pay attention to the uniqueness of the object names during the pasting.

amomain

[amomain-01]

Message:	Error while unlocking "<model name>" (<model type>)! Possibly the connection to the database was aborted.
Cause:	Possibly the connection to the ADOxx database server has been lost.
Action:	Contact your system administrator.

[amomain-02]

Message:	Error while renaming the "<model name>" (<model type>): "<model name>" (<model type>) already exists!
Cause:	When renaming an object you have attempted to give it a name which already belongs to another object of the same type in the model.
Action:	Enter a different name for the model.

[amomain-03]

Message:	Error while saving "<model name>" (<model type>) as "<model name>" (<model type>): A model with the desired name already exists! If you cannot see the model with this name, then either it does not belong to a model group or it belongs to a model group to which you have no access.Contact your ADOxx administrator.
Cause:	You have attempted to save a model under a name already held by another model.
Action:	Save the model under a different name.

[amomain-05]

Message:	"<model name>" (<model type>) cannot be deleted because it is currently locked by user <User name>.
Cause:	The specified model is currently being edited by another ADOxx user and so is locked.
Action:	You can delete this model when it is no longer locked by any ADOxx users.

[amomain-06]

Message:	"<model name>" (<model type>) could not be opened! Internal error code:<Code>
Cause:	A connection could not be established to the ADOxx Database.
Action:	Note the error code and contact your database administrator.

[amomain-07]

Message:	"<model name>" (<model type>) could not be saved in the database!
Cause:	Either there is not enough space in the ADOxxdatabase to save this model or no connection could be established to the database.
Action:	Contact your database administrator.

[amomain-08]

Message:	"<model name>" (<model type>) contains an illegal process reference! Possible causes for an illegal process reference: Either no model with the specified name exists or a future model version is referenced.
or
Message:	"<model name>" (<model type>) contains <number> illegal process references! Possible causes for an illegal process reference: Either no model with the specified name exists or a future model version is referenced.
Cause:	You have attempted to open any subprocesses contained in the model automatically. However there are one or more Subprocess objects which reference non-existent models.
Action:	Correct these references or create the appropriate models.

[amomain-10]

Message:	An error has occurred while deleting from the database!
Cause:	No connection to the ADOxx database could be established.
Action:	Contact your system administrator.

[amomain-11]

Message:	Closing model windows is impossible while the simulation is running!
Cause:	You have attempted to close a model window while the simulation is still running.
Action:	Close the window once the simulation has been completed.

Message:	Closing model windows is impossible while the analytical evaluation is running!
Cause:	You have attempted to close a model window while the analytical evaluation is still running.
Action:	Close the window once the analytical evaluation has been completed.

[amomain-12]

Message:	"<model name>" (<model type>) has the access state "read access" and so cannot be deleted.
Cause:	You have attempted to delete a model for which you have no update rights.
Action:	Contact your ADOxx administrator.

[amomain-16]

Message:	Error while creating a new model: "<model name>" (<model type>) exists already If this model does not appear in the model select box, it is not contained in an accessible model group.In this case, please contact your ADOxx administrator.
Cause:	You have entered a name for this new model which is already assigned to another model.
Action:	Enter a different name.

[amomain-17]

Message:	Error while creating a new model! Internal error code:<code>
Cause:	No connection to the ADOxx database could be established.
Action:	Please contact your system administrator.

[amomain-20]

Message:	"<model name>" (<model type>) could not be opened, because the access right on this model has been withdrawn by another user in the meantime!Update the model list and try again or contact your ADOxx administrator.
Cause:	Possibly the access status of this model was changed or it was created by a user from a different user group with more access than you.
Action:	Update the model list and try again or contact your ADOxx administrator in order to change your access rights.

[amomain-21]

Message:	Error while opening a submodel of "<model name>" (<model type>)! The submodel has the access state "no access" and therefore cannot be opened!
Cause:	Possibly the access status of this submodel was changed or it was created by a user from a different user group with more access than you.
Action:	Contact your ADOxx administrator in order to change your access rights.

[amomain-22]

Message:	"<model name>" (<model type>) could not be opened - this model has been deleted or renamed! The models which currently exist in the database are shown after clicking the "Refresh" button.
Cause:	The selected model was renamed or deleted previously.
Action:	Click on the "Refresh" button in order to refresh the list of model names.

[amomain-25]

Message:	The new model could not be created! The new model cannot be assigned to any of the selected model groups because the user rights have been changed in such a way that no write access is possible on these model groups any more or the selected model groups have been deleted by another user in the meantime!
Cause:	You have attempted to create a new model but you no longer have access to the chosen model group.
Action:	Refresh the model list and save the model to a group which you have access to or create a new model group in which to save the model.

[amomain-26]

Message:	"<model name>" (<model type>) could not be saved to the database, since the user rights have been changed in such a way that the write access to the associated model groups is no longer possible!
Cause:	The write rights on the model groups have been withdrawn by another user.
Action:	Contact your ADOxx administrator or save the model with a new name to another model group.

[amomain-27]

Message:	Error when saving "<model name 1>" (<model type 1>) as new version "<model name 2>" (<model type 2>): The selected new version already exists!
Cause:	During the storage of a model as a new version, you have entered a version number, which is already given to the current model.
Action:	Select a version number which is not already given.

[amomain-28]

Message:	Error when renaming "<model name 1>" (<model type 1>) in "<model name 2>" (<model type 2>): The selected new version already exists!
Cause:	When renaming the version number of a model ,you have entered a version number which already exists for the current model.
Action:	Select a version number which has not already been assigned.

[amomain-29]

Message:	Error when saving the "<model name 1>" (<model type 1>) as new version "<model name 2>" (<model type 2>): No write access rights for the associated model group!
Cause:	The model cannot be saved as a new version, since there are no write access rights for the model group.
Action:	Contact your ADOxx administrator.

[amomain-30]

Message:	The connection to the database is aborted! Exit ADOxx.
Cause:	There is no connection to the ADOxx database.
Action:	Export not-saved models to an ADL file, exit ADOxxand then start again. Import the models from the ADL file, to restore the status before the loss of the database connection.

[amomain-31]

Message:	"<Model name>" (<Model type>) can not be saved in the database, because the model has violated at least one of the cardinality conditions!
Cause:	The automatic cardinality check has detected an error in the model.
Action:	Check the model with help of modelling guidelines and eliminate the error.

[amomain-32]

Message:	Error while changing the name from <Model name1> (<Model typ1>) to <Model name2> (<Model typ2>): The new model name is improper!
Cause:	The model name contains improper line feed.
Action:	Change the model name .

[amomain-33]

Message:	Error while saving <Model name1> (<Model typ1>) under <Model name2> (<Model type2>): A new model name is improper!
Cause:	The model name contains improper line feed.
Action:	Change the model name.

[amomain-34]

Message:	Error while saving "<Model name1>" (<Model type1>) as new version "<Model name2>" (<Model type2>): The new version number is invalid!
Cause:	The version number contains the improper line feed.
Action:	Change the Version number.

[amomain-35]

Message:	Error while renaming "<Model name1>" (<Model type1>) in "<Model name2>" (<Model type2>): A new version number is improper!
Cause:	The version number contains the improper line feed.
Action:	Change the Version number.

[amomain-36]

Message:	"<Model name>" (<Model type>) could not be renamed, because it is currently locked by user <user name>!
Cause:	For renaming a model it must not be locked by any other ADOxx user.
Action:	Rename the model later, after the other user closed the model.

[amomain-37]

Message:	"<Model name>" (<Model type>) could not be opened - this model has been deleted in the mean time!
Cause:	Opening the model from the window "Search results" was not successful as the model had been deleted in the meantime.
Action:	Update the contents of the window "Search results" - the deleted model will not be listed any more.

[amomain-38]

Message:	"<Model name>" (<Model type>) could not be renamed, because it is opened read-only!
Cause:	To rename the model it has to be closed or opened with write-access.
Action:	Close the model and rename it afterwards.

[amomain-39]

Message:	A new model cannot be created, because the maximum number of 300 models opened at the same time is already reached!
Cause:	A new model cannot be created, because the maximum number of 300 models opened at the same time is already reached!
Action:	Close at least one of the model windows to open other model windows.

[amomain-40]

Message:	"<Model name>" (<Model type>) cannot be opened, because the maximum number of 300 models opened at the same time is already reached!
Cause:	The specified model cannot be opened, because the maximum number of 300 models opened at the same time is already reached!
Action:	Close at least one of the model windows to open other model windows.

[amomain-41]

Message:	"<Model name>" (<model type>) could not be renamed - this model has been deleted in the meantime!
Cause:	You tried to rename a model still shown in the model list but already deleted in the database.
Action:	Deleted models cannot be renamed. Refresh the view in the model list to see the current model stock.

[amomain-42]

Message:	"<The object with ID ID in model model name model type could not be found, because it has been deleted in the meantime.
Cause:	You tried to edit an attribute of an object still shown in the model list but already deleted in the database.
Action:	Attributes of deleted objects cannot be edited. Refresh the view in the painting area to see the current object stock.

amoshell

[amoshell-01]

Message:	Error when executing the open command: No model type has been specified!
Cause:	An OPEN_MODEL-command has been sent to the "modeling" message port without having specified the model type.
Action:	Correct the call of the OPEN_MODEL-command.

[amoshell-02]

Message:	Error when executing the open command: "<model type>" is not a model type!
Cause:	An OPEN_MODEL-command with a non existing specified model type has been sent to the "modeling" message port.
Action:	Correct the call of the OPEN_MODEL command.

[amoshell-03]

Message:	Error when executing the open command: "<model name>" (<model type>) does not exist!
Cause:	An OPEN_MODEL-command with a non existing specified model has been sent to the "modeling" message port.
Action:	Correct the call of the OPEN_MODEL command.

anamegen

[anamegen-01]

	Description
Message:	The definition of the name generation is erroneous: Class "<class name>" does not have an attribute "<attribute name>"!
Cause:	The attribute mentioned is not defined in the shown class and thus cannot be used for the name generation.
Action:	When define a name generation, choose an existing attribute.

anbbrow

[anbbrow-01]

	Description
Message:	Not all values could be inserted successfully!
Cause:	When inserting in the ADOxx browser, an error has occurred. The insertion has been aborted.
Action:	Check if the area to be pasted is not too large and if the attribute types go together. Then check if the insertion in the area you have selected is allowed.

anotebk

[anotebk-01]

	Description
Message:	An error occurred while attempting to save the contents of the notebook!
Cause:	Either the filename under which you are saving is invalid or there is not enough space on the disk or drive to which you are saving.
Action:	Check filename and available space.

[anotebk-02]

	Description
Message:	An error occurred while attempting to print the contents of the notebook!
Cause:	Possibly there is an error with your printer configuration.
Action:	Contact your system administrator.

[anotebk-03]

	Description
Message:	Starting the process <program name> failed!
Cause:	The value referenced in the PROGRAMCALL attribute cannot be resolved successfully as an external program.
Action:	Possibly the "Path" environment variable is incomplete or the program has not been installed.

anumber

[anumber-01]

Message:	No objects of the model could be numbered!
Cause:	There are no objects available for the numbering.
Action:	Make sure that there are objects available in the opened model and try the numbering again.

aoffanim

[aoffanim-01]

Message:	Error while reading the protocol file!
Cause:	ADOxx could not open the file you specified.
Action:	Check and correct the name and/or path listed of the protocol file to be opened.

[aoffanim-02]

Message:	Invalid file format!
Cause:	The file opened does not meet the format requirements expected by ADOxx.
Action:	Check that you have entered the correct file name.If necessary generate a new protocol file.

[aoffanim-03]

Message:	Model not found!
Cause:	ADOxx could not open a model, which is referenced in the protocol file to be opened. Perhaps the model was deleted after this file was generated or it belongs to a different database.
Action:	Check, whether the model named exists. If not, could re import it or open a different database, which still contains this model.

[aoffanim-04]

Message:	Instance not found!
Cause:	ADOxx could not find an instance, which is referenced in the protocol file to be opened. Perhaps the instance was deleted from the model or renamed after the record file was generated.
Action:	Check whether the instance named still exists in the model. If not you will probably need to re import the original model or generate a new protocol file.

[aoffanim-05]

Message:	Class not found!
Cause:	ADOxx could not find a class which was referenced in the protocol file to be opened. Perhaps the record file was generated using a model which belongs to a different application library than the current one.
Action:	Check whether the record file belongs to the model of a different application library. If not, generate a new record file.

[aoffanim-06]

Message:	Syntax error in the protocol file! Incorrect time format!
Cause:	A time specified in the protocol file does not meet the expected format requirements. Perhaps the protocol file was changed.
Action:	Generate a new protocol file. Should the error continue to occur, please contact your ADOxx consultant.

[aoffanim-07]

Message:	Subprocess does not exist!
Cause:	An error occurred.
Action:	Repeat the action (probably after having restarted ADOxx or after having deleted the simulation cache).Should the error continue to occur, please contact your ADOxx consultant.

[aoffanim-08]

Message:	Syntax error in the protocol file! Numeric value expected!
Cause:	ADOxx expects a numeric value in a certain position of the protocol file. Perhaps the protocol file was changed.
Action:	Generate a new protocol file. Should the error continue to occur again, please contact your ADOxxconsultant.

[aoffanim-09]

Message:	Syntax error in the protocol file! Line too long!
Cause:	A line in the protocol file is longer than allowed.Perhaps the protocol file was changed.
Action:	Generate a new protocol file. Should the error continue to occur again, please contact your ADOxxconsultant.

[aoffanim-10]

Message:	Syntax error in the protocol file! Unknown event!
Cause:	An event occurring in the protocol file is not known to ADOxx. Perhaps the protocol file was changed.
Action:	Generate a new protocol file. Should the error re-occur, please contact your ADOxx consultant.

[aoffanim-11]

Message:	The protocol file has been created with the detailed format.
Cause:	The protocol file you specified has the detailed protocol format. The offline animation cannot read this format.
Action:	Start another simulation run with protocol switched on and select the option "short".

[aoffanim-12]

Message:	Attribute not found!
Cause:	ADOxx could not find an attribute, which is referenced in the protocol file to be opened. Perhaps the protocol file was generated using a model that belongs to a different application librrary than the current one.
Action:	Check whether the protocol file belongs to the model of a different application library. If not, generate a new protocol file.

[aoffanim-13]

Message:	Error when accessing model!
Cause:	An error occurred.
Action:	Repeat the action (probably after having restarted ADOxx or after having deleted the simulation cache).Should the error continue to occur, please contact your ADOxx consultant.

[aoffanim-14]

Message:	The task stack cannot be displayed in the Offline Animation.
Cause:	During the Offline Animation you have clicked on a task stack.
Action:	No task stack can be displayed during the Offline Animation. To obtain this type of information you must carry out a workload analysis.

aoutgen

[aoutgen-01]

	Description
Message:	Invalid filename.
Cause:	An invalid filename was given to which the browser contents should be saved.
Action:	Enter a valid filename.

[aoutgen-02]

	Description
Message:	The file could not be opened.
Cause:	The file specified into which the browser contents should be saved could not be opened.
Action:	Possibly the disk is read-only. Remove the access restriction and attempt to save the browser contents again. Contact your system administrator if necessary.

[aoutgen-03]

	Description
Message:	Error writing to file.
Cause:	The file specified into which the browser contents should be saved could not be written.
Action:	There is possibly no longer enough space on your disk.Contact your system administrator if necessary.

[aoutgen-04]

	Description
Message:	Error when starting the postprocessors. (command line: <command>)
Cause:	When saving the browser contents in the format RTF or HTML, an error has occurred during the start of the postprocessor (jade).
Action:	Verify if the postprocessor is installed in the ADOxx installation directory or contact your ADOxxadministrator.

apercalc

[apercalc-01]

	Description
Message:	At least one model is not archived. The monthly closure will be aborted.
Cause:	To execute a monthly closure, all models concerned must previously have been archived. This is not the case.
Action:	Archive all concerned models.

aperctrl

[aperctrl-02]

Message:	The evaluation cannot be executed, since the current ADOxx configuration contains no time-related versioning!
Cause:	You have attempted to carry out an inter-period evaluation, although your ADOxx configuration does not support this.
Action:	Contact your ADOxx administrator.

aperout

[aperout-01]

	Description
Message:	The current result display is empty!
Cause:	No results are available for the current settings.
Action:	Select other settings.

aperpar

[aperpar-01]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The key word '<key word name>' is invalid or is used at an invalid location.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-02]

	Description
Message:	Error in the dynamic evaluation module "<module name>": After the key word '<key word name>', the name of the key figure is missing.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the attribute "dynamic evaluation module" must be corrected.

[aperpar-03]

	Description
Message:	Error in the dynamic evaluation module "<module name>": No formula is defined for the key figure '<key figurename>' .
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-04]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The definition of the key figure '<key figure name>' is incomplete. The correct definition of the formula is missing behind the key word '<key word name>' .
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-05]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The definition of the key figure '<key figure name>' contains errors. The expression specified behind the key word '<key word name>' '<expression> is syntactically incorrect.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-06]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The definition of the key figure '<key figure name>' contains errors. A result file type has been specified as a formula behind the key word '<key word name>'.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-07]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The redefinition of the function '<function name>' contains errors. No valid function indicator has been specified behind the key word '<key word name>'.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-08]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The following key figures are not defined, although they are referenced in at least one formula: <Name of the key figures>
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-09]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The definition of the key figure '<key figure name>' contains errors. The expression '<value>' specified behind the key word '<key word name>' is invalid.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-10]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The name of the following key figures is not unambiguous: <name of the key figures>
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-11]

	Description
Message:	No key figures are defined for the dynamic evaluation module "<module name>".
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-12]

	Description
Message:	Error in the dynamic evaluation module "<module name>": The expression "<value>" is not defined.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-13]

	Description
Message:	Error in the dynamic evaluation module "<module name>" behind the key word "<key word name>":"<value>" does not exist.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-14]

	Description
Message:	Error in the dynamic evaluation module "<module name>" behind the key word "<key word name>":"<value>" has the wrong type (expected type: "<Type name>").
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-15]

	Description
Message:	An unknown dynamic evaluation module has been discovered.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperpar-16]

	Description
Message:	The current configuration contains errors. No dynamic evaluation module has been defined.
Cause:	Your ADOxx application library contains errors.The library attribute "Dynamic evaluation module" contains a value which does not define a correct dynamic evaluation module.
Action:	Contact your ADOxx administrator. The value of the library attribute "Dynamic evaluation module" has to be corrected.

aperress

[aperress-03]

	Description
Message:	The calculation of the key figure "<key figure name>" is cyclic.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperress-04]

	Description
Message:	The key figure "<key figure name>" could not be calculated for "<object name>" . Reason: <reason>
Cause:	The specified key figure can not be calculated.Your ADOxx Application Library could possibly be defective.
Action:	Contact your ADOxx administrator.

[aperress-05]

	Description
Message:	The key figure "<key figure name>" could not be calculated, since the evaluation of the formula '<formula value>' is wrong.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

[aperress-06]

	Description
Message:	The key figure "<key figure name>" could not be calculated, since the time basis belonging to it could not be found.
Cause:	Your ADOxx application library contains errors.
Action:	Contact your ADOxx administrator. The value of the library attribute "dynamic evaluation module" must be corrected.

apersui

[apersui-01]

Message:	The ending time of the evaluation cannot be before the starting time of the evaluation!
Cause:	You have specified an ending time, which is before the starting time.
Action:	Specify an ending time, which is greater/the same as the starting time.

[apersui-02]

Message:	The evaluation cannot start with "<date>", since the model "<model name>" only exists from "<date>" !
Cause:	At least one of the models to be evaluated does not exist at the specified starting time of the evaluation.(i.e. its version number is greater than the starting time.)
Action:	Select a later starting time or create an earlier model version of the model concerned.

aplangen

[aplangen-01]

Message:	Error in library attribute (wrong number).
Cause:	The definition of the selected plan in the application library contains errors.
Action:	Contact your ADOxx administrator.

apredct

[apredct-01]

Message:	Error during the evaluation: The value of variable <variable> could not be computed! Hint: Names of variables are case sensitive.
Cause:	The specified error has occurred during the evaluation of the transition condition.
Action:	Correct the error.

[apredct-02]

Message:	Error during the transfer: <error>!
Cause:	The specified error has occurred during the transfer of the transition condition.
Action:	Correct the error.

aprint

[aprint-01]

Message:	No printer available!
Cause:	No printer is available on your workstation.
Action:	Please install a printer.

[aprint-02]

Message:	"< filename >" is not a valid filename!
Cause:	A file with the specified name could not be opened.Either the path does not exist or there is an invalid character in the name.
Action:	Correct your input.

aproobjs

[aproobjs-01]

Message:	Error in time attribute! < activity sub-class>:<activity name> Model:<model name>
Cause:	A fatal error has occurred.
Action:	If this error re-occurs when the simulation is run again, export your models to an ADL file and contact your ADOxx consultant.

[aproobjs-02]

Message:	Time attribute expected! <activity sub-class>:<activity name> Model:<model name>
Cause:	A fatal error has occurred.
Action:	If this error re-occurs when the simulation is run again, export your models to an ADL file and contact your ADOxx consultant.

[aproobjs-03]

Message:	Random generator for Variable of type enumeration expected! <object class>:<object name> Model:<model name>
Cause:	The referenced random generator contains a distribution of type normal, uniform or exponential but is connected to a variable of type enumeration.
Action:	Correct the attribute "value" in the Random generator or change the type of the Variable.

[aproobjs-04]

Message:	Random generator for a variable of type float expected! <object class>:<object name> Model:<model name>
Cause:	The referenced random generator contains a distribution of type discrete but is connected to a variable of type enumeration.
Action:	Correct the attribute "value" in the Random generator or change the type of the Variable.

[aproobjs-05]

Message:	Invalid index! Model:<model name>
Cause:	A fatal error has occurred when accessing a variable.
Action:	If this error re-occurs when the simulation is run again, export your models to an ADL file and contact your ADOxx consultant.

[aproobjs-06]

Message:	No subsequent relation found! <object class>:<object name> Model:<model name>
Cause:	No subsequent connector was found or no transition condition evaluates to true.
Action:	Possibly a subsequent connector is missing. In this case create one. If this object is a Decisionor a Parallelity, it is also possible that no transition condition evaluates to true. Check the transition conditions and the random generator of the variables used.

[aproobjs-07]

Message:	No unique subsequent exists! <object class>:<object name> Model:<model name>
Cause:	No transition condition in the subsequent relations of the specified objects evaluates to true.
Action:	Only objects of the class "Parallelity" may have many subsequent connectors which evaluate to true. Delete any unnecessary connectors or update the transition conditions.

[aproobjs-08]

Message:	No subprocess model given! <object class>:<object name> Model:<model name>
Cause:	No valid subprocess model is referenced in the "Referenced subprocess" attribute of the Subprocess object.
Action:	Correct the value of the "Referenced subprocess" attribute in the specified Subprocess object.

[aproobjs-09]

Message:	No subsequent exists or no transition condition fulfilled! <object class>:<object name> Model:<model name>
Cause:	The specified object of class "Parallelity" has no subsequent connectors or has no subsequent connectors whose transition conditions evaluate to true.
Action:	Possibly a subsequent connector is missing. In this case create one. It is also possible that no transition condition evaluates to true. Check the transition conditions and the random generator of the variables used.

[aproobjs-10]

Message:	Merging without Parallelity! <object class>:<object name> Model:<model name>
Cause:	No corresponding object of class Parallelity can be found for the specified object of class "Merging".
Action:	Change the model appropriately.

[aproobjs-11]

Message:	Unexpected stack error! <object class>:<object name> Model:<model name>
Cause:	A fatal error has occurred from which the system cannot recover.
Action:	If this error re-occurs when the simulation is run again, export your models to an ADL file and contact your ADOxx consultant.

[aproobjs-12]

Message:	Many conditions fulfilled! <object class>:<object name> Model:<model name>
Cause:	More than one transition condition was evaluated to true for the subsequent relations following the specified object.
Action:	Change the transition conditions or the distributions as appropriate.

[aproobjs-13]

Message:	No transition conditions are true! <object class>:<object name> Model:<model name>
Cause:	No transition condition of the specified decision's "Subsequent" connectors produced the result "true" on evaluation.
Action:	Change the transition conditions and/or the distributions of the variables used accordingly.

[aproobjs-16]

Message:	Performer not found! Model:<model name>
Cause:	A runtime error occurred while the performers were assigned.
Action:	Should the error occur again when the simulation is restarted, export the model into an ADL file and contact your ADOxx consultant.

[aproobjs-17]

Message:	Availability must contain a positive value! <sub-class performer>:<name performer> Model:<model name>
Cause:	The attribute "Availability" of the object specified must contain a value greater or equal to zero.
Action:	Check the value of the attribute "Availability" of the object specified.

[aproobjs-18]

Message:	Unknown subprocess model! <object class>:<object name> Subprocess model:<name of subprocess model> Model:<model name>
Cause:	The model specified in the attribute "Referenced subprocess" does not exists.
Action:	Change the value of the attribute "Referenced subprocess" in the object specified.

[aproobjs-19]

Message:	Error following a relation! <object class>:<object name> Relation:<relation class name> Model:<model name>
Cause:	A runtime error occurred which the system could not correct.
Action:	Should the error occur again, when the simulation is restarted, export the model into an ADL-file and contact your ADOxx consultant.

[aproobjs-21]

Message:	Syntax error during resource assignment! <object class>:<object name> Model:<model name>
Cause:	The value in the attribute "Selection" of the object specified does not satisfy the conventions of AQL.
Action:	Correct the value in the attribute "Selection" of the object specified.

[aproobjs-22]

Message:	No resource found! Perhaps an unknown name was used. <object class>:<object name> Model:<model name>
Cause:	The AQL expression in the attribute "Selection" did not render any resources. Perhaps an unknown name was used.
Action:	Check if the names used in the AQL expression are valid.Should the error occur nonetheless, export the model into ADL and inform your ADOxx consultant.

[aproobjs-23]

Message:	Resource Assignment. Model:<model name>
Cause:	A runtime error occurred while the resources were being assigned.
Action:	Should the error occur again when the simulation is restarted export the model into ADL and inform your ADOxx consultant.

[aproobjs-24]

Message:	No resource found! <object class>:<object name> Model:<model name>
Cause:	The AQL expression listed did not return any resources.
Action:	Check the AQL expression in the attribute "Selection" and ensure that the working environment model concerned contains the necessary resources.

[aproobjs-25]

Message:	Dynamic role variable does not exist! <object class>:<object name> Model:<model name>
Cause:	A runtime error occurred which the system could not correct.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-26]

Message:	Syntax error during performer assignment! <object class>:<object name> Model:<model name>
Cause:	The value in the attribute "Performer" of the object specified does not satisfy the conventions of AQL.
Action:	Correct the value of the attribute "Performer" in the object specified.

[aproobjs-27]

Message:	No performer found! Perhaps an unknown name was used <object class>:<object name> Model:<model name>
Cause:	The AQL expression in the attribute "Performer" did not render any performer. Perhaps an unknown name was used.
Action:	Check if the names used in the AQL expression are valid.Should the error occur nevertheless, export the model into ADL and inform your ADOxx consultant.

[aproobjs-28]

Message:	The performer assignment contains errors. model: <model name> When specifying the performer assignment, an unexpected error has occurred! Clear the simulation memory and re-start the simulation. Should the error re-occur, contact your ADOxx administrator.
Cause:	A runtime error has occurred during the performer assignment.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-29]

Message:	The assignment contains errors. An unknown variable has possibly been specified. <object class>: <object name> Model: <model name>
or
Message:	The assignment contains errors. An unknown variable has possibly been specified. Assignment:<random generator> Model:<model name>
Cause:	A variable is used but has not been defined.
Action:	Check the location in which the variable with the name listed is used.

[aproobjs-30]

Message:	The random generator expression contains errors! <object class>: <object name> Model: <model name>
Cause:	The random generator expression contains an error.The expression is probably syntactically not correct. Characters, which are added to the random generator, like for instance, "Discrete (Yes 0.5; No 0.5) values correct? Must still be checked." are a frequent cause for this error. In this example the completion "values correct? must still be checked." should have been removed before the simulation.Otherwise the error concerned appears.
Action:	Correct the random generator expression. Remove possibly added characters.

[aproobjs-31]

Message:	Process has no unique start object! Business process model:<model name>
Cause:	A business process model must contain exactly onestart object.
Action:	Delete the superfluous start objects in the business process model specified.

[aproobjs-32]

Message:	Error when accessing working environment model:Working Environment Model:<model name>
Cause:	A runtime error occurred while the working environment model was being accessed.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-33]

Message:	Missing start object in instance table!
Cause:	A runtime error occurred which the system could not correct.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-34]

Message:	Variable table of subprocess not found! Model:<model name>
Cause:	A runtime error occurred which the system could not correct.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-35]

Message:	Error searching for relation instance! Model:<model name>
Cause:	A runtime error occurred which the system could not correct.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-36]

Message:	Missing object in instance table! Model:<model name>
Cause:	A runtime error occurred which the system could not correct.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-37]

Message:	Index not found! <object class>:<object name> Index:<index> Model:<model name>
Cause:	When a subprocess was called in the model specified, the indices were not consistent.
Action:	Check the indices of the "Parameter" and "Call parameter" relation of the subprocess object and the start object in the business process called.

[aproobjs-38]

ATTENTION: The error message [aproobjs-38] contains different text parts which are all shown in the following. Should there be no further explanations, then the transition condition contains no correct elements.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> Missing ')' <Correctly interpreted part of the condition>
Cause:	The value in the attribute "Transition Condition" of a "Subsequent"-connector does not meet the syntactic conventions. A closing bracket is missing.
Action:	Check whether there is a matching closing bracket for each opening bracket.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> Unknown operator of comparison! Hint: Names of variables must not contain blanks.
Cause:	The value in the attribute "Transition Condition" of a "Subsequent" connector does not meet the syntactic conventions.ADOxx expects an operator of comparison in the place indicated. For constants and variables of the type "Floating Point Number" the operators "<", ">" and "=" are permitted. For constants and variables of the type "Enumeration" the operator of comparison "=" may be used.
Action:	Use a permitted operator.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> Unknown variable! <Correctly interpreted part of the condition>
Cause:	The value in the attribute "Transition Condition" of a "Subsequent"-connector does not meet the syntactic conventions. An undefined variable was used.
Action:	Check whether the variable used has already been defined as a global variable in the main process or as a local variable in the respective subprocess model. If so, check the variable's name.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> Illegal type of variable! <Correctly interpreted part of the condition>
Cause:	The value in the attribute "Transition Condition" of a "Subsequent" connector does not meet the syntactic conventions. An undefined variable was used.
Action:	Check whether the variable used has already been defined as a global variable in the main process or as a local variable in the respective subprocess model. If so, check the variable's name.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> No term identifier! <Correctly interpreted part of the condition>
Cause:	The value in the attribute "Transition Condition" of a "Subsequent" connector does not meet the syntactic conventions. Possibly characters which are not permitted were used for a term. The characters permitted are any numbers, letters and the signs "_", "-", and "+".
Action:	Replace the characters which are not permitted.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> Illegal operator of comparison! <Correctly interpreted part of the condition>
Cause:	The value in the attribute "Transition Condition" of a "Subsequent" connector does not meet the syntactic conventions. An illegal operator of comparison was used. For constants and variables of the type "Floating Point Number" the operators "<", ">" and "=" are permitted. For constants and variables of the type "Sequence" the operator of comparison "=" may be used.
Action:	Use a permitted operator.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> Comparison of incompatible types! <Correctly interpreted part of the condition>
Cause:	The value in the attribute "Transition Condition" of a "Subsequent" connector does not meet the syntactic conventions. Constants or variables respectively, are compared which are of different types.
Action:	Change the type of the variable used or replace the constants accordingly.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> Logical operator or end expected! <Correctly interpreted part of the condition>
Cause:	The value in the attribute "Transition Condition" of a "Subsequent" connector does not meet the syntactic conventions. The logical expression can only be extended using one of the logical operators "AND" or "OR".
Action:	Use one of the operators mentioned or remove the additional part from the condition accordingly.

Message:	Error in the transition condition! From:<object name> To:<object name> Model:<model name> The types of variables or constants on the left and on the right side of the comparison do not match! <Correctly interpreted part of the condition>
Cause:	In the value of the attribute "Transition Condition" of a "Subsequent" connector the types of variables and constants do not match. A continuously distributed (exponentially, equally or normally distributed) variable must be compared to a numerical constant (e.g.100), a discretly distributed variable to an alphanumeric constant (e.g. 'YES').
Action:	Change either the constant in the transition condition or the value of the attribute "Variable Type" in the object belonging to the class "Variable" accordingly

[aproobjs-39]

Message:	Illegal assignment to dynamic role variable! <object class>:<object name> Model:<model name>
Cause:	A value is assigned to a role variable which ADOxxhas already filled with a performer by a "done by" expression (attribute of an activity). (see AQL Rule No. 9)
Action:	Use a different variable name.

[aproobjs-40]

Message:	Error while translating a process calendar: <object class>:<object name> Model:<model name>
Cause:	A runtime error occurred while a process calendar was being translated.
Action:	Should the error occur again when the simulation is restarted, export the model into ADL and inform your ADOxx consultant.

[aproobjs-41]

Message:	Invalid process calendar or no process calendar specified. <object class>:<object name> Model:<model name>
Cause:	No process calendar was specified for the object listed or a process calendar which does not meet the syntactic conventions was specified.
Action:	Should the error re-occur when the simulation is restarted, open the model listed and try to edit the process calendar in the ADOxx notebook of the object specified. Should an error also occur here, export the model into ADL and inform your ADOxx administrator.

[aproobjs-42]

Message:	Incorrect process calendar or no process calendar specified. <object class>:<object name> Model:<model name>
Cause:	No process calendar was specified for the object listed or a process calendar which does not meet the syntactic conventions was specified.
Action:	Should the error re-occur when the simulation is restarted, open the model listed and try to edit the process calendar in the ADOxx notebook of the object specified. Should an error also occur here, export the model into ADL and inform your ADOxx administrator.

[aproobjs-43]

Message:	You must specify a number 0 and 100 for the minimum quota of presence. <object class>:<object name> Model:<model name>
Cause:	A minimum quota of presence outside the range from 0 to 100 was specified for the object listed
Action:	Enter a value between 0 and 100 for the minimum quota of presence.

[aproobjs-44]

Message:	You must specify a number greater than 0 for the average number of participants. <object class>:<object name> Model:<model name>
Cause:	An average number of participant less than or equal to 0 was specified for the object listed.
Action:	Enter a value greater than 0 for the average number of participants.

[aproobjs-45]

Message:	Expected merging object before the end of the process! If there is a merging object, you possibly modelled a loop that leads somewhere before the corresponding parallelity object. <object class>:<object name> Model:<model name>
Cause:	An attempt was made to leave the process model specified at the object indicated, although at least one merging object was still expected.
Action:	Check whether all parallel paths introduced by the parallelism objects are rejoined by merging objects.

[aproobjs-46]

Message:	Parallel execution paths initiated by the same split object must be merged by the same join object! <object class>:<object name> Model:<model name>
Cause:	Parallel paths introduced by the same split object are brought together by different merge objects.
Action:	Use the same merging object to join the parallel paths of a split object (parallelism) again. If this is not what you intended to do, you must introduce the parallel paths via different split objects.

[aproobjs-47]

Message:	Index used more than once! <object class>:<object name> Index:<Index> Model:<model name>
Cause:	The index indicated was used for several instances of relations which have their origin in the object mentioned.
Action:	Use unambiguous indices for the relations originating at the object mentioned.

[aproobjs-48]

Message:	A cooperative synchronous activity must not employ resources!
Cause:	Your model contains a cooperative synchronous activity which employs resources. This is not permitted.
Action:	Remove the relation to the resource instance or change the activity into a non cooperative or a cooperative asynchronous one.

[aproobjs-49]

Message:	The probability of a "Subsequent" relation must be in the range between 0 and 1!
Cause:	The transition condition contains a probability outside the range permitted.
Action:	Change the probability to a value in the range between 0 and 1.

[aproobjs-50]

Message:	The values of the attribute <Transition condition> of outgoing connectors of a decision contain conditions as well as probabilities!These attribute values must all be either transition conditions or transition probabilities.
Cause:	The outgoing connector must contain conditions or probabilities but it contains both.
Action:	Change the transition conditions of the decision listed in such a way that they contain either conditions or probabilities.

[aproobjs-51]

Message:	The sum of the probabilities of all outgoing edges of a Decision must be 1!! If necessary, check if the correct attribute is assigned (attribute "transition condition" for the simulation or attribute "transition probabilities" for the analytic evaluation).
Cause:	There are either no transition conditions specified at the outgoing edges of the specified decisions (or transition probabilities) or the sum of the specified probabilities is not the value 1.
Action:	Change the probabilities so that the sum makes 1. Note that each different attributes are relevant for the simulation and for the analytic evaluation: The simulation uses the value of the attribute "transition conditions". The analytic evaluation uses the value of the attribute "transition probabilities". You must assign the right attributes, according to what you are using, either the simulation or the analytic evaluation.

[aproobjs-53]

Message:	A macro of the name specified is not defined! Macro:<macro name> Model:<model name>
Cause:	You are attempting to use a macro name which is not defined.
Action:	Check whether the macro name used is already defined anywhere else. If not, replace it with a macro that is already defined or define a macro in another place with the name listed above.

[aproobjs-55]

Message:	The process model is being used recursively!
Cause:	In contrast to the simulation, the Analytical evaluation function does not allow recursions.
Action:	Make sure that no process model calls itself either directly or indirectly as a subprocess.

[aproobjs-56]

Message:	Jumping from a parellel path back before the corresponding split object occured!
Cause:	It is not permitted to jump back before the split object (parallelity) from a path which follows a split and which has not yet been brought together by a merge object with the parallel paths from the same split.
Action:	If you wish to repeat this same parallelism, there are two possibilities: 1. You copy the respective parallelism. 2. You first bring the parallel paths together and then jump back before the split object. If this is not what you intend to do, remove the relation which caused the error.

[aproobjs-57]

Message:	The process model may contain an infinite loop! If necessary, put up the maximum loop length! Model:<model name>
Cause:	The specified process model apparently contains an infinite loop. The analytic evaluation can not be continued.
Action:	Verify the specified model and remove the infinite loop . If there is no infinite loop, increase the value "maximum loop length" in the window "analytic evaluation".

[aproobjs-58]

Message:	The number of paths exceeds the upper limit! Either extend the upper limit or use the simulation!
Cause:	The actual number of different process paths exceed the "Max. number of paths" specified in the window "Analytical evaluation". Therefore, the Analytical evaluation is cancelled.
Action:	Either increase the upper limit for the maximum number of paths or use simulation for evaluating the processes.

[aproobjs-59]

Message:	A process model to which a maximum waiting time is assigned cannot start with a parallelism!
Cause:	A model to be simulated starts with a parallelism, although a value greater than 00:000:00:00:00 is entered in the attribute "maximum waiting time" (Process start).
Action:	Remove the parallelism or set the maximum "Waiting time" by the value 00:000:00:00:00.

[aproobjs-60]

Message:	The "continuous execution" cannot be activated at the same time as the "central task stack"!
Cause:	The "continous execution" implies that the activity of a specific performer is executed, whereas "central task stack" means that any performerwho has time will execute the activity. Both concepts are contradictory and therefore cannot be activated at the same time.
Action:	Deactivate either the "continuous execution" or the "central task stack" option.

[aproobjs-61]

Message:	The option "cooperative" cannot be activated at the same time as "central task stack"!
Cause:	Cooperative activities will always be executed by a group of specific performers. The "central task stack" implies on the contrary, that any performer,who has time, will execute the activity. Both concepts are contradictory and so cannot be activated at the same time.
Action:	Deactivate either the "cooperative" or the "central task stack" option.

[aproobjs-62]

Message:	The current simulation path is exceeding the maximum length allowed! Either one of the models being simulated contains an infinite loop or the current simulation path is too long!
Cause:	A path through the simulated model is exceeding the maximum length allowed of some 8000 - 9000 objects following each other (the maximum path length cannot be exactly specified, since it depends on the situation.).Paths of this length are normally due to infinite loops contained in the simulated models.
Action:	Correct the model accordingly and restart the simulation.

apwchgui

[apwchgui-01]

	Description
Message:	Password must not be shorter than three characters.
Cause:	You entered a password shorter than three characters.
Action:	Enter a password which is at least three characters in length.

[apwchgui-02]

	Description
Message:	Passwords are not consistent.
Cause:	You entered different passwords in the two input fields.
Action:	Enter the same password in both input fields.

[apwchgui-03]

	Description
Message:	The old password is wrong.
Cause:	You entered an incorrect password.
Action:	Enter your old password which you used for the previous login correctly.

[apwchgui-04]

	Description
Message:	ADOxx could not connect to the database.Task stopped.
Cause:	The connection to the ADOxx database server may have been interrupted.
Action:	Repeat the action. Should the error re-occur, please contact your system administrator.

[apwchgui-05]

	Description
Message:	The new password contains restricted characters.Please use characters in the ASCII (resp. ANSI) range 32 to 126 only (exceptions: ' \ { } and @).
Cause:	You entered illegal restricted characters or umlauts when entering the password.
Action:	The characters permitted for the password are only the numbers 0 to 9, the letters a to z and A to Z, blanks and the symbols ! # $ % & ( ) * + , - . / : ; < = > ? @ [ ] ^ _ { | } ~. Umlauts, � and other symbols must not be used. Please enter the password according to the restrictions above.

[apwchgui-06]

	Description
Message:	The new password does not match the password rule: <Rule>
Cause:	The password you entered does not match the password rule defined by the ADOxx administrator
Action:	For the password certain rules have been defined. The characters permitted for the password are only the numbers 0 to 9, the letters a to z and A to Z, blanks and the symbols ! # $ % & ( ) * + , - . / : ; < = > ? @ [ ] ^ _ { | } ~. Umlauts, � and other symbols must not be used. Please enter a password according to the restrictions above.

aqueryed

[aqueryed-01]

	Description
Message:	The value is already in the list!
Cause:	You entered an enumeration value which already exists.
Action:	Please enter a value that does not yet exist.

[aqueryed-03]

	Description
Message:	Invalid position on creating a reference!
Cause:	The selected position on creating a reference is invalid.
Action:	Select another position or click repeatedly on the button "other" to be shown the valid positions for a reference.

[aqueryed-04]

	Description
Message:	The menu item "<name of the menu item>" already exists!
Cause:	Within the query, the specified menu item appears repeatedly. This is not allowed.
Action:	Give another name to the menu item.

areena

[areena-03]

Message:	The Modelling Toolkit could not be started because another ADOxx application is already active. Close the other ADOxx application in order to be able to start the Modelling Toolkit.
Cause:	No more ADOxx applications can be run under OS/2.In order to start the Modelling Toolkit, you must first exit another application.
Action:	When you exit another ADOxx application, you will be able to start the Modelling Toolkit.

[areena-04]

Message:	The user-specific configuration of ADOxx could not be loaded.
Cause:	Due to a database error, the user-specific configuration of ADOxx could not be loaded.
Action:	Restart ADOxx. If the message re-occurs, contact your system administrator.

[areena-05]

Message:	The relation redefinition contains errors.Contact your ADOxx administrator.
Cause:	The configuration of your library contains errors.
Action:	Contact your ADOxx administrator.

[areena-07]

Message:	The initialising of ADOxx is wrong! An error has occurred when searching for the user specific library! The login process will be aborted.
Cause:	The configuration of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

[areena-08]

Message:	The initialising of ADOxx is wrong! Error on loading the meta model structures! The login process will be aborted.
Cause:	The configuration of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

[areena-09]

Message:	The initialising of ADOxx is wrong! Error on creating the meta model! The login process will be aborted.
Cause:	The configuration of your ADOxx database contains errors.
Action:	Note down the internal error code and contact your ADOxx administrator.

[areena-10]

Message:	The initialising of ADOxx is wrong! Error on loading the user-specific library! The login process will be aborted.
Cause:	The configuration of your application library or of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

[areena-11]

Message:	ADOxx can't be used with the desired language <language> since the licence number is not configured for this language. The login process will be aborted.
Cause:	The access rights defined in the licence number do not allow a login in the selected language.
Action:	Contact your ADOxx administrator.

[areena-12]

Meldung:	Invalid MDAC version - ADOxx cannot be started!
Ursache:	The Windows system did not find a sqlsrv32.dll or it has the invalid version 2000.80.184.0.
Behebung:	Check your sqlsrv32.dll version respectively contact your ADOxx administrator.

aregex

[aregex-01]

> The error message [aregex-01] contains different text parts which are all shown below. Further information can be retrieved from the chapter "Regular Expressions".

	Description
Message:	The entered search pattern is not a valid regular expression! Please note the following information: <error-specific message>
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry accordingly.

	Description
Message:	The entered search pattern is not a valid regular expression! Wrong masking (trailing '\').
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using the masking (back slash) properly.

	Description
Message:	The entered search pattern is not a valid regular expression! Missing bracket ('[' without ']' or vice versa).
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using the brackets properly.

	Description
Message:	The entered search pattern is not a valid regular expression! Missing bracket ('(' without ')' or vice versa).
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using the brackets properly.

	Description
Message:	The entered search pattern is not a valid regular expression! Missing bracket ('{' without '}' or vice versa).
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using the brackets properly.

	Description
Message:	The entered search pattern is not a valid regular expression! Wrong numerical range specified (not a number, number too large, more than two numbers or first number larger than second).
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using the numerical range properly (e.g. {2,3}).

	Description
Message:	The entered search pattern is not a valid regular expression! Invalid range specified.
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using a valid range (e.g.[a-z]).

	Description
Message:	The entered search pattern is not a valid regular expression! Missing expression before '?', '*' or '+'.
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using an expression before '?', ' *' oder '+'.

	Description
Message:	The entered search pattern is not a valid regular expression! Invalid collating element.
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using a valid collating element.

	Description
Message:	The entered search pattern is not a valid regular expression! Invalid character class.
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using a valid character class (e.g. [:alpha:]).

	Description
Message:	The entered search pattern is not a valid regular expression! Invalid backreference number.
Cause:	The search pattern entered does not meet the syntactic requirements of regular expressions.
Action:	Please correct the entry using a backreference number to an existing pattern.

[aregex-02]

	Description
Message:	Not enough memory! Search could not be performed.
Cause:	The search cannot be executed because of not enough free memory.
Action:	Exit other programs and try again.

arelrdef

[arelrdef-02]

	Description
Message:	Error in library attribute "name" ("library name"): "name" is not a valid relation name!
Cause:	There are no existing relations with the specified name.
Action:	Change the corresponding library attribute so that it uses an existing relation.

[arelrdef-03]

	Description
Message:	Error in library attribute "name" ("library name"): There is an error in attribute "attribute name" !
Cause:	An error has occurred in the specified attribute.Possible causes: The attribute has been specified without its class or relation. The specified attribute does not exist in the specified class or relation. The attribute type specified in the parameter "type" is invalid. The value specified in the parameter "value" could not be assigned to the new attribute.
Action:	The following error actions are possible: Before you specify an attribute, you must specify the class/relation it belongs to. Verify the name of the attribute, since it has not been found in the previously specified class/relation. Verify if the value specified in the parameter "type" is available in the following list: "integer", "double", "string", "distribution", "time", "enumeration", "enumerationlist", "longstring" or "program call". Change the value of the parameter "value" in such a way that it meets the type specified in the parameter "type".

[arelrdef-04]

	Description
Message:	Error in library attribute "name" ("library name"): There is an error in the facet "facet name" !
Cause:	An error has occurred in the specified facet.Possible causes: The facet has been specified without its belonging attribute. The parameter "value" has not been specified. The specified facet does not exist in the specified attribute. The value specified in the parameter "value" could not be assigned to the facet.
Action:	The following error actions are possible: Before you specify a facet, you must specify the belonging attribute. Verify if the parameter "value" has been specified. Verify the name of the facet, since it has not been found in the previously specified attribute. Change the value of the parameter "value" in such a way that it corresponds to the type of the facet.

[arelrdef-05]

	Description
Message:	Error in library attribute "name" ("library name"): "class name" is not a valid class name!
Cause:	When creating a new relation or changing an existing meta model class, an invalid class name has been specified.
Action:	Verify the name of the origin and target classes defined for the relation. Check the names of the meta model classes, which should be changed.

areposui

[areposui-01]

	Description
Message:	"name" already exists. Select another name!
Cause:	An attribute profile or an attribute profile group with the specified name already exists. Attribute profiles must have globally unambiguous names (i.e. you cannot have an attribute profile with the same name in no other attribute profile group), the name of attribute profile groups must only be unambiguous inside your own group.
Action:	Specify an unambiguous name.

[areposui-02]

	Description
Message:	"attribute profile (groups) name" is currently being edited by another ADOxx user and so cannot be edited!
Cause:	You have attempted to edit the displayed attribute profile or the displayed attribute profile group, but the profile or the profile group is currently edited by another user.
Action:	Wait until the other user has finished the editing.If necessary, you can send an express-message to the user.

[areposui-05]

	Description
Message:	The entry "value" is not allowed for the attribute "name"
Cause:	You have entered an invalid attribute value.
Action:	Enter a valid value.

[areposui-06]

	Description
Message:	The changes could not be saved! Update the attribute profile list and execute the action again. (Error code: code)
Cause:	The attribute profile or the attribute profile groups concerned have perhaps in the meanwhile been deleted by another user. The connection to the database may also be interrupted.
Action:	Update the attribute profile list and then carry out the action again. Pay attention to the error messages (e.g. database error), which could also be deleted. If the problem reoccurs, note the specified error code and contact your ADOxx administrator.

[areposui-08]

	Description
Message:	The attribute profile has already been deleted by another ADOxx user. Update the attribute profile list.
Cause:	The attribute profile has already been deleted by another ADOxx user.
Action:	Update the attribute profile list.

[areposui-09]

	Description
Message:	"name with version number" already exists.Select another version number!
Cause:	An attribute profile with this name and version number already exists.Attribute profiles must have globally unambiguous names (i.e. there shall not be an attribute profile group with the same name in another attribute profile group).
Action:	Give another name or another version number.

[areposui-10]

	Description
Message:	Not all attribute profile groups could be deleted.Some of the attribute profiles contained in the groups are possibly already used and so could not be deleted.New attribute profiles may also have been created meanwhile by another ADOxx user in the group concerned.Update the attribute profile list and try again to delete the groups.
Cause:	You have attempted to delete one or more attribute profile groups. This is not possible according to the specified reasons.
Action:	Update the attribute profile list and then try again to delete the groups.

[areposui-11]

	Description
Message:	The attribute profile group "name" is currently updated by another ADOxx user. This is why no new attribute profiles could be created at the moment.Try again later.
Cause:	An other user is currently editing the current attribute profile group. To avoid inconsistencies, it is not possible in the meantime to create new attribute profiles in this attribute profile group.
Action:	Wait until the other user has finished his editing and try it again.

[areposui-12]

	Description
Message:	The selected attribute profiles are not based on the same class!
Cause:	The attribute profiles selected for editing are not instances from the same class.
Action:	For the editing, select attribute profiles from only one class.

[areposui-13]

	Description
Message:	The move in the attribute profile group "<group>" is wrong! This can be due to the following causes: - the attribute profile group has meanwhile been deleted by another user. - you have attempted to move a super ordinated group to a group which is one of its subordinated groups. - An attribute profile group with the same name as the attribute profile group to move already exists in the target group. If necessary update the attribute profile list and repeat the action.
Cause:	1. The attribute profile group has been meanwhile deleted by another user. 2.You have attempted to move a subordinated group to one of its subordinated groups. 3. An attribute profile group with the same name as the attribute profile group to move already exists in the target group.
Action:	Depending on the cause, the move to the selected target group is under impossible conditions.

[areposui-14]

	Description
Message:	The attribute profile group concerned has been already deleted by another ADOxx user. Update the attribute profile list and then repeat the action.
Cause:	The attribute profile group concerned does not exist any more.
Action:	Update the attribute profile list and repeat the action for as long as necessary.

aresattr

[aresattr-02]

Message:	Server error while saving.
Cause:	After the simulation results were deleted an error occurred while saving.
Action:	Try to delete the simulation result attributes again.If the error occurs again, contact your ADOxx administrator.

[aresattr-03]

Message:	Error in the application library attribute sim result mapping.
Cause:	The application library's definition is incorrect in the attribute sim result mapping.
Action:	Contact your ADOxx administrator or if necessary your ADOxx consultant.

arightmg

[arightmg-01]

	Description
Message:	Could not define new user group!
Cause:	An error occurred while a user group was about to be created.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your system administrator.

[arightmg-02]

	Description
Message:	Could not delete selected user group!
Cause:	An error occurred while a user group was about to be deleted.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your system administrator.

[arightmg-03]

	Description
Message:	No new name was entered!
Cause:	You did not enter a new name when renaming the group.
Action:	Please enter a new name when renaming the group.

[arightmg-05]

	Description
Message:	An error has occurred when loading the user group containing the user !
Cause:	Not all user groups could be loaded.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your ADOxx administrator.

[arightmg-06]

	Description
Message:	All user groups to which the user is assigned could not be loaded!
Cause:	An error occurred while the user groups to which the user is assigned were about to be loaded.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your ADOxx administrator.

[arightmg-07]

	Description
Message:	An error has occurred when creating the model group <model group name>!
Cause:	An error occurred while a new model group was about to be defined/generated.
Action:	Update the model group list and repeat the action.Should the error reappear, exit ADOxx and re-start the application. Should the error appear again, contact your ADOxx administrator.

[arightmg-08]

	Description
Message:	An error occured while deleting model group <model group name>!This can have various reasons:- Additional subordinated model groups may just have been created by other users.- Maybe the connection to the ADOxx database was lost.- An unexpected internal error may have occured.- A sub-administrator cannot delete main model groups.Depending on the reason, the following actions may help solving the problem:- Refresh the model group list. Then try to delete model group again.- Exit and restart ADOxx. Then try to delete model group again.- Contact your ADOxx customer support.
Cause:	An error occurred while deleting a model group.
Action:	Update the model group list and repeat the action.Should the error appear again, exit ADOxx and re-start the application. Should the error occur again, contact your ADOxx customer support.

[arightmg-11]

	Description
Message:	An error has occurred when assigning the user <user name> to the user group <user group name>!
Cause:	An error occurred while users were about to be assigned to a user group.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your ADOxx administrator.

[arightmg-12]

	Description
Message:	An error has occurred when assigning the user group <user group name> to the user <user name>!
Cause:	An error occurred while user groups were about to be assigned to a user.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your ADOxx administrator.

[arightmg-13]

	Description
Message:	An error has occurred during the assignment of <model name> (model type) to model group <model group name>! The model may have possibly been deleted by another user .
Cause:	An error has occured during the assignment of a model to a model group, as this model group may have meanwhile been deleted by another user.
Action:	Close the error message - the model group list will automatically be updated - and then repeat the action.Should the error appear again, exit ADOxx and restart the application. Should the error occur repeatedly, contact your ADOxx administrator.

[arightmg-17]

	Description
Message:	Error occured when assigning user group <user group name> to model group <model group name>!The access rights of the user group could not be set to the model group. The user or model group has possibly been deleted by another ADOxx user in the meanwhileor your access rights have been possibly changed in the meanwhile. Update the user group list or the model group list and repeat the action.Should the error appear again, exit ADOxx and restart the application.Should the error occur repeatedly, contact your ADOxx administrator.
Cause:	The access rights of the user group could not be set to the model group. The user or model group has possibly been deleted by another ADOxx user in the meanwhile or your access rights have been possibly changed in the meanwhile.
Action:	Update the user group list or the model group list and repeat the action. Should the error appear again, exit ADOxx and restart the application. Should the error occur repeatedly, contact your ADOxx administrator.

[arightmg-19]

	Description
Message:	The selected user group <user group name> is not empty and cannot be deleted!
Cause:	A user group which still contains users may not be deleted.
Action:	Remove all user references from the user group, either by changing the assignment of users or by deleting users from the ADOxx database. Then start the deletion process again.

[arightmg-20]

	Description
Message:	The selected model group <model group name> is not empty and cannot be deleted!
Cause:	A model group, which still contains other model groups or models, may not be deleted.
Action:	Remove all model references and model groups from the model group, either by changing the assignment of models or by deleting the models - or model groups, respectively - from the ADOxx database. Then start the deletion process again.

[arightmg-21]

	Description
Message:	A model group with the name <model group name> already exists!
Cause:	All model groups contained in a model group must have a non-ambiguous name.
Action:	Update the model group list to be aware of changes of other ADOxx users. Rename the model group with a new name that is non-ambiguous within the hierarchically superordinated group and restart the action.

[arightmg-22]

	Description
Message:	A user group with the name <user group name> already exists!
Cause:	Each user group must have a non-ambiguous name.
Action:	Rename the user group with a new non-ambiguous name and start the action again.

[arightmg-23]

	Description
Message:	An error has occurred when renaming the user group <user group name> could not be renamed!
Cause:	An error occurred while one of the user groups was about to be renamed.
Action:	Quit ADOxx and restart it. Should this error re-occur, please contact your ADOxx administrator.

[arightmg-24]

	Description
Message:	An error has occurred when renaming the model group <model group name>!
Cause:	An error occurred while a model group was about to be renamed.
Action:	Update the model group list and repeat the action.Should the error appear again, exit ADOxx and re-start the application. Should the error appear repeatedly, contact your ADOxx administrator.

[arightmg-25]

	Description
Message:	An error has occurred when moving the reference to the model <model name> (<model type>)!
Cause:	An error occurred while a model was about to be moved.
Action:	Update the model group list and repeat the action.Should the error appear again, exit ADOxx and restart the application. Should the error appear repeatedly, contact your ADOxx administrator.

[arightmg-27]

	Description
Message:	An error has occurred when copying the reference in the model <model name> (<model type>) to the model group <model group name>! Changes have possibly been carried out by another user. Update the model group list.
Cause:	An error has occurred when copying a model reference.The target model group may have been deleted by another user in the meanwhile.
Action:	Update the model group list and repeat the action.Should the error appear again, exit ADOxx and re-start the application. Should the error appear repeatedly, contact your ADOxx administrator.

[arightmg-29]

	Description
Message:	When moving the model group <model group name> into model group <target-model group name> an error has occurred!A sub-administrator can only move model groups to which the sub-administrator has write access.Also the model group might have been deleted by another user.Please update the list of model groups.
Cause:	An error has occurred when moving a model group.
Action:	Update the model group list and repeat the action. Should the error appear again, exit ADOxx and re-start the application. Should the error appear repeatedly, contact your ADOxx administrator.

[arightmg-30]

	Description
Message:	The model group <target model group name> already contains a model group with the name <model group name>!.
Cause:	A model group has been moved into a group which already contains a group of the same name.
Action:	Please move the model group to a different group.

[arightmg-31]

	Description
Message:	Cannot create a new main model group!
Cause:	An error occurred while a new main model group was about to be created.
Action:	It is not possible to create new main model groups in the Modelling Toolkit. Contact your ADOxx administrator, who can create new main model groups with the Development Toolkit. If this error occurs in the Development Toolkit, update the model group list and repeat the action. Should the error re-occur, exit ADOxx and re-start the application. Should the error appear repeatedly, contact your ADOxx administrator.

[arightmg-32]

	Description
Message:	An error has occurred when deleting the reference of a model <model name> (model type)!
Cause:	An error occurred while a model reference was about to be deleted.
Action:	Update the model group list and repeat the action.Should the error appear again, exit ADOxx and re-start the application. Should the error appear repeatedly, contact your ADOxx administrator.

[arightmg-33]

	Description
Message:	The target model group <model group name> is write protected and cannot be changed!
Cause:	You do not have sufficient rights to change the respective target model group you wish to change.
Action:	Contact your ADOxx administrator. He is responsible for assigning access rights on models and model groups to users.

[arightmg-34]

	Description
Message:	The reference to <model name> (model type) cannot be deleted, since the model is no longer contained in any model group!
Cause:	There shall always be at least one reference to each model.
Action:	Delete the last reference to a model using the Development Toolkit or contact your ADOxx administrator.

[arightmg-35]

	Description
Message:	The model <model name> (model type) cannot be assigned to a model group!
Cause:	The specified model could not be assigned to the selected model group.
Action:	Update the model group list and repeat the action.Should the error occur again, exit ADOxx and restart the application. Should the error appear again, contact your ADOxx administrator.

[arightmg-36]

	Description
Message:	The reference from the model <model name>(model type) cannot be reassigned, since the model is currently opened with write access by the user <user name> !
Cause:	The model is currently being edited by another user.The reference cannot be moved.
Action:	Make sure that the user which is currently editing the model, closes it or you can move the model reference later.

[arightmg-37]

	Description
Message:	The reference to the model <model name>(model type) cannot be deleted, since the model is currently opened with write access by the user <user name>!
Cause:	The model is currently edited by another user.The reference cannot be deleted.
Action:	Make sure that the user which is currently editing the model, closes it or you can delete the model reference later.

[arightmg-38]

	Description
Message:	The reference to the model "<model name>" (<model type>) cannot be copied, since the model is currently opened with write access by the user <user name>!
Cause:	The model is currently edited by another user.The reference cannot be copied.
Action:	Make sure that the user which is currently editing the model, closes it or you can copy the model reference later. (You can also send an appropriate message to the specified user via ADOxx mail (menu "Extras", menu item "Message").)

[arightmg-39]

	Description
Message:	The model group "<model group name>" cannot be moved, since the following models it contains are currently opened with write access by the following users: <model name> (<model type>) - <user name>
Cause:	Models from the specified model groups are being edited by other users. The model group cannot be moved.
Action:	Make sure that the user, who is currently editing the model, closes it or you can move the model group later. (You can also send an appropriate message to the specified user via ADOxx mail (menu "Extras", menu item "Message").)

[arightmg-40]

	Description
Message:	The reference to the model "<model name>" (<model type>) cannot be assigned, since the model is currently opened with write access by the user <user name>! Should the action be continued because of the expanded administrator rights?
Cause:	The model is currently being edited by another user.The model reference cannot be reassigned.
Action:	Make sure that the user, who is currently editing the model, closes it or you can arrange the model reference later. (You can also send an appropriate message to the specified user via ADOxx mail (menu "Extras", menu item "Message").)

[arightmg-41]

	Description
Message:	The reference to the model "<model name>" (<model type>) cannot be deleted, since the model is currently opened with write access by the user <user name>! Should the action be continued because of the expanded administrator rights?
Cause:	The specified model is currently being edited by another user. The model reference cannot be deleted.
Action:	Make sure that the user, who is currently editing the model, closes it or you can delete the model reference later. (You can also send an appropriate message to the specified user via ADOxx mail (menu "Extras", menu item "Message").)

[arightmg-42]

	Description
Message:	The reference to the model "<model name>" (<model type>) cannot be copied, since the model is currently opened with write access by the user <user name>! Should the action be continued because of the expanded administrator rights?
Cause:	The specified model is currently edited by another user.The model reference cannot be copied.
Action:	Make sure that the user, who is currently editing the model, closes it or you can copy the model reference later. (You can also send an appropriate message to the specified user via ADOxx mail (menu "Extras", menu item "Message").)

[arightmg-44]

	Description
Message:	Insufficient rights for at least one of the model groups selected!
Cause:	You have no write access on at least one of the model groups selected.
Action:	Update the model group list and/or select only the model groups for which you have write access rights.

[arightmg-45]

	Description
Message:	You have no write access to the super ordinated model group of the model "<model name>"! Update the model group list or select another model group.
Cause:	You have no write access to the super ordinated model group of the selected model!
Action:	Update the model group list or select another model group.

[arightmg-46]

	Description
Message:	You do not have sufficient rights to delete or move the model group "<model group name>"!
Cause:	You have no write access rights to the specified model group and therefore cannot delete or move it.
Action:	If necessary, contact your ADOxx administrator, to obtain write access rights to the specified model group.

[arightmg-47]

	Description
Message:	The user group structure has been changed by another "ADOxx" user. Update the user group list!
Cause:	The user group structure has been changed by another "ADOxx" user.
Action:	Update the user group list!

[arightmg-48]

	Description
Message:	The model group "<model group name>" cannot be moved to a specific subgroup.
Cause:	You have attempted to move a model group to one of your subgroups.
Action:	Move the specified model group to another model group, which is not a subgroup of the specified model group.

[arightmg-49]

	Description
Message:	The reference to the model <model name>(model type) cannot be moved, since you do not have enough access rights in the target model group.
Cause:	You have attempted to move a model reference to a model group, in which you have no write access rights.
Action:	You cannot move the reference to the selected model group. If necessary, contact your ADOxx administrator to adapt your rights.

[arightmg-50]

	Description
Message:	The model group <group name> cannot be moved to itself.
Cause:	You have tried to move a model group in a way that it would have become its own sub group.
Action:	Moving a model group into itself is not possible. If necessary, create a new sub group manually and move only the model references into it.

[arightmg-51]

	Description
Message:	The model group <group name> could not be created as a main model group because it is already used as a main model group.
Cause:	You tried to move a main model group in a way that it would again have been a main model group after moving.The cause is most probably a handling error.
Action:	None - moving a model group in a way that it appears in its old place afterwards is pointless.

[arightmg-52]

	Description
Message:	The user group <group name> could not be deleted as it is a global user group!
Cause:	You tried to delete a global user group. As a sub-administrator you do not have the rights to delete a global user group.
Action:	Contact your ADOxx administrator.

[arightmg-53]

	Description
Message:	The last assignment of a user to a local user group can not be removed as the user would not be visible for the sub-administrator anymore!
Cause:	You tried to delete a user from a user group. As this is the last visible assignment of the user to a user group for you it cannot be removed.
Action:	Contact your ADOxx administrator.

[arightmg-54]

	Description
Message:	A sub-administrator can assign user groups only to model groups for which the sub-administrator has write access!
Cause:	You tried to set user group rights on a model group on which you do not have write access. As a sub-administrator you only have the right to change user group rights on model groups you have write access on.
Action:	Contact your ADOxx administrator.

[arightmg-55]

	Description
Message:	A sub-administrator can assign models only to model groups for which the sub-administrator has write access!
Cause:	You tried to assign models to a model group you don't have write access on. As a sub-administrator you are only allowed to assign models to a model group you have write access on.
Action:	Contact your ADOxx administrator.

[arightmg-56]

	Description
Message:	The sub-administrator cannot remove himself from local user groups as the users of these groups would then not be visible for the sub-administrator anymore!
Cause:	You tried to remove your assignment to a user group. You are not allowed to remove yourself from a local user group otherwise the users would not be visible for you anymore.
Action:	Contact your ADOxx administrator.

[arightmg-57]

	Description
Message:	The model group <model group name> could not be created, because sub-administrators are not allowed to create main model groups!
Cause:	You tried to create a main model group. As a sub-administrator you don't have the rights to create main model groups.
Action:	Contact your ADOxx administrator.

[arightmg-58]

	Description
Message:	Sub-administrators cannot create main model groups!
Cause:	You tried to create a main model group with moving a model group. As a sub-administrator you don't have the rights to create main model groups.
Action:	Contact your ADOxx administrator.

[arightmg-59]

	Description
Message:	The model group <model group name> could not be created. Sub-administrators are not allowed to change the model group access rights of global user groups. If a sub model group is created, the access rights of the superior group are adopted. If global user groups possess access rights to the superior group, creating the sub model group would change the model group access rights of the global user groups.
Cause:	You tried to create a sub group of a model group on which global user groups have access rights. Due to automatic inheritance of rights to the sub group the global user group would have access rights to the sub group. As a sub-administrator you are not allowed to change the model group access rights of global user groups.
Action:	Contact your ADOxx administrator.

[arightmg-60]

	Description
Message:	The access rights of the user groups to a model group must not all be set to "no access", as the model group would not be visible for the sub-administrator anymore!
Cause:	You tried as a sub-administrator to set the access rights of all user groups of a particular model group to "no access". This is not allowed, because the model group would not be visible for you anymore.
Action:	Contact your ADOxx administrator.

[arightmg-61]

	Description
Message:	The component access of the user group <user group name> can not be changed!
Cause:	You are sub-administrator and tried to change the component access of a global user group. Sub-administrators can only change the component access of local user groups.
Action:	You need administration rights to change the component access of a global user group.

[arightmg-62]

	Description
Message:	The new user must be assigned to at least one user group,as otherwise the user would not be visible for the sub-administrator!
Cause:	The new user must be assigned to at least one user group, because otherwise he would not be visible for you as a sub-administrator.
Action:	Assign the user to least one user group. Use the button User group to open the window User Management - Assign users groups, in which the assignment is done.

[arightmg-63]

	Description
Message:	Error occured when assigning user group <user group name> to model group <model group name>!The access rights of the user group could not be set to the model group.You are sub-administrator and tried to assign a model group to a global user group.Sub-administrators are just allowed do assign model groups to local user groups.
Cause:	You are sub-administrator and tried to assign a model group to a global user group. Sub-administrators are just allowed do assign model groups to local user groups.
Action:	You need administration rights to assign a global user group to a model group.

as2rdlg

[as2rdlg-01]

Message:	Specify the class and relation.
Cause:	You have selected a simulation representation, which enables you to make statements about Static groupings (roles, organisational units etc.). These results require the selected grouping to be specified.
Action:	Specify the class and the relation.

[as2rdlg-02]

Message:	Some of the models into which the results are to be transferred have been loaded write-protected. The transfer is not possible, because it would cause the simulation results to be mixed up and thus cause inconsistencies.
Cause:	You simulated at least one model that is loaded in read-only state and want to transfer the simulation results for evaluation purposes into these models. This is not possible, since models which were loaded in read-only state cannot be saved.
Action:	Close the simulation result display and the models which were loaded as read-only. Then load them again, this time without write-protection. After this, start the evaluation again.

[as2rdlg-03]

Message:	The model "<model name>" has been closed during the simulation. It is therefore not possible to transfer the simulation results.
Cause:	You have prematurely closed the model mentioned.This is why you cannot transfer the simulation results to the model. For consistency reasons, the transfer of simulation results to other models will also be stopped.
Action:	Carry out again the simulation and close the models only after the transfer of the simulation results.

[as2rdlg-04]

Message:	There is no sim result mapping defined. The simulation results can therefore not be transferred.
Cause:	Since the entries of the library attribute sim result mapping are empty, the results cannot be transferred.
Action:	Contact your ADOxx administrator.

[as2rdlg-05]

Message:	Model "<model name>": There are no objects to which the grouping specified could apply.Please select a different class or a different relation.
Cause:	In the model specified, there is no performer which is linked to the class selected by the relation selected.For this grouping, no results can be displayed.
Action:	Select a different class and/or a different relation in the group "Working Environment".

[as2rdlg-06]

Message:	The simulation results could not be calculated. The result calculation period (workload analysis) was possibly too short or the simulated model contain no object, for which you can calculate the results.
Cause:	For the last selected models, you have entered a result calculation period which is too short or the simulated models contains no object, for which you can calculate the results.
Action:	Define a longer results calculation period or expand the models to the appropriate objects and repeat the simulation.

ascope

[ascope-01]

	Description
Message:	The library could not be saved.
Cause:	Due to an internal error the library changed could not be saved.
Action:	Please inform your ADOxx consultant.

[ascope-02]

	Description
Message:	The character "<character>" must not be used.
Cause:	The new value by which you wish to extend the value range contains an illegal character.
Action:	Please enter a value which does not contain the illegal character.

[ascope-03]

	Description
Message:	This value is already contained in the list.
Cause:	You want to extend the value range of an attribute by a value which is already part of the value range.
Action:	The value is already part of the value range.Therfore, you do not need to add it. Just continue with your work.

[ascope-04]

	Description
Message:	This library does not contain classes with extendable attributes.
Cause:	The library selected contains no classes with attributes of which the value ranges could be extended.
Action:	Please select a different library. If you should need extendable attributes in your current library, contact your ADOxx consultant.

[ascope-05]

	Description
Message:	<Library name>: The new attribute value range is too large. All changes will be cancelled and the previous attribute value range will be restored.
Cause:	You have extended the value range of attributes in the library listed. The new value range of at least one attribute is too large to be stored/saved in the database.
Action:	Extend the value ranges to a little lesser extent.Instead, you may also contact your ADOxx consultant.

ascript

[ascript-01]

	Description
Message:	<Token> is neither a key word nor a defined procedure!
Cause:	The AdoScript contains no command, which is either defined as internal or as a procedure.
Action:	Check and correct the AdoScript.

[ascript-02]

	Description
Message:	<Token> without CASE or OBJECTIF!
Cause:	The attribute contains an element, in which a preceding CASE or OBJECTIF element is missing.
Action:	Check and correct the AdoScript.

[ascript-03]

	Description
Message:	<Token> without ITEM!
Cause:	The attribute contains AdoScript commands, which are not assigned to a menu item.
Action:	Check and correct the AdoScript.

[ascript-05]

	Description
Message:	<Token1> without <Token2>!
Cause:	The AdoScript contains a branching or a loop end, in which the opening token is missing.
Action:	Check and correct the AdoScript.

[ascript-06]

	Description
Message:	<Token1> without <Token2>!
Cause:	The AdoScript contains a branching or a loop end, in which the ending token is missing.
Action:	Check and correct the AdoScript.

[ascript-09]

	Description
Message:	CC without message element!
Cause:	The AdoScript contains a CC call, which is not followed by a message element.
Action:	Check and correct the AdoScript.

[ascript-10]

	Description
Message:	CALL with defective attribute function: "<Text>"!
Cause:	The value of the parameter function is not a valid function specification.
Action:	Check and correct the AdoScript.

[ascript-11]

	Description
Message:	No function "<function name is existing in the DLL "<file name>">"!
Cause:	Using CALL in the AdoScript, you have attempted to call a function which is not defined in a DLL.
Action:	Check and correct the AdoScript.

[ascript-12]

	Description
Message:	"<Command name>" is not a command in message port "<message port>"!
Cause:	In the AdoScript, using SEND or CC, a command has been sent to the specified message port, where it is not defined .
Action:	Check and correct the AdoScript.

[ascript-13]

	Description
Message:	message port "<Name>" does not exist!
Cause:	In the AdoScript, using SEND or CC, a command has been sent to the specified, non existing message port.
Action:	Check and correct the AdoScript.

[ascript-14]

	Description
Message:	defective call of <procedure name>!
Cause:	When calling this procedure, the parameters specified are not the exact same parameters that are specified in the procedure definition.
Action:	Check and correct the AdoScript.

[ascript-15]

	Description
Message:	PROCEDURE without definition element!
Cause:	The AdoScript contains a PROCEDURE element, which is not followed by a definition element.
Action:	Check and correct the AdoScript.

[ascript-16]

	Description
Message:	Type incompatibility in a procedure call! <function call> <context>
Cause:	When calling the procedure, at least one parameter is not of the type defined in the procedure definition.
Action:	Check and correct the AdoScript at the specified place.

[ascript-17]

	Description
Message:	The old syntax (IF...ENDIF) cannot be used together with the new syntax (IF...{...}) !
Cause:	The AdoScript contains both constructs of old and of new syntax.
Action:	Check and correct the AdoScript.

[ascript-18]

	Description
Message:	Starting the process <Process name> failed!
Cause:	The START command has been called from an AdoScript but the program could not be started.
Action:	Check and if necessary correct the AdoScript.Make sure that the program to be started exists in the respective directory.

[ascript-19]

	Description
Message:	LEO call with unauthorised index (set-cur-elem-index:<index>)! Number of parsed elements: <number>
Cause:	The LEO command has been called in an AdoScript with the index specified with set-current-index outside the authorised area (from 0 to (number of parsed elements) - 1).
Action:	Check and correct the AdoScript.

[ascript-20]

	Description
Message:	LEO call with <indication > without previous parse!
Cause:	The LEO command has been called in an AdoScript, where no text to be parsed has been specified. However, this must be the case for each call of LEO.
Action:	Check and correct the AdoScript.

[ascript-21]

	Description
Message:	The external DLL "<DLL name>" could not be loaded!
Cause:	Within an AdoScript the specified DLL file is called from a CALL command although the file dos not exist or is not accessible.
Action:	Enable access to the specified DLL file or correct the CALL command.

[ascript-22]

	Description
Message:	Abnormal terminition of function "<Funktionsname>" in DLL"<DLL name>"! Contact your ADOxx consultant if this problem persists.
Cause:	Within an AdoScript an executed CALL command was aborted due to a fatal error within the specified DLL file.
Action:	Correct the CALL command or update the DLL file with a corrected version.

[ascript-23]

	Description
Message:	Double definition of ON_EVENT <event name>!
Cause:	In the attribute "external linking" there are more than one event handlers defined for one event.
Action:	Check and correct the AdoScript.

[ascript-25]

	Description
Message:	PROCEDURE <procedure name> is currently being executed and therefore cannot be overwritten!
Cause:	An AdoScript with the specified procedure is executed.The procedure exists already and is executed simultaneously.Therefore the procedure overwrites itself.
Action:	Ensure that the specified procedure is defined only once (globally).

[ascript-26]

	Description
Message:	The EXECUTE file <file name> cannot be loaded!
Cause:	You tried to launch an *.exe file from the file system. This attempt failed. Possibe reasons are that the specified file does not exist, is damaged, or cannot be launched due to insufficient user rights.
Action:	Check the file reference for errors, look for the file in the file system or contact your system administrator.

asetref

[asetref-01]

Message:	The entered value is invalid!
Cause:	The value specified for depth of the reference is invalid. (only non negative, whole numbers smaller than 65535 are authorised.)
Action:	Enter a valid value.

[asetref-02]

Message:	The maximum depth of 65535 has been exceeded!
Cause:	The value specified for the depth of the reference cannot exceed 65535.
Action:	Enter a smaller value.

asetsel

[asetsel-01]

	Description
Message:	The parameter of the selected arrangement function could not be changed!
Cause:	An error occurred while attempting to change the parameter of the selected arrangement function.
Action:	Close ADOxx and re-start it. If this error re-occurs, contact your ADOxx administrator.

[asetsel-02]

	Description
Message:	No quotation marks may be used in the name of the arrangement function and the name may not be blank!
Cause:	Quotation marks were specified in the name of the arrangement function or the name was left blank.
Action:	Enter a new name.

[asetsel-04]

	Description
Message:	The new arrangement function could not be added!
Cause:	An error occurred when attempting to add a new arrangement function.
Action:	Close ADOxx and re-start it. If this error re-occurs, contact your ADOxx administrator.

[asetsel-05]

	Description
Message:	The arrangement function could not be deleted!
Cause:	An error occurred when attempting to delete an arrangement function.
Action:	Close ADOxx and re-start it. If this error re-occurs, contact your ADOxx administrator.

[asetsel-08]

	Description
Message:	An arrangement function with this name already exists !
Cause:	A unique name must be entered for each arrangement function.
Action:	Retry the action but enter a different name.

[asetsel-10]

	Description
Message:	The process hierarchy function is not defined for <model type>!
Cause:	The arrangement function is not defined for this model type.
Action:	Open a model or create a model for which it is possible to build a hierarchy. If the model type required for this is not known, then contact your ADOxx administrator, who is competent in the configuration of the (not user-definable) process hierarchy.

asgmlexp

[asgmlexp-01]

	Description
Message:	Error while writing the export data.
Cause:	An error occured while writing the data.Possibly there is not enough space on the disk.
Action:	Check if there is enough space on the disk where the data is stored or on the disk where the "TEMP" folder is located.

[asgmlexp-02]

	Description
Message:	Cannot load model. Please refresh the model list.
Cause:	One of the models selected for export could not be loaded. Possibly this model was renamed or deleted by another user.
Action:	Click on the button "Refresh" before selecting your models.

[asgmlexp-05]

	Description
Message:	Model <model name>, Instance <instance name>: The subprocess called does not exist. The program will continue. Do you want to be notified of further identical errors?
Cause:	The specified instance refers to a model which cannot be loaded from database (does not exist).
Action:	Correct the model reference.

[asgmlexp-06]

	Description
Message:	Model <model name>, instance <instance name>: The referenced object does not exist. The program will continue. Do you want to be notified of further identical errors?
Cause:	The specified instance refers to a model inter-reference. This model no longer exists.
Action:	Correct the model reference.

[asgmlexp-07]

	Description
Message:	Model <model name>, instance <instance name>: Invalid value for program and/or parameter. The program will continue. Do you want to be notified of further identical errors?
Cause:	The content of an attribute of type "program call" (e.g.External documentation) is invalid.
Action:	Correct the attribute.

[asgmlexp-08]

	Description
Message:	Model <model name>, instance <instance name>: Error when determining the target model. The process will be continued. Should messages of this type still be shown?
Cause:	The specified instance has an inter model relation with no target instance.
Action:	Correct the defective reference accordingly.

[asgmlexp-09]

	Description
Message:	Error in the attribute "documentation configuration". Invalid sorting mode: "<sorting mode>"
Cause:	In the library attribute, an invalid value has been specified as sorting mode.
Action:	Repair the error using the Development Toolkit or contact your ADOxx administrator.

[asgmlexp-10]

	Description
Message:	Error in the attribute "documentation configuration". Invalid target directory for the referenced documents:"<target directory>"
Cause:	The specified target directory does not exist and cannot be created.
Action:	Verify you have write access rights in the target directory and if there is enough memory space in the target directory.

[asgmlexp-12]

	Description
Message:	Error in the attribute "documentation configuration". Invalid model type: "<model type>"
Cause:	The specified model type does not correspond to any model type in the library.
Action:	Verify the exact spelling of the model type.Correct the error using the Development Toolkit or contact your ADOxx administrator.

[asgmlexp-13]

	Description
Message:	Error in the attribute "documentation configuration". No default LIBRARY element is defined in a SOURCE Block.
Cause:	In the library attribute "documentation configuration", no standard settings are defined in an documentation export.
Action:	Correct the error using the Development Toolkit or contact your ADOxx administrator.

[asgmlexp-14]

	Description
Message:	Error in the attribute "documentation configuration". The value "<value>" in the LIBRARY element of the row <no.> is not a whole number.
Cause:	The value specified in the library attribute "documentation configuration" not a whole number.
Action:	Correct the error using the Development Toolkit or contact your ADOxx administrator.

[asgmlexp-15]

	Description
Message:	Model <model name>, instance <instance name>: Create program and/or parameter:An external file was referenced but could not be found. The process will be continued. Should messages of this type still be shown?
Cause:	In an attribute, either an external file has been referenced, which has been meanwhile deleted or moved or an internet address has been entered.
Action:	Correct the reference in the model or copy the missing file to the specified directory. If you have specified an internet address in attributes click on the "No" button to suppress messages of this type in the future.

[asgmlexp-16]

	Description
Message:	Program error: <error code>(<error number>).
Cause:	A general program error has occurred.
Action:	Note the error code and error number and contact your ADOxx administrator.

[asgmlexp-17]

	Description
Message:	Error in the attribute "Documentation configuration". No LIBRARY element has been defined for the model type "<model type name>".
Cause:	No element "LIBRARY" has been defined in the library attribute "Documentation configuration" of an element EXPORT.
Action:	Add an element LIBRARY for the specified model type.

[asgmlexp-18]

	Description
Message:	File "<file name>" could not be copied.
Cause:	The file could either not be found or not be created.
Action:	Verify if the file in the specified directory exists, if there is enough free hard disk memory available and if you have the required access rights.

[asgmlexp-19]

	Description
Message:	Graphic for the model "<model name>" could not be generated.
Cause:	There is either not enough available memory space in the target directory or you do not have sufficient access rights to the target directory.
Action:	Free up memory space or have your access rights extended. Alternatively select another target directory before the generation without the above-mentioned restrictions.

[asgmlexp-20]

	Description
Message:	The specified path "<path>" is invalid for the referenced documents. The process will be continued.
Cause:	The path contains invalid characters or an invalid structure.
Action:	Make sure during the entry of path names, that the total amount does not exceed 120 characters and that no more than seven directories are contained in the path.Moreover the characters / \ : * ? < > and **|**are not allowed.

asik

[asik-01]

Message:	Failure while querying an attribute!
Cause:	A fatal error has occurred from which the system cannot recover.
Action:	If this error re-occurs when the simulation is run again, export your model to an ADL file and contact your ADOxx consultant.

[asik-02]

Message:	Error when searching for instances of a model!
Cause:	A fatal error has occurred from which the system cannot recover.
Action:	If this error re-occurs when the simulation is run again, export your model to an ADL file and contact your ADOxx consultant.

[asik-03]

Message:	Business process model has no start object! Business process model:<model name>
Cause:	The specified model does not contain a start object.
Action:	Check the model and insert an appropriate start object.

[asik-04]

Message:	Resource could not be found! Model:<model name>
Cause:	No resource could be found when evaluating the given AQL command.
Action:	Check the content of attribute "Selection" and check that your working environment model contains corresponding resources.

[asik-05]

Message:	Failed to open the template for the simulation result comparison! Microsoft Excel Version 2000 or higher is required to open the template. Please check, if Microsoft Excel is installed correctly.
Cause:	The template for the simulation result comparison is based on Microsoft Excel. In order to perform such a simulation result comparison, this template has to be opened in Microsoft Excel version 2000 or higher. This was not possible.
Action:	Check if a compatible version of Microsoft Excel is installed on your computer. If not, install the program. If Excel 2000 or higer is availble but the template file still fails to open, then contact your system administrator.

asim1dlg

[asim1dlg-03]

Message:	The input parameters are not defined correctly.A simulation cannot be executed. Please contact your ADOxx consultant.
Cause:	The input parameters for the simulation are not consistent with the class and attribute definitions of the application library.
Action:	Define the attribute "sim mapping" in the Development Toolkit correctly or contact your ADOxxconsultant.

asim1end

[asim1end-01]

Message:	The results values are too large to be transferred to the models.
Cause:	The results values are larger than what the values area of the results attribute allows. This is probably due to the fact that the evaluation was carried out with unusually large input values (e.g. very large performance times and very large process quantities).
Action:	Carry out the evaluation with smaller input values.

asim2dlg

[asim2dlg-07]

Message:	The protocol file contains an invalid path.
Cause:	The protocol file's filename contains an invalid path.
Action:	Correct the filename.

[asim2dlg-15]

Message:	The application model "<model name>" is no longer valid. Please refresh the application models list.
Cause:	You selected an application model which is no longer valid. One or more models of the application model could not be found.
Action:	Refresh the model list by clicking on the button "Refresh" and repeat the action.

[asim2dlg-16]

Message:	The application model "<model name>" does not exist. Please refresh the application models list.
Cause:	You selected an application model which does not exist in the database any more. Presumably, it was deleted by another ADOxx user.
Action:	Refresh the model list by clicking on the button "Refresh" and select a different application model.

[asim2dlg-17]

Message:	The date of the simulation start has to be before the date of the results gathering start!
Cause:	You entered a simulation start date later than the calculation start date into the start window of the workload analysis (fixed-time-period view).
Action:	Define the simulation start date in such a way that it lies before the calculation (result) start date.

[asim2dlg-18]

Message:	The date of the results gathering start has to be before the date of the results gathering end!
Cause:	You entered a calculation start date later than the calculation end date into the start window of the workload analysis (fixed-time-period view).
Action:	Define the calculation start date in such a way that it lies before the calculation (result gathering) end date.

[asim2dlg-21]

Message:	No input parameters for the simulation are defined. (The simulation cannot run.) Please contact your ADOxx customer support
Cause:	An error occurred while the sim mapping was read.The sim mapping is invalid or not defined.
Action:	Define an input parameter configuration in the ADOxx Development Toolkit or contact your ADOxx administrator or customer support.

[asim2dlg-22]

Message:	The protocol file "<File Name>" contains a directory, not a filename.
Cause:	You entered the directory name listed instead of a file name.
Action:	Correct your entry accordingly.

asimmap

[asimmap-01]

	Description
Message:	The sim mapping could not be interpreted correctly.
Cause:	A non-identifiable error occurred during the interpretation of the sim mapping.
Action:	Check the sim mapping in the library configuration in the ADOxx Development Toolkit and correct possible errors or contact your ADOxx administrator.

[asimmap-02]

	Description
Message:	Syntax errors were found in the sim mapping.
Cause:	There is a syntax error in the sim mapping.Perhaps a closing inverted comma is missing or not all of the keywords are written in capital letters.
Action:	Check the sim mapping in the library configuration in the ADOxx Development Toolkit and correct possible errors or contact your ADOxx administrator.

[asimmap-03]

	Description
Message:	The expression "<indicator>" (library attribute "sim mapping") contains errors.
Cause:	An invalid indicator has been used in the sim mapping.
Action:	Correct the specified indicator in the library attribute "sim mapping" or contact your ADOxx administrator.

[asimmap-04]

	Description
Message:	The attribute "<attribute name>" of the sim mapping is corrupt.
Cause:	The sim mapping is incomplete.
Action:	Add the attribute listed to the sim mapping or contact your ADOxx administrator.

[asimmap-05]

	Description
Message:	No entry parameters have been defined. Contact your "ADOxx" administrator to define entry parameter combinations in the library attribute "sim mapping".
Cause:	Your ADOxx application library contains errors.The attribute "sim mapping" must be corrected.
Action:	Contact your ADOxx administrator.

asimobj

[asimobj-01]

Message:	No (available) performer found! <object class>:<object name> Model:<model name>
Cause:	The AQL expression in the attribute "Performer" did not render an (available) performer.
Action:	Check the AQL expression in the attribute "Performer" and make sure that the corresponding working environment model contains at least one suitable performer. In addition the performer has to be available (i.e.the attribute "Presence" has to be set to a value greater than zero).

[asimobj-02]

Message:	No process calendar supplied for any process model of the application model.
Cause:	None of the process models of the application model has a process calendar. Therefore, there is nothing to be simulated. A workload analysis cannot take place.
Action:	If you wish to run a Workload Analysis, you have to define process calendars in the main processes to be simulated.

[asimobj-03]

Message:	Some of your simulation results have exceeded the maximum integer value. The simulation will be aborted!
Cause:	The simulation time is exceeding the period of time which ADOxx is able to represent.
Action:	Check whether you entered the correct times everywhere in your business process models. If the times are okay, try it with a smaller number of runs. Should this be impossible, contact your ADOxx consultant.

[asimobj-04]

Message:	You did not enter any times of presence for the performers in your working environment model. Model:<model name>
Cause:	All performers of your working environment model are regarded as permanently absent. Therefore, there is nothing to simulate.
Action:	Enter times of presence for the performers of your working environment model via the performers' calendars.

[asimobj-05]

Message:	Error reading a performer calendar.
Cause:	A runtime error occurred while a performer calendar was read.
Action:	If the error occurs again after re-starting the simulation, export the model into an ADL file and inform your ADOxx consultant.

[asimobj-06]

Message:	No further times of presence exist for any performer of your working environment. The simulation will be aborted.
Cause:	According to the calendars of the performers in your working environment, there are no times of presence after the present time. Since there is nothing left to be simulated, the simulation is aborted.
Action:	Either enter further times of presence which exceed the current point of time in the simulation or shorten the simulation time by decreasing the number of runs or the number of oscillation phases.

[asimobj-07]

Message:	Illegal interruption of a synchronous cooperative activity!
Cause:	During the simulation is has been tried to illegally interrupt a synchronous cooperative activity. This is not possible.
Action:	Correct the model to be simulated.

asimtext

[asimtext-01]

	Description
Message:	The library attribute "SimText" is not defined.
Cause:	The library attribute "SimText" is not defined.
Action:	Define the library attribute "SimText" in the Development Toolkit. If necessary, contact your ADOxx administrator.

[asimtext-02]

	Description
Message:	The library attribute "SimText" is not defined. The expression "<Expression>" is incomplete or undefined.
Cause:	The expression listed could not be found in the library attribute "Simtext". The library attribute "Simtext" of the BP library either contains a value which is incorrect or incomplete or is not defined.
Action:	Check the library attribute "Simtext" in the Development Toolkit and correct the definition of the expression listed. If necessary, contact your ADOxx administrator.

asqladm

[asqladm-01]

Message:	Serious error: No MSDE or SQL Server default instance found. Program will terminate.
Cause:	There is no "MSDE" or "SQL Server" default instance installed on your computer.
Action:	Install either "MSDE" or "SQL Server Express Edition" from your ADOxx installation CD-ROM or create a SQL Server default instance. (Further information about creating a SQL Server default instance can be derived from the SQL Server documentation.)

[asqladm-04]

Message:	A database with the specified name already exists as ODBC data source. Enter another database name.
Cause:	An ODBC data source with the specified name already exists.
Action:	Enter another database name.

[asqladm-05]

Message:	A database with the name entered already exists. Enter a different name.
Cause:	You have tried to enter a name already assigned to an existing database.
Action:	Choose a different database name.

[asqladm-06]

Message:	Serious error: SQL Server is stopped and could not be started. Try to start SQL Server manually. If this message is shown again, contact your system administrator.
Cause:	The database server has been stopped and could not be restarted automatically.
Action:	Restart the MSDE or SQL Server manually. If the problem still exists afterwards, contact your system administrator.

[asqladm-07]

Message:	The specified licence number does not entitle you to create a new database. If necessary, contact your ADOxx administrator.
Cause:	No new databases can be created with the specified licence number.
Action:	Specify a licence number, which entitles you to create a new database. Contact your ADOxx administrator if necessary.

[asqladm-08]

Message:	Serious error: The Template-Script to create the database is not available or could not be opened. Contact your ADOxx administrator.
Cause:	The file "createdb.tpl" is not available in the ADOxx program directory.
Action:	Make sure that the file "createdb.tpl" is available in the ADOxx program directory.If necessary, contact your ADOxx administrator.

[asqladm-09]

Message:	Serious error: The Script to create the database is not available or could not be opened.
Cause:	The file "createdb.sql" is not available in the ADOxx program directory.
Action:	Make sure that the user currently logged on has write rights on the ADOxx program directory. If necessary, contact your ADOxx administrator.

[asqladm-10]

Message:	Serious error: The user 'ADOxx' could not be created.
Cause:	The user 'ADOxx' could not be created
Action:	Restart the program and try to create a new database.Should the error occur again, contact your ADOxx administrator.

[asqladm-11]

Message:	Serious error: The ADOxx database could not be opened.
Cause:	The ADOxx database could not be opened.
Action:	Restart the program and try to create a new database.Should the error occur again, contact your ADOxx administrator.

[asqladm-12]

Message:	The ODBC data source could not be installed.
Cause:	No ODBC data source could be created for the specified database.
Action:	Restart the program and try again to create a new database. Should the error occur again, contact your ADOxx administrator.

Hint: When using Windows Vista you can open the programm via the context menu item "Run as Administrator". The "User Access Control" of Windows Vista prevents to run applications with administration-rights per default.

[asqladm-13]

Message:	Error when creating the database. The ADOxx database could not be initialised.
Cause:	An error has occurred during the execution of the program to initialise the database.
Action:	Restart the program and try again to create a new database. Should the error occur again, contact your ADOxx administrator.

[asqladm-14]

Message:	Unable to delete the ADOxx database. Maybe there are still users being connected to the database.
Cause:	An error occurred when deleting the database.
Action:	Restart the program, logoff all users and try again to delete the database. Should the error occur again, contact your ADOxx administrator.

[asqladm-15]

Message:	The ODBC entry of the ADOxx database could not be deleted. If necessary, remove it manually from the ODBC data source administration.
Cause:	The entry of the database in the ODBC data source administration could not be deleted.
Action:	Delete the entry manually from the ODBC data source administration. If necessary, contact your ADOxx administrator.

[asqladm-16]

Message:	Invalid path or file name. If necessary, transfer the proposed values.
Cause:	The specified path and/or file name is invalid.
Action:	Enter another path and/or file name or accept the proposed values.

[asqladm-17]

Message:	Backup could not be executed. The Template Script for database backup is not available or could not be opened.
Cause:	The file "backMSDE.tpl" is not available in the ADOxx program directory.
Action:	Make sure that the file "backMSDE.tpl" is available in the ADOxx program directory.Contact your ADOxx administrator if necessary.

[asqladm-18]

Message:	Backup could not be executed. The Script to backup the database is not available or could not be opened.
Cause:	The file "backMSDE.sql" is not available in the ADOxx program directory.
Action:	Make sure that the user currently logged in has write access to the ADOxx program directory.If necessary, contact your ADOxx administrator.

[asqladm-19]

Message:	An error occured during backup of the ADOxx database. The backup has not been successful. Make sure that you have write-access to the backup directory.Note that saving is only possible in the default backup directory of the SQL Server directory.
Cause:	An error has occurred during the backup of the ADOxx database.
Action:	Restart the program and attempt to save the ADOxx database again. Note that saving is only possible in the default backup directory of the SQL Server directory. Should the error occur again, contact your ADOxx administrator.

[asqladm-20]

Message:	Unable to restore database. The template script to restore the database is not available or could not be opened.
Cause:	The file "restMSDE.tpl" is not available in the ADOxx program directory.
Action:	Make sure that the file "restMSDE.tpl" is available in the ADOxx program directory. If necessary, contact your ADOxx administrator.

[asqladm-21]

Message:	Unable to restore database. The Script to restore the database is not available or could not be opened.
Cause:	The file "restMSDE.sql" is not available in the ADOxx program directory.
Action:	Make sure that the user currently logged in has write access to the ADOxx program directory.If necessary, contact your ADOxx administrator.

[asqladm-22]

Message:	An error has occurred during the restoration of the ADOxx database. The restoration could not be executed.
Cause:	An error occurred during the restoration of the ADOxx database.
Action:	Restart the program and try again to save the ADOxx database. Should the error occur again, contact your ADOxx administrator.

[asqladm-23]

Message:	The entered key words don't correspond.
Cause:	Both entered key words don't correspond.
Action:	Enter the key word again and make sure that both key words correspond.

[asqladm-24]

Message:	Wrong old password. Could not change password of the database default administrator "sa".
Cause:	The specified old password of the database default administrator "sa" is wrong.
Action:	Enter the correct old password.

[asqladm-27]

Message:	Invalid file name. You can change the path, NOT the file name of the backup file.
Cause:	The file name of the backup file has been changed (=database name of the database to be saved). It is only permitted to change the path of the backup file, since otherwise a restoration is not possible.
Action:	Restart the storage process. Transfer the recommended values or change the path of the backup file.The file name must be "<database name>.bkp".

[asqladm-28]

Message:	The database system "SQL Server" can not be found on this computer.You might not have sufficient access permissions to access SQL Server.Make sure that SQL Server is installed and that you can access it. If theproblem persists, contact your system administration.
Cause:	Possibly SQL Server or MSDE is not installed on your computer or you haven't the sufficient access permissions to access SQL Server.
Action:	Make sure that SQL Server or MSDE is installed on your computer, if the problem occurs again contact your system administrator.

[asqladm-29]

Message:	Error initialising the database administration program!SQL Server may not be started or SQL Server may not be installed properly.Program will exit now.Please contact your ADOxx customer support.
Cause:	An error occured with initialising the database administration program. Maybe SQL Server has not been started or is not installed.
Action:	Make sure that SQL Server is installed on your computer. Contact your your ADOxx administrator.

[asqladm-30]

Message:	The database name is not valid.Consider the following guidelines for a valid database name:- The database name must contain at least 3 characters.- The database name may not contain more than 8 characters.- The database name must not start with a digit.- The database name may only contain the characters a - z, A - Z, '_' and the digits 0 - 9.- The database name must not be "adoxx".Enter a valid database name.
Cause:	You have entered a database name which is not valid. Please consider that the database name must contain no less than three and no more than eight characters. The database must not start with a digit and only consists of the characters a - z, A - Z, '_' and the digits 0 - 9. The name ADOxx also must not be used as the database name.
Action:	Make sure you have considered all the guidelines and try it again.

[asqladm-31]

Message:	The restore file file name could not be opened! Please make sure that the file name is correct and the file does really exist.Note that restoring is only possible from the default restore directory of the SQL Server directory.
Cause:	The restore file specified could not be found.
Action:	Check if the file name is correct and if the file really exists. Note that restoring is only possible from the default restore directory of the SQL Server directory.

[asqladm-32]

Message:	The current instance could not be changed!
Cause:	The password for the default database administrator "sa" is not correct for the selected instance.
Action:	Enter the correct password.

[asqladm-33]

Message:	The SQL server service for the instance <instance name> is not started!Either start the service manually or choose - if available - another instance. or The SQL server service for the default instance is not started!Either start the service manually or choose - if available - another instance.
Cause:	The SQL server service for the selected or the default instance is not started.
Action:	Either start the service manually or choose - if available - another instance.

asrchmod

[asrchmod-01]

Message:	Error while copying: Not all values could be pasted!
Cause:	An error has occurred during the paste in the ADOxx browser. Not all values to be inserted have been assigned.
Action:	Check if the area to be pasted is not too large and if the attribute types correspond. Check if it is possible to paste in the area you have selected. An insertion is not possible if the model, which model attribute should be changed by the insertion, is not loaded or if it is loaded only with read access.

[asrchmod-02]

Message:	Error while copying: No value could be inserted!
Cause:	During the pasting in the ADOxx browser, none of the value assigned could be pasted.
Action:	Check if the area to be pasted is not too large and if the attribute types correspond. Check if the pasting is allowed within the area you have selected. An insertion is not possible if the model, which model attribute should be changed by the insertion, is not loaded or if it is loaded only with read access.

asrchtlb

[asrchtlb-01]

	Description
Message:	Saving the contents of the model select box failed!
Cause:	An illegal file name was entered in the "Save as" window of the model select box.
Action:	Please enter a file name that is permitted and make sure that there is sufficient storage space on the data medium.

astarth

[astarth-01]

Message:	The start of the process<command rows> went wrong!
Cause:	The attempt to start the specified program went wrong.
Action:	Contact you system administrator. The program is either to be installed or system settings must be adjusted.

astdcfg

[astdcfg-01]

	Description
Message:	Error when creating the <%mm>: The class "<class name>" could not be created! Super class: "<super class name>" Error code:<error code> ADOxx will be closed!
Cause:	The configuration of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

[astdcfg-02]

	Description
Message:	Error when creating the <%mm>: The relation class "<relation class name>" could not be created! From class: "<starting class name>" To class: "<target class name>" Error code:<error code> ADOxx will be closed!
Cause:	The configuration of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

[astdcfg-03]

	Description
Message:	Error when creating the <%mm>: The attribute "<attribute name>" could not be created! Owner: "<owner name>" Error code:<error code> ADOxx will be closed!
Cause:	The configuration of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

[astdcfg-04]

	Description
Message:	Error when creating the <%mm>: No value could be assigned to the attribute "<attribute name>"! Owner: "<owner name>" Value: "<value>" Error code:<error code> ADOxx will be closed!
Cause:	The configuration of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

[astdcfg-05]

	Description
Message:	Error when creating the <%mm>: No value could be assigned to the facet "<facet name>"! Attribute: "<attribute name>" Value: "<value>" Error code:<error code> ADOxx will be closed!
Cause:	The configuration of your ADOxx database contains errors.
Action:	Contact your ADOxx administrator.

asubsrch

[asubsrch-01]

Message:	The Business process model <model name> does not exist.
Cause:	The specified business process model does not exist.
Action:	Enter the name of an existing model.

asuibrw

[asuibrw-01]

Message:	Select the attributes which should be displayed in the diagram!
Cause:	You have not selected any attributes for the diagram.
Action:	Select the attributes which should be displayed in the diagram.

[asuibrw-02]

Message:	The action could not be performed, as the concerned model was deleted in the meantime!Perform the simulation again.
Cause:	A model which was used by the simulation has been deleted in the meantime.
Action:	Close all windows concerning the simulation and start the simulation again.

[asuibrw-03]

Message:	The action could not be performed, as the concerned object was deleted in the meantime!Perform the simulation again.
Cause:	An object which was used by the simulation has been deleted in the meantime.
Action:	Close all windows concerning the simulation and start the simulation again.

asysbox

[asysbox-01]

	Description
Message:	System user groups could not be loaded.
Cause:	When loading system user groups from the system an error occurred.
Action:	Please try again and if necessary contact your ADOxx consultant.

[asysbox-02]

	Description
Message:	System users could not be loaded.
Cause:	When loading system users from the system an error occurred.
Action:	Please try again and if necessary contact your ADOxx consultant.

[asysbox-03]

	Description
Message:	System users of the system user group "<system user group name>" could not be loaded.
Cause:	When loading system users from the system group an error occurred.
Action:	Please try again and if necessary contact your ADOxx consultant.

[asysbox-04]

	Description
Message:	The domain "<Domain name>" could not be initialised.
Cause:	Within the current system environment no domain could be found or you do not have access rights for the existing domains.
Action:	Log off from the system and login to a domain of which your computer is a member. Note: You CANNOT load domains when you are logged in at the local domain of your computer or your computer is not a member of a work group and therefore not member of a domain. If necessary please contact your ADOxx consultant.

[asysbox-05]

	Description
Message:	The list of system domains could not be loaded.
Cause:	Within the current system environment no domain could be found or you do not have access rights for the existing domains.
Action:	Log off from the system and login to a domain your computer is a member. Note: You CANNOT load domains when you are logged in locally or your computer is not a member of a work group and therefore not a member of a domain. If necessary please contact your system administrator.

ausmgt

[ausmgt-01]

	Description
Message:	No application library was selected!
Cause:	You did not select any of the application libraries listed.
Action:	Select by mouse-click the application library you wish to assign to the ADOxx user.

[ausmgt-02]

	Description
Message:	Passwords are not consistent!
Cause:	Your entry for re-confirming the password does not match the password entry.
Action:	Enter the same password twice. (**Note:**The system distinguishes between capital and small letters!)

[ausmgt-03]

	Description
Message:	Password must not be shorter than three characters!
Cause:	You entered a password shorter than three characters.
Action:	Enter a password which is at least three characters in length.

[ausmgt-05]

	Description
Message:	The user already exists!
Cause:	You tried to add an ADOxx user who is already stored in the ADOxx database.
Action:	Enter a different user name for the ADOxx user to be added.

[ausmgt-13]

	Description
Message:	The user "<user name>" does not exist!
Cause:	The ADOxx user has possibly been already deleted by another ADOxx administrator.
Action:	Close the error message - the user list will automatically be updated - and repeat the action. Should the error appear again, close ADOxx and restart the application. Should the error appear again, contact your ADOxx administrator.

[ausmgt-14]

	Description
Message:	The user name must have at least three characters.
Cause:	You entered a password shorter than three characters.
Action:	Enter a password which is at least three characters in length.

[ausmgt-15]

	Description
Message:	The new password contains restricted characters! Please only use characters in the ASCII (resp. ANSI) range 32 to 126 (exceptions: ' { } and @) and no umlauts.
Cause:	You entered restricted characters or umlauts when entering the password.
Action:	The characters permitted for the password are only the numbers 0 to 9, the letters a to zand A to Z and special characters exept of ** ' { } and @. Umlauts and ** ' { } and @ must not be used.

[ausmgt-16]

	Description
Message:	Invalid filename entered!
Cause:	You have entered an invalid filename for user import or export.
Action:	Check your input.

[ausmgt-17]

	Description
Message:	No filename entered!
Cause:	No filename has been entered for user import or export.
Action:	Enter a filename.

[ausmgt-18]

	Description
Message:	The user has not been assigned to any user group!
or
Message:	The selected users have not been assigned to any user group!
Cause:	Each user must be assigned to a user group.
Action:	Assign the user(s) (button "user groups").

[ausmgt-19]

	Description
Message:	File <filename> does not exist!!
Cause:	You entered a file which does not exist for the user import.
Action:	Check the path and the file name entered and repeat the action.

[ausmgt-21]

	Description
Message:	Some tasks could not be processed as the user list has been changed by another user. The user list has been updated.
Cause:	Another ADOxx administrator has changed the user list and therefore your tasks could not be performed.
Action:	The user list has been updated accordingly. Please repeat the intended tasks.

[ausmgt-22]

	Description
Message:	The character '<Invalid character>' is not allowed in user names. Allowed characters include the alphanumerics a-z A-Z 0-9 as well as blanks and the characters '.' (full stop), '-' (hyphen) and '_' (underscore).
Cause:	You entered a password with an invalid character.
Action:	Enter a password using the following permitted characters only: Alphanumerics a-z, A-Z, and 0-9 as well as blanks and the characters '.' (full stop), '-' (hyphen) and '_' (underscore).

[ausmgt-23]

	Description
Message:	The system user <user> of the domain <domain> does not exist!
Cause:	The system user doesn't exist in the domain, maybe it was deleted from the domain.
Action:	Update the user list and repeat it again.

[ausmgt-24]

	Description
Message:	The user <user> could not be created!The current licence number only allows that at most <number> users are created.
Cause:	The user can't be created because the number of your licence supported users allready exist.
Action:	Delete an existing user to create a new one. If you want to extend your licence to increase the number of users contact the ADOxx administrator.

[ausmgt-25]

	Description
Message:	Error while resetting the workstation key!
Cause:	Possibly an error occurred with your connection to the ADOxx database.
Action:	If the error re-occurs, then please contact your ADOxx administrator.

[ausmgt-26]

	Description
Message:	The user <username> can not be deleted as he is currently logged in!
Cause:	The user you want to delete is logged in at the moment.
Action:	Log the user off and delete it again.

[ausmgt-27]

	Description
Message:	The user <username> can not be deleted as he is currently logged in!Only the other selected users can be deleted.Do you want to proceed anyway?
Cause:	The user you want to delete is logged in at the moment.
Action:	Continue without deleting the user or log the user off and delete it again.

[ausmgt-28]

	Description
Message:	The user "<username>" can not be renamed as he is currently logged in!
Cause:	The user you want to rename is logged in at the moment.
Action:	Log the user off and rename it again.

[ausmgt-29]

	Description
Message:	The user "<username>" can not be renamed as he is a system user!
Cause:	The user you want to rename is a system user.
Action:	System users are not created in ADOxx therefor they also can not be renamed here.

[ausmgt-30]

	Description
Message:	An error occured while renaming user "<username>"!
Cause:	An error occurred while renaming the user. It is possible that your connection to the database server has been aborted or the database server is overloaded.
Action:	Repeat the action. Should the error appear again, exit ADOxx and re-start the application. Should the error occur again, contact your database or ADOxx administrator.

[ausmgt-31]

	Description
Message:	The user "<username>" could not be copied!
Cause:	An error occurred while copying the user. It is possible that your connection to the database server has been aborted or the database server is overloaded.
Action:	Repeat the action. Should the error appear again, exit ADOxx and re-start the application. Should the error occur again, contact your database or ADOxx administrator.

[ausmgt-32]

	Description
Message:	The user "<username>" can not be copied as he is a system user! or The users "<usernames>" can not be copied as they are system users!
Cause:	The user you want to rename is a system user respectively the users you want to rename are system users.
Action:	System users are not created in ADOxx therefor they also can not be edited or copied in ADOxx.

[ausmgt-33]

	Description
Message:	The user "<username>" could not be deleted, because sub-administrators can not delete other sub-administrators!
Cause:	The user you want to delete is a sub-administrator. Sub-administrators are not allowed to delete other sub-administrators.
Action:	Contact your ADOxx administrator.

[ausmgt-34]

	Description
Message:	The user <username> could not be copied, because sub-administrators can not copy other sub-administrators!
Cause:	You tried to copy another sub-administrator as a sub-administrator.
Action:	You need administration rights to copy a sub-administrator.

[ausmgt-35]

	Description
Message:	The user <username> can not be renamed, because sub-administrators can not rename other sub-administrators!
Cause:	You tried to rename another sub-administrator as a sub-administrator.
Action:	You need administration rights to rename a sub-administrator.

[ausmgt-36]

	Description
Message:	The user <username> could not be created!
Cause:	Your administration rights have possibly been changed in the meanwhile.
Action:	Close the error message and repeat the action. Should the error appear again, close ADOxx and restart the application. Should the error appear again, contact your ADOxx administrator.

[ausmgt-37]

	Description
Message:	The user <username> is invalid.Blanks are only allowed in combination with other valid characters.Leading and trailing blanks are not allowed.Allowed characters include the alphanumerics a-z A-Z 0-9 as well as blanks and the characters '.' (full stop),'-' (hyphen) and '_' (underscore).
Cause:	The username either consists solely of blanks or includes leading or trailing blanks.
Action:	Correct the user name accordingly. Please note that blanks must be combined with other characters. Leading and trailing blanks are not allowed.

[ausmgt-38]

	Description
Message:	The user settings could not be changed!
Cause:	An error occurred while changing the user settings. Maybe the connection to the database server has been interrupted or your access rights have been changed.
Action:	Quit ADOxx and restart ADOxx. If the error occurs again, contact your ADOxx administrator.

avedbox

[avedbox-01]

	Description
Message:	Figures chain "<Text>" not found!
Cause:	The figures chain searched for does not appear in the text field.
Action:	The search has possibly not been carried out from the beginning of the text. If necessary place the cursor at the beginning of the text field before starting the search.

averdate

[averdate-01]

	Description
Message:	Internal error: the version handler has not been initialised.
Cause:	An internal error has occurred.
Action:	Contact your ADOxx administrator.

[averdate-02]

	Description
Message:	A syntactical error has occurred when parsing the expression: <LEO expression>
Cause:	The value of the library attribute "versioning format" contains errors. The specified LEO expression contains syntactical errors. Pay attention to the appropriate [aleo] error message.
Action:	Correct the value of the library attribute "versioning format" and pay attention to the specified [aleo] error message or contact your ADOxx administrator.

[averdate-04]

	Description
Message:	The key word "VERSIONING" has not been found.
Cause:	The first key word of the LEO expressions is not "VERSIONING".
Action:	Correct the value of the library attribute "versioning format" by inserting the key word "VERSIONING" at the first position or contact your ADOxx administrator.

[averdate-05]

	Description
Message:	An invalid key word has been used.
Cause:	The LEO expression contains an invalid key word.
Action:	Correct the value of the library attribute "versioning format" by deleting all invalid key words or contact your ADOxx administrator. Valid key words are "VERSIONING", "START_DATE", "TEXT_FIELD", "DAY_FIELD", "MONTH_FIELD" and "YEAR_FIELD".

[averdate-06]

	Description
Message:	The start date can only be defined once.
Cause:	The LEO expression contains the key word "START_DATE" more than once.
Action:	Correct the value of the library attribute "versioning format" by deleting all unnecessary "START_DATE" key words or contact your ADOxx administrator.

[averdate-07]

	Description
Message:	The day field can only be defined once.
Cause:	The LEO expression contains the key word "DAY_FIELD" more than once.
Action:	Correct the value of the library attribute "versioning format" by deleting all unnecessary "DAY_FIELD" key words or contact your ADOxx administrator.

[averdate-08]

	Description
Message:	The month field can only be defined once.
Cause:	The LEO expression contains the key word "MONTH_FIELD" more than once.
Action:	Correct the value of the library attribute "versioning format", by removing all unnecessary "MONTH_FIELD" key words or contact your ADOxx administrator.

[averdate-09]

	Description
Message:	The year field can only be defined once.
Cause:	The LEO expression contains the key word "YEAR_FIELD" more than once.
Action:	Correct the value of the library attribute "versioning format", by removing all unnecessary "YEAR_FIELD" key words or contact your ADOxx administrator.

[averdate-10]

	Description
Message:	The value of the day attribute in the start date is too small. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "START_DATE":The value of the attribute "day" is too small.
Action:	Correct the value of the library attribute "versioning format", by specifying the attribute "day" of the key word "START_DATE" with a valid value between 1 and 31 or contact your ADOxx administrator.

[averdate-11]

	Description
Message:	The value of the day attribute in the start date is too high. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "START_DATE":The value of the attribute "day" is too high.
Action:	Correct the value of the library attribute "versioning format", by specifying the attribute "day" of the key word "START_DATE" with a valid value between 1 and 31 or contact your ADOxx administrator.

[averdate-12]

	Description
Message:	The value of the month attribute in the start date is too small. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "START_DATE":the value of the attribute "month" is too small.
Action:	Correct the value of the library attribute "versioning format" by specifying the attribute "month" of the key word "START_DATE" with a valid value between 1 and 12 or contact your ADOxx administrator.

[averdate-13]

	Description
Message:	The value of the month attribute in the start date is too high. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "START_DATE":the value of the attribute "month" is too high
Action:	Correct the value of the library attribute "versioning format", by specifying the attribute "month" of the key word "START_DATE" with a valid value between 1 and 12 or contact your ADOxx administrator.

[averdate-14]

	Description
Message:	The value of the year attribute in the start date is too small. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "START_DATE":the value of the attribute "year" is too small.
Action:	Correct the value of the library attribute "versioning format", by specifying the attribute "year" of the key word "START_DATE" with a valid value between 0 and 9999 or contact your ADOxx administrator.

[averdate-15]

	Description
Message:	The value of the year attribute in the start date is too high. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "START_DATE":the value of the attribute "year" is too high.
Action:	Correct the value of the library attribute "versioning format", by specifying the attribute "year" of the key word "START_DATE" with a valid value between 0 and 9999 or contact your ADOxx administrator.

[averdate-16]

	Description
Message:	The minimum value of the day field is greater than the maximum value.
Cause:	An error has occurred in the key word "DAY_FIELD":the value of the attribute "minimum" is greater than the value of the attribute "maximum".
Action:	Correct the value of the library attribute "versioning format" by specifying in key word "DAY_FIELD" the value of the attribute "minimum" with a value, which is smaller than the value of the attribute "maximum" or contact your ADOxx administrator.

[averdate-17]

	Description
Message:	The minimum value of the month field is greater than the maximum value.
Cause:	An error has occurred in the key word "MONTH_FIELD":the value of the attribute "minimum" is greater than the value of the attribute "maximum".
Action:	Correct the value of the library attribute "versioning format", by specifying in key word "MONTH_FIELD" the value of the attribute "minimum" with a value, which is smaller than the value of the attribute "maximum" or contact your ADOxx administrator.

[averdate-18]

	Description
Message:	The minimum value of the year field is greater than the maximum value.
Cause:	An error has occurred in the key word "YEAR_FIELD":the value of the attribute "minimum" is greater than the value of the attribute "maximum".
Action:	Correct the value of the library attribute "versioning format", by specifying in key word "YEAR_FIELD" the value of the attribute "minimum" with a value, which is smaller than the value of the attribute "maximum" or contact your ADOxx administrator.

[averdate-19]

	Description
Message:	The default value of the day field is too small. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "DAY_FIELD":the value of the attribute "default" is either not in the area 1 to 31 or the value is smaller than the value of the attribute "minimum".
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "default" in the key word "DAY_FIELD" with a value, which is both between the values of the attributes "minimum" and "maximum" and between 1 and 31 or contact your ADOxx administrator.

[averdate-20]

	Description
Message:	The default value of the day field is too high. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "DAY_FIELD":the value of the attribute "default" is either not in the area 1 to 31 or the value is higher than the value of the attribute "maximum".
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "default" in the key word "DAY_FIELD" with a value, which is both between the values of the attributes "minimum" and "maximum" and between 1 and 31 or contact your ADOxx administrator.

[averdate-21]

	Description
Message:	The minimum value of the day field is too small. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "DAY_FIELD":the value of the attribute "minimum" is too small.
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "minimum" in the key word "DAY_FIELD" with a value between 1 and 31 or contact your ADOxx administrator.

[averdate-22]

	Description
Message:	The minimum value of the day field is too high. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "DAY_FIELD":the value of the attribute "minimum" is too high.
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "minimum" in the key word "DAY_FIELD" with a value between 1 and 31 or contact your ADOxx administrator.

[averdate-23]

	Description
Message:	The maximum value of the day field is too small. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "DAY_FIELD":the value of the attribute "maximum" is too small.
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "maximum" in the key word "DAY_FIELD" with a value between 1 and 31 or contact your ADOxx administrator.

[averdate-24]

	Description
Message:	The maximum value of the day field is too high. It is only allowed within the area <1> to <31>.
Cause:	An error has occurred in the key word "DAY_FIELD":the value of the attribute "maximum" is too high.
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "maximum" in the key word "DAY_FIELD" with a value between 1 and 31 or contact your ADOxx administrator.

[averdate-25]

	Description
Message:	The default value of the month field is too small. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "MONTH_FIELD":the value of the attribute "default" is either not in the area 1 to 12 or the value is smaller than the value of the attribute "minimum".
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "default" in the key word "MONTH_FIELD" with a value, which is both between the values of the attributes "minimum" and "maximum" and between 1 and 12 or contact your ADOxx administrator.

[averdate-26]

	Description
Message:	The default value of the month field is too high. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "MONTH_FIELD":the value of the attribute "default" is either not in the area 1 to 12 or the value is greater than the value of the attribute "maximum".
Action:	Correct the value of the library attribute "versioning format" by specifying the value of the attribute "default" in the key word "MONTH_FIELD" with a value, which is both between the values of the attributes "minimum" and "maximum" and between 1 and 12 or contact your ADOxx administrator.

[averdate-27]

	Description
Message:	The minimum value of the month field is too small. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "MONTH_FIELD":the value of the attribute "minimum" is too small.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "MONTH_FIELD" the value of the attribute "minimum" with a value between 1 and 12 or contact your ADOxx administrator.

[averdate-28]

	Description
Message:	The minimum value of the month field is too high. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "MONTH_FIELD":the value of the attribute "minimum" is too high.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "MONTH_FIELD" the value of the attribute "minimum" with a value between 1 and 12 or contact your ADOxx administrator.

[averdate-29]

	Description
Message:	The maximum value of the month field is too small. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "MONTH_FIELD":the value of the attribute "maximum" is too small.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "MONTH_FIELD" the value of the attribute "maximum" with a value between 1 and 12 or contact your ADOxx administrator.

[averdate-30]

	Description
Message:	The maximum value of the month field is too high. It is only allowed within the area <1> to <12>.
Cause:	An error has occurred in the key word "MONTH_FIELD":the value of the attribute "maximum" is too high.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "MONTH_FIELD" the value of the attribute "maximum" with a value between 1 and 12 or contact your ADOxx administrator.

[averdate-31]

	Description
Message:	The default value of the year field is too small. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "YEAR_FIELD":the value of the attribute "default" is either not within the area 0 to 9999 or the value is smaller than the value of the attribute "minimum".
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "YEAR_FIELD" the value of the attribute "default" with a value which is both between the values of the attributes "minimum" and "maximum" and between 0 and 9999 or contact your ADOxx administrator.

[averdate-32]

	Description
Message:	The default value of the year field is too high. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "YEAR_FIELD":the value of the attribute "default" is either not within the area 0 to 9999 or the value is greater than the value of the attribute "maximum".
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "YEAR_FIELD" the value of the attribute "default" with a value which is both between the values of the attributes "minimum" and "maximum" and between 0 and 9999 or contact your ADOxx administrator.

[averdate-33]

	Description
Message:	The minimum value of the year field is too small. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "YEAR_FIELD":the value of the attribute "minimum" is too small.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "YEAR_FIELD" the value of the attribute "minimum" with a value between 0 and 9999 or contact your ADOxx administrator.

[averdate-34]

	Description
Message:	The minimum value of the year field is too high. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "YEAR_FIELD":the value of the attribute "minimum" is too high.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "YEAR_FIELD" the value of the attribute "minimum" with a value between 0 and 9999 or contact your ADOxx administrator.

[averdate-35]

	Description
Message:	The maximum value of the year field is too small. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "YEAR_FIELD":the value of the attribute "maximum" is too small.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "YEAR_FIELD" the value of the attribute "maximum" with a value between 0 and 9999 or contact your ADOxx administrator.

[averdate-36]

	Description
Message:	The maximum value of the year field is too high. It is only allowed within the area <0> to <9999>.
Cause:	An error has occurred in the key word "YEAR_FIELD":the value of the attribute "maximum" is too high.
Action:	Correct the value of the library attribute "versioning format", by specifying in the key word "YEAR_FIELD" the value of the attribute "maximum" with a value between 0 and 9999 or contact your ADOxx administrator.

[averdate-37]

	Description
Message:	The value of the day field is too small. It is only allowed within the area <1> to <31>.
Cause:	The day of the specified date is either smaller than the value of the attribute "minimum" of the key word "DAY_FIELD" or less than 1.
Action:	Change the date, so that the day is between Minimum and Maximum or between 1 and 31.

[averdate-38]

	Description
Message:	The value of the day field is too high. It is only allowed within the area <1> to <31>.
Cause:	The day of the specified date is either greater than the value of the attribute "maximum" of the key word "DAY_FIELD" or greater than 1.
Action:	Change the date, so that the day is between Minimum and Maximum or between 1 and 31.

[averdate-39]

	Description
Message:	The value of the month field is too small. It is only allowed within the area <1> to <12>.
Cause:	The day of the specified date is either smaller than the value of the attribute "minimum" of the key word "MONTH_FIELD" or smaller than 1.
Action:	Change the date, so that the month is between Minimum and Maximum or between 1 and 12.

[averdate-40]

	Description
Message:	The value of the month field is too high. It is only allowed within the area <1> to <12>.
Cause:	The day of the specified date is either greater than the value of the attribute "maximum" of the key word "MONTH_FIELD" or greater than 1.
Action:	Change the date, so that the month is between Minimum and Maximum or between 1 and 12.

[averdate-41]

	Description
Message:	The value of the year field is too small. It is only allowed within the area <0> to <9999>.
Cause:	The day of the specified date is either smaller than the value of the attribute "minimum" of the key word "YEAR_FIELD" or smaller than 0.
Action:	Change the date, so that the year is between Minimum and Maximum or between 0 and 9999.

[averdate-42]

	Description
Message:	The value of the year field is too high. It is only allowed within the area <0> to <9999>.
Cause:	The day of the specified date is either greater than the value of the attribute "maximum" of the key word "YEAR_FIELD" or greater than 9999.
Action:	Change the date, so that the year is between Minimum and Maximum or between 0 and 9999.

[averdate-43]

	Description
Message:	The internal display of the date is not correct.
Cause:	An internal error has occurred: the format of the date is invalid.
Action:	Contact your ADOxx administrator.

[averdate-44]

	Description
Message:	The internal display of the date contains a day although no day field is defined.
Cause:	An internal error has occurred: the format of the date is invalid.
Action:	Contact your ADOxx administrator.

[averdate-45]

	Description
Message:	The internal display of the date contains a month although no month field is defined.
Cause:	An internal error has occurred: the format of the date is invalid.
Action:	Contact your ADOxx administrator.

[averdate-46]

	Description
Message:	The internal display of the date contains a year although no year field is defined.
Cause:	An internal error has occurred: the format of the date is invalid.
Action:	Contact your ADOxx administrator.

[averdate-47]

	Description
Message:	The specified date cannot be increased.
Cause:	The specified date is the last possible date.
Action:	Use an earlier date since this is the last possible date or contact your ADOxx administrator.

[averdate-48]

	Description
Message:	Error when parsing the string: The content of the text field does not correspond with the defined content.
Cause:	A string has been found which does not correspond to the one in the library attribute "versioning format".
Action:	Adapt the string that it corresponds with the format defined in the library attribute "versioning format".Pay attention to the order! If necessary, contact your ADOxx administrator.

[averdate-49]

	Description
Message:	Error when parsing the string: The month name is not valid.
Cause:	The name of a month is expected but could not be found.
Action:	Possible month names are "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November" and "December".

[averdate-50]

	Description
Message:	Error when parsing the string: The string contains additional characters.
Cause:	The string contains excess characters.
Action:	Adapt the string so that it corresponds with the format defined in the library attribute "versioning format" or contact your ADOxx administrator.

[averdate-51]

	Description
Message:	Error when parsing the string: The combination of day and month is invalid.
Cause:	You have attempted to use an invalid combination of day and month.
Action:	Change the string so that it only contains valid combinations of day and month, invalid combinations include "29" and "2" or "31" and "4".

[averdate-52]

	Description
Message:	Error when parsing the string: No number has been found at the current place.
Cause:	A number is expected in the string but could not be found.
Action:	Adapt the string so that it corresponds with the format defined in the library attribute "versioning format" or contact your ADOxx administrator.

[averdate-53]

	Description
Message:	Error when parsing the string: The number found is too small.
Cause:	A number found in the string is too small.
Action:	Adapt the string so that it corresponds with the format defined in the library attribute "versioning format" or contact your ADOxx administrator.

[averdate-54]

	Description
Message:	Error when parsing the string: The number found is too high.
Cause:	A number found in the string is too high.
Action:	Adapt the string so that it corresponds with the format defined in the library attribute "versioning format" or contact your ADOxx administrator.

[averdate-55]

	Description
Message:	Error while parsing string: Between two dynamic values at least one TEXT field must exist.
Cause:	When defining the library attribute "Versioning format" two dynamic fields (for day, month or year) have been entered consecutively.
Action:	Change the definition by inserting a text field between the two dynamic fields or contact your ADOxx administrator.

awrjpeg

[awrjpeg-01]

	Description
Message:	<Error-specific Message>
Cause:	When generating the graphic file, an unexpected error was encountered.
Action:	Retry.

[awrjpeg-02]

	Description
Message:	Too little space!
Cause:	Not enough main memory is available.
Action:	Close a number of applications and try again.

[awrjpeg-03]

	Description
Message:	Error on opening file "filename".
Cause:	The file specified could not be opened with write-access.
Action:	Ensure that enough space exists in the directory to which you are writing and that you have access to update that directory.

[awrjpeg-04]

	Description
Message:	Error while closing file.
Cause:	An error occurred while closing the graphics file.
Action:	Ensure you have enough space in the directory to which you are writing. If this directory is on the network, ensure that you are still connected. Try again.

axml

[axml-01]

Message:	Invalid message: "message"
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-02]

Message:	Error when initialising a new parser!! A file has already been parsed.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-03]

Message:	Error in the XML interface! No parser has been initialised.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-04]

Message:	The file "file name" does not exist!
Cause:	The specified file is required but could not be found.
Action:	Control if the specified file actually exists.

[axml-05]

Message:	Error in the function XML_ADD_CALLBACK! The type "type" does not correspond with any valid type.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-06]

Message:	Error in the function XML_SET_SCRIPT! The procedure for the XML import has already been initialised.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript .Contact your ADOxx administrator.

[axml-08]

Message:	Error in the function "function name"! A required parameter is missing.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-09]

Message:	Error in the function XML_ADD_CALLBACK! The procedure "procedure name" does not exist.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-10]

Message:	Error in the function XML_ADD_CALLBACK! A procedure already exists for the element "element name".
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-11]

Message:	An error has occurred during the initialising of the XML parser: Error message
Cause:	Pay attention to the error message for more information.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-12]

Message:	An error has occurred when parsing the XML file.
Cause:	The XML file does not respond to the prescribed syntax.
Action:	Control the XML file to be read in.

[axml-13]

Message:	An error has occurred when parsing the XML file.File file name, row row number, column column number
Cause:	The XML file does not respond to the prescribed syntax.
Action:	Control the XML file to be read in.

[axml-15]

Message:	The element with the ID ID could not be stored in the memory.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-16]

Message:	The element "element name" does not contain any attribute with the name "attribute name".
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-17]

Message:	The element "element name" is already kept in the memory under the ID ID.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-18]

Message:	The format of the search string "search string" is invalid. Valid format: "name=value"
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-19]

Message:	The searched element could not be kept in the memory.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-20]

Message:	The element "element name" has no parent node as it is the root element.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-21]

Message:	The element has no child node.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-22]

Message:	The parse has been aborted.
Cause:	The XML import has been aborted.
Action:	Pay attention to the preceding error messages.

[axml-23]

Message:	Error in the function XML_OPEN! A file has already been opened to be written.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-24]

Message:	Error in the function XML_OPEN! The file "file name" already exists.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-25]

Message:	Error in the function XML_OPEN! The file "file name" could not be written.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-26]

Message:	Error in the function XML_WRITEATTRIBUTE! Attributes can only be specified in start nodes.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-27]

Message:	Error in the function XML_OPEN! The value "code page" does not correspond with any valid code page.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-28]

Message:	Error in the XML interface! No file has been opened to be written.
Cause:	An invalid message has been sent to the documentation message port.
Action:	There is an error in an AdoScript . Contact your ADOxx administrator.

[axml-29]

Message:	Error in the XML interface! There is no more free memory space in the target drive.
Cause:	During the XML export, it was not possible to write in the file, since there is not enough memory space available in the target data carrier.
Action:	Verify the memory space in the target drive.Select a target driver with enough memory space and repeat the export.

hacevalacq

[hacevalacq-02]

Message:	The acquisition tables are not consistent. The consolidation will be aborted.
Cause:	Corresponding processes have been found but they are inconsistencies in the values of the variables, names of objects or sequences of objects .
Action:	Verify the processes to be consolidated and repair the inconsistencies.

[hacevalacq-03]

Message:	The selected file is already contained in the file.
Cause:	You would like to add a file for the consolidation but it has already been added.
Action:	Add another file.

[hacevalacq-04]

Message:	The selected file does not correspond with the options set for the current scenario.
Cause:	You would like to add a file for the consolidation which does not correspond with the settings of the selected HOMER scenario.
Action:	Select a file for the consolidation which corresponds to the current HOMER settings or change the scenario settings according to the file you wish to use.

hacexp

[hacexp-01]

Message:	You have not specified a model name. The generation will be aborted. The model name should be in the below-specified cell. Cell:<cell name>
Cause:	There is no model name in the specified cell.
Action:	Enter the model name in the specified cell.

[hacexp-05]

Message:	A missing attribute has been found. If you want you can abort the generation. Defective attribute:<Attribute name> Object:<Object name>
Cause:	You have decided to abort the generation, if a missing attribute is found.
Action:	Fill the specified attribute and repeat the process.

[hacexp-06]

Message:	A wrong number format has been found. The generation will be aborted. Defective attribute:<attribute name> Object:<object name>
Cause:	A number value is in the specified attribute of the specified object, which does not correspond with the attribute settings for this attribute.
Action:	Correct the number value according to the selected attribute settings.

[hacexp-08]

Message:	You have created the same object twice. Rename or remove one of the objects. Object:<object name>
Cause:	You have created an object twice in your table.
Action:	Delete one of the objects or change the name of one of these objects.

[hacexp-10]

Message:	An internal error has occurred. Try again.Should the error appear again, note the error value and contact your ADOxx administrator.
Cause:	An unexpected error has occurred.
Action:	Repeat the action. Should the error appear again, note the error value and contact your ADOxx administrator.

[hacexp-14]

Message:	An unknown short description has been found in the mentioned cell below. You can change the short description of the object to an already defined one or redefine it. Cell:<cell name>
Cause:	A short description of class, which is not defined, has been found.
Action:	Change the short description of class in the specified cell to an already available short description of class or define a new class with the available short description of class.

[hacexp-17]

Message:	An unknown short description has been found in the mentioned cell below. You can change the short description of the object to an already defined one or redefine it. Cell:<cell name>
Cause:	A short description of class, which is not defined, has been found.
Action:	Change the short description of class in the specified cell to an already available short description of class or define a new class with the available short description of class.

hacfile

[hacfile-01]

Message:	The file cannot be opened. Check if the file corresponds with the selected options.
Cause:	You have attempted to open a file which cannot be opened. Verify if you have full access to this file and if the file is not blocked or being used by another user.
Action:	Once you have checked the causes, repeat the process.

hacimp

[hacimp-05]

Message:	The ADL file does not correspond with the HOMER settings and so cannot be imported. The import will be aborted. Verify if the library type and if necessary the model type correspond with the settings.
Cause:	You have selected an ADL file for the import, which library properties do not correspond with the HOMER settings.
Action:	Select an ADL file which conforms to the HOMER settings, an INI file of INI administration which is adapted to the selected ADL file or adjust the current INI settings to the ADL file.

hacini

[hacini-04]

Message:	An unexpected error has occurred. Save your changes and try it again.
Cause:	An unexpected action of the user or of another program has led to an error.
Action:	Close HOMER and re-start it. Should the error appear again, note the error code and description and contact your ADOxx administrator.

[hacini-06]

Message:	There is already an attribute in the column you have selected. Select another column.
Cause:	You have selected a column for the current attribute which is already assigned.
Action:	Select an available column. The furthest right free column is specified in the field 'next free column'.

[hacini-14]

Message:	The specified cell is already used. Select another cell.
Cause:	You have selected a cell which is already assigned.
Action:	Select another cell or abort the process.

[hacini-15]

Message:	The below-mentioned class already exists. Class:<class description>
Cause:	The entered class description already exists.
Action:	Change the class description or abort the process.

[hacini-16]

Message:	The short description mentioned below already exists.Change either the short description of this class or before you repeat this process the class mentioned below.Class short description: <class short description> Class:<Class description>
Cause:	The class short description you have selected already exists for the specifed class.
Action:	Change the current short description or the description of one of the specified classes.

[hacini-17]

Message:	The specified column is already used for the object name. Column: <Column name>
Cause:	The column you have selected will be used for the object name.
Action:	Select another column or abort the process.

[hacini-18]

Message:	The specified column is already used for the short description of the objects. Column: <column name>
Cause:	The column you have selected is used for the class short description.
Action:	Select another column or abort the process.

[hacini-24]

Message:	The specified column is already used for the attribute profile version. Column:<column name>
Cause:	You have attempted to place an attribute in a column, which is already used for the attribute profile version.
Action:	Select another free column or abort the process.

[hacini-26]

Message:	The specified column is already used for the short description of the ADOxx tables.
Cause:	You have attempted to place an attribute in a column, which is already used for the ADOxx tables.
Action:	Select another free column or abort the process.

[hacini-27]

Message:	All fields must be filled. You have forgotten to fill the following field.
Cause:	You have attempted, to close the dialogue without having filled all required fields.
Action:	Fill the specified field and continue.

[hacini-28]

Message:	There is already an attribute with this name for this class. Change the name of the attribute.
Cause:	An attribute with the selected name has already been created for the current class.
Action:	Change the name of this attribute or of the already created attribute.

[hacini-29]

Message:	The ADOxx record mentioned below already exists.
Cause:	An ADOxx record with the name mentioned already exists.
Action:	Change either the short description of this ADOxxrecord or the mentioned ADOxx record, before you repeat the process.

[hacini-30]

Message:	The below mentioned short description already exists.Change either the short description of this ADOxxrecord or, before you repeat the process, the below mentioned ADOxx record.
Cause:	The short description you have selected already exists.
Action:	Change either the short description of this ADOxxrecord or, before you repeat the process, the mentioned ADOxx record

[hacini-31]

Message:	The cell entered is already used for the model name.
Cause:	You have attempted to use a cell for the current model attribute, which is already used for the model name.
Action:	Select another cell.

[hacini-32]

Message:	The cell entered is already used for the version number.
Cause:	You have attempted to use a cell for the current model attribute, which is already used for the version number.
Action:	Select another cell.

[hacini-33]

Message:	The cell entered is already used for the attribute below.
Cause:	You have attempted to use a cell for the current model attribute, which is already used for the mentioned attribute.
Action:	Select another cell.

hacinit

[hacinit-01]

Message:	The below specified INI field is not compatible with the HOMER version used. Import the file to convert the data.
Cause:	You have attempted to use HOMER with an INI file, which is not compatible with the current version.
Action:	Use the INI file, which is delivered with the version used and import the old INI file using the scenario manager.

simrescomp

[simrescomp-01]

Message:	The new data set could not be added. The maximum possible number of simulation results has already been reached.
Cause:	You have tried to append more data to the Excel sheet, although the maximum number of data sets is already in the sheet.
Action:	Try to split the planned result comparison into several different files or leave some sets of data out of the evaluation.

[simrescomp-02]

Message:	No simulation results have been added as yet, so a result comparison is currently not possible. Add the simulation results beforehand.
Cause:	You have tried to perform a result comparison with an empty Excel sheet.
Action:	Add the data sets for the comparison before running the evaluation.

[simrescomp-03]

Message:	The data in the clipboard does not have the result comparison data format. The data cannot therefore be added.
Cause:	You have tried to add data from the clipboard to the result comparison table which is in no connection to the ADOxx result comparison function.
Action:	Switch to the ADOxx Modelling Toolkit, export the result data again to the clipboard and try once more to add the data to the Excel sheet.

[simrescomp-04]

Message:	The raw data could not be interpreted. Make sure that the raw data originates form ADOxx and that nobody has tampered with it afterwards.
Cause:	You have tried to add invalid data from the clipboard to the result comparison table. Perhaps this data was manipulated after the export by someone.
Action:	Switch to the ADOxx Modelling Toolkit, export the result data anew to the clipboard and try again to add the data to the result comparison table.

[simrescomp-05]

Message:	The data from the clipboard does not match the data already in the comparison table. You can only add and compare data originating from identical ADOxx result browsers. To be able to perform a result comparison using the data currently in the clipboard, you have to delete all of the existing raw data sets from the sheet. To be able to perform a result comparison using the data currently in the clipboard, you have to delete all of the existing raw data sets from the sheet."
Cause:	You have tried to add data from different kinds of results (e.g. from different simulation algorithms) to one result comparison table. As this data is structured differently, it cannot be compared.
Action:	Make sure that all sets of raw data originate from the same kind of simulation algorithm.

[simrescomp-06]

Message:	The clipboard is empty or the simulation results have already been added. It is not possible to add simulation results from the clipboard multiple times. Export the results every time before adding them to the result comparison table.
Cause:	You have tried to add a set of simulation result data from the clipboard several times to a result comparison table. This is not possible, as the result data is deleted after insertion.
Action:	In order to add the same set of result data to several different result comparison tables, export them every time from the ADOxx result browser. However, take care that this data is only added once to each table, as the evaluation results may otherwise be incorrect.

svxwins

[svxwins-01]

	Description
Message:	No file name has been specified!
Cause:	A file name must be specified for the selected action.
Action:	Enter a valid file name.

[svxwins-02]

	Description
Message:	The file does not exist!
Cause:	You have attempted to open a file to read which does not exist.
Action:	Enter a valid file name.

[svxwins-03]

	Description
Message:	An error has occurred during the storage!
Cause:	An error has occurred during the storage of the file.
Action:	There may be not enough space on the data medium or the specified path is not valid. Check the data medium or the path.