Microsoft Dynamics AX Resource Pages

Resource Page for Upgrading to Microsoft Dynamics AX 2012

David W. Robinson — Tue, 07 May 2013 20:34:00 GMT

Help Refresh Includes New Upgrade Poster

Upgrade is complex. As writers, we work closely with the upgrade feature team to anticipate and understand your needs as customers and partners. We also engage frequently with the customer support team to react to your questions and suggestions. With the release of Microsoft Dynamics AX 2012 R2, we have completely restructured the upgrade documentation to include the following improvements:

In the Microsoft Dynamics AX 2012 Upgrade Guide, which provides end-to-end guidance for every stage of upgrade, we have arranged the content around upgrade scenarios that system administrators are likely to encounter. An advantage to using scenarios is the high-level view they afford. You’ll be able to see the big picture first, and then view the details through tables of linked tasks as you need them. The task topics can also be browsed alphabetically in a single reference section.The following scenarios are documented:

- Upgrade Microsoft Dynamics AX 4.0 or AX 2009 to Microsoft Dynamics AX 2012 (all versions)
- Perform in-place upgrade to Microsoft Dynamics AX 2012 R2
- Perform in-place upgrade to Microsoft Dynamics AX 2012 Feature Pack
- Upgrade a Retail system
- Upgrade a country-specific system

The online upgrade documentation on TechNet, which is updated more frequently than the downloadable Upgrade Guide, now mirrors the same scenario-based structure.
Your feedback on your experience with in-place upgrades (those between two different releases of Microsoft Dynamics AX 2012) led the upgrade team to create upgrade best practices that include a recommended upgrade topology. The documentation team has responded with a process diagram (available for download and suitable for printout as a poster) that depicts this recommended approach. We expect it to be an aid to both the planning and execution of upgrades. You can explore the poster right now at Microsoft Zoom.It by clicking the image below:

Resource Page for Purchase Order Invoicing in Microsoft Dynamics AX

Erin Koffler MSFT — Thu, 11 Apr 2013 14:55:00 GMT

This blog post summarizes common questions and answers about purchase order invoicing (PO invoicing). The following questions are included:

Where is the documentation for PO invoicing?
Why are there extra journal entries for Purchase order expenditure, un-invoiced and Purchase expenditure for product when vendor invoices are posted?
Why are ledger entries missing after I post vendor invoices? (Hint: They’re not really missing…)
How does invoice matching work in the Vendor invoices form?
Can I use invoice matching with service items and category-based items, as well as stocked items?
What do I do if I get a message about pending invoices not being displayed?

This blog post will be updated with additional questions. Add your question as a comment to the blog, or send email to adocs@microsoft.com.

Where is the documentation for PO invoicing?

If you’ve searched online for PO invoicing, you probably haven’t found much official documentation about it. That’s because the terminology changed in Microsoft Dynamics AX 2012. References to purchase order invoice were changed to vendor invoice. Search for vendor invoice AX 2012 to find the most up-to-date documentation.

Start with the following topics on TechNet:

Why are there extra journal entries for Purchase order expenditure, un-invoiced and Purchase expenditure for product when vendor invoices are posted?

Amounts are posted to these posting accounts when the product receipt is posted, and are then backed out when the invoice is posted. For more information, see the following white paper and blog posts:

Why are ledger entries missing after I post vendor invoices? (Hint: They’re not really missing…)

If a subledger journal is posted and the Transfer mode field in the General ledger parameters form is set to Batch or Asynchronous, the ledger entries might not be posted immediately after you click the Post button. For more information, see the following resources:

General ledger parameters (form) — Synchronous, Asynchronous, and Scheduled batch are the options for the transfer mode. The Asynchronous option transfers when there are resources available. The Scheduled option transfers on a periodic basis, such as daily.
Vendor invoice (form) — When you click the Post button, the source document line might not be posted immediately if batch or asynchronous posting is set up.
Batch transfer for subledger journals (form) — If vouchers seem to be missing from the Voucher transactions form, it might be because the batch hasn't been processed yet.
Dynamics AX2012 Posting and Summarization (blog post)

How does invoice matching work in the Vendor invoices form?

