Running AX report through batch job in AX2009 (batch printing)

Running batch report in AX2009 (batch printing)

Since the change of AX2009 batch framework, printing of report through batch can be done through two methods:
- Printing from server (to printer or file)
- Printing from client (the legacy batch processing)
Prerequisites: For both of the method, there're some mandatory setup:

1. Enable any of the AOS that you want to make it as batch AOS
   (Administration -> Setup -> Server configuration)
2. Create batch group for printing.
   Eg. One for client printing and one for server printing.
   (Administration -> Setup -> Batch groups)
3. Add the batch group created in #2 into the AOS enabled for batch processing (in #1)

complete article available here

Regular maintenance activities in Dynamics AX that affect performance

The following list describes some of the maintenance activities that we recommend that you perform regularly in your production environment:

• Defragment indexes – You can defragment indexes from either SQL Server Management Studio or the Intelligent Data Management Framework (IDMF).

• Update SQL Server statistics from SQL Server Management Studio – We recommend that you run both manual and automatic updates of statistics. Manual updates may become more important as the size of your database increases, because automatic updates are less likely to be completed on large data sets.

• Reduce the size of the database – You can use IDMF to keep the size of the production database small. A small database makes database operations more efficient. For example, you can delete or archive data that is not required in your production system.

The administration of number sequences – AX 2012

The administration of number sequences is performed by using actions provided in the Administration group on the action pane on the Number sequences list page.

Organization Administration –> Common –> Number Sequences ---> Number Sequences

• Status list

Provides a list of numbers that have been generated for continuous number sequences, but which have not been committed to the database. The numbers are either currently being used in a user session, are reserved for future use in a user session, or are free for use if a new client user session requests a new number for a particular number sequence in the list. If a new number does not exist for a specific continuous number sequence, it is generated by the sequence number framework from the next value for that number sequence in the Number sequence table (NumberSequenceTable).

• Manual cleanup

Allows the administrator to manually clean up numbers in the status list. Use of this option is only recommended after an unexpected system failure; in such rare circumstances, numbers might not be automatically cleaned up.

• History

Provides the history of changes to the number sequences themselves.

 

A number of administrator tasks can be performed from the Details page. An administrator can, for example, schedule an automated periodic cleanup for every number sequence by entering intervals on the Automatic cleanup FastTab as displayed in image below

An administrator can also assign number sequences by using a page in the parameters forms in individual application modules. For example, you can view or assign the number sequences to specific references in the General ledger module. You can navigate to the form by using the path General ledger > Setup > Parameters.

Recalculation Error Dynamics AX 2009

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.

Configuring the instance of SQL Server for Dynamics AX

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.

Configuring physical storage for SQL server of Dynamics AX

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.

• Many factors contribute to optimal I/O performance for a disk. By default, Windows Server 2008 aligns partitions. When you upgrade to Windows Server 2008, preexisting partitions are not automatically aligned and must be manually rebuilt to guarantee optimal performance. Therefore, until you rebuild the migrated partitions, alignment of disk partitions remains a relevant technology.

Check existing disks on the server, and be aware of the differences in the analysis of basic partitions and dynamic volumes. Rebuild the partitions, if you can, and appropriate and create all new partitions based on guidance from the SAN vendor. If the vendor does not provide recommendations, follow the best practices for SQL Server. See Disk Partition Alignment Best Practices for SQL Server.

The partition offset value must be a multiple of the stripe size. In other words, the expression, partition offset / stripe size, must resolve to an integer value.

• Create the tempdb database files, data files for the Microsoft Dynamics AX database, and Microsoft Dynamics AX log files on disk arrays of type RAID 1, RAID 0 + 1, or RAID 10. We recommend RAID 10 for these files. Do not use RAID 5.
• Store the data files for the Microsoft Dynamics AX database on separate physical stores from the transaction log files.
• Store the tempdb data files on a separate physical store from the data files and log files for the Microsoft Dynamics AX database.
• Store other database files on separate physical stores from the data files and log files for tempdb and the Microsoft Dynamics AX database.

Uninstall Microsoft Dynamics AX

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.

1. Open Add or Remove Programs. (Start > All Programs > Control Panel > Add or Remove Programs).
2. Select the component that you want to remove, and then click Remove. The components that are listed in the following table can be removed.

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.

