AX2012 R2 Retail: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

5 Sep

The scenario is that POS pc and Store database pc is joined to domain however they are on a remote location and without VPN access it cannot resolve Active directory user and FQDN. Instead domain account we used local pc account to perform all actions on SQL and connect Retail POS through the same local user.
One thing is to remember we had different accounts logon for POS and Store database pc, e.g. POSPC and StorePC.

After all setups for POS when I started AX 2012 R2 Retail POS it stopped working, event viewer showed following error:

“Login failed. The login is from an untrusted domain and cannot be used with Windows authentication”

In order to resolve this error make sure the these:
1. Username on POS and Store database Pc must be SAME.
2. Password for both users must be SAME.

This user will authenticate POS user on Store database PC to connect to SQL database.


Error while deploying Analysis services Cubes – Dynamics AX

28 Nov



OLE DB error: OLE DB or ODBC error: Login failed for user domain\username; 28000; Cannot open database "Ax2012Contoso" requested by the login. The login failed.; 42000.

Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘Dynamics Database’, Name of ‘Dynamics Database’.


Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘LEDGERDERIVEDFINATTRVALUECOMBINATIONS’, Name of ‘Ledger derived financial attribute value combinations’ was being processed.



Errors in the OLAP storage engine: An error occurred while the ‘Derived financial hierarchy attribute value combination’ attribute of the ‘Ledger derived financial attribute value combinations’ dimension from the ‘Dynamics AX initial’ database was being processed.


Internal error: The operation terminated unsuccessfully.

Server: The operation has been cancelled.


If this kind of error appeared while Deploying Analysis project from Analysis services project wizard, follow these steps to resolve it.

By default the "service account" will be used when processing.

In case error still appears, change the impersonation to Administrator account, in our case we grant all administrative rights to bcproxy account.

If you get an error like the one below when you execute the first dimension of your cube, it is because the user that runs the SQL Server Analysis Services service does not have sufficient rights to access the data warehouse, which it needs to process the cubes.

To resolve this you have to give at least db_datareader to the user that the Analysis Services Service is running as on the data warehouse.

To find out which user this is:

– Start -> Run -> Services.msc

– Locate the service with the display name: SQL Server Analysis Services (…)

– Locate the username in the Log on as column, this is the username that needs permissions on the data warehouse.

How to add the user rights to the data warehouse:

· Open SQL Server Management Studio.

· Expand the Security node, Expand Logins, if the username from the error message above exists in the list, right click and Properties. Otherwise right click Logins, "New Login…" and type in the correct Login Name:

· On the "User Mapping" tab check the data warehouse Map checkbox and select db_datareader for it.

· Click OK

This will add sufficient rights.

Blog by:
Wasiq Manzoor

Microsoft Delivers Additional Project Execution Functionality in Dynamics AX 2012 R2 CU7

28 Nov

Microsoft has recently made available the CU7 release of their Microsoft Dynamics AX 2012 R2 ERP system.  As a provider of Microsoft Dynamics AX ERP solutions to the professional services industry, we’ve been anxiously awaiting the CU7 release due to the addition of some significant enhancements to the Project Management & Accounting functionality in Dynamics AX.  This blog will be the first of a series of blogs that will explore new functionality introduced in Dynamics AX 2012 R2 CU7.

One of the major enhancements in the CU7 release is the addition of a true Work Breakdown Structure or WBS within Dynamics AX.  In prior versions of Dynamics AX, the WBS was simply a tool for building a list of tasks or activities within the project.  These tasks were mostly used for project accounting-related functions such as defining the level of detail for project budgeting and time entry.  There was very limited project execution functionality within the WBS.

In Dynamics AX 2012 R2 CU7, Dynamics AX now has a true Microsoft Project-style WBS as shown in the screenshot below.

Work Breakdown Structure in Dynamics AX 2012 R2 CU7

