Dynamics Folder missing from Event Viewer – Dynamics 365 for Finance

For provisioned Dynamics 365 Development environment in some case you will notice Event Viewer is missing Dynamics folder.

Execute this PowerShell script in your development environment. Make sure you open PowerShell ISE in Administrator mode, then paste the following script and execute:

$AOSSetupETWManifestDir = “k:\AosService\WebRoot\Monitoring”
foreach ($manifestFile in Get-ChildItem -Path $AOSSetupETWManifestDir*.man | select-object -Property BaseName,Name)
{
$dllFile=””
if ((Test-Path “$AOSSetupETWManifestDir\$($manifestFile.BaseName).Instrumentation.dll”))
{
$dllFile = “$AOSSetupETWManifestDir\$($manifestFile.BaseName).Instrumentation.dll”
}
elseif ((Test-Path “$AOSSetupETWManifestDir\$($manifestFile.BaseName)Resource.dll”))
{
$dllFile = “$AOSSetupETWManifestDir\$($manifestFile.BaseName)Resource.dll”
}
elseif ((Test-Path “$AOSSetupETWManifestDir\$($manifestFile.BaseName).dll”))
{
$dllFile = “$AOSSetupETWManifestDir\$($manifestFile.BaseName).dll”
}
else
{
Write-Host “Warn : Skipping $AOSSetupETWManifestDir\$($manifestFile.Name) as DLL not found”
Continue
}
Write-Host “Installing $AOSSetupETWManifestDir\$($manifestFile.Name) using $dllFile”
wevtutil.exe im “$AOSSetupETWManifestDir\$($manifestFile.Name)” /rf:”$dllFile” /mf:”$dllFile”
Write-Host “Finished installing $AOSSetupETWManifestDir\$($manifestFile.Name) nn”
}

Close are reopen the event viewer and we can see the Dynamics folder

Ref: https://azd365.com/2022/08/10/dynamics-folder-is-missing-from-event-viewer-after-provisioning-dynamics-365-for-finance-scm-version-10-0-29/

How to clear visual studio cache

During development you would face situations where project references are not loaded properly or you get missing/error DLL’s. This is because the Component cache gets corrupted randomly and without any warnings.

As a quick step we need to clear component cache and restart Visual Studio since the Cache might be holding onto previous DLL versions.

Steps on how to clear Visual Studio Cache:

Clearing Component Cache:

• Close all Visual Studio Instances running in your machine. Also, make sure devenv.exe is not running in the Task Manager
• Delete the Component cache directory -%USERPROFILE%\AppData\Local\Microsoft\VisualStudio\1x.0\ComponentModelCache
• Restart Visual Studio

The above steps should fix the cache issue most of the times, but sometimes that is not enough, and you need to perform the below steps as well.

Clearing User’s Temp Folder:

• Open the temp folder in this location – %USERPROFILE%\AppData\Local\Temp
• Delete all the files in the temp folder

If both of the above-listed steps don’t work there is a final option(hard-route option) that you could try to clear cache in Visual Studio.

Delete the files from these locations

• %USERPROFILE%\AppData\Local\Microsoft\Team Foundation
• %USERPROFILE%\AppData\Local\Microsoft\VisualStudio
• %USERPROFILE%\AppData\Local\Microsoft\VSCommon

Run the below command after deleting the files from the above folders,

C:\Program Files (x86)\Microsoft Visual Studio 1x.0>devenv /resetuserdata

This command will reset the user information in VS. Please make sure you export your settings under Tools -> Options before running this command

Authenticate to Visual Studio if required.

Uninstalling package in D365 Finance and Operation

1. Create a file that is named ModuleToRemove.txt.

2. In the file, put the name of each module (Ex: TestModel) that you want to remove on a separate line. Make sure that you’ve completed the prerequisites for each module that you’re removing.

Prerequisites

• If any models reference the module that will be removed, the references must be removed from them. For information about how to find the references that must be removed, see Viewing model dependencies.
• Build and deploy any modules that references were removed from.
• All references to and from the modules must be removed before you begin to uninstall the module. To remove all a module’s references, add a single class to the model. This class should contain no code. It should contain only a reference to the application platform.