3. A message box asks you to confirm that you want to uninstall. To proceed, click Yes.

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.

Plan data import, export, and migration [AX 2012]

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

Document Management - AX 2012 R2

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.

How to: Resolve Conflicts After Importing a Model [AX 2012]

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

To resolve conflicts after importing a model

1. 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.

2. 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

3. 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.

4. 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.

     Tip

     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

5. 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.

AOS clusters without a dedicated load balancer [AX 2012]

You can configure Microsoft Dynamics AX Application Object Server (AOS) clusters that include a dedicated load balancer. You can also configure clusters that do not include a dedicated load balancer. This topic describes planning considerations for an AOS cluster that does not include a dedicated load balancer.

Overview

The following figure shows how a client establishes a connection with an AOS instance in a cluster when a dedicated load balancer is not present.

1. When a Microsoft Dynamics AX client starts, the client reads the list of AOS instances that is specified in the Microsoft Dynamics AX 2012 Configuration utility. The client initiates a handshake with the first AOS instance in the list. If the first AOS instance does not respond, the client initiates a handshake with the next AOS instance in the list. The client continues in this manner until the handshake occurs.

2. The AOS instance that received the client request queries the database and all active AOS instances in the cluster. The AOS instance returns to the client a list of all active AOS instances in the cluster, sorted by workload. The server that has the smallest workload is at the top of the list. The workload is based on the number of connected clients, divided by the maximum number of clients that are allowed on the server.

3. The client attempts to connect to each AOS instance in the sorted list until a successful connection is established. The client then uses the AOS instance that it connected to for the whole session.

Considerations for using an AOS instance in a cluster that does not include a dedicated load balancer

• If a dedicated load balancer is not present, each AOS instance in the cluster functions as both an active AOS instance and a load balancer.

• An active AOS instance has higher hardware requirements than an AOS instance that functions as a dedicated load balancer.

For information about how to configure load balancing clusters, see Create a load balancing cluster post.

Create a load balancing cluster [AX 2012]

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

1. Click System administration > Setup > System > Cluster configuration.

2. Press CTRL+N to create a new cluster.

   Caution

   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.

3. Enter a name and description for the cluster.

4. Press CTRL+S to save your changes.

Add an AOS instance to a cluster

1. Click System administration > Setup > System > Cluster configuration.

2. In the Map AOS instances to clusters section, select an AOS instance.

3. If you want the AOS instance that you selected to function as a load balancer, select the Load balancer option.

   Note

   If an AOS instance is used as a load balancer, it cannot be used as a batch server.

4. Click the Cluster name field to display a list of available clusters. Select the cluster that you want to add the AOS instance to.

5. 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 .

Grant users access to reports [AX 2012]

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic explains how to give users access to reports. Two procedures are described in this topic. The procedure that you should use depends on whether you are running Microsoft SQL Server Reporting Services in native mode or SharePoint integrated mode.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

Assign users to the DynamicsAXBrowser role on the Report Manager site

If you are running Reporting Services in native mode, you must assign users or groups to the DynamicsAXBrowser role on the Report Manager site. The following procedure explains how to complete this task.

1. Open the Report Manager website for the Reporting Services instance. By default, the URL is http://[SSRSServerName]:80/Reports.

2. Click the DynamicsAX folder.

3. Click Folder Settings.

4. Click Security.

5. Click New Role Assignment.

6. Enter the Active Directory user name or group to assign to the DynamicsAXBrowser role.

7. Select the DynamicsAXBrowser role.

8. Click OK.

Grant users permission to view reports in SharePoint

If you are running Reporting Services in SharePoint integrated mode, you must grant users permission to view reports in SharePoint. To grant this permission, grant users Read permission to the document library that stores the reports. Alternatively, if the document library inherits permissions from the site, you can grant users Read permission to the site. The following procedure describes how to grant users Readpermission to the site.

Important

If the SharePoint site is configured for claims-based authentication, you must also grant the following accounts Read permission to the document library or site:

• The account that is used as the Business Connector proxy

• The account that is used to run the Microsoft Dynamics AX Application Object Server (AOS) service.