After invoice matching is set up, invoices are automatically matched when you enter or edit them in the Vendor invoices form. Invoice matching discrepancies are shown in the Invoice matching details form. For information about how to set up invoice matching, see the following topics on TechNet.

For information about how to resolve matching discrepancies or make corrections, see the following topics on TechNet.

The Financial I training manual explains invoice matching in “Chapter 10: Accounts Payable Daily Procedures.”

Can I use invoice matching with service items and category-based items, as well as stocked items?

You can set up two-way and three-way invoice matching for categories in the Category policy rule form. You might do this if you want to match the expected quantities and costs for services or other items that are not stocked.

1. Click Procurement and sourcing > Setup > Policies > Purchasing policy.

2. On the Action Pane, click Policy to create a new policy.

3. Enter a name and select an organization node.

4. On the Policy rules FastTab, select the Category policy rule type, and then click Create policy rule.

5. In the Category policy rule form, click Add.

6. Select a category, and then select a matching policy in the Category matching policy field. Select from the following options:

- Company policy
- Three-way matching
- Two-way matching
- Not required

What do I do if I get a message about pending invoices not being displayed?

Sometimes, an invoice might end up in a state where it has unsaved changes and you can’t edit it. If this happens, you’ll get the following message when you try to open the Vendor invoice form:

A pending invoice cannot be displayed because it is in use. If nobody else is working with the invoice, you can delete the unconfirmed changes to the invoice, and then you can modify the invoice. Use the Invoice history and matching details form or the Approval journal history and matching details form to delete the unconfirmed changes.

A pending invoice might be “in use” for one of three reasons:

Microsoft Dynamics AX stopped responding while you were working with the invoice. This is the most common reason for this message.
You already have the invoice open in another instance of the Vendor invoice form.
The invoice is in a batch that is waiting to be posted.

If the application stopped responding, you can delete the unsaved changes, and then modify the invoice. If you saved an earlier version of the invoice, you won’t have to start over. You will only have to enter the changes that haven’t been saved.

To delete the unsaved changes from a pending invoice, use the Invoice history and matching details form or the Approval journal history and matching details form.

Invoice history and matching details form

1. Click Accounts payable > Inquiries > History > Invoice history and matching details.

2. Select the purchase order, and then click Invoice.

3. In the Invoice journal form, select the invoice that has unsaved changes.

4. Click File > Delete Record.

Approval journal history and matching details form

1. Click Accounts payable > Inquiries > History > Approval journal history and matching details.

2. Select the purchase order, and then click Invoice.

3. In the Invoice journal form, select the invoice that has unsaved changes.

4. Click File > Delete Record.

Don’t see your question here?

This blog post will be updated with additional questions. Leave a question in the comments or send email to adocs@microsoft.com.

Resource page for Retail for Microsoft Dynamics AX 2012

Eriel Ross — Wed, 20 Feb 2013 00:35:00 GMT

This page provides you with a consolidated list of published documentation, sources of information, known issues, solutions and tips and tricks for troubleshooting the Microsoft Dynamics AX 2012 Feature Pack and Microsoft Dynamics AX 2012 R2.

Important Note: The documentation for the Retail features of Microsoft Dynamics AX 2012 is now available on TechNet, MSDN, and on the Help Server, rather than as separate guides.

On this page:

Top Downloads
Critical Hotfixes
Resources
Best practices
Troubleshooting tips
Still having trouble...

Top Downloads

View and download demo packages, training guides and popular documents for Microsoft Dynamics AX 2012, and Microsoft Dynamics AX 2012 R2.

Link	Description
Microsoft Dynamics AX 2012 R2 Demo package and VM	The Microsoft Dynamics AX2012 R2 demo package includes links to a virtual machine (VM) that includes a full set of demo data, a database backup, demo scripts, click-through demos and related material.
Microsoft Dynamics AX for Retail 2012 R2 training guide	The Microsoft Dynamics AX for Retail 2012 R2 training guide is intended for partners who want to set up and use the application functionality in Microsoft Dynamics AX for Retail. This guide explains how to use the Retail module to manage a retail business from the head office to the retail stores.
PCI Implementation guide for Microsoft Dynamics AX 2012 R2	This guide describes how to implement Microsoft Dynamics AX 2012 R2 in compliance with the Payment Card Industry (PCI) Data Security Standard version 2.0.
Changes to credit card processing for Microsoft Dynamics AX 2012 R2	This document describes what has changed in the implementation of credit card processing in Accounts receivable in Microsoft Dynamics AX 2012 R2. These changes are driven primarily by the switch from a single credit card processor to support for multiple credit card processors. Support for multiple credit card processors is a benefit of using the Payment SDK.
New, changed and deprecated features for Microsoft Dynamics AX 2012	This document provides a summary of new and changed features that have been implemented in Microsoft Dynamics AX 2012, Microsoft Dynamics AX 2012 Feature Pack, and Microsoft Dynamics AX 2012 R2. It also provides deprecated feature notices that describe features that have been removed in these releases, or that are planned to be removed in future releases

