Инструменты пользователя

Инструменты сайта


Раздел: Администрирование


В Axapta поддерживаются следующие соглашения для расширений файлов:

Первая буква – владелец файла:

  • A – Application (Приложение)
  • K – Kernel (Ядро)

Вторая буква – содержание файла:

  • L – Label (Метка)
  • O – Object (as is AOT) (Объект)
  • T – Text (only TKD) (Текст)
  • D – Developer Documentation (Документация разработчика)
  • H – Online Help (Справка)

Третья бкува: Тип файла.

  • D – Data (Данные)
  • I – Index (Индекс)
  • C – Cache (Кэш)
  • T – Temporary (Временные)

Таким образом, файл с расширением .ald это Application Label Data – Данные Меток Приложения

Подробное описание

5. There are lots of files with different file extensions in the Application\Appl\Std folder. Can you please explain the key files in that directory?

Yes. There are quite a lot of files in Axapta Application\Appl\Standard folder. Please note that all these files will be updated whenever a new version is released. Most important them are -

1. .aod - Acronym for Application Object Data file. Each Application object layer is saved in a separate file called «Ax< layer >.aod». For example, Axsys.aod for the SYS layer, Axusr.aod for the USR layer and so on.

Tip : It is not very uncommon to Axapta programmers to move one particular layer file from one machine to another machine. For example, in one of the client places, while I was compiling a fresh installation, I got one error message pointing to SYS layer. So I deleted the Axsys.aod file in that particular machine. Copied and pasted Axsys.aod from another machine which was working fine. And this time when I compiled, I did not had that old error.

2. .ald - Acronym for Axapta Label Data. For each layer, there is a corresponding label file. The naming convention for label file goes like this. For example, for the label files supplied with the standard system (SYS layer), the file name could be like AxSYS< country >.ald where country is an abbreviation of the language used, for example En-us for American English, En-gb for British English, or Da for Danish.

New texts for service packs may be released in a label file called AxSYP< country >.ald.

Tip : When you need to create new user interface texts, you should create a label file of your own. For this purpose, Axapta has included a Label file wizard. Please note that Axapta has defined some standards for creating label files. If you want to know more about standard for creating label files, creating actual label files, please click here.

In addition to the label data file, Axapta also creates index (.ali) and description (.alc) file.

3. .udb - Acronym for Axapta User Database. As the acronym indicates, Axapta stores its user details in this file. Also this file is responsible for allocating session ID to users. If this file is deleted, then Axapta would regenerate whenever the system is started.

Tip : Some times in Axapta 3-tier installations, when you look at online users form, it could return false information. For example, let us assume 5 users are currently online. But this form, might show 7 or 8 users online. Or some times, though you have enough licenses, you might receive «maximum users reached» error message from Axapta.

In such cases, the solution would be deleting the «axdat.udb» file. But before deleting it, make sure that all users are exited and AOS is properly shut down. Once this is done and the file is deleted, as mentioned above, Axapta would regenerate the «Axdat.udb» file. Please note that you might not even come across this problem. But to be on the safer side, particularly on 3-tier installations, it is always advisable to regularly delete «axdat.udb» file.

But in some special conditions, online user form may be empty in Axapta ver 2.5. This condition may happen if your license has an expiry date. Even though your license may not have expired, you might still come across this condition. In such cases please go to Technet website and do a search with this key words «The online user form is empty». You would come across an Export file. Import that export file in your installation. That would solve the problem.

4. .ktd - Acronym for Kernel Text Data.

Tip : Some times when you upgrade your installation (say for example you have installed a new SP), you might not be able to see the new features of the installed SP after the upgrade is complete.

The solution for this would be manually copying the .ktd files from Client\Bin\ directory to Axapta Application\Bin directory. The reason being - when Service pack is installed, for some reasons files in Axapta Application\bin directory are not updated. Only the files that are there in Client\Bin are updated.

5. .aoi - Acronym for Application Object Index. As the name indicates this is an index file for the Application objects.

Tip : Some times you may get funny error messages. Though you might have hard disk space, sometimes the following error might popup -

    Error in file: ...\standard\axapd.aoi while reading in record ... 
    Error code: 38 = hard disk is full 

For all the error messages involving axapd.aoi, the solution would be deleting the «axapd.aoi» file from Axapta Application\Appl\Standard directory. When you restart the system again, Axapta would rebuild this index file.

If the problem persists even after deleting the file, then check whether «Open application files in exclusive mode» is enabled (Axapta Configuration Utility –> Under General Tab). If enabled, then disable it. This should solve the problem.

6. What is «Master.aoc» file and how can I create it ?

aoc stands for Axapta Object Cache. This functionality was introduced in Axapta ver 2.5 mainly intended for best performance possible.

When running a 3-Tier Navision Axapta 2.5 client, we will cache different objects as we use the application. All objects are cached in the memory on the client machine. When the client is shutdown, the cache objects are written to disk, in a file with the extension .aoc (Axapta Object Cache). The next time a user starts the client, the executable ax32.exe checks for the .aoc file and if one exists it is loaded into memory. This gives us a performance gain, as we do not have to cache these objects again.

How to create a preconfigured cache file?

This is very simple. We configure a 3-tier client and go through the parts of the application all clients will use. Ex - General Ledger, Sales Order and Accounts Receivable. Doing this will create an .aoc file, with the following naming convention - «ax_AOS [Instance name]@[Hostname]_[username].aoc». In my case, I got a file like this - ax_Annai@Himalaya_Harish.aoc. This file, if used as the preconfigured cache file, must be renamed to «master.aoc». Please note that this naming convention of the .aoc file would be different if you have configured an Object Server Cluster. (Ex - ax[cluster name][username].aoc)

When installing the Navision Axapta 2.5 client software, the setup.exe program will look for the master.aoc file in the directory where setup.exe is located. After completing the installation of the client, the setup.exe program will, if a master.aoc file exists, copy this file to the \Log directory, located in the default directory structure of the installed client.

When a user starts the client software for the first time, the executable as32.exe, will look for a cache file that belongs to the user, who is currently logged in. If one exists then this cache file is loaded into memory. If none exists, then the ax32.exe will look in the \Log directory for the master.aoc file. If one exists, the objects in this cache file would be loaded into memory.


axapta/расширенияфайлов.txt · Последнее изменение: 2018/04/13 22:43 (внешнее изменение)