while running inventory recalculation process, I got this error
“Cannot edit a record in stock transactions (InventTrans) An update
conflict occurred due to another user process deleting the record or changing
one or more fields in the record"
solution to avoid this error, go to AOT –> DataDictionary –> Tables ----> InventTrans
right click on table to display properties window then change OccEnabled property to No.
then resume recalculation again, it will work successfully.
Improve SQL performance lead us to optimize AX performance, this post is one of posts to achieve that
1- Configuring max degree of parallelism
The max degree of parallelism option is a setting that affects the entire instance of SQL Server. Microsoft Dynamics AX workloads generally perform better when intra-query parallelism is disabled. However, the upgrade process benefits from parallelism, as do activities that are used exclusively for batch jobs or maintenance. Use the following settings when the system performs maintenance activities or an upgrade:
· Before an upgrade to a new release of Microsoft Dynamics AX, or before a large number of maintenance or batch activities, set max degree of parallelism to the smallest of the following values:
· 8
· The number of physical processor cores
· The number of physical processor cores per non-uniform memory access (NUMA) node
· When the Microsoft Dynamics AX database is used in a production environment, set max degree of parallelism to 1.
Use the following statements to set the value of max degree of parallelism.
Examine the output from the second sp_configure 'max degree of parallelism' statement, and confirm that the value has been changed. In the following query, the first sp_configure 'max degree of parallelism' statement sets the value of max degree of parallelism to 1. The second sp_configure 'max degree of parallelism' statement returns a value of 1.
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
GO
EXEC sp_configure 'max degree of parallelism', 1;
RECONFIGURE;
GO
EXEC sp_configure;
For more information, see max degree of parallelism Option. For general guidelines, see Knowledge base article 329204, General guidelines to use to configure the MAXDOP option. For tips from the SQL Server team, visit the SQL Server Relational Engine team's blog, SQL Server Engine Tips.
2- Configuring max server memory
SQL Server dynamically acquires and frees memory as required. Typically, an administrator does not have to specify how much memory is allocated to SQL Server. However, the max server memory option can be useful in some environments. Make sure that sufficient memory is available for the operation of Windows Server. For more information, see Configure SQL Server and storage settings, later in this topic.
If you find that the dynamic allocation of memory adversely affects the operation of Windows Server, adjust the value of max server memory based on the available random access memory (RAM). For more information, see Effects of min and max server memory.
3- Monitoring available memory
Make sure that sufficient memory is available for the operation of Windows Server. For example, make sure that you run a dedicated instance of SQL Server on a server that has at least 4 gigabytes (GB) of memory. If the available memory for the server drops below 500 megabytes (MB) for extended periods, the performance of the server may degrade.
Use the Memory: Available Mbytes performance counter for the Windows Server operating system to determine whether the available memory drops below 500 MB for extended periods. If the available memory drops below 500 MB frequently or for extended periods, we recommend that you reduce the max server memory setting for SQL Server or increase the physical memory of the server.
Detailed guidance about memory management is beyond the scope of this topic. For more information about how to monitor memory and troubleshoot performance issues, see the Windows Server and SQL Server documentation.
4- Allocating storage for tempdb
We recommend that you determine the total size of the data files and transaction log files that are required for the tempdb database, and that you set a specific value. Do not use automatic growth, or autogrow, setting for space management. Instead, use autogrow as a safety mechanism, so that tempdb can grow if tempdb files use the space that was originally allocated to them. Follow this process to determine the number and placement of data files.
· Determine the number of processors that are available to SQL Server. Unless you are using an affinity mask, this number is same as the total number of processors that you see on the Performance tab of Windows Task Manager. When hyperthreading is not enabled, each processor corresponds to a processor core. Affinity masks and processor cores are beyond the scope of this topic. For more information, see the Windows Server and SQL Server documentation.
· Based on performance testing of the OLTP workload for Microsoft Dynamics AX, we recommend that you maintain one tempdb data file per processor. For more information, see the performance benchmark reports on PartnerSource or CustomerSource.
· Isolate tempdb on dedicated storage, if you can. We recommend that you move the primary data file and log file for tempdb to high-speed storage, if high-speed storage is available. The Microsoft Dynamics AX database runs in read committed snapshot isolation (RCSI) mode. In RCSI mode, row versions are stored in tempdb. By creating multiple files for tempdb data, even if these files reside on the same storage device, you can improve the performance of tempdb operations.
· Determine the size of the tempdb data files and log files. You must create one primary data file and one log file. Determine how many additional, secondary data files you require for the tempdb data. For best results, create data files of equal size. The total number of data files must equal the total number of processor cores. The aggregate size of the primary data file and all other data files must equal the total data size that you determined for the tempdb database.
For more information, see Optimizing tempdb performance.
· Resize the primary data file and log file for tempdb. Move the primary data file and log file to dedicated storage, if dedicated storage is available. The primary tempdb data file cannot be moved while the instance of SQL Server is running. To complete the move, you must use an ALTER DATABASE statement and restart the instance of SQL Server. For more information, see ALTER DATABASE.
Note: The data files and transaction log files for tempdb can reside on the same storage device.
· If space is available on the drive where tempdb files are allocated, do not configure the autogrow property for data files and log files as a percentage. Instead, configure the autogrow property as a specific number of megabytes. If you can, configure the data files and log files to grow by 100 to 500 MB, depending on the available space. Monitor the data files, and when they grow, adjust the original allocation to prevent automatic growth later. If the autogrow property is configured in megabytes instead of as a percentage, the allocation of space is more predictable, and the chance of extremely small or large growth increments is reduced.
· Monitor the tempdb data files and log files to make sure that they are all sized correctly, and that all data files are of equal size. Use SQL Server Management Studio or a transact-SQL query to view the database properties. Verify that all the data files are of equal size, and that they have the same size as the value that you originally provided. If one or more files have grown, adjust the initial size of all files.
This post provides general recommendations for physical storage. Determine the applicability of these recommendations to your environment. Some storage area network (SAN) vendors may have alternative recommendations that take precedence. Recommendations are listed in order of priority.
This topic explains how to uninstall Microsoft Dynamics AX by using Add or Remove Programs on the Control Panel.
Databases, log files, and application files must be removed manually. Information about how to manually remove components is also included in this topic.
Uninstall components by using Add or Remove Programs
Use this procedure to remove Microsoft Dynamics AX components.
| Option | Removes |
| Microsoft Dynamics AX Components | Selecting this option removes the following components: o Client o Role Centers and the Enterprise Portal framework o Workflow o Reporting extensions o Debugger o Enterprise Portal developer tools o Reporting tools o .NET Business Connector o AIF Web services o BizTalk adapter o Synchronization proxy for Microsoft Office Project o Synchronization service for Microsoft Office Project This option removes all components that are installed on the local computer. You cannot select to remove individual components. |
| Microsoft Dynamics AX Client Help Files | Select this option to remove all Help files in all installed languages. You should not remove Help files unless the client is also being removed. |
| Microsoft Dynamics AX Object Server (instance name) | Select this option to remove a specific Application Object Server (AOS) instance. Before you remove an AOS instance, use the Microsoft Dynamics AX Configuration utility to point all clients to a valid AOS instance, or update the shared configuration file. When you remove an AOS instance, it is not automatically removed from the list of batch and load balancing servers. After you uninstall an AOS instance, you must manually delete it by using the Server configuration form or the Cluster configuration form. |
Remove remaining components manually
If you choose to remove an entire installation, some components remain after Add or Remove Programs is finished. The following table provides more information about removing components manually.
| To remove this | Do this |
| Application files | Delete the application file directory from the location that you installed it to. |
| Database and log files | Use database server administration tools to delete the database and log files. |
| Role Centers and the Enterprise Portal framework | Delete Web sites by using SharePoint Central Administration. |
| Reporting extensions | · Delete SQL Server Reporting Services objects, such as data sources, reports, and report models by using Reporting Services. · Delete the contents of the Microsoft Dynamics AX report folder. |
| Analysis extensions | Delete SQL Server Analysis Services objects, such as databases, cubes, and models by using Analysis Services. |
I think this topic is very useful with AX new Implementation and all points mentioned here should be taken into our consideration.
This topic describes the tools and strategies that you can use when you are planning to import or export Microsoft Dynamics AX data. The topic also describes how to plan to move data from one enterprise resource planning (ERP) system to another. Finally, the topic describes performance and security considerations when you import and export data. read more
This topic provides answers to common document management questions. You can use document management in Microsoft Dynamics AX to attach files to records. For example, you can attach PDF, Microsoft Word, or Microsoft Excel files to a purchase order or a sales order. You can also create Word and Excel templates from Microsoft Dynamics AX data.
What is the difference between document handling and document management?
There is no difference. Both terms refer to the same functionality. In earlier versions of Microsoft Dynamics AX, the functionality was called document handling. In more recent versions, it’s called document management.
What is the difference between document management and print management?
What is the difference between document management and print management?Document management lets you add notes, documents, and other files to records in Microsoft Dynamics AX.
Print management lets you control print settings for selected reports. Print settings include the number of copies, the printer destination, and the multilanguage text that can be included on the report. For more information, see Print management.
What is the difference between document types and file types?
Document types are used to categorize the documents that you attach to records or the templates that you create. The document management system handles several types of documents. These include letters, worksheets, and notes. Before you can create templates or attach documents to records, you must configure document types in the Document types form. For more information, see Configure document management.
A file type is the extension of the document. For example, .doc, .xlsx, and .pdf are all file types.
Can I export or import document types?
Yes. For more information, see Export and import a document type.
What is the difference between document management and print management?
Yes. Document attachments can be located anywhere on the Internet or on an intranet and can be attached by using the URL DocuType. For example, if you attach a Word document that is located on SharePoint Online to a record, the attachment opens in the web version of Word
Can I store Microsoft Dynamics AX attachments in SharePoint?
Yes, but only if you’re using Microsoft Dynamics AX 2012 R2. For more information, see Configure Microsoft Dynamics AX document management to use Microsoft SharePoint document libraries.
Can I use templates that are stored in SharePoint as Microsoft Dynamics AX document templates?
Yes, but only if you’re using AX 2012 R2. For more information, see Configure Microsoft Dynamics AX document management to use Microsoft SharePoint document libraries.
Can I move a document archive?
Yes. However, you must copy the documents from the old archive to the new archive before you enter the new location in the archive directory field. This precaution is necessary so that you don’t break existing document references to existing documents.
To move a document archive, follow these steps:
1. Copy all documents from the old archive to the new archive.
2. Click Organization administration > Setup > Document management > Document management parameters.
3. In the General area of the form, in the Archive directory field, enter the path of the new document archive.
Why can’t I click the attachments icon in the Document handling form?
The attachments icon is available only if all of the following scenarios are true:
· You have selected a record.
· You have activated document management. For more information, see Configure document management.
· You have permission to view attachments for the record.
How do I lock the Document handling form?
The Document handling form always lists the documents that are attached to the selected record. If you leave the Document handling form open and you select another record, the form is updated to list the documents that are attached to the newly opened record.
To avoid updating the Document handling form when you select a different record, you can lock the view so that the information in the form doesn’t change.
To lock the Document handling form view, follow these steps:
1. Select a record.
2. Click File > Command > Document handling to open the Document handling form.
3. Click Functions > Lock.
4. Select another record. The documents for the locked record are still displayed in the Document handling form.
You can distribute the user load in Microsoft Dynamics AX across multiple instances of Application Object Server (AOS) by creating a load balancing cluster.
Clustering overview
Microsoft Dynamics AX offers two types of load balancing clusters:
A cluster that includes a load balancer
A cluster that does not include a load balancer
A cluster that includes a load balancer
If you set up a cluster that includes a load balancer, the load balancing AOS instance is dedicated to distributing the user load. The load balancing AOS instance does not process Microsoft Dynamics AX business logic or data.
In this configuration, you must set up client configurations to connect to the load balancing AOS instance. You can then add and remove other AOS instances from the cluster without updating client configurations.
When a client starts, it connects to the load balancing AOS instance. The load balancing AOS instance returns a list of active AOS instances in the cluster, sorted by workload. The client attempts to connect to the first AOS instance in the list. If that connection fails, the client attempts to connect to the second AOS instance in the list, and so on.
A cluster that does not include a load balancer
If you set up a cluster that does not include a load balancer, each AOS instance functions as both a load balancer and an active AOS instance that accepts client connections.
When a client starts, it sends a request to the first server that is listed in the client configuration. That server returns the list of active AOS instances in the cluster, sorted by workload. The client attempts to connect to the first AOS instance in the list. If that connection fails, the client attempts to connect to the second AOS instance in the list, and so on.
Before you begin
Before you can create a cluster, you must install multiple AOS instances. Each instance must point to the same database. For more information, see Install multiple AOS instances and Configure an AOS to access a different database.
Create a cluster
Click System administration > Setup > System > Cluster configuration.
Press CTRL+N to create a new cluster.
You cannot configure the Non Load Balanced AOS Instances as a load balancing cluster. The Non Load Balanced AOS Instances is a default entity that enables AOS communications for non-load balanced AOSs. To create an AOS cluster, you must create a new cluster.
Enter a name and description for the cluster.
Press CTRL+S to save your changes.
Add an AOS instance to a cluster
Click System administration > Setup > System > Cluster configuration.
In the Map AOS instances to clusters section, select an AOS instance.
If you want the AOS instance that you selected to function as a load balancer, select the Load balancer option.
If an AOS instance is used as a load balancer, it cannot be used as a batch server.
Click the Cluster name field to display a list of available clusters. Select the cluster that you want to add the AOS instance to.
Press CTRL+S to save your changes.
Change client configurations
If the cluster uses one or more load-balancing AOS instances, set client configurations to connect to these load balancing AOS instances.
Use the Microsoft Dynamics AX Configuration utility to change client configurations. For more information, see my post Manage a client configuration .
When you import a model into the model store, the resources in the model may have conflicts with resources in other models that are already part of that layer. If you use the push option when importing the model, the conflicting resources will be put into a new conflict model that is located in the patch layer for the current layer in the AOS. This new model will have a name that indicates it contains resources that have caused a conflict. For example the model named Facility Management (Conflict 1) contains the resources that caused a conflict when the Facility Management model was being imported.
Often, it is a developer responsibility to help resolve conflicts that occur when a model is imported. Use the following procedure as a general guideline to help you through this process.
Resolving Conflicts after Importing a Model
Determine whether any conflicts occurred during the model import process.
If you imported a model from the command line, the results returned from the command will indicate whether conflicts occurred during the import process.
If you do not know the results of the import process, use the Models installed command as described in How to: View Model Information to view the list of models that are installed. If you see any conflict models in a patch layer, they will contain the resources that caused the conflict.
Retrieve the list of resources that caused conflicts. Use the view command to see the list of resources in the conflict model. These are the conflicts that you have to resolve. For detailed information about how to list resources in a model, see How to: View and Verify Contents of a Model. For example, the following command uses axutil.exe to list resources in the Facility Management (Conflict 1) model:
axutil.exe view /model:"Facility Management (Conflict 1)" /verbose
In the AOT, select a resource that has a conflict. Right-click the resource and choose Compare. In the Comparison window, click Compare to see the differences between the resource in the patch layer and the resource in the main layer.
Resolve the conflict. There are many ways to resolve the conflict, depending on the resource type and the actual conflict. Some of the ways to resolve the conflict include the following:
Use the information and the available actions from the Comparison window to merge changes from the conflict model into an existing layer.
Make a change in the resource in an existing model in the current layer. For example, if two different models in the layer have modified the same resource, you could consider creating a new “shared” model in the layer that contains a single version of the resource that can be used by both of the other models.
Switch to the patch layer and modify the resource there. In some cases, this is the easiest way to resolve the conflict.
You can switch to the patch layer by creating a new configuration with the Microsoft Dynamics AX 2012 Configuration tool. You can also switch to a specific patch layer by using the following command to start Microsoft Dynamics AX:
Ax32.exe –AOL=USP
Repeat the conflict resolution process for each resource in the conflict model.
After you have resolved all of the conflicts, consider removing the conflict model from the patch layer. That way, somebody looking at the system will not assume that there are model conflicts that have to been resolved. If you are leaving a resource in the patch layer, move the resource out of the conflict model into another model in the patch layer. Then delete the conflict model.
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
This topic describes how to close client sessions that are connected to an instance of Application Object Server (AOS) for Microsoft Dynamics AX. When you close client sessions without force, you are said to drain users. Administrators drain users from an AOS instance before they perform maintenance on the server or take it offline.
Important
The following procedure requires that you click the Reject new clients button in Microsoft Dynamics AX. After you click this button, you must not close your client. If you close your client before you click the Accept new clients button, you cannot open a new client session unless you restart the AOS instance by using the Windows Services Management console, or unless you reset Status of the SysServerSessions table in Microsoft SQL Server to a value of 1.
Click System administration > Common > Users > Online users.
On the Server instances tab, select the AOS instance that you want to perform maintenance on.
Click Reject new clients.
When you are prompted, click OK to stop the AOS instance from accepting new client connections.
After 5 minutes, all users receive a message informing them that they must save their work, because the administrator is shutting down the AOS instance. No new client connections are accepted during this time. The server forces client sessions to close after they have been idle for 2 minutes. Client sessions for administrators are never closed. When the number of clients that are connected to the AOS instance is displayed as 0 (zero), you can perform maintenance on the server.
After you have finished performing maintenance on the server, click Accept new clients or restart the AOS instance.
