MicrosoftDynamicsAX2012BetaKnownIssues
MicrosoftDynamicsAX2012BetaKnownIssues
Information in this document, including URLs and other Internet Web site references, are subject to change without
notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos,
people, places, and events depicted in examples herein are fictitious. No association with any real company,
organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any
purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights
covering subject matter in this document. Except as expressly provided in any written license agreement from
Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or
other intellectual property.
Microsoft, Excel, InfoPath, Internet Explorer, Microsoft Dynamics, MS-DOS, SharePoint, SQL Server, Visual Basic,
Visual Studio, Windows, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks
or trademarks of Microsoft Corporation in the United States and/or other countries.
April 8, 2011
Setup
The AXUtil IMPORTSTORE command does not prompt you to back up data
When you import data using the AXUTIL IMPORTSTORE /file:filename command, you are not prompted to back
up your data before you start the process. Running the AXUTIL IMPORTSTORE /file:filename command
overwrites all models and metadata in the target database. This can affect business data and production
environments.
To work around this issue, stop the AOS, and then back up the target database. Restart the AOS. Before you start
the import process, verify that you are importing the appropriate file.
Multiple instances of Microsoft SQL Server Reporting Services cannot be installed on the same
server
Report deployment fails if multiple instances of SQL Server Reporting Services are installed on a computer, and each
instance is linked to a different AOS server. There is no workaround for this issue.
The SQL Server Reporting Services framework does not support SharePoint integrated mode
You cannot use SharePoint integrated mode for reporting in Microsoft Dynamics AX. To work around this issue,
install SQL Server Reporting Services in native mode to use the computer as a dedicated reporting server for
Microsoft Dynamics AX.
Installation
Some languages are not available in the Beta release of Microsoft Dynamics AX
During installation of the Beta release of Microsoft Dynamics AX, the default language is EN-US for English (United
States). The only other languages that are available for this release are French (France), German (Germany), Italian
(Italy), Spanish (Spain), Dutch (Netherlands), and Danish (Denmark). If you select any of the languages other than
EN-US, follow the workaround in The Foundation Label Model must be installed if you select a language
other than EN-US later in this document.
The Foundation Label Model must be installed if you select a language other than EN-US
If you select a language other than EN-US during installation and you do not also select the Foundation Label Model
component, Microsoft Dynamics AX will not open after installation. To work around this issue, run Setup again, and
select the Foundation Label Model component.
Microsoft Visual Studio 2010 Service Pack 1 is not supported for Microsoft Dynamics AX
Development for Microsoft Dynamics AX using Visual Studio 2010 Service Pack 1 is not supported. To work around
this issue, install an earlier version of Microsoft Visual Studio.
Installation of the synchronization service and configuring queues fails on a computer that is
running Microsoft Windows Server 2008 Service Pack 2 (SP2)
The Message Queuing feature must be enabled on the local server for Setup to configure Microsoft Message Queuing
for the synchronization service. Setup is unable to correctly detect the Message Queuing feature on a computer that
is running Windows Server 2008 SP2, which prevents the installation of the synchronization service.
Use existing queues. If the synchronization service must be installed with SP2, you can create the queues
manually, and then specify them in Setup.
Use Windows Server 2008 R2. Setup can configure the queues for you on Windows Server 2008 R2 or a later
version.
Opening Microsoft Visual Studio from MorphX might not reuse layer, model, and company setup
If you start MorphX using command-line options for layer, model, or company, and you start Visual Studio from
MorphX, Visual Studio might not retain the settings of layer, model, and company. To work around this issue, use
client configurations when you open MorphX instead of using command-line options.
Deployment of C# and Microsoft Visual Basic projects to SQL Server Reporting Services is not
supported
C# and Visual Basic projects that are added to the AOT have a DeployToSSRS property. Setting this property to
Yes has no effect. To work around this issue, deploy managed code to SQL Server Reporting Services by using data
methods in reports.
System administration
Modifying a server configuration with the Server Configuration Utility might incorrectly set the
firewall rule
When using the Server Configuration Utility to modify an AOS configuration, the Windows Firewall rule might not
contain the executable name. This will prevent clients from connecting to the AOS. To work around this issue,
include the executable name if you use the server configuration utility to create the inbound rule in Windows Firewall
with Advanced Security. The following examples show an incorrectly set rule and a correctly set rule:
1. Click System administration > Setup > Services and Application Integration Framework > Inbound
ports.
2. In the Inbound ports form, on the Port name list, select the CommerceServiceXXX port, where XXX is the
company code.
3. Click Deactivate.
4. Click Configure.
5. On the Microsoft Service Configuration Editor form, in the Configuration pane, click Services >
Microsoft.Dynamics.Ax.Services.CommerceServices >Host. In the right pane, on the Binding tab, in the
OpenTimeout field, set the value to 5:00 minutes.
6. In the Configuration pane, click Bindings > DefaultServiceGroupBinding (netTcpBinding). In the right
pane, on the Binding tab, set the value to 5:00 minutes for each of the following fields:
SendTimeout
OpenTimeout
CloseTimeout
7. Close the Microsoft Service Configuration Editor form.
8. In the Inbound ports form, select the CommerceServiceXXX port, where XXX is the company code, and
then click Reactivate.
Organization administration
Office Add-ins
Error messages cannot be viewed when you use the Office Add-ins
When you publish data by using tables or services in the Office Add-in for Excel, some classes of errors are not
transmitted back to the status sheet. In these cases, you will see errors such as “Creation was canceled.” To work
around this issue, review the exception message in the Microsoft Dynamics AX client at the following location:
System Administration > Periodic > Services and Application Integration Framework > Exceptions.
Microsoft Excel workbooks that contain matrix fields are not refreshed
If you create a matrix field within an Excel worksheet, save the workbook, and then reopen it, the workbook is not
refreshed. There is no workaround for this issue.
Financial
Creating travel and expense policies with multiple conditions does not work
If you create an expense report or a travel requisition policy rule that contains more than one condition, an error
message is displayed for entries that break the policy. The error message appears when you attempt to save lines
that reference the policy rule in an expense report and travel requisition. To work around this issue, do not add more
than one condition when you create an expense report or travel requisition policy.
Analysis cubes project update causes an error when currency conversion is not selected
When updating the analysis cubes project by using the SQL Services Analysis Service Project Wizard, an error is
displayed and the project will not build if the Add foreign currency support to the Analysis Service project
check box is not selected. To work around this issue, select a currency conversion in the wizard.
Dimension attribute labels might be blank when you use the SQL Server Analysis Services Project
Wizard
The dimension attribute labels might be blank if you do not select at least one language when you use the SQL
Server Analysis Services Project Wizard. To work around this issue, select at least one language for translations
when you update an Analysis Services project by using the wizard.
The custom expression editor for Microsoft Visual Studio 2010 does not work when you create a
precision design for a report
The custom expression editor is not working. You can reference Microsoft Dynamics AX labels directly and access
public APIs that are provided by the reporting framework. However, you can only access the generic SQL Server
Reporting Services expression editor that is available in Precision Designer. To work around this issue, add all
references to Microsoft Dynamics AX labels and public APIs in the auto design solution before converting the report
into a precision design.
Production control
Resource scheduling does not work if you select a specific configuration option
Resource scheduling is not working if the option Allow hot swapping of assemblies when the server is running
is activated in the Microsoft Dynamics AX server configuration. To work around this issue, do not select that option.
A chart in the role center for Accounts receivable activities is not displayed
The role center for Accounts receivable activities displays an error message in place of the Receivables by
billing classification and period chart. There is no workaround for this issue.