Service	Error	Error Text	Explanation
BillOfMaterials	Invalid Keys	Cannot load [AxdBillsOfMaterials]. The data source [BOMVersion] does not have a valid replacement key or a primary index other than RecId.	The root of the underlying query has no visible means of identifying the BOMVersion recordbecause RecId is the only unique index.
CustService	Invalid Relation within the service	The relation between data source CustTable and data source DirParty contains an unsupported RecId relationship	The parent data source custTable references the child data source dirParty. Child data sources must reference the parent for use with Excel Office Add-in.
ExchangeRate	Invalid relation outside the service	The relation between data source CurrencyPair and data source RateType contains an unsupported RecId relationship	The field CurrencyPair is a RecId-based relation to an external table, Rate Type, which has no replacement key specified.
VendTable	Invalid Relation within the service	The service [VendTableService] has surrogate foreign key expansion errors: The table [VendTable] surrogate foreign key field [Party] does not have a reference data source.	The parent data source vendTable references child data source dirParty. Child data sources must reference the parent for use with Excel Office Add-in.

Issue:	Error message when inserting a table into the Excel Office Add-in component. The error is: Cannot load [tablename]. Tables must have a valid replacement key or a primary index other than RecID for using in the Office Add-ins.
Solution:	Modify the table to have a valid replacement key to allow the Office Add-in to function the way you want it to. See Dynamics AX 2012 Excel Add-in - Replacement Keys and Table Keys: Surrogate, Alternate, Replacement, Primary, and Foreign
Issue:	Dynamics AX 2012 Office Add-ins and Office 2007 Compatibility
Solution:	See Dynamics AX 2012 Office Add-ins and Office 2007
Issue:	Dynamics AX 2012 Excel Add-in: Timeout issues when working with a lot of data
Solution:	See Dynamics AX 2012 Excel Add-in: Timeout issues