1. Open your browser and navigate to the SharePoint site that contains the document library that stores the reports.

2. Click Site Actions > Site Permissions.

3. Click Grant Permissions. The Grant Permissions window is displayed.

4. In the Users/Groups field, enter the Active Directory names of the users or groups that you want to view reports.

5. In the Grant Permissions area, select the Grant users permission directly option.

6. Select the Read check box.

   Note

   If you want users of Enterprise Portal for Microsoft Dynamics AX to be able to filter reports by using a custom parameter value, select the Design check box. For more information about the permissions that are required to use Enterprise Portal, see Enable users to access Enterprise Portal.

7. Click OK.

Create a document library to store reports [AX 2012]

Applies To: Microsoft Dynamics AX 2012 R2

If you are using Microsoft Dynamics AX 2012 R2, and if Microsoft SQL Server Reporting Services is running in SharePoint integrated mode, create a document library in SharePoint to store your reports. Complete this procedure before you deploy the default reports that are included with Microsoft Dynamics AX.

Note

This procedure does not apply to you if you are running Reporting Services in native mode.

Create a document library

Create a document library on your SharePoint site to store reports. For information about how to create a document library, see the SharePoint documentation.

After you create the document library, add Reporting Services content types to the library. For more information, see Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode) in the SQL Server documentation.

Specify the URL of the document library

After you have created the document library, complete the following procedure to specify the URL of the document library in the Report servers form in Microsoft Dynamics AX.

1. Open Microsoft Dynamics AX.

2. Click System administration > Setup > Business intelligence > Reporting Services > Report servers.

3. In the Configuration ID field, enter a name that identifies the Reporting Services instance and the Application Object Server (AOS) instance that you are connecting.

4. In the Description field, enter a brief description to help you identify the Reporting Services instance and the AOS instance that you are connecting.

5. Select the Default configuration check box to make the Reporting Services and AOS instances that are specified in this record the active connection.

6. On the Reporting Server information tab, enter the following information:

   1. In the Server name field, enter the name of the server that is running Reporting Services.

   2. In the Server instance name field, enter the name of the Reporting Services instance.

      Note

      If you are using Reporting Services 2012, enter @Sharepoint.

   3. Leave the Report Manager URL field blank. This field becomes unavailable when you select the SharePoint integrated mode check box in a later step.

   4. In the Web service URL field, enter the URL of the Reporting Services web service.

      • If you are using Reporting Services 2008, the URL is typically http://[SSRSServerName]/ReportServer.

      • If you are using Reporting Services 2012, the URL is typically http://[SharePointServerName]/_vti_bin/ReportServer or http:[SharePointServerName]/sites/[SiteName]/_vti_bin/ReportServer.

   5. Select the SharePoint integrated mode check box.

   6. In the Microsoft Dynamics AX report folder field, enter the URL of the document library that you created to store reports.

      For example, suppose that you have created a document library that is named Reports on a SharePoint site that is named Contoso. In this example, the URL is as follows:

      http://[SharePointServerName]/sites/Contoso/Reports

7. On the Application Object Server information tab, select the name of the AOS instance.

Install Microsoft Dynamics AX in Silent Mode

When you run the Setup wizard, Setup is running in interactive mode. This means a graphical user interface (GUI) prompts you for required information.
Alternatively, you can run Setup in silent mode, with no GUI displaying. In this mode, required information is supplied at the command prompt or in a parameter file. You can install any Microsoft Dynamics AX component in silent mode.
NOTE: A silent installation is especially useful when deploying multiple clients at one time.

Deploy Multiple Clients
To deploy multiple Microsoft Dynamics AX Windows clients at one time, it is recommended that you use the following process.
1. Copy the contents of the Microsoft Dynamics AX DVD to a shared directory on the network.
2. Create a common configuration file in a shared directory on the AOS computer that clients will connect to.
3. Create a batch file to install clients with a shared configuration. The file must be located in a shared directory in  the Microsoft Dynamics AX DVD shared folder, at the same level as Setup.exe.
4. Test the batch file on a local computer.
5. Use a mass deployment tool such as Group Policy or Microsoft Systems Management Server to run the batch file from a logon script.