3. Create a valid deployable package, and put the ModuleToRemove.txt file in the  package\AOSService\Scripts folder.

4. Install the deployable package to uninstall the required package.

5. Verify that the package was uninstalled before you complete this procedure in Sandbox or Production environment.

Delete model in D365 Finance and Operation

ModelUtil.exe can be used for the purpose of removing or deleting a model. It is command prompt utility.
Details here about the usage. At command prompt:

1. Browse to: K:\AOSService\PackagesLocalDirectory\bin folder.
2. Type in ModelUtil.exe /? to get to know about parameters.
3. Custom model name was “Test_Model”.
4. Remove it using following command:

K:\AOSService\PackagesLocalDirectory\Bin>ModelUtil.exe -delete -metadatastorepath=”K:\AOSService\PackagesLocalDirectory” -modelname=”Test_Model”

Are you sure you want to delete model Test_Model? (Y/N) y

K:\AOSService\PackagesLocalDirectory\Bin>

Dynamics 365 F&O/ Workflow Error

Error message is displaying while opening the workflow engine 

“An error occurred while the HTTP request. This could be due to the fact that the server certificate is not configured properly with HTTP.sys in the https case. this could also be caused by the mismatch of the security binding between the client and the server”

Run in PowerShell as Administrator and run the following command on your local client machine:

Set-ItemProperty HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 -Name SchUseStrongCrypto -Value 1 -Type dword -Force -Confirm:$false

if ((Test-Path HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319))

{ Set-ItemProperty HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 -Name SchUseStrongCrypto -Value 1 -Type dword -Force -Confirm:$false}

Ref: https://community.dynamics.com/365/financeandoperations/f/dynamics-365-for-finance-and-operations-forum/370625/dynamics-365-f-o-workflow-error

Access Dynamics AX (aka ‘7’) performance counters with “&debug=develop”.

The new Dynamics AX have some very powerful capabilities to show exactly where time is spent. You would like to explore more about what is happening behind the scene, try adding the “&debug=develop” to the URL. This will bring up a small timer that shows how much time was spent on opening and showing the current form.

If you click on it, it will give more performance details. Like if I open the all customers in the Contoso form, my system gives me the following.

I see here that the loading the customers took 366 ms, where 131 ms was from the AOS loading the data. You also see a color coding (green/blue) that indicates at what sequence the time was spent.

There is also a section to show what the server is doing, and it also shows you the exact SQL call that was the longest running SQL statement.

At the bottom of the performance screen we can also see something interesting;

Ref: https://kurthatlevik.wordpress.com/2016/02/03/access-dynamics-ax-aka-7-performance-counters-with-debugdevelop/#comment-2779

AX7 – Cloud estimation sheet

When working with new clients, I just love to show Life Cycle Services, and all the new tools and gadgets now available to us. Prices on licenses and Azure services are beginning to come into light, but there is one “unknown” factor. How much would it cost to in time to setup and implement all the tools and services?

 

 

 

 

 

 

 

 

I will not
give you the estimates, but I can give you the sequenced task list of what to do