Issue	Error trying to deploy reports: Microsoft Dynamics AX Reporting Project Deployment: The following components have not been installed or are not configured correctly: AL.exe
Solution	Download and install the Windows SDK for Windows Server 2008 and .NET Framework 3.5 Ensure it is fully installed. Note: Install regardless of operating system
Issue	Error trying to deploy reports System.InvalidOperationException: The following components have not been installed or are not configured correctly: Microsoft Domain-Specific Language Tools
Solution	Download and install these required components. Microsoft Visual Studio 2008 Shell (isolated mode) Redistributable Package Save the download locally . Extract the package. Run the vs_appenvredist.msi Note: Install regardless of operating system
Issue	Error trying to deploy reports Microsoft Dynamics AX Reporting Project Deployment: ClrBridgeLoader: fatal error : Microsoft.Dynamics.ClrBridge.dll cannot be loaded. Fatal error: ClrBridge is note loaded.
Solution	Ensure you are trying to deploy reports from the SSRS server and that you can validate the SSRS server name in the Reporting Servers from within Microsoft Dynamics AX 2009. If this error appears right after installing the reporting extensions, launch the report deployment tool again.
Issue	Enterprise Portal (EP) or SSRS Reports don’t run or stop working An attempt has been made to use a data extension 'AXDATAMETHOD' that is not registered for this report server. (rsDataExtensionNotFound) or data extension 'AXQUERY' and 'AXADOMD'
Solution	Installing or Reinstalling Reporting Extensions will resolve this issue. As a precaution make a Backup of: Program Files\Microsoft SQL Server\MSSQL.<Instance>\Reporting Services\ReportServer folder Note: SSRS updates or Service Packs may remove entries from rsreportserver.config file.
Issue	Enterprise Portal (EP) Reports don’t run or stop working A ProgressTemplate must be specified on UpdateProgress control with ID 'AxProgressControl'
Solution	You can resolve the issue by using one of the three methods below: Apply the hotfix from KB957312 to the RTM version. Upgrade to Microsoft Dynamics AX 2009 SP1. Un-install Microsoft .NET 3.5 SP1 and reinstall Microsoft .NET 3.5 without SP1
Issue	Report deployment tool crashes Attempted to read or write protected memory. This is often an indication that the memory is corrupt
Solution	If multiple versions of Dynamics AX are installed on the same server you will need to change your AX 2009 Path in your environment variables ahead of your AX 4.0 path to avoid running the wrong version of DLL’s
Issue	Error running reports Error during processing of 'AX_CompanyName' report parameter. (rsReportParameterProcessingError).
Solution	Process OLAP the cubes to supply data to the reports or An incorrect Execution account has been specified in the Reporting Services Configuration Manager Note: For SSRS 2008 the Business Connector proxy account is required to be the SSRS service account and for SSRS 2005 the Business Connector Proxy account should be running as the SSRS application pool in IIS. Also look at application event log for details on other issues.
Issue	Enterprise Portal (EP) web site runs but not the reports in the EP web parts: Dynamics Adapter LogonAs failed or Microsoft.Dynamics.BusinessConnectorNet.LogonFailedException
Solution	Leave the Execution account blank on SSRS 2005 or set to BC Proxy account on SSRS 2008 (Microsoft Dynamics AX 2009 SP1 only) Note: SSRS Execution account is set to an account other than BC Proxy Account
Issue	EP or SSRS Reports don’t run or stop working Dynamics Adapter LogonAsGuest failed or FatalSessionException...
Solution	The issue is caused by the Reporting Services web site set to anonymous Authentication. Changing the SSRS website to Integrated and/or un-marking Anonymous Authentication will resolve this issue.
Issue	Double Hop \ Kerberos Authentication An Error has occurred while establishing as connection to the Analysis Server or Reports don’t display in the EP website from a Client Browser not local to the IIS server Cannot read information from SQL Server Reporting Services. Validate that the Report Manager URL is correct
Solution	Setup Service Principle names (SPN) and Delegation to allow the passing of Kerberos certificate References: White Paper: Configuring Kerberos Authentication with Role Centers KB917409: How to configure SQL Server 2005 Analysis Services to use Kerberos authentication MSDN blog: Enterprise Portal Kerberos Delegation for connecting to Reporting/Analysis Services on a different box TechNet blog: Understanding Kerberos Double Hop
Issue	Office Data Connection (ODC) file deployment fails with SQL Server 2008 Microsoft Dynamics AX is searching for the SQL Server 2005 Microsoft.AnalysisServices.dll (v9.0.242.0)
Solution	Apply one of the following hotfixes: For Microsoft Dynamics AX 2009 RTM: Apply the fix from KB957312 For Microsoft Dynamics AX 2009 SP1: Apply the fix from KB960158 If the hotfix does not resolve the issue, make sure you are running a Dynamics AX 2009 client on the EP web server when deploying the ODC files. As a workaround you can manually deploy the ODC files by following these steps: Click here to download a new ODC file (Dynamics_AX.odc). Save the ODC on the SSAS server. Open the ODC file with Notepad or any other text editor. Edit the odc file with the following changes: Data Source=OLAPServerName Initial Catalog=OLAPDbName Add SSPI=Kerberos after Initial Catalog if using Kerbersos (in red only required for Kerberos authentication) … …. <odc:Connection odc:Type="OLEDB"> <odc:ConnectionString>Provider=MSOLAP.3;Integrated Security=SSPI;Persist Security Info=True; DataSource=<Server1>;Initial Catalog=Dynamics AX;SSPI=Kerberos </odc:ConnectionString> … Save the changed ODC file. Go to EP main site. Click Site Actions, and then click Site Settings. Under Galleries, click Master pages. Click View all site content (top left). Click Data Connections folder. Import the edited ODC file.
Issue	DataSet panel is missing in Report Designer when creating reports in Visual Studio Server 2008
Solution	For Visual Studio 2008, apply the fix in KB947173 OR apply Microsoft Visual Studio 2008 Service Pack 1.
Issue	"Connection forcibly closed by remote host" in Dynamics setup log when trying to create an EP site in Microsoft Dynamics AX 2009
Solution	Download and install the Microsoft Analysis Management Objects: for SQL Server 2005: Microsoft SQL Server 2005 Management Objects Collection package for SQL Server 2008: Microsoft Analysis Management Objects package
Issue	"Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'"
Solution	Ensure SSRS service is running and are able to connect to instance via SQL Server Management Studio. Note: Additional information can be found in SSRS error log.
Issue	Exception from HRESULT: 0X80041FFF
Solution	Change Visual Studio project location to local drive if using a network share
Issue	The Analysis extension is not seeing the SQL cluster name for Analysis Services when Analysis services is setup on a SQL cluster. You will get an error similar to this when trying to install Analysis Extension in this environment: Connecting to SQL Server 2005 Analysis Services on server 'SQL02' and instance 'MSOLAP$ANALYSIS'. A connection cannot be made. Ensure that the server is running. No connection could be made because the target machine actively refused it 127.0.0.1:2383 An error occurred while Setup was connecting to SQL Server Analysis Services instance 'MSOLAP$ANALYSIS' on server 'SQL02'. An error occurred while Setup was connecting to SQL Server Analysis Services instance 'MSOLAP$ANALYSIS' on server 'SQL02'.
Solution	The workaround is to manually run the script to create the Dynamics AX OLAP db from the AX 2009 CD. Navigate to this folder: \support\Analysis Services\Scripts on the Microsoft Dynamics AX 2009 installation CD. Then run the dynamicsax.xmla script from within SQL Management Studio (connected to the SSAS instance). This script will create the Dynamics AX OLAP database.
Issue	BC Proxy account fails to start for the SSRS reports in Enterprise Portal with RPC exception 5 When Enterprise Portal starts for the first time and displays SSRS reports, normally two Business Connectors are started. After a period of time or if the impersonated web user logs out for the SSRS Proxy account you may experience an RPC error 5 access denied and the SSRS reports will no longer display in Enterprise Portal. Example Event Type: Error Error: Event Source: Dynamics .NET Business Connector 5.0 Event Category: None Event ID: 180 Date: 10/7/2008 Time: 6:21:04 PM User: N/A Computer: AX2009 Description: Microsoft Dynamics AX Business Connector Session 18. RPC error: RPC exception 5 in Ping occurred in session 36
Solution	RPC error 5 can occur if the SSRS Execution account is set in the Reporting Services Configuration Manager. If the account used is the Business Connector proxy account the first startup of the Business Connector will work, but not any subsequent startups unless the IIS application pool if recycled or an IIS reset is done. SSRS 2005 Remove the SSRS execution account through Reporting Services Configuration Manager and ensure the Business Connector account is running the IIS Application Pool for the SSRS web site. SSRS 2008 Change the SSRS service to start as the Business Connector Proxy account and remove the SSRS execution account through Reporting Services Configuration Manager. Note: Changing the SSRS account would require a change in the registered SPN’s if you are using Kerberos authentication

