Microsoft Dynamics NAV

Team Blog

March, 2011

  • Microsoft Dynamics NAV Team Blog

    Connector for Microsoft Dynamics - New Blog


    Check out the new blog for Connector for Microsoft Dynamics!

    It's all about integrating Dynamics ERP with Dynamics CRM. Currently, Connector for Microsoft Dynamics supports these versions of Dynamics ERP products:

    • Microsoft Dynamics NAV 2009 R2
    • Microsoft Dynamics AX 2009
    • Microsoft Dynamics GP 2010
    • Microsoft Dynamics GP 10

    For more information about NAV 2009 R2 and CRM, see Integrating Microsoft Dynamics NAV with Microsoft Dynamics CRM.

  • Microsoft Dynamics NAV Team Blog

    NAV install in "another" way


    Last time i published this article i received many claims as compliment too. Claims about "NAV doesn't work after this installation" and compliments about "this is very good for test or dev environment installation". So after one claim i removed article, and now added again (with minor modifications), but now mentioning in the begin: this article purpose is help you to understand how NAV server, client work/connects; if accidentally you have problems, where it could come from, but i didn't propose to use this installation.

    This article is not focused on "real secure" NAV installation, it just describes "how to install NAV and set it to work" (for example for application tests) and nothing else. Also I'm talking about simplest setup: Database + NAV Service Tier + Classic client/WS; there is nothing about other NAV components/integrations - just simplest connection.

    It is always is best way (supported way) install NAV as it is described in but some time we just need to have working environment. And here we are...

    Let's start from empty Windows 2003/2008 server.

    It has already installed:

    ü  SQL server (or it could be on another PC)

    ü  All other prerequisites required for NST (NAV service tier). You can find it in installation cd in folder "\Prerequisite Components".

    First point: all actions must be done under server administrator account. Of course you can set any other account with required permissions but it is fastest&easiest way to use administrator.

    1.                   Install SQL database to SQL server. Backup of demo Cronus db is on CD in the folder "SQLDemoDatabase\CommonAppData\Microsoft\Microsoft Dynamics NAV\60\Database".

    a)      Create new database in SQL and restore this backup.

    b)      If you are restoring W1 database, but will use from not EN-US, then you can change filed "checkcodepage" value to 0 in table "$ndo$dbproperty". This will prevent from possible error about different code pages when you will try to connect to db.

    c)       Copy "CsideClient" folder from installation cd to somewhere on server. Start NAV CC by run finsql.exe. It is in "CsideClient\program files\Microsoft Dynamics NAV\60\Classic". Better is install CsideClient using installer, however if there is already installed another version of NAV, you can only copy folder (by copying CC you will lose integration like: report designer; run CC reports from RTC; outlook integration and etc.). But here we have some workarounds as described in  

    d)      Possible you will receive license error, so be ready to upload license to client and to SQL server.

    2.                   Install NST as it is described in (or you can do not install NST, but go to point 3 and do points “a..e” and then  “I”)

    a) . Please pay attention that in SC CREATE statement must to have space after every equal sign (for example: binpath= "something" DisplayName= "name")

    b)      And one more time: more reliable is to install as described in , but current is faster :)

    3.                   Go to NST folder and edit CustomSettings.config file. Most possible you need to change values for :

    a)                  DatabaseServer – SQL server name

    b)                  DatabaseName – database name on SQL server

    c)                   ServerInstance – serverinstance name (any name) will be used to recognize this service from RTC

    d)                  ServerPort – tcp port will be used for communication (it must be opened), usually 7046

    e)                  WebServicePort – tcp port will be used for web service, usually 7047

    f)                   Open server manager>Configuration>Services. Find your installed service and open properties. In “Log On” tab set up administrator account and password (we don’t talk about security, just about how to run it). Start service and it must to start.

                                                I.            You can start NST without installing NST to services: open command prompt and run “Microsoft.Dynamics.Server.exe /console”.
    This will start service tier and WS form console using settings from CustomSettings.config file. However keep in mind console will starts under user who loaded cmd. This will start service tier and WS, you can see results in event viewer.

    4.                   Go to Diagnostics>Event Viewer>Applications. There must be new information event logged with text similar to: Service: "Service MicrosoftDynamicsNAVServer is listening to requests at net.tcp://full_qualified_servername:7046/DynamicsNAV/Service". If you have any errors instead of this message then you need to analyze where problems comes from.

    5.                   You can install RTC from installation cd (best way), but just for testing connection to service tier you can:

    a)      Copy RTC folder to somewhere on server. Copy from installation folder "RoleTailoredClient\CommonAppData\Microsoft\Microsoft Dynamics NAV\" file ClientUserSettings.config to new created RTC folder. Modify this file and add info from earlier described event:

    ·         Server - this must be NST computer name

    ·         ServerInstance - what you set previously on server

    ·         ServerPort - tcp port set on server


    6.                   Start RTC like I described in meaning create shortcut and start RTC.

    7.                   If you didn't install Web Service in point 3 then install it now (if you run console then forget this)  and:

    a)      Open server manager>Configuration>Services. Find your installed service and open properties. In "Log On" tab set up administrator account and password (we don't talk about security, just about how to run it). Start service and it must to start.

    b)      Go to Diagnostics>Event Viewer>Applications. There must be new information event logged with text similar to: "Service: Service Microsoft Dynamics NAV Business Web Services are available at http://full_qualified_servername:7047/DynamicsNAV/WS/Services". If you have any errors instead of this message then you need to analyze where problems comes from.

    c)       If you click on it, Internet Explorer must open web service page with published services. These addresses are case sensitive - be careful with it if enter addresses manually.

    Yeeeee. Both services are working (it are not secure but it works). Now we can try to connect from users pc's. But usually it doesn't work - firewalls/DNS/AD replication problems... :(

    8.                   Before start next actions, check does user pc really connected to network and see server pc (even "NAV classic client" or "network ping" are good tool here); is in the same domain; user is logged to domain; and user has permissions to db on SQL server. One day I lost half hour because network cable was unplugged. If everything OK in network, go to next point.

    a)      Go to server and open command prompt by run "cmd". Run "ipconfig". In answer must be IPv4 Address...... (o something similar). Remember it.

    b)      Return to users pc. Start RTC and set connection server address instead of "servername:7046/DynamicsNAV" to "" and push "Tab". In "available companies" must to appear available companies.

    c)       Check web service using ip address too. In IE address field must be :

    d)      If it still doesn't work, check firewall on server and on client: are ports 7046 & 7047 opened; is communication on these ports available and not filtered in network environment; and etc. I'm pointing on this because if we came to point 7 then services itself are good - network is bad :)

    e)      If everything works, then easiest part is done. Now we must to make system secure, change services accounts, set SPN/delegations/users/permissions... as it is described at . But this isn't in scope of current article.

    These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

    Best Regards

    Gedas Busniauskas

    Microsoft Lithuania
    Microsoft Customer Service and Support (CSS) EMEA

  • Microsoft Dynamics NAV Team Blog

    Designing reports for better performance on RTC II (page file)


    Increasing the page file in Windows to allow for larger datasets 

    As we have seen already in some cases, some reports which were optimised for the Classic Client may run slowly on RTC. This is especially the case when a report involves a lot of data. The post in the link below describes how to reduce the dataset for RTC reports. This is especially useful when a report may need to process lots of data but not actually print it (so process away on the NAV Server but no need to send all the data to RTC):

    Designing reports for better performance on RTC

    And of course - everything else being equal - smaller datasets also means faster reports. In some cases much faster.

    In other cases, maybe a user actually needs to print a lot of data. Or for some other reason it's not possible to reduce the dataset.

    The dataset is sent from NAV Server into memory on the RTC machine. If the dataset is larger than the amount of memory that Windows makes available, then Windows will stop allocating more memory and RTC will likely crash. There is nothing that RTC or NAV can do about this. So, if it is absolutely not possibly to reduce the dataset, then logically the only alternative is to increase available memory on the RTC machine.

     You can do this without physically buying more memory but increasing the page file in Windows. Windows is pretty good at handling the size of the page file itself for general Windows performance. So interfering with this can easily cause problems for any other tasks running on that machine. So if you do choose to increase the page file, then I would recommend that you do that on a dedicated machine which is not much used for anything else than printing large reports on RTC.

    You change the page file from Control Panel –> System and Security –> System –> Advanced System Settings –> Advanced, and then click “Settings…” in the “Performance” section.

    This will not affect performance of reports (maybe on the contrary). It will just allow RTC to receive a little more data before running out of memory.


    Just to test this method, I created a report which combined Integer table with Customer Ledger Entries to generate lots of data. My default settings were to let Windows manage the page file, and it had allocated 8053 MB to the page file:




    With this setting, after transferring approximately 850.000 rows, my machine ran out of memory and RTC crashed. This corresponds to almost 60.000 pages.

    I then set the page file to “Custom Size” and set both Initial size and Maximum Size to 15.000. Then rebooted. Note: In my first attempt I only set Maximum Size to 15.000 but this did not make any difference until I also increased the Initial Size. After rebooting, the same report was now able to transfer 2.000.000 rows which corresponds to hopefully more pages than anybody will ever need to print from RTC.

    I should also mention that setting my page file to 15.000 left not much else and even my screen resolution suffered greatly. So finding the right balance  may take a bit of trial and error, and unfortunately a reboot is necessary every time you try a new page file setting.

    The test report I used here is a very simple one, and I was running on quite good hardware. The amount of pages any user is able to print will very much vary from one machine to the next.


    I hope that this sharing of some basic testing with my page file can be useful or at least save a few reboots in a few RTC installations. And feel welcome to add your own experiences with this as comments below!


  • Microsoft Dynamics NAV Team Blog

    NAV 2009 Tips and Tricks: Personalize the Departments Menu


    Did you know you can remove the Departments menu from the navigation pane? You may want to do this as you customize the RoleTailored experience for yourself or your customers. The ease of doing this has been improved beginning with Microsoft Dynamics NAV 2009 SP1 and also applies to Microsoft Dynamics NAV 2009 R2.

    1. On the menu bar, click Customize , and then click Customize Navigation Pane.

    2. In the Customize Navigation Pane window, in the Navigation pane buttons list, click Departments and then click Remove. You can also remove other buttons, such as Administration. You cannot remove the Home button.

    3. Click OK.

    4. Select Yes to restart the RoleTailored client and see your changes.

  • Microsoft Dynamics NAV Team Blog

    New Hands-on Labs for Microsoft Dynamics NAV 2009 R2 Inventory Costing


    Microsoft Learning released hands-on labs covering the Microsoft Dynamics NAV 2009 R2 Inventory Costing functionality. These are a series of stand-alone hands-on labs that guide you through the process of working with the Inventory Costing module. The labs include:

    1. Introduction to Hands-on Lab in Inventory Costing in Microsoft Dynamics NAV 2009 R2
    2. Inventory Acquisition in Inventory Costing in Microsoft Dynamics NAV 2009 R2
    3. Cost of Sold Goods in Inventory Costing in Microsoft Dynamics NAV 2009 R2
    4. Inventory Adjustments in Inventory Costing in Microsoft Dynamics NAV 2009 R2
    5. Inventory Costing in the General Ledger in Inventory Costing in Microsoft Dynamics NAV 2009 R2
    6. Inventory Revaluation and Physical Inventory in Inventory Costing in Microsoft Dynamics NAV 2009 R2

    All labs are available in the Training Materials section of PartnerSource and CustomerSource.


  • Microsoft Dynamics NAV Team Blog

    Commerce Gateway and BizTalk Server 2010


    Microsoft's new release of BizTalk Server 2010 provides a solution that allows organizations to more easily connect disparate systems. Including over 25 multi-platform adapters and a robust messaging infrastructure, BizTalk Server provides connectivity between core systems both inside and outside your organization. In addition to integration functionality, BizTalk also provides strong durable messaging, a rules engine, EDI connectivity, Business Activity Monitoring (BAM), RFID capabilities and IBM Host/Mainframe connectivity. For more information on BizTalk Server 2010 please go to the launch page at

    Microsoft Dynamics NAV 

    With Commerce Gateway (Utilizing BizTalk capabilities), companies can use Microsoft Dynamics NAV to electronically exchange trading documents with business partners regardless of conversion requirements and data formats. This can help streamline business processes and reduce transaction costs. Commerce Gateway also makes it easier for companies to meet the changing demands of their trading partners, regardless of the industry they are in, the system that they use, or the standards that their partners require.


    Over the last few months, the NAV product team has tested Commerce Gateway in the Microsoft Dynamics NAV 2009 SP1, Microsoft Dynamics NAV 2009 R2, and Microsoft Dynamics NAV 5.0 SP1 Update 2 releases  for compatibility with the BizTalk Server 2010 RTM release.

    The following scenarios are fully supported:

    NAV Release BizTalk Version OS SQL Server Version
    NAV 2009 SP1 BizTalk 2010 x86 Windows Server 2008 x86 SQL Server 2005
    SQL Server 2008
    NAV 2009 R2 BizTalk 2010 x86 Windows Server 2008 x86 SQL Server 2005
    SQL Server 2008
    NAV 5.0 SP1 Update 2 BizTalk 2010 x86 Windows Server 2008 x86 SQL Server 2005
    SQL Server 2008


    • BizTalk Server 2010 can only be installed on Windows 7 or Windows Server 2008 architecture.
    • Commerce Gateway Request Server can only be installed on x86 OS and does not run WOW 64.
    • Commerce Gateway is previously verified to run on Biztalk Server 2006 R2 SP1 and Biztalk Server 2009 x86 releases
Page 1 of 1 (6 items)