How to delete AUC files

             How to delete AUC files

During many development we face some cache related issues. There is no error in code and still changes are not reflecting. Even after performing CIL, Compile and Synch but issue still existing. All these are happened due to axc {GUID} .auc files. We need to clear (delete) these files from App data folder.

To delete AUC (Application Unicode Cache) files we need to perform below steps.
1. Stop AOS
2. Delete AUC files from below path
C:\Users\<UserId>\AppData\Local
3. Restart AOS.
PS: AOS restart is not mandatory. It’s better to do it in this way however it will work without AOS restart.

Dynamics AX:Tuning an AOS for best performance

        Dynamics AX: Tuning an AOS for best performance

Optimizing an AOS depends on what the AOS is used for. For example, an AOS that is load balanced should only allocate a certain number of resources on the server it is running on. Similarly, an AOS that is only used for the Enterprise Portal may not want to allow access to rich client users. Therefore, before taking any steps to optimize the performance of an AOS, make sure you have properly defined a role that the AOS has.
There are two ways to distribute load in a Dynamics AX environment. They are the following:
• Non-load-balanced cluster
• Load-balanced cluster
A cluster of AOSes are simply a group of AOSes. It doesn't necessarily mean that they are load balanced. However, a load-balanced cluster does indeed mean that a group of AOSes in a cluster are load balanced. The following sections will describe in more detail what a non-load-balanced cluster and a load-balanced cluster are.

Non-load-balanced cluster
A non-load-balanced cluster does not have a main AOS that is dedicated to
delegating client connections to the appropriate AOS. Instead, each AOS in the cluster acts independently. Each AOS has to be provided in the client configuration file for the client to connect. Based on a list of provided AOS servers in the client configuration file, the client will attempt to access each server in the order listed to find an available server. If a server's workload has reached its maximum level, then the client will simply attempt to connect to the next AOS.

Load-balanced cluster
Microsoft Dynamics AX provides the option to load balance two or more AOS's together. This is similar to how a web farm works for a SharePoint site. Alternatively, you may opt to use hardware or another software solution to load balance AOS access. It is recommended to have one AOS for no more than 50-60 users. In a load balanced cluster, one AOS is a dedicated load balancer, delegating client connections to the appropriate AOS. It is not directly used either for interactive purposes or for processing application code. Once a client is connected to the load balancer AOS, it will then determine which AOS it should connect to. If an AOS goes down, the load balancer AOS will automatically re-route clients to an active and available AOS without having to make any modifications to client configurations. Also, as a company grows and more users are needed, it is as simple as installing a new AOS and connecting it to the load balancer.

As previously mentioned, to set up load balancing, we must set up one AOS as the load balancer. Afterwards, each additional AOS in the load-balanced cluster will automatically listen for client connection requests from the Load Balancer AOS.

However, in order for an AOS to be a load balancer, it must first satisfy the
following criteria:
• Cannot be a Batch Server.
• Must be an AOS that is active.

The following steps describe the process of setting up load balancing in Microsoft Dynamics AX 2009:
1. Open the Cluster configuration form by going to Administration | Setup |
Cluster configuration.

2. Once in the Cluster configuration form, click on the Map AOS instances to
clusters tab.

3. In the Map AOS instances to clusters tab, select the AOS instance in which
to act as the load balancer and mark the Load Balancer field.

As you can see, setting up a load-balanced cluster in Dynamics AX is quite simple and requires very little configuration or tweaking of settings. When load tends to increase and performance degrades, adding a new AOS into a load-balanced cluster greatly improves performance and is quite simple to do. You can add as many AOS's as desired to a cluster. The process is the same for every additional AOS that is added.
To summarize, a non-load-balanced cluster requires more administrative work to update the client configuration files with the available AOS's. However, with a load-balanced cluster, the AOS that acts as the load balancer, once setup with all the available AOS's will automatically delegate clients to an AOS in a cluster with the most available resources.
Certainly, having a load-balanced cluster may seem like a desired setup to go
with, as it requires less administrative maintenance. It also provides a method for consolidating specific business functions. For example, one cluster of AOS's may be specifically dedicated to batch processing. Similarly, another cluster may be dedicated to an external Enterprise Portal site that can experience a significant load of external user access while a cluster for internal users may not experience as much load. Also consider that in a load-balanced cluster, at least three AOSes are required while in a similar non-load-balanced cluster, only two are required—to provide load distribution.

Installing Windows Server 2012 (step by step)

Installing Windows Server 2012 (step by step)

Windows Server 2012, code named "Windows Server 8", is the sixth release of Windows Server. It is the server version of Windows 8 and succeeds Windows Server 2008 R2. Two pre-release versions, a developer preview and a beta version, were released during development. The software was generally available to customers starting on September 4, 2012.

In this easy step by step guide, we will learn how to install and activate Windows Server 2012.