Issue	The setup fails to deploy the Microsoft Dynamics AX site template if not licensed for EN-US. In the DynamicsSetup.txt file, you find the following error: Creating new Enterprise Portal Site with following the parameters:\n URL: http://server/sites/DynamicsAX\n Title: Enterprise Portal Site\n LCID: 1033\n OwnerLogin: domain\user Administration Web Service URL: http://server:44901/_layouts/ep/WSSAdmin.asmx Error: The site /sites/DynamicsAX could not be created. The following exception occured: File or arguments not valid for site template 'AXSITEDEF#0'.. An error occured while Setup was creating a new site. Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown. File or arguments not valid for site template 'AXSITEDEF#0' Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
Solution	This issue is solved by applying the hotfix available in KB 960048. Note: If the Enterprise Portal installation still fails with the same error after applying KB 960048, recompile the SysEpDeployment class on a computer where the Microsoft Dynamics AX Client and the .NET Business Connector are both installed.
Issue	The setup fails if the .NET Business Connector is not installed on the Microsoft Dynamics AX client computer in which the initialization checklist is run. If the .NET Business Connector is not installed on the Microsoft Dynamics AX client when the initialization checklist is run, the SysDevelopmentProxy class does not get compiled. If SysDevelopmentProxy class is not compiled, then setup fails to install Enterprise Portal. In the DynamicsSetup.txt file, you find the following error: In SysEPDeployment::clrGenerateProxies... Error executing code: SysDevelopmentProxy (object) has no valid runable code in method 'generate'.
Solution	This issue is solved by applying the hotfix available in KB 971185. Additionally, there is the following workaround: Manually compile the SysDevelopmentProxy class: Start the Microsoft Dynamics AX 2009 Client on a computer where the .NET Business Connector is also installed. Open the AOT window. Expand the Classes node. Locate the SysDevelopmentProxy class. Right-click at the class, and then choose Compile from the context menu. If the manual compile does not work, then rebuild the axapd.aoi and then repeat the manual compile. br>
Issue	The setup fails when the installer uses the NETBIOS domain name instead of the fully qualified domain name In the DynamicsSetup.txt file, you find the following error: Entering method UpdateBusinessConnectorProxyAccount An error has occured while Setup was establishing a connection through Business Connector. Error: Dynamics Adapter CallStaticClassMethod failed. Leaving method UpdateBusinessConnectorProxyAccount The Microsoft Dynamics AX installer reads the .NET Business Connector Proxy account from the System Service Accounts form and truncates the fully qualified domain name (FQDN), to the NETBIOS name. If NETBIOS is not configured on the domain the then the Business Connector Proxy account will not be authenticated and the installer will fail.
Solution	Blank out the Business Connector Proxy account in the System Service Accounts form. Run the installer again and you will be allowed to enter in the fully qualified domain name (FQDN) Note: A similar issue can occur if the Business Connector account stored in the Microsoft Dynamics AX database is using the NETBIOS name and the application pool is using the fully qualified name or vise versa. Make both accounts match using format stored in the Microsoft Dynamics AX database.
Issue	The setup fails and the IIS worker process crashes if AMO is not installed. In the DynamicsSetup.txt file, you find the following error:br> An Existing Connection was forcibly closed by remote host
Solution	The IIS/EP server requires AMO objects to be installed. Install the AMO objects and run setup again. Refer to the Install prerequisites for Enterprise Portal and Role Centers page on TechNet for SQL specific version downloads of the SQL Server Analysis Management Objects (AMO)
Issue	Opening Manage Deployments form generates error when using the 64bit version of WSS If you have Windows SharePoint Services(WSS) and the .NET Business Connector installed as 64bit versions, you cannot use the 32bit Microsoft Dynamics AX Client to deploy or update Enterprise Portal sites. When you try to open the Manage Deployments form you receive the following error message: Manage Deployment cannot be run because Enterprise Portal is not deployed on this computer.
Solution	Microsoft Dynamics AX 2009 Service Pack 1 has a new command line utility, AxUpdatePortal.exe, that gets installed in the C:\Program Files\Microsoft Dynamics AX\50\Setup folder that serves this purpose. More information on this utility is available at http://msdn.microsoft.com/en-us/library/dd261467.aspx You can execute the utility with the following command line parameters to update all local Enterprise Portal sites: AxUpdatePortal.exe -updateWebSites -iisreset Note: On Windows Server 2008 make sure you run AxUpdatePortal.exe from an elevated command prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator. More information available on these blogs: MSDN (public) Dynamics AX Partner Forum (login required) Please be aware that there is a hotfix KB974767, which will check if you are running AXUpdatePortal in admin mode.
Issue	401 Error on a web site that has Host Headers configured When .NET Framework 3.5 Service Pack 1 is installed and the IIS web site has a Host Header configured, the following error occurs: The Web site http://server/sites/Dynamics AX was not created correctly. The remote server returned an error: (401) Unauthorized. System.Net.WebException at System.Net.HttpWebRequest.GetResponse() at Microsoft.Dynamics.Framework.Portal.Deployment.EPFeatureReceiver.CreateAxSitesAndPages(SPWeb site) at Microsoft.Dynamics.Framework.Portal.Deployment.EPFeatureReceiver.ProvisionAxSite(SPWeb site)
Solution	The release of .NET Framework 3.5 Service Pack 1 introduced changes to NTLM authentication for HTTPWebRequest. More information on this change is available at http://msdn.microsoft.com/en-us/library/cc982052.aspx The changes in .NET Framework 3.5 Service Pack 1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name. The changes in .NET Framework 3.5 Service Pack 1makes it necessary to configure the BackConnectionHostNames registry to match the Host Header name on the IIS web site. Adding a registry value tells Windows that the Host Name used in the request is a valid alternate name for the local computer. Refer to one of the Related Articles for detailed steps for editing the BackConnectionHostNames registry key. After making the change in the Registry, reboot the server and repeat Enterprise Portal install. Related Information: KB 896861 - You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6 KB 956158 - You receive an error message when you use SQL Server 2008 Reporting Services: "HTTP 401.1 - Unauthorized: Logon Failed" NLB Deployment of Enterprise Portal Setup: Stream or Download (WMV - 13 MB)
Issue	Microsoft Dynamics AX 2009 was only supported with WSS 3.0 SP2, we now support SharePoint 2010 by Appling KB 2278963
Solution	See Compatibility Result for Microsoft SharePoint 2010 - August 2010 Resolving some issues you may experience when creating an AX 2009 Role Center and Enterprise Portal Site using SharePoint Server/Foundation 2010 after installing Microsoft Dynamics AX 2009 SP1 hotfix 2278963

