Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We recently discoverred that our production AOS servers are running different versions of AX; 1500.3240 on some, and 1500.2985 on others; so all have RU5, but some have additional hotfixes. The same situation is true of our AX Clients.
I found that you can view a list of installed hotfixes via the SysHotfixManifest class. Sadly exporting this from the AOT and comparing the resultant XPOs from each server showed the same results. That's unsurprising as all AOSes look at files on a common application directory.
Do you know of a way that I can view which hotfixes are installed, including those applied to binaries? Is there anyway to determine this from the build number?
Sadly we don't have the option of applying RU6 & 7 immediately to all servers to bypass the issue as this will require regression testing.
I suspect that copying the binaries between servers would resolve the issue, but that's risky and also I'm not sure which version's correct - i.e. though some servers have a later version I don't know what the hotfix is / what potential impact this could have. Part of the benefit of knowing which hotfixes were missing from some servers is this may help to explain a number of intermittent issues we've been seeing.
Thanks in advance,
Can you please CRM 4.0 Diag tool to colect the installed hotfix information:blogs.msdn.com/.../crmdiagtool4-for-microsoft-crm-4-0-available-now-on-the-emea-dynamics-crm-support-blog.aspx
Sadly that tools seems to be designed for Dynamics CRM; my issue is with Dynamics AX. I've had a play with the tool in case it was compatible with both but I get an "object is not associated with an instance of an object" exception. Is the source code for the app available? I may be able to port it to something that works for AX, or at least glean a little more info about where this information's held?
Have you tried looking in Control panel->Programs & Features-> View installed updates on the AOS servers. There usually is a KB number attached to each individual update you apply to the AOS.
sadly when I go to that screen no updates show; i.e. a progress bar shows up behind the address bar whilst the system searches for updates, but then nothing's returned for any program.
I ended up exporting the SysHotfixManifest to an XPO, then openning this in Excel and using various string functions to strip out a list of the KB numbers.
I then did the same with the data available on the link below to get a list of hotfixes mapped to the rollup / sp in which they're contained and the description of the hotfix.
Finally I did a vlookup from the manifest's kb# to the lists to pull back rollup and description info for what's in our environment, filtered out anything on SP1 / RUs1-5, then was left with just the interesting bits.
Here is another way to get the list of installed KBs in AX 2009:
1. Open Application Object Tree (AOT)
2. Navigate to the class SysHotfixManifest and expand the class
3. Select one of the methods under that class and press Ctrl + A to select all the methods
4. Right-click on the selected methods and click Add-Ins \ Copy \ Name
5. Now all the names of the KBs are copied to the clipboard. You can then paste it in Notepad / Excel to get the names of all the KBs installed in the instance.
6. You need to remove some of the method names that do not begin with KB.
Thanks Siva; good tip for anyone else hitting this issue.
How to do this in ax 2012?
You may want to check out Lifecycle Services for this: lcs.dynamics.com/.../Index
Once configured this can tell you which hotfixes you're missing (as well as providing great info on configuration and custom code issues, and much more besides).
Hope that helps,
Additional Useful Notes:
1) Kernel Updates are cumulative; so if you deploy the latest one, you get everything up to that update.
2) Application Updates should be applied to the SYP layer; using the VAR layer only to correct customised code which is negatively affected by the application patch.
3) Kernel updates are not dependent on application updates; so you can deploy the latest kernel version ahead of any application updates (since kernel updates shouldn't affect business logic they're generally easier/quicker to get in).
4) Application updates are (sometimes) dependent on kernel updates; so you should always ensure that your kernel is at or ahead of the patch level of your application files.
Business Applications communities