Before you start make sure you have the minimum requirements to install Windows Server (Windows Server Requirements):

Processor: Minimum: 1.4 GHz 64-bit processor
Ram: Minimum: 512 MB
Disk Space: Minimum: 32 GB
Other requirements:

DVD drive

Super VGA (800 x 600) or higher-resolution monitor

Keyboard and Microsoft® mouse (or other compatible pointing device)

Internet access

 You can then download the evalution copy of Windows Server 2012 from here, Download the ISO and burn it to some DVD:
http://technet.microsoft.com/en-US/evalcenter/hh670538.aspx?ocid=&wt.mc_id=TEC_108_1_33

Now that we have everything we need, We can Start:

1-      Insert the Windows Server 2012 DVD, and once you get the following message press Enter to boot from the setup

2- Wait for a while till the setup loads all necessary files (Depending on your machine, it will take couple of minutes)

 3- Once the setup files are loaded, the setup will start with the following screen. You can change these to meet your needs (the default values should be fine for now)

 4- Once you click Next, you can start the installation, click "Install now"

5- You will see the following screen, wait until it finishes loading

6- In the following setup screen, you will see four options. Select Windows Server 2012 DataCenter Evaluation (Server With GUI).

7- After you click Next from previous screen, Read the License terms, tick the "I accept the license terms" and click Next

8- Now It will ask you for the drive (or partition) you want to install Windows on. Here I'm installing it on the one partition I have here. NOTE: This will remove the content of the partition. Either you create a partition to install windows on, or you can test this on a testing machine

9- Now once we picked our partition, clicking on next from previous screen will start the setup. This process might take a while.

10- Once the setup is done, it will restart and start your Windows Server 2012 for the first time. It will ask you then to set up a password for the Administrator user

11- The setup will finalize your settings, might take a couple of minutes

12- Once the setup is done, you can log in for the first time to your Windows Server, as the screen says, press Ctrl+Alt+Delete to log in, and use the password you set in the setup process

13 - Once you Log in, Windows Server 2012 will show the Server Manager

 Congratulations! you have now Windows server 2012 Installed with Datacenter.

AX 2012 R3 Step by Step Installation Process Of Base Components

AX2012R3 Step by Step Installation Process Of Base Components

As long as waited for AX 2012 R3, today i have installed the base components successfully without any issues.

I have installed the AX 2012 R3 on Windows Server 2012 with SQL SERVER 2012. Also make sure the server is joined to Domain and .Net framework 4.5 is installed.

Please follow the below step by step installation process.

Step 1:- AX 2012 R3 New appearance, run the AX installation media. Check the Validate System requirements and then click on Microsoft Dynamics AX components.

Step 2:- Click on the accept license terms and go with Next button.

                     

Step 3:- As your wish you can select any of the below options and then go with Next button.

           

Step 4:- Select the path to install the Application file directories and then go with Next button.. 

           

Step 5:- Setup Support files will be installed once the install button clicked.

               

Step 6:- Setup Support files will be installed and then go with Next button.

           

Step 7:- Select the Microsoft Dynamics AX option to install the components and then go with Next button.

           

Step 8:- Select the Custom Installation and then go with Next button.

           

Step 9:- Select the base components to install (Databases, Application Object Server, Client, office add-ins, Remote Desktop Service Integration, .Net Business Connector and Management utilities) and then go with Next button.

           

Step 10:- Validate all the pending tools by marking the check box and click on the Configure button and then Revalidate.

            

Step 11:- Please click on the Link button to download and then install the MS Chart controls for Microsoft .Net framework 3.5
and then go with Next button.

               

Step 12:- Re-validate again and then go with Next button. If you got any other error at this step please resolve to enable the Next button to proceed with.

           

Step 13:- Please select the file location to install the 32 bit components in a separate directory and then go with Next button.

          

Step 14:- Click on the Create new database to install the AX databases and then go with Next button.

         

Step 15:- In the Server name enter the SQL database server name and database names as well and then go with Next button.(IMP:- Logged on user account must have the rights to create the databases into this SQL server and also enough disk space in the database server drive)

         

Step 16:- Select the model files to install into the ax model database and then go with Next button.

              

Step 17:- Enter the Custom Instance Name, TCP/IP, Services WSDL port and Services endpoint port or you can go with default name and port numbers as well and then go with Next button.

       

Step 18:- You can select any below account, i have chosen domain account this user account must have proper rights to the above mentioned SQL server and then go with Next button..

       
           

Step 19:- Select your convenient language, installation type and click on the check box to create the desktop shortcut for AX application and then go with Next button..

       

Step 20:- Check in the Configure option to install the SQL server full-text daemon launcher service startup type tool and then go with Next button.

     

Step 21:- Please double check the selected components before start installing, once the components are verified and then go with Install button.(IMP:-Please make your having the enough disk space in the SQL server database drive before start installing)

   