Microsoft Dynamics AX Resource Pages

Resource Page for Upgrading to Microsoft Dynamics AX 2012

Help Refresh Includes New Upgrade Poster

Resource Page for Purchase Order Invoicing in Microsoft Dynamics AX

Where is the documentation for PO invoicing?

Why are there extra journal entries for Purchase order expenditure, un-invoiced and Purchase expenditure for product when vendor invoices are posted?

Why are ledger entries missing after I post vendor invoices? (Hint: They’re not really missing…)

How does invoice matching work in the Vendor invoices form?

Can I use invoice matching with service items and category-based items, as well as stocked items?

What do I do if I get a message about pending invoices not being displayed?

Invoice history and matching details form

Approval journal history and matching details form

Don’t see your question here?

Resource page for Retail for Microsoft Dynamics AX 2012

Resource Page for Troubleshooting Common Office Add-in Issues for Microsoft Dynamics AX 2012

Resource Page for Financials Management in Microsoft Dynamics AX 2012

Provides relevant resources as it relates to understanding the Financials Management application areas in Microsoft Dynamics AX 2012.

On this page:

Top Downloads

Critical Hotfixes

Related Resources

Still having trouble...

Resource Page for CRM Connector in Microsoft Dynamics AX 2012

On this page:

Top Downloads