Area	Sub Area	Task
Life Cycle Services	Installation	Create LCS Site
Life Cycle Services	Installation	Add Users to LCS
Office 365	Installation	Create Office 365 Azure AD
Office 365	Installation	Create SharePoint Site
Visual Studio Online	Installation	Create VSO Site
Visual Studio Online	Installation	Add users to VSO
Customer source	Installation	Add users to Customer Source
Azure	Installation	Create Azure Account
Azure	Installation	Setup Administrators to Azure
Azure	Installation	Connect Azure subscription to CSP account
LCS	Setup	Create LCS Project
LCS	Setup	Connect Azure, VSO and SharePoint to LCS
LCS	Setup	Invite project users into LCS
LCS	Setup	Select and setup methodology in LCS
LCS	Setup	Infrastructure estimation tool in LCS
LCS	Setup	License sizing estimation tool in LCS
LCS	Deploy	Deploy Demo/CRP based on Contoso
LCS	Deploy	Deploy Development environments (per developer)
LCS	Deploy	Deploy VSO Build/Staging environment (One VM)
LCS	Deploy	Deploy Acceptance Test environments (2-3 VM’s)
LCS	Deploy	Deploy Production Environments (3-10 VM’s)
LCS	Monitor	Setup LCS System Diagnostics
Visual Studio Online	Setup	Setup VSO Projects and users rights
Visual Studio Online	Setup	Setup Process for nightly builds and automated test
Visual Studio Online	Setup	Define product backlog
Visual Studio Online	Setup	Define sprints
Office 365	Setup	Setup Microsoft Power BI
LCS	Setup	Setup Configuration manger (Data Transfer)
Office 365 / LCS	Setup	Add ODM templates to be used in the project
AX 7	Setup	Setup Data Entities for ODATA/Integrations
AX 7	Setup	Basic parameters and generic setup

Ref: https://community.dynamics.com/ax/b/kurthatlevik/archive/2016/02/10/ax7-cloud-estimation-sheet

AX RTW – Hack to enable configuration mode

When downloading the AX RTW local VM from connect, you often want to disable some configuration keys. (Like catch weight etc). But now you will see the following warning;

“This form is read-only unless the system is in the maintenance mode. Maintenance mode can be enabled in this environment by running maintenance job from LCS, or using Deployment.Setup tool locally”

This warning is to prevent that configurations are enables/disabled, and that the system is set in maintenance mode. There are 2 ways of dealing with this.

1. The proper way; Use the Microsoft.Dynamics.AX.Deployment.Setup.exe command; (Credits to Joris de Gruter)
   Run this from command line:

   c:\packages\bin\Microsoft.Dynamics.AX.Deployment.Setup.exe –metadatadir c:\packages –bindir c:\packages –sqlserver . –sqldatabase axdbrain –sqluser AOSUser –sqlpwd AOSWebSite@123 –setupmode maintenancemode –isinmaintenancemode true

   and then run the command with “false” at the end to turn if back off.

2. The Hack way; Use the Microsoft SQL Server Management Studio, and edit the following record in the table dbo.SQLSystemvariables ; CONFIGURATIONMODE
   

After that, you can change configurations. But make sure you never
EVER do this in a production environment!

Ref: https://community.dynamics.com/ax/b/kurthatlevik/archive/2016/03/02/ax-rtw-hack-to-enable-configuration-mode

Document Conversions Launcher issues on SharePoint 2013 SP1 with APP on WFE

Error: Not launching Document Conversions Launcher because registry key acknowledging service running on app server (‘AcknowledgedRunningOnAppServer’) is not set.

Solution: The new key is called “AcknowledgedRunningOnAppServer” and is of the DWORDtype. It must be set to 1 to enable the services to start. The paths on which the key must be set are as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15\LauncherSettings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15\LoadBalancerSettingsSource

Source: http://support.microsoft.com/kb/2910363/en

Exception from HRESULT: 0xC0048021 in DMF AX 2012 R3

If you’re using Excel 2013 , the problem is caused by DMConfig XML file.

Go to the DMConfig.xml file in the Microsoft Dynamics AX\60\DataImportExportFramework  folder and replace the PipelineComponentInfo_Multicast, PipelineComponentInfo_ExcelSource and  <PipelineComponentInfo_ExcelDestination> nodes by the following:

<PipelineComponentInfo_Multicast>
{33D831DE-5DCF-48F0-B431-4D327B9E785D}
< /PipelineComponentInfo_Multicast>
< PipelineComponentInfo_ExcelSource>
{9F5C585F-2F02-4622-B273-F75D52419D4A}
< /PipelineComponentInfo_ExcelSource>
< PipelineComponentInfo_ExcelDestination>
{90E2E609-1207-4CB0-A8CE-CC7B8CFE2510}
< /PipelineComponentInfo_ExcelDestination>

Ref: Dynamicesuser.net