For more information about using Group Policy to deploy software, refer to: http://go.microsoft.com/fwlink/?LinkId=92736.
For more information about using Systems Management Server to deploy software, refer to: http://go.microsoft.com/fwlink/?LinkId=115327.
The following procedures contain more detailed information about creating a shared configuration file and creating a command file.

 

Determine Which Parameters to Use
The same parameters are available whether you enter them at the command prompt or create a parameter file. For information about individual parameters, refer to the Setup parameters reference (http://go.microsoft.com/fwlink/?LinkId=191476) on TechNet.
To determine which parameters to use, it is recommended that you install a client on a single computer and then review the Setup log file, which is located at <Drive>\Program Files\Microsoft Dynamics AX\Dynamics AX\60\Setup
logs\Date Time\DynamicsSetupLog.txt. The log lists the parameters used in the installation.

Specify Installation Parameters at the Command Prompt
Use the following procedure to run the installation by entering parameters at the command prompt.
1. Open a Command Prompt window.
2. At the command prompt, type the following information: <Path to DVD or shared directory>\Setup.exe parameter1="value" parameter2="value". When using multiple parameters, insert a single space between parameters.
WARNING: If you enter duplicate parameters, Setup will fail silently.
3. After you have listed all parameters, press Enter.

Specify Installation Parameters Using a Parameter File
Use the following procedure to run the installation by specifying a parameter file at the command prompt.
1. Create a text file that lists the appropriate installation parameters and their values. In the parameter file, the Name=Value combination for each parameter must be on a separate line.
WARNING: If you enter duplicate parameters, Setup will fail silently.
2. Do not include double quotation marks in parameter files. Because a line return is used as a delimiter in a parameter file, values that otherwise require the use of double quotation marks do not require them here. To prevent a line in a parameter file from being read, type a number sign (#) before the line. The line will be treated as a
comment rather than a command or parameter.
3. Open a Command Prompt window.

4. At the command prompt, type the following information: <Path to DVD or shared directory>\Setup.exe ParmFile=<path to file\FileName.txt>. The path can be fully qualified or relative to the location of the Setup.exe file. Relative paths can include upward qualifiers such as "..\..\".
5. Press Enter.

NOTE: To set up clients to use a shared configuration file, set the ClientConfigFile path parameter to the file in the shared directory. ClientConfigFile="X:\<name of configuration file>.axc"

Sample Parameter File
The following is an example of a parameter file that can be used to install the databases and the Application Object Server (AOS). Your parameter file will vary, based on the components that you are installing.
HideUI=1
AcceptLicenseTerms=1
DbSqlServer=SQLServerName
DbSqlDatabaseName=DatabaseName
InstallApplication=1
ApplicationInstanceName=ApplicationInstanceName
InstallAos=1
AosInstanceName=AOSInstanceName
AosApplicationPath="C:\Program Files\Microsoft Dynamics AX\60"
AosReportErrors=0

Procedure: Create a Group Policy Logon Script
To install clients using Group Policy, follow these steps:
1. Open Start > Administrative Tools > Group Policy Management.
2. Expand Group Policy: Management > Forest: Contoso.com > Domains > Contoso.com.
3. Right click Contoso.com, and select Create a GPO in this domain, and Link it here.

4. In the Name field, type "Dynamics AX Logon Script", then click OK.
5. Right-click "Dynamics AX Logon Script", then click Edit.
6. Expand User Configuration > Policies > Windows Settings > Scripts (Logon/Logoff).
7. In the right pane right click Logon, and then click Properties.
8. Click Show Files. This will bring up a file dialog in a logon folder.
9. Right-click the folder and then click New > Text Document to create a new text document in this directory.
10. Double-click the new file to open it in Notepad.
11. Enter the following script and save the file: D:\Setup.exe HideUI=1 AcceptLicenseTerms=1 InstallClientUI=1
ClientAosServer=Company1 ClientLanguage=en-US ClientHelpLanguages=en-US

NOTE: The directory path for Setup.exe should be a network path.

12. Right-click and rename "New Text Document.txt" to "AxInstallClient.cmd", then confirm the change of the file name extension when you are prompted.
13. Close the Windows Explorer menu.
14. Click Add, then click Browse.
15. Select "AxInstallClient.cmd", and then click Open.
16. Click OK.
17. Notice that the script has been added to logon properties, and then click OK.
18. Close Group Policy Management Editor.

NOTE: This setup can be proven by uninstalling the client, look to verify that the client has been removed, logoff the Virtual Machine (VM), logon to the VM, and verify that the client has been reinstalled. It might take several minutes after the logging on for the Microsoft Dynamics AX 2012 to apply.

NOTE: Scripts can also be set to run on the startup and shutdown of a server.

Include cumulative updates and hotfixes in a new installation (slipstreaming) AX 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

If you are installing Microsoft Dynamics AX components for the first time, and cumulative updates, binary hotfixes, or service packs for Microsoft Dynamics AX are available, you can incorporate the updates into the installation by using a process that is known as slipstreaming.

When updates are slipstreamed, Setup automatically detects and applies them. In this way, the time that is required to install the whole Microsoft Dynamics AX solution is reduced.

Note

Components that were previously installed are not updated during a later slipstream installation. For example, an instance of Application Object Server (AOS) is installed on a server. Later, you add updates to the installation source, and you also install another Microsoft Dynamics AX component on the same server. In this scenario, the existing AOS instance is not updated.

You can slipstream the following kinds of updates:

• Cumulative updates
• Binary hotfixes
• Help content updates
• Service packs

Application (database) hotfixes cannot be included in the slipstreaming process. They must be installed by using AxUpdate.exe.

The Updates folder

Before you install Microsoft Dynamics AX, you copy the DVD to a network location. This lets you modify the installation media to create a slipstream installation. Incorporate updates into the installation process by copying files to the Updates folder in the shared network location.

Note

For more information about how to install Microsoft Dynamics AX from a shared network folder, see Create a shared directory for installation.

In the Updates folder, create a subfolder for each update package that you download. We recommend that you use the Knowledge Base article numbers of the updates as the names of the subfolders. For example, for the update that is associated with Knowledge Base article number 123456, create a subfolder that is named KB123456.

Extract each update into the appropriate subfolder. The following illustration shows an example of the recommended folder structure:

Any time that you apply a cumulative update package or a binary hotfix to your environment, we strongly recommend that you add the installation package to the Updates folder. This practice ensures that you can deploy new servers, clients, and other components of the correct version quickly. You should also make a copy of the updated installation media per your system recovery strategy.

The slipstreaming process

The following is a high-level overview of the slipstreaming process:

1. To find cumulative updates, visit the hotfix pages for Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 R2 on the CustomerSource web site. Logon is required.
2. Create a shared network location from which to install Microsoft Dynamics AX.
3. In the Updates folder, create a subfolder for each update package that you download. Then extract each update into the appropriate subfolder.
4. Run Setup and select the components that you want to install. Setup detects and installs the updates.

Follow the usual installation procedures to install Microsoft Dynamics AX components. For detailed installation instructions for each Microsoft Dynamics AX 2012 component, see Install Microsoft Dynamics AX.

To install updates for Help content, you must select the Help Server component, and then select the updated content sets on the Language and content selection page.

Firewall settings for Microsoft Dynamics AX components [AX 2012]

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

If you use Windows Firewall to help protect your computers, Microsoft Dynamics AX components require the settings in the following table. For more information about Windows Firewall, see the Windows documentation.

Component	Computer	Firewall setting	Notes
Setup	Any	Allow outbound HTTP connections.	To access the documentation that is available from the Setup wizard, you must be able to connect to the Internet from the computer where you are running Setup.
Databases	Database server	Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433.	For more information, see the SQL Server documentation.
Application Object Server (AOS)	AOS server	· Exclude the TCP/IP port that is used by the AOS instance. By default, AOS uses port 2712. Setup automatically creates the inbound rule "Dynamics AX 6.0 –MicrosoftDynamicsAX (RPC)" for the TCP/IP port. · Exclude the services WSDL port that is used by the AOS instance. By default, AOS uses port 8101. Setup automatically creates the inbound rule "Dynamics AX 6.0 –MicrosoftDynamicsAX (WSDL)" for the WSDL port. · Exclude the services endpoint port that is used by the AOS instance. By default, AOS uses port 8201. Setup automatically creates the inbound rule "Dynamics AX 6.0 –MicrosoftDynamicsAX (NetTCP)" for the services endpoint port.	Windows Firewall must be enabled on the computer. Each AOS instance must use a different port number. Note By default, every time that you install an additional AOS instance on a computer, the TCP/IP port number and the services endpoint port numbers are incremented by 1. For example, by default, the second AOS instance on a computer is assigned to TCP/IP port 2713.
Client	Client workstation	Exclude Ax32.exe.	The client uses a TCP port to connect to the AOS instance.
Microsoft SQL Server Reporting Services extensions	Report server	Exclude the port that is used by Reporting Services virtual directories, if Reporting Services uses a port other than port 80.	If you are installing Reporting Services extensions in a perimeter network, you may need to add a firewall policy that enables you to connect to the Microsoft Dynamics AX database. For example, if you are using Forefront Threat Management Gateway (TMG), you must add a Non-Web Server Protocol Rule. For more information, seeConfiguring SQL Server publishing in the Forefront TMG documentation.
Microsoft SQL Server Analysis Services integration	Analysis server	· Exclude the port that is used by Analysis Services. By default, Analysis Services uses port 2383. · If you are using SQL Server Browser, you must also exclude port 2382.	For more information about how to configure access to Analysis Services through Windows Firewall, see the SQL Server documentation on MSDN.
Debugger	Developer workstation	Exclude AxDebug.exe and its target programs, such as Ax32.exe and AxServ32.exe.	The debugger uses a dynamically allocated TCP port.
Enterprise Portal for Microsoft Dynamics AX	Web server	· Enable the Web Server (HTTP). · Exclude the port that is used by the Enterprise Portal website, if the site uses a port other than port 80.	If you do not enable the Web Server in Windows Firewall, you can view the site only from the local server.
Help Server	Web server	Exclude the port that is used by the Help Server web site, if the site uses a port other than port 80.
Enterprise Search	Web server	Exclude the port that is used by the Search web site, if the site uses a port other than port 80.
Web services	Web server	Exclude the port that is used by the services web site, if the site uses a port other than port 80.	External programs use this port to consume the Microsoft Dynamics AX web services that are based on Internet Information Services (IIS).
Management utilities	Remotely managed computer	Enable Remote Administration.	You must enable Remote Administration on computers that are administered remotely by using Windows PowerShell. For example, enable Remote Administration on a computer if you deploy reports to that computer from another computer where Windows PowerShell is installed.
Synch Service	Head-office communications server	· Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. · Exclude the port that is used by Synch Service. By default, Synch Service uses port 16750. · Exclude the port that is used by Real-time Service. By default, Real-time Service uses port 1239.	For instructions, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Synch Service	Store communications server	· Enable Internet Protocol security (IPsec). · Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. · Exclude the port that is used by Synch Service. By default, Synch Service uses port 16750.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Real-time Service		Exclude the port that is used by Real-time Service, if the site uses a port other than port 80.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Retail POS	Store communications server	Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. Exclude the port that is used by Synch Service. By default, Synch Service uses port 16750.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Retail POS	Store database server	Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. On a register that has its own local database, you only need to open the firewall to SQL Server if Synch Service is on a computer other than the register.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Microsoft Dynamics ERP RapidStart Connector	Microsoft Dynamics ERP RapidStart Services host machine	· Exclude the executable file for the Microsoft Dynamics ERP RapidStart Connector service. By default, the file is installed in this location: %SystemDrive%\Program Files\Microsoft Dynamics AX\60\RapidStartConnectorService\Microsoft.Dynamics.AX.AppConfig.ConnectorLoaderService.exe · Exclude the endpoint port that is used by the Microsoft Dynamics ERP RapidStart Connector service. By default, the service communicates with the Windows Azure Service Bus on ports 9350-9354, 80, and 443. · Exclude the Windows Azure Cloud Services Protocols.

Drain users from an AOS – AX 2012

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.

 

1. Click System administration > Common > Users > Online users.

2. On the Server instances tab, select the AOS instance that you want to perform maintenance on.

3. Click Reject new clients.

4. 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.

5. After you have finished performing maintenance on the server, click Accept new clients or restart the AOS instance.