Step 22:- Pre-installation validation process will begin to configure the setups internally.

      

Step 23:- Model database will be configured and then go with Next button.

    

Step 24:- Please make sure all the selected components were installed correctly.

   

Step 25:- Please be patience, for the first time AX application will take 5 to 10 mins to start, when service entered into the running state please click the created shortcut in your desktop. AX 2012 R3 application will launch.

           

Keep you posted on further components installation and configuration, many new features were included into the AX2012 R3 installation media (For eg:-Management Reporter, DIEF, Dynamics Connector etc..)

Happy AX 2012 R3 and enjoy with the new features.

AX Server Configuration (form) [AX 2012]

AX Server Configuration (form) [AX 2012]

Click System administration > Setup > System > Server configuration.

Use this form to set up an AOS instance as a batch server or a load-balancing server. You can also use the form to change performance settings and cache limits for all AOS instances, or cache limits for a single AOS instance.

A batch server is an Application Object Server (AOS) instance that processes batch jobs. The first AOS to be set up is automatically designated as a batch server. You can designate additional servers, and you can specify when each server is available. Use multiple batch servers to increase throughput and reduce the time that is required to run batches.

A load-balancing server is an AOS instance that balances the load of client connections to Microsoft Dynamics AX. An AOS instance set to be a load-balancing server does not host any client sessions. Instead, it regulates the load among other AOS instances.

The following tables provide descriptions for the controls in this form.

Tabs 

Tab	Description
Batch server schedule	View or change when the selected AOS instance is available for running batch jobs.
Batch server groups	Specify which batch groups can be run on the selected batch server.
Performance Optimization	Specify performance and cache limit settings for all AOS instances, or cache limit settings for a single AOS instance.

Fields

Field	Description
AOS instance name	The name of the AOS instance, in the format InstanceName@ServerName.
Is batch server	Select this check box to set the AOS instance to be used as a batch server.
Load balancer	Select this check box to set the AOS instance to be used as a dedicated load balancing server. When this option is selected, the AOS instance will not host any client sessions. Instead, it regulates the load among other AOS instances.
Max concurrent sessions	The number of total threads for batch tasks or client sessions that can run at the same time on this server.
Cluster name	The name of the load balancing cluster that the selected AOS instance belongs to.
Maximum batch threads	The number of threads for batch tasks that can run on the selected server at the specified time.
Start time	The time when the batch server becomes available to run batch jobs.
End time	The time when the batch server is no longer available to run batch jobs.
Selected groups	The batch groups that can run on this batch server.
Remaining groups	The available batch groups that are not assigned to this batch server.
Error on invalid field access	Determines system behavior when SELECT statements access fields that have not been explicitly selected. If the value of this field is set to 0, no error is generated. If the value of this field is set to 1, an error is generated.
Error on exceeding maximum number of tables in join	Determines the behavior when the number of joins in a table exceeds the maximum number of joins allowed. If the value is set to 1, an error will be generated. If the value is set to 0, a warning will be generated.
Maximum number of tables in join	The maximum number of tables allowed in a JOIN statement. Note If this limit is exceeded, a message is displayed, but application logic continues to run.
Client record cache factor	The value used to determine the relationship between the number of elements in the record cache stored on the server and the number of elements stored in the Windows client record cache. For example, if the cache limit for the Framework table group is 2000 and the cache factor is 20, then 2000 elements can be saved in the record cache on the server, but only 100 (2000 divided by 20) elements can be saved in the record cache on the client.
Entire table cache size	Size beyond which the table cache will be flushed to disk.
Global Object Cache elements	Number of elements that can be stored in the Global Object Cache.
Record cache elements for Framework table group	Number of elements that can be stored in the record cache for the Framework table group.
Record cache elements for Parameter table group	Number of elements that can be stored in the record cache for the Parameter table group.
Record cache elements for Reference Table group	Number of elements that can be stored in the record cache for the Reference table group.
Record cache elements for Group table group	Number of elements that can be stored in the record cache for the Group table group.
Record cache elements for Main table group	Number of elements that can be stored in the record cache for the Main table group.
Record cache elements for Miscellaneous table group	Number of elements that can be stored in the record cache for the Miscellaneous table group.
Record cache elements for Transaction table group	Number of elements that can be stored in the record cache for the Transaction table group.
Record cache elements for Transaction Header table group	Number of elements that can be stored in the record cache for the Transaction Header table group.
Record cache elements for Transaction Line table group	Number of elements that can be stored in the record cache for the Transaction Line table group.
Record cache elements for Worksheet table group	Number of elements that can be stored in the record cache for the Worksheet table group.
Record cache elements for Worksheet Header table group	Number of elements that can be stored in the record cache for the Worksheet Header table group.
Record cache elements for Worksheet Line table group	Number of elements that can be stored in the record cache for the Worksheet Line table group.

 

Setting