Update Rollup 5 for Microsoft Dynamics NAV 2013 R2 has been released


Update rollup 5 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2.

With update rollup 5, local hotfixes for additional countries have been added, and update rollups for Microsoft Dynamics NAV 2013 R2 now include hotfixes that apply to all countries and hotfixes specific to the following local versions:

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

 

Where to find update rollup 5

You can download update rollup 5 from KB 2937999 – Update Rollup 5 for Microsoft Dynamics NAV 2013 R2 (Build 36281). Note: Implementing this update rollup will require a database conversion.

The hotfixes that have been released since update rollup 4 are listed in KB 2937999. For a full list of all hotfixes included in update rollups for Microsoft Dynamics NAV 2013 R2, see the following CustomerSource and PartnerSource pages: 

CustomerSource:

PartnerSource

 

More Information

For more information about update rollups for Microsoft Dynamics NAV 2013 R2, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

Comments (27)

  1. nutcracker says:

    I wish that you will add China into NAV in future

  2. Quick1034 says:

    I have looked up the KB article. I could not find Belgium.

  3. Sebastiaan Lubbers says:

    @Quick1034 it is there only most countries are given the English label. Look for BEKB2937999.

    Also it is not UK but GB.

  4. Arndt Loermann says:

    The Build from Rollup 5 is the same as the privat hotfix delivered 2 weeks ago.  the privat hotfix has the error of

    "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state" error message when you import or compile a table".

    our binary check says that the fin.sql is the same, but here: mbs2.microsoft.com/…/KBDisplay.aspx

    MS told us that the error was fixed .

    What is right , what is wrong?

  5. Frustrated says:

    Totally agree with Arndt Loermann. What is this?

    I honestly can not believe you have released this Rollup which is a total disaster, since it has the same Build 7.1.36281 as the Hotfix released a week or so ago. This Build has a major Platform issue: "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state" error message when you import or compile a table". We were waiting specifically for this Rollup hoping this error will be fixed. Who cares about application updates when platform is not functioning any longer?

    How should we now explain it to customers? They are not even able to import objects into their databases unless 'Prevent data loss from table changes' setting is manipulated! With every Rollup it is getting worse and worse. I do not want to know what comes with the next one.

  6. Mad Customer says:

    Hi Microsoft,

    what is wrong with you?

    Please start to test your software before you start to release a RTM or a UpdateRelease.

    Dynamics NAV was never so buggy than it is know.

    kind Regards,

    Mad Customer

  7. Arend-Jan Kauffmann says:

    The hotfix that was released on March 20, and this Rollup Package 5 indeed contain the same platform files and has the same buildnumber.

    But the description of the hotfix itself says that it includes the solution for mentioned problem with ServiceChannel. So how can one say that the hotfix contains (or introduces) the problem that it is trying to solve?

    Besides that, I can confirm that RU5 does not contain the problem with ServiceChannel anymore. I was able to upgrade without any problem.

    Tip: Before you start importing your objects, first update the clients and service tier and open the Windows Client once. After that you can import the objects without manipulating the setting for preventing dataloss.

    Thanks,

    Arend-Jan Kauffmann | Dynamics NAV MVP

  8. Confused says:

    Can somebody give an honest answer regarding the issue at hand: Does rollup 5 address the ServiceChannel bug?  If yes, how come the build # did not change?  To the naked eye, having the same build number means what is in the hotfix file = rollup 5 files…

  9. glathe@gmx.de says:

    Hi,

    I can understand that all partners and customers are a bit nervous. Now, it's not only me who's bitching about the major cockup that is the RTC and the underlying design. We're at a new all-time low in product quality and (worse!) fitness for real-world business.

    I have been a NAV developer for more than 15 years (started doing things in NAV in 1995). In that time there have been highs and lows in product quality and two major product generation changes. The first one – moving from text-based to classic client – was a huge step, and it took some releases until it was working nicely. However, it was more or less stable, performance was good (for the time). Even the first Navision Attain (3.01) was somehow fit for business use. The second generation change – introducing the service tier and RTC – was (mostly) a major step in the wrong direction. The service tier itself – why not. It gives us web services, which are a really good technology for interfacing with other systems. The RTC on the other hand is a train wreck of an application, now even worsened with the ribbon (now you can't find anything anymore) and tiles (screen real estate? what's that?). And, to complete it, you can be sure that it doesn't work as expected from rollup to rollup. Performace-wise, it is S-L-O-W in the real world. Reports are a complete disaster. The tooling to set up a new installation is shot. This sounds like a major problem to me. It is a real business risk to buy NAV now, and even more to sell it.

    What to do now? How about slowing down on the rapid changes to the whole product, and working out the biggest messes before the next rollup update? I honestly don't believe that anybody serious is using NAV2013R2 in production. As for this build number/fix chaos – better communication would help. It was to be expected that every developer who is following the issues with 2013R2 would become skeptical when a build number with a known problem shows up as the next rollup update. I haven't applied it either, because I've read about the issues it has caused. This might be unfounded, but then it's a matter of communication to give the partners a handle on why the build number hasn't changed, what was the cause for the problem and why we should be confident to use it.

    @Microsoft: Please try harder.

    with best regards

    Jens Glathe

  10. spriess says:

    Hotfix 2934572, build 36310 which solves “The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communications because it is the Faulted state” error message when you compile an object in a development environment that is on a different machine than the NAV Server will be released later today. When KB 2934572 has been published you can find the article at this link: mbs.microsoft.com/…/KBDisplay.aspx. Until the article is available, you can download build 36310 from this link: support.microsoft.com/…/KBHotfix.aspx.

  11. Torben Siggaard (Microsoft) says:

    The Rollup 5 (KB2937999) and the Platform hotfix (KB2934571) share the same build number because the binaries are identical. A platform hotfix only contains that binaries needed to fix a given set of issues. A Rollup on the other hand contains the full product with the cumulative set of all application and platform hotfixes. In this specific situation, Rollup 5 is based on the latest available platform available, in this situation binaries identical to KB2934571.

    So why is the rollup released later than the hotfix? Since the rollup is a full product and we strive to deliver the highest level of quality possible, we have decided to apply additional testing and validation before we release, hence the short delay.

    Please note that as of next month we will rename the rollups to "Cumulative Update #" to align with overall Dynamics naming.

    With regards to the "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communications because it is the Faulted state" the short version of the story is that we unfortunately introduced a regression as part of one of the other fixes in KB2934571. This is of cause very unfortunate and, as Susanne already wrote, we have already released a new platform hotfix (KB2934572) that will address the issue.

  12. Rushabh says:

    Even after applying build 36310 (KB2934572), SeriveChannel issue (Faulted State) still exist. I tried first rollup 5 and then build 36310 but still error is thrown when trying to compile table or importing table object. This is on development server for upgrade of client database.

    I tried to replace NST-Service, RTC-Role Tailored Client and Web client folder files. Do I need to do anything else?

    Thanks.

  13. Marc Breuer says:

    The unsynched SQL index error is also not fixed with build 36310 (KB2934572)!

  14. Saurav Dhyani says:

    Hi Team,

    After applying the Rollup 5, the Database is Slow and i am getting Record Locked By Another User Issue in many pages.

    ** I am the only user connected to the database and it was working fine before i applied rollup 5.

    Please suggest the resolution for same, the project have to go live this week.

  15. Saurav Dhyani says:

    Exact Error Message –

    "The operation could not complete because a record was locked by another user. Please retry the activity."

    Please suggest…

  16. Peter says:

    @Saurav: I'll suggest to go live with the build no. that the solution was tested and approved with. If you wish to go live with a more recent build, then you will need to re-do the entire testing and approval of the solution.

  17. rdhansen says:

    We've installed build 36310 but are still getting the servicechannel faulted state issue trying to save/compile table changes (with the service tier on a different machine than the development environment…haven't tried both on the same machine).

  18. Ursula says:

    After installing Rollup 5 I get the message, that I have to convert the database. I have nowhere seen the information, that the database has to be converted. Is this normal? Can I say yes to convert it?

    Or what do I have to do? Or what CAN I do???

    Thanks for fast help.

  19. Marc Breuer says:

    @Ursula: Yes, the database needs to be converted. Be sure to backup the database before updating, as you cannot use it anymore when you downgrade to a previous build (when experiencing some of the problems discussed before).

  20. Ursula says:

    @Marc Breuer: thank you for your answer. Would be nice, if there was an corrspondent information on the "how to install" instruction…

  21. spriess says:

    Hi Ursula, the KB article for Update Rollup 5 (KB 2937999) has the following note right before the list of problems that are resolved in the rollup: "Note: Implementing this update rollup will require a database conversion". I have added the note to this blog post as well for added visibility.

  22. BugFinder says:

    Bug in UR5:

    T39 Purchase Line; Table Relation on field "No.". For G/L Account

     Second Line "Type=CONST(G/L Account),System-Created Entry=CONST(No)" Should be "Type=CONST(G/L Account),System-Created Entry=CONST(Yes)" like in Sales.

    please correct this "Feature" in UR6

    kind Regards,

    BugFinder

  23. spriess says:

    Hi BugFinder, this bug has been logged and will be fixed in UR7.

  24. Nuno says:

    Hi,

    Be carefull, if you open a database from a earlier build with the UR5, it asks you to convert the database, even you choose cancel you get the following error:

    The Object table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the SQL Server data type.

    Field : Version List

    Type: Text 248

    SQL type : VARCHAR(80)

    The only solution is to convert the database, so be very careful with this build

  25. ondrej.zavodny says:

    Hello,

    Today I solved problem "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state"

    by installing SQL Server Database Components on SQL Server:

    msdn.microsoft.com/…/dd983698(v=nav.70).aspx

    Maybe this helps to someone…

  26. zavodny@navisys.cz says:

    And, if you are not developing on same server as NAV Server middle-tier, you should enable your NAV Management port in firewall (by default 7045).

  27. Huba Buba says:

    Was this testing performed by Chinasoft?