This WBS allows for improved management of project tasks within a traditional WBS grid view, similar to what you’d see in Microsoft Project.  Some of the features of the new WBS include:

  • The ability to use WBS or task templates to create a new WBS
  • Support for predecessors and successors
  • Automatic scheduling assistance
  • Automatic creation of estimates and forecasts at WBS granularity
  • Multiple views of the WBS:
    • Planning View – build up project structure, timeframes, dependencies, etc.
    • Effort Tracking View – WBS in the context of hours (original, to completion, etc.)
    • Cost Tracking View – WBS in the context of costs (original, to completion, etc.)
    • Revenue Tracking View – WBS in the context of revenue (original, to completion, etc.)
    • Visual status indicators to highlight variances
    • Ability to open the WBS and/or manage the WBS in the Microsoft Project client

These new WBS features will help project managers that want to use Dynamics AX as more of a true project execution system, in addition to a project management and accounting tool.

As part of the release of CU7, Microsoft has also confirmed a couple of roadmap related items.  The next interim release of Dynamics AX (AX 2012 R3) will be released by April of next year, followed by the next major release of Dynamics AX (AX 2015) in Q4 of 2014.  So Microsoft continues to make significant R&D investments into Dynamics AX, which will position it well for the future.

In the meantime, we’re excited about these enhancements to the CU7 release.  Watch for additional blog articles in our series about the new features that are available in CU7.


Blog By:
Wasiq Manzoor

Microsoft Releases Dynamics Lifecycle Services Tools for Dynamics AX

26 Nov

As a Microsoft Dynamics AX partner specializing in implementing the Dynamics AX ERP system for Professional Services firms, we’re always on the lookout for tools and methods that will help us provide our consulting and technical services in an efficient and cost-effective manner.  Microsoft shares this aspiration for its channel partners, and in an effort to provide its partners and customers with a series of tools to help implement and manage their Dynamics AX system, has released Dynamics Lifecycle Services.

Dynamics Lifecycle Services is a set of new cloud-based tools that allow customers and partners to better manage Dynamics AX projects all the way from the pre-sales stage through to implementation and ongoing operations.  Here’s a quick diagram that depicts the various tools in Dynamics Lifecycle Services and which stage of the ERP lifecycle that it applies to.


Dynamics Lifecycle Services is made available through the Windows Azure cloud platform.   You can set up a "Project" for each customer or implementation, and then based on the phase of the project and the vertical that the customer is in, Lifecycle Services will provide you with a series of checklists and tools that you can use to manage the project.  It also provides a project dashboard that consolidates access to this information.   Here’s an example of a project dashboard in Dynamics Lifecycle Services:


Here’s a quick run-down of the tools that are available in the initial release of Dynamics Lifecycle Services.  

  • Collaboration Workspaces – One feature is the collaboration workspaces, which allow you to set up secure, web-based customer-managed collaboration workspaces for your projects.  You can then manage your projects in these workspaces using either Microsoft SureStep or other implementation methodologies. 
  • Business Process Modeler – The Business Process Modeler is a great new tool for creating cross-functional business process flowcharts based on the metadata in Dynamics AX.  You can easily map business process and perform a gap/fit analysis using this tool, as well as quickly generate business process documentation and flowcharts using the new Advanced Task Recorder.  Here’s a screenshot of the BPM tool:


  • Code & Upgrade Analysis Tool – A new code and upgrade analysis tool leverages a cloud-based rules engine to analyze your code and identify potential best practices, performance, and upgradeability issues.  This will then generate reports that can be imported into the MorphX development toolset as a to-do list for developers. 
  • Usage Profiler – The usage profiler helps you model user and batch processing loads as a starting point for sizing your servers and other infrastructure requirements. 
  • Diagnostics Tool – A new diagnostic tool helps monitor the heal of your AX systems, collecting data from your AX environments and comparing that data against some pre-defined rules to provide you with a list of corrective actions that you can take. 
  • Issue Search – The issue search is a repository of system issues that have been reported, are in-progress, and have been fixed.  It also identifies specific code objects and lines of code that might be affected by a hotfix.   

In order to visit Microsoft Dynamics Lifecycle Services, visit this link:

Overview Videos

You can watch the Overview of Microsoft Dynamics Lifecycle services here:

  • Business Process Modeler

