• Microsoft Dynamics NAV Team Blog

    How to manage NAV DBCS data using C#


    It is known that NAV CC (Classic Client) does not support natively DBCS (Double-Byte Character Set) and so does the new NAV 2009 RTC (Role Tailored Client).

    Due to differences in how the CC and RTC check the code page isn’t still possible to enable DBCS in the RTC but this is possible for the CC by implementing new fin.stx file.

    This last sentence is duly written and explained in KB 915374.

    How to enable and to display double-byte character sets in Microsoft Dynamics NAV

    Following  the KB link is possible to enable DBCS for several NAV versions included NAV  2009.

    … But what if we want to develop a simple WinForm project in VC# that access the database in order to retrieve and write information in the same way NAV does?

    The following example will guide you through the creation of a simple Form using VS (Visual Studio ) and transforming Japanese characters in their “NAV equivalent” in order to deal correctly with the DBCS data management inside the NAV database.

    The example proposed has been developed using the following scenario:

    1.       Windows Server 2008

    2.       SQL Server 2008

    3.       Visual Studio 2008 SP1

    4.       NAV 2009 RTM W1


    a.       Download and install a copy of NAV 2009 W1 RTM.

    Install the sample database and the Classic Client.

    The SQL sample database should use Windows Collation for Afrikaans, Basque, Catalan, Dutch, English, Faeroese, German, Indonesian, Italian, Portuguese.

    This can be easily checked in NAV by checking the collation tab in

    File > Database > Alter

    b.      In Windows Server 2008 select Japanese as language for non-Unicode programs.

    Control Panel > Regional and Language Options > Administrative tab

    Change the current language for non-Unicode programs to: Japanese (Japan)

    (you will be prompted to reboot the machine)

    c.       Download the zip file contained in KB 915374

    d.      Extract the fin.stx file from the folder NAV 2009

    e.      Substitute the fin.stx file that is located in the Classic client folder with the brand new one extracted.

    E.g. Path for Classic Client folder:

    C:\Program Files (x86)\Microsoft Dynamics NAV\60\Classic

    f.        Substitute the fin.stx file that is located in the ENU folder of the Classic Client with the brand new one extracted.

    E.g. Path for Classic Client folder:

    C:\Program Files (x86)\Microsoft Dynamics NAV\60\Classic\ENU

    Now you should be able to manage Japanese characters like those ones…


    NAV with DBCS enabled




    Roughly speaking regarding what we have done is merely enabling the Japanese characters to be stored into SQL Server but… not directly!

    The Japanese code page is 932 (Shift-JIS) while we are using the  Latin1 code page 1252 to store the data. To know more about Windows Collation Designators you can check:


    This means that while we are typing Japanese chars in the NAV classic Client (using code page 932), this have been reverted (translation encoded) in their respective characters using code page 1252 and stored in this way in the SQL Server field.

    This means that while we are seeing this in NAV :


    … those are the characters effectively stored in SQL Server …


    Then the solution can come out clearly: use C# encoding function to manage the ‘translation’ between one set of character to another.


    1.       Open Visual Studio 2008

    2.       Create a brand new Visual C# project

    Go to File > New > Project

    Select project types: Visual C# > Windows > Windows Forms Application

    Give the project a Name: WinFormDBCS

    Click OK

    3.       Design your form like this (2 TextBox, 1 Button)


    4.       Add this code to your form:

    using System;

    using System.Collections.Generic;

    using System.ComponentModel;

    using System.Data;

    using System.Drawing;

    using System.Linq;

    using System.Text;

    using System.Windows.Forms;


    namespace WinFormDBCS


        public partial class Form1 : Form


            public Form1()





            private void button1_Click(object sender, EventArgs e)


                //Create a new variable of type Encoding and

                // assign it the Latin

         //  code page 1252

                //To know more about it

                // http://msdn.microsoft.com/en-us/library/system.text.encoding_members.aspx

                Encoding nav = Encoding.GetEncoding(1252);


                //Create a new variable of type Encoding and assign it the Japanese

         //  code page 932

                Encoding unicode = Encoding.GetEncoding(932);


                //Populate a byte variables withe the value of the first TextBox written

         //  in Japanese characters using the Japanese code page 932

                byte[] unicodeBytes = unicode.GetBytes(textBox1.Text);


                //Display in the second TextBox the result of the encoding conversion of

         //  the byte stored in Japanese directly in the Latin code page equivalent

                //Tip: you can substite the mere text display with some simple code that

         //  writes directly this value into a NAV Text field

                textBox2.Text = nav.GetString(unicodeBytes);





    5.       Press F5 to start debugging your project.

    6.       Insert this Japanese string (or whatever Japanese sentence you want to) in the first TextBox:


    7.       Press the Transform Data button and… see the results:


    8.       To check if NAV ‘digest’ those newly created string you have to select the whole string converted in the second TextBox and copy it:


    9.       Open SQL Server Management Studio and paste it into the “Address 2” field of customer 01121212.

    Expand “Demo Database NAV (6-0)”

    Expand “Tables”

    Search for “CRONUS International Ltd_$Customer” table

    Right click on “CRONUS International Ltd_$Customer” and click on “Edit top 200 rows”

    Search for customer 01121212

    Place the cursor in the “Address 2” field and paste the content in this field


    10.   Browse to the next record and close SQL Server Management Studio.


    Open NAV and… go to customer 01121212.



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

    Best Regards,

    Duilio Tacconi (dtacconi)

    Microsoft Dynamics Italy

    Microsoft Customer Service and Support (CSS) EMEA


    Special thanks to Kenny Vaes of Helios-IT

  • Microsoft Dynamics NAV Team Blog

    What do SPNs actually do - NAV 2009


    Three terms keep coming up when setting up NAV 2009 when NAV-server (middle tier) runs on a different machine than SQL Server:
      - Delegation / Impersonation
      - Kerberos
      - SPN

    Delegation / Impersonation is what it says it is. Kerberos is handled more or less automatically by Windows. But what do SPNs actually do....

    (un)fortunately SPN can't be explained without first explaining Delegation and Kerberos.


    Delegation / Impersonation:
    The end-user (RTC) logs on to the NAV-Server which then logs on to the SQL Server - using the end-user's credentials (impersonating the end-

    user). All logins here are Windows logins. Impersonation would also be a nice way for a hacker to gain access, so therefore Windows requires

    that a domain administrator specifically allows the NAV-server to impersonate users on the SQL Server.

    This is only when the NAV-Server and SQL Server runs on two different machines. When they run on the same machine, then Windows has already

    authenticated the end-user when they connected to the NAV-Server. So when the NAV-Server logs on to the SQL Server (on the same machine),

    Windows has already knows the end-user. So in this case there is no need to set up delegation, and hence no need to worry about Kerberos and


    But with two machines, delegation is needed. Delegation requires Kerberos.


    Connections between two users happen all the time. What Kerberos adds to such a connection is a certificate (ticket) which ensures that each

    of the two users can trust the identity of the other user. This is actually a kind of countermeasure against a user (hacker) impersonating

    another user. Windows requires that before it allows delegation, that the connection being delegated is a Kerberos connection. In this way,

    Windows has assurance that the user credentials being forwarded are valid. So when RTC connects to the NAV-server, it has to do this with a

    Kerberos connection.

    A Kerberos connection is between two Windows user accounts. A user doesn't know (shoulnd't know) what user account the NAV-server runs under.

    This is where SPNs come in. So, finally we get to the SPNs:


    SPN (Service Principal Name) is a simple table that maps a service to a user account. Think of it as a table with two fields: Service-name,

    and Windows User name. When the NAV client wants to start a Kerberos connection to the NAV-server, it will connect to for example

    DynamicsNAV\Nav-Server:7046. Kerberos requiring a user name will then look this up in the SPN table and find the user name there. So, only if

    an SPN has been created for the account that runs the NAV-service, will Windows be able to then start a Kerberos connection. And the user will

    never need to know which that account the NAV-server is running under.

    When setting up SPNs, make sure that:
      1) The account that runs the NAV-service has an SPN that contains what the NAV client will connect to (Server name in the right format),and
      2) Quite a common probem: Make sure that there are no duplicate SPNs. If you change the NAV-service to run under a different account you must set up SPNs for the new account. Then make sure to also remove the SPNs for the old account.


    So in short: Delegation / Impersonation requires Kerberos. Kerberos connection to a service running an unknown account, requires SPN. And,

    visa versa, if SPNs have not been set up correctly, then Kerberos won't work so then Delegation wont work either.


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


    Best regards

    Lars Lohndorf-Larsen (Lohndorf)

    Microsoft Dynamics UK

    Microsoft Customer Service and Support (CSS) EMEA

  • Microsoft Dynamics NAV Team Blog

    Failed to open key when Installing Dynamics NAV 2009


    When installing Dynamics NAV 2009 one of my friend's rune into this problem:

    Microsoft Dynamics NAV 2009 Build 27808
    Error Report
    RoleTailored client
    Microsoft Dynamics NAV 2009 RoleTailored client
    Fatal error during installation.

    Could not open key: UNKNOWN\MSComDlg.CommonDialog.1\CLSID. Verify that you have sufficient access to that key, or contact your support personnel.

    The problem here is that we have a mismatch of .NET. The simplest solution is to install latest version of a .NET and run the installer again.

    .NET Framework 3.5 SP1

  • Microsoft Dynamics NAV Team Blog

    Setting up NAV 2009 on Three machines


    Setting up delegation and SPNs for NAV 2009 on three machines (when the NAV Server and SQL Server are on two seperate machines) is described in "Walkthrough: Installing the Three Tiers on Three Computers". But in addition to this, also be aware of the following:

    • The syntax of SPNs has changed since KB 968189
    • You may need to set UserAccountControl flag in Active Directory

    Also thanks to our German colleagues for already posting this information here and here.


    Syntax of SPNs has changed since KB 968189

    After installing KB 968189 for NAV 2009 (Build 6.0.28795.0) the SPNs now have this format:
    <Instance>/<server host>:<port>
    <Instance>/<server FQDN>:<port>

    So for example if the SPNs used to be set like this:


    From this build and later they have to be set like this:

    About KB 968189 itself, it solves a very specific problem where it may not be possible to connect if the domain has multiple DNS Suffixes, which is quite unusual. Most installations are not affected by this. You can check whether you are affected by running ipconfig from a command prompt, and see if it lists more than one domain name under "Connection-specific DNS Suffix".


    Setting UserAccountControl flag

    In some cases you have to set UserAccountControl as described in KB 305144. You set this flag by running ADSIEDIT.msc, go to properties of the user account running your NAV Server, and then select UserAccountControl. Setting it to 17301504 means TRUSTED_FOR_DELEGATION+TRUSTED_TO_AUTH_FOR_DELEGATION



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


    Best regards

    Lars Lohndorf-Larsen (Lohndorf )

    Microsoft Dynamics UK

    Microsoft Customer Service and Support (CSS) EMEA

  • Microsoft Dynamics NAV Team Blog

    Trace flag in SQL Server for Dynamics NAV 2009


    When starting the RTC client or open the database in classic client you will get a warning if you have not set the trace flag correct. Because of changed security in SQL Server 2005 Dynamics NAV 2009 will only connect to the SQL Server if the trace flat ‘4616' is set.

    How to:

    1. Open SQL Server Configuration Manager
    2. Right click on MSSQLSERVER and select properties
    3. In properties click advanced tab
    4. Click to the right of Setup Parameters and go to the end of the line
    5. Add this string ";-T4616"
    6. Click ok and restart your SQL Server.
  • Microsoft Dynamics NAV Team Blog

    SQL Query to show tables, their indexes and index usage


    The SQL query below shows a list of tables sorted by the largest tables first. For each table, the indexes in the table are shown. For each index it shows when the index was last used. The query is designed to collect various pieces of information in one place, and give an overview to help supporting decisions when doing index tuning.

    The left hand columns show data for the table (No. of receords, data- and index size) to have a view of the impact of having indexes on the table.

    The right hand columns show data for each index, including Updates (costs) and Reads (benefits) and when it was last used sine the last time SQL Server was restarted.

    Further comments:

    • The query only works on SQL Server 2005 and later.
    • The numbers in the query are reset every time SQL Server restarts.
    • The query may take up to a few minutes to run.
    • The query is provided "as is", with no warranties and confers no rights. You assume all risk for your use.

    If you have comments or feedback, please feel free to post them here.


    Best regards

    Lars Lohndorf-Larsen (Lohndorf)
    Microsoft Dynamics UK
    Microsoft Customer Service and Support (CSS) EMEA



    --use NavisionDatabase

    IF OBJECT_ID ('z_IUQ2_Temp_Index_Keys', 'U') IS NOT NULL

    DROP TABLE z_IUQ2_Temp_Index_Keys;

    -- Generate list of indexes with key list

    create table z_IUQ2_Temp_Index_Keys(

    [l1] [int] NOT NULL,

    [F_Obj_ID] [int] NOT NULL,

    [F_Schema_Name] [nvarchar] (128) NULL,

    [F_Table_Name] [nvarchar] (128) NOT NULL,

    [F_Row_Count] [int] NULL,

    [F_Reserved] [int] NULL,

    [F_Data] [int] NULL,

    [F_Index_Size] [int] NULL,

    [F_UnUsed] [int] NULL,

    [F_Index_Name] [nvarchar] (128) NOT NULL,

    [F_Index_ID] [int] NOT NULL,

    [F_Column_Name] [nvarchar] (128) NOT NULL,

    [F_User_Updates] [int] NULL,

    [F_User_Reads] [int] NULL,

    [F_Last_Used] [datetime] NULL,

    [F_Index_Type] [nvarchar] (128) NOT NULL,

    [F_Index_Column_ID] [int] NOT NULL,

    [F_Last_Seek] [datetime] NULL,

    [F_Last_Scan] [datetime] NULL,

    [F_Last_Lookup] [datetime] NULL,

    [Index_Key_List] [nvarchar] (MAX) NULL



    CREATE NONCLUSTERED INDEX [Object_ID_Index] ON [dbo].[z_IUQ2_Temp_Index_Keys]

    ([F_Obj_ID] ASC



    CREATE NONCLUSTERED INDEX [Index_ID_Index] ON [dbo].[z_IUQ2_Temp_Index_Keys]

    ([F_Index_ID] ASC



    CREATE NONCLUSTERED INDEX [RowCount_ID_Index] ON [dbo].[z_IUQ2_Temp_Index_Keys]

    ([F_Row_Count] ASC




    insert into



    (row_number() over(order by a3.name, a2.name))%2 as l1,

    a1.object_id, ---

    a3.name AS [schemaname],

    a2.name AS [tablename],

    a1.rows as row_count,

    (a1.reserved + ISNULL(a4.reserved,0))* 8 AS reserved,

    a1.data * 8 AS data,

    (CASE WHEN (a1.used + ISNULL(a4.used,0)) > a1.data THEN (a1.used + ISNULL(a4.used,0)) - a1.data ELSE 0 END) * 8 AS index_size,

    (CASE WHEN (a1.reserved + ISNULL(a4.reserved,0)) > a1.used THEN (a1.reserved + ISNULL(a4.reserved,0)) - a1.used ELSE 0 END) * 8 AS unused,

    -- Index Description




    -- Index Stats


    US.user_seeks + US.user_scans + US.user_lookups User_Reads,


    when (ISNULL(US.last_user_seek,'00:00:00.000') >= ISNULL(US.last_user_scan,'00:00:00.000')) and (ISNULL(US.last_user_seek,'00:00:00.000') >= ISNULL(US.last_user_lookup,'00:00:00.000')) then US.last_user_seek

    when (ISNULL(US.last_user_scan,'00:00:00.000') >= ISNULL(US.last_user_seek,'00:00:00.000')) and (ISNULL(US.last_user_scan,'00:00:00.000') >= ISNULL(US.last_user_lookup,'00:00:00.000')) then US.last_user_scan

    else US.last_user_lookup

    end as Last_Used_For_Reads,










    SUM (


    WHEN (ps.index_id < 2) THEN row_count

    ELSE 0


    ) AS [rows],

    SUM (ps.reserved_page_count) AS reserved,

    SUM (


    WHEN (ps.index_id < 2) THEN (ps.in_row_data_page_count + ps.lob_used_page_count + ps.row_overflow_used_page_count)

    ELSE (ps.lob_used_page_count + ps.row_overflow_used_page_count)


    ) AS data,

    SUM (ps.used_page_count) AS used

    FROM sys.dm_db_partition_stats ps

    GROUP BY ps.object_id) AS a1




    SUM(ps.reserved_page_count) AS reserved,

    SUM(ps.used_page_count) AS used

    FROM sys.dm_db_partition_stats ps

    INNER JOIN sys.internal_tables it ON (it.object_id = ps.object_id)

    WHERE it.internal_type IN (202,204)

    GROUP BY it.parent_id) AS a4 ON (a4.parent_id = a1.object_id)

    INNER JOIN sys.all_objects a2 ON ( a1.object_id = a2.object_id )

    INNER JOIN sys.schemas a3 ON (a2.schema_id = a3.schema_id)

    inner join sys.indexes SI ON (SI.object_id = a1."object_id") ---

    inner join sys.index_columns SIC ON (SIC.object_id = SI.object_id and SIC.index_id = SI.index_id)

    left outer join sys.dm_db_index_usage_stats US ON (US.object_id = SI.object_id and US.index_id = SI.index_id)

    WHERE a2.type <> N'S' and a2.type <> N'IT'

    order by row_count desc


    -- Populate key string

    declare IndexCursor cursor for

    select F_Obj_ID, F_Index_ID from z_IUQ2_Temp_Index_Keys

    for update of Index_Key_List

    declare @objID int

    declare @IndID int

    declare @KeyString VARCHAR(MAX)

    set @KeyString = NULL

    open IndexCursor

    set nocount on

    fetch next from IndexCursor into @ObjID, @IndID

    while @@fetch_status = 0 begin

    set @KeyString = ''

    select @KeyString = COALESCE(@KeyString,'') + F_Column_Name + ', '

    from z_IUQ2_Temp_Index_Keys

    where F_Obj_ID = @ObjID and F_Index_ID = @IndID

    ORDER BY F_Index_ID, F_Index_Column_ID

    set @KeyString = LEFT(@KeyString,LEN(@KeyString) -2)

    update z_IUQ2_Temp_Index_Keys

    set Index_Key_List = @KeyString

    where current of IndexCursor

    fetch next from IndexCursor into @ObjID, @IndID


    close IndexCursor

    deallocate IndexCursor


    -- clean up table to one line per index

    delete from z_IUQ2_Temp_Index_Keys

    where [F_Index_Column_ID] > 1



    [F_Table_Name] TableName,

    [F_Row_Count] No_Of_Records,

    [F_Data] Data_Size,

    [F_Index_Size] Index_Size,

    [F_UnUsed] UnUsed_Space,

    [F_Index_Name] Index_Name,

    [F_User_Updates] Index_Updates,

    [F_User_Reads] Index_Reads,

    [F_Last_Used] Index_Last_Used,

    [F_Index_Type] Index_Type,

    [Index_Key_List] Index_Fields

    from z_IUQ2_Temp_Index_Keys

    order by F_Row_Count desc, F_Table_Name, [F_Index_ID]




  • Microsoft Dynamics NAV Team Blog

    Failed to execute SQL string when Installing Dynamics NAV 2009 #2


    When reinstalling Dynamics NAV 2009 or if you have attached a Demo Database manually you will probably run into this problem:

    Microsoft Dynamics NAV 2009 Build 27808
    Error Report
    SQL Server option
    Cronus Sample Database for Microsoft Dynamics NAV 2009
    Fatal error during installation.

    Error -2147467259: failed to execute SQL string, error detail: A database with name Demo Database NAV (6-0) already exists., SQL key: StopIfDatabaseExist SQL string: IF EXISTS (SELECT * FROM [master].[sys].[databases] WHERE name = ‘Demo Database NAV (6-0)') RAISERROR (N'A database with name %s already exists.',20,1,'Demo Database NAV (6-0)') WITH LOG

    The problem is here that a database already exists with from a previous installation. The problem can be solved by starting SQL Server Management Studio and deleting the database that already exists. After you have deleted the database start the installation program again and select repair. In Microsoft Dynamics NAV 2009 SP1 you will have one new option saying replace database that you can set to override existing database. If you need to save the existing database for some reason simple do a backup of it before deleting it or read my previous post about how to have more than one Demo Database installed at the same time.

  • Microsoft Dynamics NAV Team Blog

    Installing Stored Procedures for Dynamics NAV 2009 Manually


    It’s recommended that you use the installer on the product DVD to install the stored procedures. But if you are running more than one name instance of SQL server on the same machine that approach will not work. Then you need to do it manually:
    1. Copy the xp_ndo.dll file to the location you want store it. The file can be found under “D:\SQLDatabase\PFiles\Microsoft Dynamics NAV\60\Database” on the product DVD.
    2. Run the following SQL command to add the stored procedures.

    USE master
    EXEC sp_addextendedproc xp_ndo_enumusersids, ‘C:\[Location of file]\xp_ndo.dll’

    ON [xp_ndo_enumusersids]

    USE master
    EXEC sp_addextendedproc xp_ndo_enumusergroups, ‘C:\ [Location of file]\xp_ndo.dll’

    ON [xp_ndo_enumusergroups]

  • Microsoft Dynamics NAV Team Blog

    New Statement of Direction Document for Microsoft Dynamics NAV


    We have released a new Statement of Direction document for partners. We know preparation and product roadmap knowledge is a key factor in building a successful business. With the release of the new Statement of Direction we are able to share our vision and plans for the future direction of Microsoft Dynamics NAV. This will bring partners ahead of most competitors, who struggle to provide customers with product roadmaps. Microsoft Dynamics NAV partners can now speak confidently to customers about the future strategy, aspirations and roadmap for the next major releases of Microsoft Dynamics NAV through to 2017, including NAV "7", "8" and "9".

    PartnerSource: https://mbs.microsoft.com/partnersource/marketing/statementofdirection/NavProdStratToolkit.htm

    CustomerSource: https://mbs.microsoft.com/customersource/documentation/whitepapers/navsod.htm

    -Lotte Cordt Ihlemann

  • Microsoft Dynamics NAV Team Blog

    How to use WCF Performance Counters with NAV 2009 Server


    NAV Server (middle tier) utilises Windows Communication Foundations (WCF), which includes a number of performance counters that you can use to monitor NAV Server performance in real-time. This example shows how to monitor "Calls Per Second" for NAV Server to get some idea of how busy it is over a working day / over time. Many other counters are available.

    Enable Counters

    First, enable WFC Performance Counters as described in this article WCF Performance Counters:

    1)  Use Notepad to edit "Microsoft.Dynamics.Nav.Server.exe.config" in the NAV Service folder (default is C:\Program Files\Microsoft Dynamics NAV\60\Service).


    2)  Add the section below, marked with Red:

    <?xml version="1.0" encoding="utf-8" ?>
      <appSettings file="CustomSettings.config" />
        <assert assertuienabled="false" />

          <diagnostics performanceCounters="All" />



    3)  Restart NAV Server.


    Watch Counters

    Use Windows Performance Monitor to select and view counters from NAV Server:

    1)  Start Windows Performance Monitor (Start -> Run -> Perfmon.exe)


    2)  Add a Counter, then from available categories, select ServiceModelService. This will list the NAV Server, so select this. Then add the counter(s) you are interested in - in this example "Calls Per Second":



    I found that in a stand-alone situation, the only counter that really shows anything is "Calls Per Second". But in a multi user system, this could well be very different - please share your experiences here.


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


    Best regards

    Lars Lohndorf-Larsen (Lohndorf )

    Microsoft Dynamics UK

    Microsoft Customer Service and Support (CSS) EMEA

  • Microsoft Dynamics NAV Team Blog

    Upgrading to Dynamics NAV 2009


    Upgrade procedure to Dynamics NAV 2009 is not very different from upgrade procedures we had in previous versions, but some differences do apply, depending on what we want to achieve with the upgrade.

    First scenario is executables only upgrade, which is the same as traditional executables upgrade in NAV. That means upgrading classic NAV client to NAV 2009 version by opening previous database versions with new client, and selecting yes when prompted to convert database, without any object changes or data transfer. Or alternatively, creating a new database with NAV 2009 client, and restoring a backup of customer's database.

    This will, as before, upgrade the version of executables running NAV to 2009 version (builds 6.0 and higher) and create necessary system tables, but this will not automatically open up for using new NAV 2009 functionality (like RTC client or Web Services). Running the first scenario is a mandatory part of any upgrade scenario, just as it was in previous versions.

    Beware of few issues that can rise from this scenario, see the link below for description.


    Another scenario is doing an executable upgrade that would open up for using Web services, but would not include any object upgrade or data transfer.

    This is where 3-tier scenario enters stage and a Dynamics NAV server should be set up and connected to the database (this is the normal installation/setup process of the service). Dynamics NAV Web service should also be installed, see Dynamics NAV documentation for installation and setup of different components.


    To be able to use Web Services after doing an upgrade of executables and setting up a NST and Web service, one must also import and populate web service form (810) from a NAV 2009 client. This will open up for exposing codeunits (and also pages, but at this stage, pages are not yet present in database).

    To further enable using RTC, one should also import tables 9050-9060, these are cue tables used in role centers of RTC. If you are creating and running custom Role Center pages, remember to create a record in each table by specifying any value as primary key (or follow code examples from standard Role Center pages that will insert a record if table is empty). A record in any of these tables will be automatically inserted when using standard NAV Role Page (based on that table).

    In addition, reports should be 'transformed' to add RDLC layer and forms should be transformed to pages. You can also run reports with classic engine form RTC (that is run classic NAV report in RTC), in which case no object upgrade is necessary for reports. Note though, to run reports with classic engine on RTC client, each machine running RTC client (and classic reports) needs to have Classic client installed as well.

    Furthermore, Role Center pages should be created or standard ones imported from NAV 2009 client (pages in range 9000-9020). Finally, PROFILE table (table 2000000072) should be populated with standard (or custom) profiles, and role center pages tied to these.

    Last, but not least, you must make sure the existing code is modified to run in both scenarios (see MSDN documentation on code considerations for NAV 2009). 

    However, the job needed in this last scenario (specially transforming forms and reports) is not much different than using full database upgrade . In full upgrade version, objects in standard and custom version of NAV (version we are upgrading) would be merged with standard NAV 2009 objects to create custom NAV 2009 database. Note, all forms in standard NAV 2009 version are transformed to pages, so it is advisable to run Form transformation to create pages, once forms are merged to NAV 2009 object version. Also, one should 'upgrade' reports to add RDLC layer, once custom reports are merged to NAV 2009 version.

    No data transfer would occur from W1 5.0 to W1 NAV 2009 version, as there are no changes to table structure from 5.0 version. Upgrading from earlier version would still imply data transfer using Upgrade Toolkit.


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


    Best regards,

    Jasminka Vukovic (jvukovic )

    Microsoft Dynamics NO

    Microsoft Customer Service and Support (CSS) EMEA


  • Microsoft Dynamics NAV Team Blog

    How to install more than one Dynamics NAV 2009 Demo Database


    By default when you are installing the demo database by the installation program you can only install one Demo Database. But if you would like to have more than one Demo Database to try different things in, how to accomplish that? I assume that you know that you can create a new company in the classic client, but you will then not get the demo data. The solution is simple to use SQL Server Management Studio to attach more than one version of the Demo Database.

    1. Stop the SQL Server
    2. Make a copy the database files in "C:\Program Files\Microsoft Dynamics NAV\60\Database" to new location. For example "C:\NAVTestDB\"
    3. Start the SQL Server
    4. Start SQL Server Management Studio and connection to the instance where you have installed the other Demo Database.
    5. Right click on "Databases" and select "Attach" and click "Add". Then pick the database file that you did copy to new location.
    6. Change the "Attach As" column for the new Demo Database file to "NAVDEMO"
    7. Press OK
    8. Update the Microsoft Dynamics NAV server configuration file to use the new database by open "CustomSettings.config" file in notepad. The file is normally located under "C:\Program Files\ Microsoft Dynamics NAV\60\Service".
    9. Locate the DatabaseName key.
    10. Change the value attribute to "NAVDEMO"
    11. Restart the "Microsoft Dynamics NAV Server" service in the Windows Service manager
  • Microsoft Dynamics NAV Team Blog

    Installing Business Notification with SQL Server 2008


    We are glad to announce that compatibility between Business Notification and SQL Server 2008 is as of now verified and confirmed. Business Notification can run on SQL Server 2008 provided that the 2 following components are also installed:


    -          SQL Server Notification Services 2005

    -          SQL Server 2005 Service Pack 3.


    Notification Services is no longer part of SQL Server 2008. What SQL Server 2005 Service Pack 3 does is that it allows Notification Services 2005 to run with the SQL Server 2008 database engine. For further information, please also refer to "What's New in SQL Server 2005 SP3":



    While refering to the Business Notification Installation Guide (https://mbs.microsoft.com/customersource/documentation/setupguides/installationmanualsnav2009.htm ) as your main source of information, below are the steps that you need to include in the installation process in order to use SQL Server 2008.


    Installation steps:


    1. Install SQL Server 2008.

    2. Install SQL Server 2005 Notification Services only. When the SQL Server 2005 setup is started, a list of installation components is available. Selected Notification Services only and complete the installation.

    3. Apply SQL Server 2005 Service Pack 3. This can be downloaded from here:



    Continue with the steps described in the Business Notification Installation Guide.


    Smaranda Calin

    Program Manager

  • Microsoft Dynamics NAV Team Blog

    Filtering out blank fields


    Some of you have noticed that the Chart displayed in “Customer Order - Summary” contained a series label called Series 1.


    Well the reason for that being shown is because we have missed to filter out all customer with have no data in the field: Chart_SalesOrderAmountLCY.Value

    So how is that actually done? Well let me show you:

    1. Design Report 70000

    2. Select “View / Layout”

    3. Right click the chart in the bottom of the report


    4. Select “Filters” tab

    5. Type the follow:





    6. With this filter we now filter out where "Chart_SalesOrderAmountLCY.Value” is equal blank.


    7. Now save and compile the report and display in RoleTailored client. Now only customers with outstanding orders are shown in the chart.


    I have updated the demo reports package to reflect this change.

    The reports can be downloaded from here.


    Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

  • Microsoft Dynamics NAV Team Blog

    Failed to execute SQL string when Installing Dynamics NAV 2009


    One not complete uncommon error when installing Dynamics NAV 2009 is the one bellow:

    Microsoft Dynamics NAV 2009 Build 27808
    Error Report
    SQL Server option
    Microsoft Dynamics NAV 2009 Components for Microsoft SQL Server
    Fatal error during installation.

    Error -2147217865: failed to execute SQL string, error detail: Invalid object name ‘master.sys.objects'., SQL key: DropXpNdoGroups SQL string: IF EXISTS (SELECT * FROM [master].[sys].[objects] WHERE name = ‘xp_ndo_enumusergroups') EXEC sp_dropextendedproc xp_ndo_enumusergroups
    Cronus Sample Database for Microsoft Dynamics NAV 2009
    Fatal error during installation.

    Error -2147217865: failed to execute SQL string, error detail: Invalid object name ‘master.sys.databases'., SQL key: StopIfDatabaseExist SQL string: IF EXISTS (SELECT * FROM [master].[sys].[databases] WHERE name = ‘Demo Database NAV (6-0)') RAISERROR (N'A database with name %s already exists.',20,1,'Demo Database NAV (6-0)') WITH LOG
    Fatal error during installation.


    The problem is normally wrong version of SQL Server or access right problems. The first problem is easy to solve since you only need to ensure that you have SQL Server/Express 2005 or 2008 installed or no SQL Server installed at all. The SQL Server need to user service account "NETWORK SERVICE". The user that is installing Dynamic NAV 2009 needs to be sysadmin for the server and on the system database "master".

Page 32 of 43 (637 items) «3031323334»