ArcherPoint Dynamics NAV Developer Digest – vol 52
The ArcherPoint technical staff—made up of developers, project managers, and consultants – is constantly communicating internally, with the goal of sharing helpful information with one another.
As they run into issues and questions, find the answers, and make new discoveries, they post them companywide on Yammer for everyone’s benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this group—so we thought, wouldn’t it be great to share them with the rest of the Microsoft Dynamics NAV Community? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from the ArcherPoint staff. We hope these insights will benefit you, too.
Matt Traxinger on a problem saving objects in SQL database:
Cannot save any objects. This is a 5.0 SQL database.
Things we have tried:
Saving with our license (multiple versions of it)
Saving with their license
Saving to an ID both in and out of the customer license
Verified the License Permission table is allowed to create or modify the object with both licenses
Synchronized security (yes, they are Enhanced) for the windows login
Verified the windows login is SUPER
Checked the object table in SQL, everyone appears to have Insert/Modify/Update/Read
Kyle Hardin: Probably a SQL permission problem – they might have locked it down. Whatever the account (database or windows), have them set the SQL user to have DBOwner rights to the NAV database, and I think you also need some access to Master in order to update objects. You can have them set that user to have the sysadmin role and that grant access to everything. If that works, then they can try backing down the security for that account a step at a time until they figure out the minimums.
Matt Traxinger: The login has sysadmin as a server role, only public on the master, and DB owner on the NAV database. I always thought the SQL level was really only for table changes.
Kyle Hardin: Anything useful in the SQL log? Another idea is to create a brand new NAV account and give that full privileges, just in case the account you are currently using has gotten mangled by enhanced security somehow.
Michael Heydasch: Recently ran into issues at a client site trying to make changes to NAV objects. In their case, it was a vertical that was causing issues...objects outside our license range that were being called from CU1. I commented out the code in CU1 and it stopped being an issue.
Bill Warnke: You could try SQL Profiler filtered on some Warning events. If SQL is throwing an error it should pick it up, but I would think that would bubble back to dev environment...
Jon Long: What error are you getting when you try to save?
Denise Blaisdell: The error is: “You do not have permission to create the ‘xxx Trial Balance’ Report. Contact the system manager if you need to have your permissions changed.”
Denise Blaisdell: UPDATE: Thanks to everyone and their ideas on how to address this issue. Come to find out, was not SQL at all, there was a company permission in NAV where the developer user was restricted to the testcompany. Even though the user had SUPER rights it would not let me save any objects. As soon as we removed the company restriction I was able to save the custom object. Very strange... I will remember this one.
Question on SystemOutOfMemory error running reports:
Crystal Hill: I have a client that is getting the SystemOutOfMemory error when running a report in NAV 2013 R2. One of the suggestions I had was to create a SQL report that can be run in place of the report (Sales Taxes Collected). This client has 90+ thousand lines entered per week per location, and they have about 10+ locations that they are running. Is there a possible solution to give to the client, or do you know of any other work around for this error?
Michael Wong: Are they loading the company logo on this report?
Crystal Hill: No, this is simply the amount of data they are trying to pull.
Michael Wong: I had experienced something like this once before with a client. Do you know the specs of the computer trying to run the report? If I recall correctly, we were able to get them to generate the report by running it on a system that was using a 64-bit operating system with a lot of available RAM. Another solution that I had proposed to them was to have this particular report print through the Job Queue, that way it would utilize the server's RAM as opposed to the local system. They would need to set up the printer selections for this report if they were going to go that route.
Brian Winfrey: The real problem lies in the fact that the reports are rendered on the 32-bit RTC client which can only address about 2GB of RAM and limits the dataset to somewhere between 70k and 90k rows. The attached article provides a few tricks, the basics of which is either filter the report and run it N times or try to render it on the server using job queue.
Helle Madsen: While this news will not help this client right now, the next NAV release (called Corfu for now) will be a 64-bit Windows client, and that should alleviate this issue. Another option (available in NAV2015) is to run the report in the background (server).
Question on NAS licensing for NAV 2015:
Question: Do any of you know how licensing works for NAS for 2015? It looks like that isn't a separate granule any longer. Does a NAS just take a regular user spot now, meaning if I add 6 service tiers to be 6 NAS connections that I need to buy 6 more regular user licenses?
Answer: The NAS granules as we knew them, do not exist starting with NAV2013. In older versions one NAS was included in the license, and additional NAS needed to be purchased separately. Starting with 2013, and when upgrading from a pre-2013 version, the existing NAS granules are removed from the license. You configure NAS Services with the Server Admin tool, but no NAS actual granules are necessary, and they are not even available to be purchased. Full or Limited Users are required (depending on read/write requirements) if using the Microsoft SharePoint Client or any other mode of access going through the API (including Web Services). But, this will also fall under the concurrent access rules so if there is no impact due to timing of NAV access, then no additional users would need to be purchased.