Helps you describe your organization’s business processes based on industry-standard business process definitions (APQC) and supports to identify gap/fit.

  • Usage Profiler

Provides insights into your planned usage scenarios, and is a basis for hardware sizing and/or performance support.

  • License Sizing Estimator

Provide IT/procurement with a tool to determine the mix of client access licenses (CAL) for your organization

  • Customization Analysis

Optimize your customizations to improve system performance and reliability.

  • System Diagnostic

Pro-actively monitor the health of your Microsoft Dynamics AX installation to minimize system downtime

  • Upgrade Analysis

Prepare for your code and data upgrade from Microsoft Dynamics AX 4.0 and 2009



Blog by:
Wasiq Manzoor

AOS service issue while Upgrading to Windows 8.1

7 Nov

If you are planning to upgrade Windows 8 to Windows 8.1, do consider following point otherwise Dynamics AX AOS service won’t start on your machine.

How to make AX Server work after Upgrading to Windows 8.1.

Recently I have updated my Windows 8 to Windows 8.1. Everything seemed to be ok, until I realized that I cannot start neither of my AOS (AX 4.0, AX 2009 and AX 2012)

Service is still in place. If you tried to start e.g. AX 2012 AOS you would encounter the following errors:
Object Server 01: Error accessing registry: Cannot open key SYSTEM\CurrentControlSet\Services\Dynamics Server\6.01.

Object Server 01: The directory "C:\WINDOWS\system32\\bin" does not exist or access to it has been denied by the operating system.

Object Server 01: The home directory for Axapta (C:\WINDOWS\system32\) does not match the required structure or cannot be accessed. Please check installation, configuration and access rights.

If you tried to open AX Server Configuration Utility you would see it completely empty:


The problem is that registry keys located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\ were deleted during the update.


Proactive solution

If you have not updated yet when the best solution would be to export that node and import after update.


Note: Provided solution works for AX 2012 R2 CU6 version.

But if you have already updated and facing this issue then you have the following options:

· Recreate keys manually;

· Import from your colleague;

· Create the reg file yourself by copying and pasting the contents below.

AOS uninstall or repair won’t work for this.

For your convenience below is the exported AX 2012 CU6 registry keys for Original (installed configuration). Copy the text to notepad, save as reg file and import using regedit.

Do not forget to change the flowing info before importing:

  1. AOS instance name
  2. DB Server Name
  3. DB Name
  4. Ports (TCP/IP, WSDL and netTCP) defaults 2712, 8101, 8201.
  5. User running the AOS service.
  6. Configuration name (optional)

Restart your computer after importing (otherwise you won’t see changes in AX Server Configuration Utility.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.0]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.01]
"Current"="Original (installed configuration)"
"AOSPath"="C:\\Program Files\\Microsoft Dynamics AX\\60\\Server\\AX2012AOSNAME\\Bin\\Ax32Serv.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.01\Original (installed configuration)]
"bindir"="C:\\Program Files\\Microsoft Dynamics AX\\60\\Server\\AX2012AOSNAME\\Bin\\"
"directory"="C:\\Program Files\\Microsoft Dynamics AX\\60\\Server\\AX2012AOSNAME\\bin\\Application"
"logdir"="C:\\Program Files\\Microsoft Dynamics AX\\60\\Server\\AX2012AOSNAME\\Log"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.01\Original (installed configuration)\SetupProperties]
"AOSAPPLICATIONPATH"="C:\\Program Files\\Microsoft Dynamics AX\\60\\Server\\AX2012AOSNAME\\bin\\Application"
"AOS_LOC_DESC"="Executes application logic and manages data access for Microsoft Dynamics® AX 2012"

Hope it works for you.

System Center Monitoring Pack for Dynamics AX 2012

12 Sep

Hi guys, this is my first article in a Blog  and I am here to write about the Microsoft SCOM (System Center Operations Manager) Monitoring pack for Microsoft Dynamics AX 2012.

Below link get you to the downloading page that contains the Guide for using Monitoring pack and its installation file.