Cumulative Update 2 for Microsoft Dynamics NAV 2015 has been released


Cumulative Update 2 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015. 

 The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

  •   AU – Australia
  •   AT – Austria
  •   BE – Belgium
  •   CH – Switzerland
  •   DE – Germany
  •   DK – Denmark
  •   ES – Spain
  •   FI  – Finland
  •   FR – France
  •   IS – Iceland
  •   IT – Italy
  •   NA – North America
  •   NL – Netherlands
  •   NO – Norway
  •   NZ – New Zealand
  •   RU – Russia
  •   SE – Sweden
  •   UK – United Kingdom

Where to find Cumulative Update 2

You can download the cumulative update from KB 3020885  – Cumulative Update 2 for Microsoft Dynamics NAV 2015 (Build 38798). 

Additional Information

For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2015 Cumulative Update

For information about how to work around a recent process change, see How to Get Back the ‘Hotfix Directories’ from NAV 2015 Cumulative Update 1.

For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2015.  

Comments (16)

  1. Pallea says:

    @Martin

    Back on the NAV 2015 – Update 1 thread (blogs.msdn.com/…/10569714.aspx) you talked about the naming of the DVD-images. Unfortunately this has NOT improved.

    I have just downloaded NAV 2015 Update 2

    The – W1 image is called W1DVD.ZIP and the Danish one is calle: Dynamics.80.DK.1585809.DVD.zip

    You did mention that the naming was supposed to be:

    [Product Group].[Version].[Country].[Build Number].DVD.zip – but it aint.

    It might seem crazy that I and others are annoying you guys with this. But we have to rename our downloads every single month in order keep track of the files.

    Thanks

    Palle

  2. Austria is listed here, but the Austrian download link is missing in the KB article.

  3. Martin Nielander says:

    @Palle; we did hear you and we have a change ready in our build system to align these file names across product versions and local versions. Timing was unfortunately not in favor for us to make it for this round of CU releases. In the next CU round you will see file names across product versions and local versions aligned.

    So in the future you can expect it to be like:

    NAV.<Product>.<BuildNo>.<Country>.DVD.zip

    Examples:

    NAV.8.0.30000.W1.DVD.zip

    NAV.8.0.30000.W1.ChangeLog.txt

    NAV.8.0.30000.W1.AccumulatedChangeLog.txt

    NAV.8.0.30000.W1.CUObjects.txt

    NAV.8.0.30000.W1.CUObjects.fob

    Above file naming will also be aligned in 7.0 and 7.1 versions of Microsoft Dynamics NAV.

    Hope this will help you when we get there.

    Best regards Martin

  4. Martin Nielander says:

    @Kai, it is on the way. The server is currently having a hard time to make the file public.

  5. Jens Glathe says:

    Hi there,

    a little warning – apparently the W1 demo database of the CU2 hotfix download is a strange mixture of W17.10 objects (date is also this of 2013 R2, 23.09.13) that previously were W18.00, 09.09.14, and the CU2 changes. This is not the case for the DE variant of the hotfix download. It appears better to use the new W1 objects and load them into a CU1 demo database.

    Also, using the directories of the install DVD to copy them over your installation replaces the config file of the NST with a default version that needs to be edited. One one hand it is good to have the new config file with all available settings, on the other hand you need to pay attention not to loose your previous settings.

    with best regards

    Jens

  6. Allan Bangsbro says:

    @Martin

    Why don´t you include the Cumulative Update No. in the string as well? The Build No. itself does not hold much information when you want to be able to find or specify a certain Cumulative Update. Or can you tell me the Cumulative Update No. of NAV 2013 Build No. 36605 without looking it up somewhere?

    Suggestion:

    NAV.<Product>.<BuildNo>.<CumulativeUpdateNo>.<Country>.DVD.zip

    Example:

    NAV.8.0.39012.3.DVD.zip

    In addition, another request: Could you please rename the demo database? The demo database bak-file is called "Demo Database NAV (8-0)", and this bak-filename is identical for all three present versions of NAV 2015. However, the bak-files are NOT identical as they hold different Builds/Cumulative Updates, so I don´t think that the bak-filenames should be identical either.

    This of course also applies to the SQL Server database name, logical filenames and physical filenames. Those should also not be identical for different Builds/Cumulative Updates.

    The naming "Demo Database NAV (8-0) also seems like it is aligned with no other naming conventions in NAV. Where does the "-" in "8-0" come from? Why not just "80" as in for example the default Server Instance (DynamicsNAV80), the name of the folder containing the Service (80) or the name of the folder containing the RoleTailored Client (80)?

    For the three present versions of NAV 201 I would suggest:

    DynamicsNAV80Demo.37874

    DynamicsNAV80Demo.38457.1

    DynamicsNAV80Demo.38798.2

    for:

    bak-filename

    database name

    logical names

    physical filenames

    I would very much appreciate this, as this would save me the time I use renaming these names every time an update is released.

  7. Martin Nielander says:

    @Allan, I am not sure if you are aware but each CU has an overview where you can see which build numbers we released and what countries the CU is released for. See this one for NAV 2015: mbs2.microsoft.com/…/kbdisplay.aspx. Each version of NAV, where we have release a CU, has a kb like this one.

    I will need to look a little further into renaming of the demo database.

  8. Martin Nielander says:

    @Jens, I am not sure if you are aware but did you see the blog post referenced in Additional Information of this blog post?

    For information about how to work around a recent process change, see How to Get Back the 'Hotfix Directories' from NAV 2015 Cumulative Update 1.

  9. Jens Glathe says:

    Hi there,

    @Martin: How about a simple "Update" button in the installer? Wich does exactly this: update all installed NAV components of the right major release on this machine? I've seen the blog post about restoring the old directories. Did you read the latest comments on it? Same issue. 🙂

    with best regards

    Jens

  10. Martin Nielander says:

    @Jens, yes configuration files is a bit of a grey zone. Typically you wouldn't include them when patching, but in some situations patching can be needed and then you will have to consider how to do that for customers with individual configurations. I guess this is common for most software products with options for individual configurations.

    In regards to your suggestion about an "Update Button" then this is not possible with the current design of the NAV installer. I believe this has been discussed before.

  11. Martin Nielander says:

    @Jens version numbers are correct in the W1 version of CU 2. Unfortunately they where wrong for quite a number of objects in the W1 version of CU 1 and that has been fixed for CU 2.

    All local versions have correct version lists in both CU 1 and CU 2.

  12. bangsbro@hotmail.com says:

    @Martin

    We have a whiteboard here at the office with lots of Build No.´s and Cumulative Update No.´s! We don´t want to consult a KB article every time we for example discuss an upgrade for a customer and need the correct reference to a Cumulative Update No. I work with Cumulative Update No.´s. If I ask an ISV Partner about their update plans, they could for example tell me that they plan to release a version of their solution for NAV 2015 Cumulative Update 4. The Build No. is irrelevant – even if I knew it.

    When I download the Cumulative Updates, I rename the folders so that both Build No. and Cumulative Update No. is included. Why? Because I need to be able to tell them apart. And the inclusion of just the Build No. will not help me when I need to know which Cumulative Update No. the build applies to.

    If you are planning to change the filenames to include the Build No. please also include the Cumulative Update No. I can´t see any downside to this addition.

  13. Jens Glathe says:

    @Martin

    …? I have installed the demo database .bak from the CU2 W1 download. The objects from it checked into source control are over 900 files changed against CU1 W1. The changes in DE are 120 or so objects plus a few new ones – minus the tables in the 2000000000 range from a new database. So, you're saying that around 800 objects have a wrong versioning since 2015 RTM? Why arent't they in the application folder, then? And, are they wrong in the localized versions, too?

    with best regards

    Jens

  14. @Martin

    1. The download link for Austria is still missing.

    2. I would welcome an explicit naming for the DVD,backup files etc. as Allan has suggested too. All the renaming and comparing which has to be carried out in several places just to tell all these files and folders apart in the long run is time-consuming and error-prone.  

  15. Poul says:

    When is a Polish version expected to be available?

  16. Concerning Polish version - contact local dealer says:

    Hi,

    Microsoft is not from what I know making a polish version.

    We are getting our polish version from IT.Integro in Poland.

    And are eagerly waiting for the version 2015 to be localized. It should happen during january 2015..

    Best regards,

    Henrik Frederiksen

    hf@ibf.dk

Skip to main content