30 September 2014

AX Installation fails because of Windows Update Service

If you get an error during AX EnterprisePortal (EP) installation that looks like the following you should check if the Windows Update Service is up and running. On the Machine where I tried it lately the service was set to disabled :(

2014-09-30 19:19:22Z ******************************************************************************************************
2014-09-30 19:19:22Z Der angegebene Dienst kann nicht gestartet werden. Er ist deaktiviert oder nicht mit aktivierten Geräten verbunden. (Ausnahme von HRESULT: 0x80070422)
2014-09-30 19:19:22Z ******************************************************************************************************
2014-09-30 19:19:22Z ******************************************************************************************************

2014-09-30 19:19:22Z System.Runtime.InteropServices.COMException (0x80070422): Der angegebene Dienst kann nicht gestartet werden. Er ist deaktiviert oder nicht mit aktivierten Geräten verbunden. (Ausnahme von HRESULT: 0x80070422)
2014-09-30 19:19:22Z    bei WUApiLib.UpdateServiceManagerClass.QueryServiceRegistration(String ServiceID)
2014-09-30 19:19:22Z    bei Microsoft.Dynamics.Setup.MuApiWrapper.IsMachineAlredyOptedIntoMU()
2014-09-30 19:19:22Z    bei Microsoft.Dynamics.Setup.Support.SetupQueue.MsiInstallationClass.SearchDownloadInstallMicrosoftUpdates(String executionName)
2014-09-30 19:19:22Z    bei Microsoft.Dynamics.Setup.Support.SetupQueue.ComponentsInstaller.PerformWork()
2014-09-30 19:19:22Z    bei Microsoft.Dynamics.Setup.Support.SetupQueue.InstallationClass.DoWork(Object sender, DoWorkEventArgs e)
2014-09-30 19:19:22Z    bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

2014-09-30 19:19:22Z ******************************************************************************************************
2014-09-30 19:19:23Z S260FinishedInfo

23 September 2014

Microsoft Dynamics AX 2012 R3 Update Experience

Microsoft Dynamics AX 2012 R3 Update Installer provides contextual and metadata driven update experience powered by the cloud. It simplifies discovery of updates and strives to reduce the maintenance cost by providing the ability to stay current with AX updates. This video demonstrates the features and capabilities of the new Microsoft Dynamics AX 2012 R3 Update Installer.

18 September 2014

Intelligent Data Management Framework - you do not have administrative rights

After the installation of IDMF I was frustrated because of the following error message:

You do not have administrative rights to access the Data Management Framework. But what does it mean?
Actually this message is reuslting from a request that is send via business connector to AX to validate if the user that starts IDMF is having the required role within AX. And guess what Microsoft lives in an english world. There is a macro defined in the method DMTValidateAdminUser.validateUser() that searches for the security role "System Administrator".
If your environment is not English you need to replace this with the rolename in your language. In my case for a german environment it is "Systemadministrator"

Installing - Intelligent Data Management Framework - MSDTC

Before you can install the Intelligent Data Management Framework (IDMF) you need to configure the Microsoft Distributed Transaction Co-Ordinator (MSDTC) which is part of the server OS.

  1. run the component Services (run: dcomcnfg) or go to ControlPanel -> AdministrativeTools -> Component Services
  2. Navigate to the Distributed TRansaction Coordinator and right click on the Local DTC select Properties
  3. Navigate to security and check the following checkmarks:

    Network DTC Access Enabled
    Client and Administration  
    Allow Remote Clients Enabled
    Allow Remote Administration Enabled
    Transaction Manager Communication  
    Allow Inbound Enabled
    Allow Outbound Enabled
    No Authentication Required Enabled
  4. Click Okay and yes to let the MS DTC do a restart. After that try to install IDMF again

15 September 2014

Prerequisite check: WSDL URI not accessible (port missing)

When installing the Helpserver on I got the error message from prerequisite check 'Application Object Server (AOS) Services WSDL URI accessible'. - Check failed."Resolution: Attempt to access the WSDL port manually by entering the URI http://[NameOfTheServer]:8101/DynamicsAx/Services/MetadataService. ..."

The problem in my Case was that the AOS 1 was uninstalled and obviously the port (8101) is not accessible. But there is a quick workaround. Just let the check talk to another WSDL port by forwarding the port 8101 to another WSDL port. In my Case 8101 --> 8103.

Therefor just open a command prompt an d enter the following command:

netsh interface portproxy add v4tov4 listenport=8101 listenaddress=[NameOfTheServer] connectport=8103 connectaddress=[NameOfTheServer]

German message:

URI der AOS-Dienste-WSDL zugreifbar

Von dem Computer auf dem Setup ausgeführt wird muss auf den URI der AOS-Dienste-WSDL (Web Services Definition Language) zugegriffen werden können. Beim Setup werden Webdienste zum Kommunizieren mit Microsoft Dynamics AX verwendet, um einen Teil der Konfiguration abzuschließen.

Versuchen Sie, manuell auf den WSDL-Port zuzugreifen, indem Sie den URI http://DEWUE-VS-PLDEV2:8101/DynamicsAx/Services/MetadataService eingeben. Wenn Sie nicht auf den URI zugreifen können und die Firewall aktiviert ist, versuchen Sie gemeinsam mit dem Netzwerkadministrator zu ermitteln, warum der URI auf dem Anwendungsobjektserver (AOS) nicht erreicht werden kann.

Informationen zur Überprüfung der Voraussetzung erhalten Sie durch Klicken auf den Link 'Protokolldatei anzeigen'. Detaillierte Problembehandlungsschritte finden Sie im Problembehandlungsabschnitt des Installationshandbuchs unter http://go.microsoft.com/fwlink/?LinkId=211990.

11 September 2014

SSRS Report Error: Parameter FormLetterRecordId does not exist on this Report

When you see this error "Parameter FormLetterRecordId does not exist on this Report" when trying to open an SSRS Report then you should check the corresponding TMP Tables for the Report. These DataProvider tables are normally temp tables and should not contain data. In my case in the VendInvoiceDocumentTMP where still two records left which created this message. Deleting these records solved the Problem for me ;)