Critical Hotfixes

Featured Videos

Related Resources

Common Problems & Solutions

Troubleshooting Tips

Still having trouble...

Resource Page for Inventory Costing in Microsoft Dynamics AX 2009

On this page:

Top Downloads

Critical Hotfixes

Featured Videos

Related Resources

Still having trouble...

Resource Page for SSRS and SSAS Integration in Microsoft Dynamics AX 2009

On this page:

Top Downloads

Prerequisites - Installation and Setup

Featured Videos

Related Resources

Common Problems & Solutions

Troubleshooting Tips

Still having trouble...

Acronyms used in this article

Resource Page for Application Object Server in Microsoft Dynamics AX 2009

On this page:

Top Downloads

Critical Hotfixes

Featured Videos

Related Resources

Tools

Common Problems & Solutions

Troubleshooting Tips

Still having trouble...

Acronyms used in this article

Resource Page for Invoice Settlements/Discounts/Reversals in Microsoft Dynamics AX 2009

On this page:

Top Downloads

Featured Videos

Related Resources

Critical Hotfixes

Still having trouble...

Acronyms used in this article

Resource Page for Enterprise Portal and Role Centers in Microsoft Dynamics AX 2009

On this page:

Top Downloads

Critical Hotfixes

Featured Videos

Related Resources

Common Problems & Solutions

Troubleshooting Tips

Still having problems...

Acronyms used in this article

Resource Page for Workflow in Microsoft Dynamics AX 2009

On this page:

Top Downloads