Microsoft Dynamics AX 2009 Known Issues

https://mbs.microsoft.com/downloads/customer/AX2009Docs/Dynamics_AX_Known_Issues.htm?wa=wsignin1.0

Information in this document, including URL and other Internet Web site references, is 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.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Microsoft Dynamics, Microsoft Office Excel, Microsoft Office InfoPath, Microsoft SQL Server, Microsoft Windows Internet Explorer,.NET Framework, Office, and X++ are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

Welcome to the May 2008 Release of Microsoft Dynamics AX 2009

<?XML:NAMESPACE PREFIX = [default] http://ddue.schemas.microsoft.com/authoring/2003/5 NS = "http://ddue.schemas.microsoft.com/authoring/2003/5" />

This Known Issues document contains information about known issues in the May 2008 release of Microsoft^® Dynamics^TM AX 2009.

Visual Studio will crash when you attempt to preview a report if the AOS is not running

Visual Studio will crash if the AOS is not running when you attempt to preview a report at the design time, and you will lose any unsaved changes. To work around this issue, make sure that the AOS is running during a report preview.

Installation components are not deployed successfully when Windows Message Queuing (MSMQ) is installed on a machine running on Windows Server 2008, and the AOD is not installed on the same machine

If you install components to integrate with Microsoft Office Project Server 2007 on a machine that is running Windows Server 2008, the deployment will fail. The failure occurs when the MSMQ and the synchronization service are installed on the machine without the AOS. To work around this issue, install the AOS on the same machine with MSMQ and the synchronization service. Because of this issue, multiple Project Server installations cannot be supported if the MSMQ and synchronization service are set up on Windows Server 2008.

Microsoft Dynamics AX 2009 reports deployment creates an incorrect data source connection type for OLAP documents

The data source created by the deployment tool for a project with binding to an MDX query contains an incorrect connection type that points to the SQL database instead of the Analysis database. To work around this issue, edit the deployed data source by using the report manager.

Cube processing will fail after you run the BI Project Update

Adding a new cube and making changes to the Out of the box (OTB) cube solution, can cause the cube processing step to fail if you are running the BI project update function from Microsoft Dynamics AX 2009 to update a project. When the processing fails, you will receive the following error:

Error1OLE DB error: OLE DB or ODBC error: Invalid column name 'DELIVERYDATECONTROL'.; 42S22.

To work around this issue, use the following steps to fix the Salesquotationtable_DIM and Quotations dimension in the BI cubes solution in the BI Development Studio.

1. Open the updated Microsoft Dynamics AX 2009 cube solution, and then find Salesquotationtable_DIM in the Data Source View.
2. Select all of the columns, and then right-click Delete logical primary key.
3. Select the Quotationtype, Quotationsstatus, and Deliverydatacontroltype columns, right-click, and then select Set logical primary key.
4. Select the table header again, right-click, and then select Edit named query.
5. Click OK.
6. Open the Quotations dimension, and then select the Quotation key attribute.
7. In the Quotation key attribute property sheet, click the KeyColumns property button.
   The DataItem Collection Editor opens.
8. Remove the DeliveryDateControlType column from the key, and then click OK.
   You can now process the cubes.

Axsetup does not recognize the SQL SP2 installation reporting extension installation

When you are installing the reporting extensions for Microsoft Dynamics AX 2009, you might receive a warning that SQL server SP2 is not installed even if you have already installed it. Use the following steps to work around this issue.

1. Locate the existing registry key at HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\.
2. Create a new key called Reporting services
3. Create a new String Value called Version
4. Enter a new keyvalue of 9.00.3042.00

AOT node properties are disabled

The AOT node properties HTMLHelpFile and HTMLHelpTopic are disabled. The properties are located in the AOT subnodes of System Documentation, Application Documentation, and Application Server Documentation. With these properties disabled, you are unable to update the properties to link to custom help.

To work around this issue, export the node to an XPO file, make the necessary changes, and then import the edited XPO back into the AOT.

Installing Microsoft Dynamics AX 4.0 and Microsoft Dynamics AX 2009 clients simultaneously on the same computer can result in CLR bridge DLL version confusion

Running Microsoft Dynamics AX 4.0 and Microsoft Dynamics AX 2009 side-by-side can result in activities involving .NET Business Connector that may be at risk for an AccessViolationException. These activities may include, for example, using the Reporting Services (AxReports.exe). The AccessViolationException can occur because the incorrect version of Microsoft.Dynamics.ClrBridge.dll might be loaded.

To work around this issue, copy the Microsoft.Dynamics.ClrBridge.dll file into the same directory where the executable program is located.

Report Builder is not supported for use with an Oracle database

Report Builder, which is a component of SQL Server Reporting Services, is not supported for use with Oracle databases. If you store your Microsoft Dynamics AX 2009 data in an Oracle database, you will not be able to use the Report Builder. To work around this issue, store your Microsoft Dynamics AX 2009 data in another database.

When installing the synchronization proxy and specifying the project server URL, an error displays when the URL page is entered

When installing the synchronization proxy while on the AX install wizard, an error displays when the URL page is entered in the "Connect to MS Office Project Server" page. To work around this situation, enter the site URL of the project server. For example, instead of entering http://machinename/PWA/default.aspx which is the page URL, enter http://machinename/PWA which is the site URL.

Modifying the Name extended data type can cause synchronization failure

During the installation process for Microsoft Dynamics AX 2009, if you change the Name extended data type in step 5 of the Initialization checklist, you will receive the following message when you synchronize the database:

"Synchronize database" form appears with 1 error: "Synchronize databaseThere is a field mismatch in the union query. Field AccountNum is not compatible with field PartyId."

Use the following steps to work around this issue.

1. Open the AOT.
2. Click Data Dictionary > Extended Datatypes.
3. Right-click DirPartyID, and then select Properties.
4. Change the StringSize to 20, and then save your changes.

Totals for a purchase order cannot be viewed

Viewing purchase order totals in the Totals form is not possible for a user. To work around this issue, click Administration > Setup > Security > User group permissions. On the Permissions tab, expand Administration and select the Tables node. It is not required that you select the subnodes.

Upgrade script for Quality Management System (QMS) module not available

The script to upgrade the QMS module (formerly Fullscope TQM) from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2009 is not available at this time.

A compiler error in perspectives will occur when you upgrade from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2009

When you upgrade from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2009, and you reach the end of compile (SYS, CUS, USR layers), the perspective save operation will fail and the following errors are displayed:

• "Error Message (01:57:20 pm) Unable to save. Unable to save Perspective COSCosting"
• "Error Message (01:57:20 pm) Unable to save. Unable to save Perspective HRM"

To work around this issue, before you begin the upgrade, export your perspectives into an .xpo file. After you perform the upgrade, if no errors have occurred, no additional steps are necessary. However, if you complete the upgrade and receive errors, delete all of the perspectives in the current layer, and then import the .xpo that you previously created.

An error occurs when running data import operations on a database with Turkish collation or when you opt in for reporting customer experience data to Microsoft servers by using SQM

If you have a database with Turkish collation, or if you have opted in for reporting customer experience data to Microsoft servers by using SQM and you run the data import operation (Administration > Periodic > Data export/import > Import on a database), you will receive the following error message: "No system GUID found in SysSomSetting table." If you receive this error message, data import will not occur. To work around this issue, work with your Microsoft Dynamics AX partner to contact Microsoft support to obtain a SQL script that can be run before importing the data.

Topic built:5/21/2008 4:00:45 PM

转载于:https://www.cnblogs.com/joshuali/archive/2011/03/24/4339445.html