April, 2012

  • Microsoft Dynamics NAV Team Blog

    Complicating the synchronization setup with newly created entities

    • 0 Comments

    During one of the conferences I attended where I spoke about Outlook Synchronization, the request was to talk about the creation of new entities and extending the solution with new fields. Let’s do this now with a new blog. First of all, you need to ensure you have applied latest patches and fixes. For this you can use my earlier blog I created Baseline implementation utilizing Outlook Synchronization in Dynamics NAV 2009 R2, especially we must apply the following code adjustment discussed in the following KB article 2703500 Empty contacts are created in dedicated Outlook Synch folder when you perform the Outlook synchronization in Microsoft Dynamics NAV 2009

    The scenario is as follows. We want to split the Dynamics NAV contacts of person type in Belgium ones and Dutch ones. We first delete the CONT_PERS entity. To do so, start up RTC and select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. User Setup. Manually select all lines and either press CTRL+DEL or right click and select Delete. Second step is to delete the CONT_PERS entity. To do so, follow these steps. In RTC, select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, select CONT_SP and press CTRL+SHIFT+E or right click the entity and select Delete. Confirm the deletion that collections will be updated automatically.

    Result of this is that we now have the following standard entities: CONT_SP, CONT_COMP, TASK and APP. Let us now create a two new entities. In RTC, select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, press New and type in a unique code and a unique description. E.g.:

    image

    After that select Related Information, Synch. Entity, Reset to defaults, select Microsoft Dynamics NAV Contacts of the Person type and press OK.

    NOTE: you should do similar steps to create another entity for the Dutch contacts of person type.

    Now it is time to add dependencies for APP entity and TASK entity. To do so, in RTC select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, select APP entity, press Actions, select Edit or right click on the entity and select Edit. You could also select the entity and press CTRL+SHIFT+E. Now select the first line and select Recipients under Outlook Collection. Press SHIFT+F8 or right click on Recipients and select DrillDown.

    Now ensure the Table Relations do look like the following:

    image

    We also need to change Table Relations for the Links of the TASK entity. To do so, in RTC select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, select TASK entity, press Actions, select Edit or right click on the entity and select Edit. You could also select the entity and press CTRL+SHIFT+E. Now select the first line and select Links under Outlook Collection. Press SHIFT+F8 or right click on Links and select DrillDown.

    Now ensure the Table Relations do look like the following:

    image

    Last but not least we need to add the Outlook Synchronization Users. In RTC, select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. User Setup. For every entity, add a line. E.g.:

    image

    To test this new configuration, you could try the following.

    1. (Re)Configure the Outlook Add-In so that they are populated with new folders
    2. Ensure there are contacts where Country/Region Code do have NL / BE set
    3. Perform a synchronization

    Result:
    The Dynamics NAV contacts of company type assigned to salesperson Marco Mels do synchronize correctly.
    The Belgium Dynamics NAV contacts of person type do synchronize correctly.
    The Belgium Dynamics NAV contacts of person type do synchronize correctly.

    4. Create a To-Do of meeting type and add two attendees where one attendee is a Dutch contact of person type and the other attendee is a Belgium contact of person type
    5. Perform a synchronization

    Result:
    A calendar entry is created in Outlook with the meeting organizer which is the salesperson Marco Mels and the Belgium and Dutch contact of person type

    Regards,

    Marco Mels
    CSS EMEA

    This posting is provided "AS IS" with no warranties, and confers no rights

  • Microsoft Dynamics NAV Team Blog

    "CREATE USER" SQL Error when creating and Synchronising New User in Dynamics NAV 2009

    • 2 Comments

     

    In Dynamics NAV 2009 Service Pack 1 also later Builds on SQL Server 2005, SQL Server 2008 also SQL Server 2008 R2, when a new user is created and synchronised sometimes following error is thrown.

     

    15023, "42000" User, group, or role '<Name>' already exists in the current database.

    SQL: CREATE USER [<Name>] FOR LOGIN [<Name>]

     

      

    Possible Reason of the Error:

    In this NAV Version when a new user is created in NAV Database it is also added in Master Database, but when deleting the same User from NAV Client it is not deleted from Master Database. It might also be possible that this user was manually added to Master Database or already existing due to other requirements.

    So once you create this user again in NAV it is not checked if the User already exists in Master Database. So this error is thrown by the NAV Client.

     

    Solution:

    To void this error please check if this User exists already in the Master Database, if yes delete the User first from the Master Database and then add the user from NAV Client and this time Synchronisation should work without error.

     

  • Microsoft Dynamics NAV Team Blog

    Jet Express - Improved User Interface for the General Ledger Wizard

    • 0 Comments

    The General Ledger wizard included in Jet Reports Express for Microsoft Dynamics NAV has been redesigned to provide ease-of-use benefits and offer consistent styling with the Table Builder.

     

    Key improvements include:

    • Generic description of the Global and Advanced Dimension code captions (e.g. “Global Dimension 1” or “View Dim 1”) has been replaced by the specific dimension code captions (e.g. “Department Code” or “Business Group Code”) (see fig 1).  
    • Advanced capabilities are exposed to make them easier to discover and use.  Examples include:
      • Allowing special characters (e.g.  “&”) in a filter
      • Using Microsoft Excel’s named ranges in filters
    • Improved descriptions of what is retrieved when you use the General Ledger wizard.  This provides the users with a simpler understanding of what is being retrieved (see fig 2).

    Fig 1 – Updated Wizard with specific dimension code highlighted.

    Fig 2. Clear decriptions of what is retreived.  This message varies based on whether the user enters a start date, and end date, both or neither.

  • Microsoft Dynamics NAV Team Blog

    Baseline implementation utilizing Outlook Synchronization in Dynamics NAV 2009 R2

    • 0 Comments

     

    Some people asked me to update the original blog posting Outlook Synchronization and baseline implementation for Dynamics NAV 5.0 SP1 and Dynamics NAV 2009 SP1 since Microsoft did release Dynamics NAV 2009 R2. Let’s take the opportunity to mention latest news regarding Outlook Synchronization solution in a complete new blog, specifically written for Dynamics NAV 2009 R2.

    What do you need for Outlook Synchronization as a minimum:

    - Dynamics NAV Application Server of build 32012 or Dynamics NAV NST of build 32012 
    - Dynamics NAV CSIDE Client of build 32012 or Role Tailored Client of build 32012
    - Office 2007 with latest service pack and latest application patches or 32-bit Office 2010 with latest service pack and latest application patches
    - Outlook Add-In of build 33240 (KB 2675368)

    Hot fixes to be applied:

    2675368 Outlook Synchronization: latest Outlook Add-In Dynamics NAV 2009 R2
    2288271 A time-out error occurs when the Outlook Synchronization process is run from Microsoft Office Outlook to synchronize with Microsoft Dynamics NAV
    2291055 "Contact No. '[Contact_number]' does not exist" error message when you perform an Outlook synchronization to synchronize with Microsoft Dynamics NAV 2009 SP1
    2703500 Empty contacts are created in dedicated Outlook Synch folder when you perform the Outlook synchronization in Microsoft Dynamics NAV 2009
    2692299 "The date is invalid" error message when you perform the Outlook synchronization for an entity that contains a date field in Microsoft Dynamics NAV 2009 
    2642239 "Et Outlook-element kan ikke synkroniseres, fordi feltet Virksomhedsnr. ikke kan behandles" error message when you synchronize contacts in the Danish version of Microsoft Dynamics NAV 2009

    Outlook Synchronization via web services:

    For implementation via web services, you need to do the following:
    1. start up Dynamics NAV RTC and ensure language is set to the Dynamics NAV client language you are synchronizing with
    2. ensure Regional Settings are set to to the Dynamics NAV client language you are synchronizing with
    3. ensure entities were originally populated with language settings same as the Dynamics NAV client language you are synchronizing with
    4. ensure the two web services do start up with a domain user account or a user account in format MACHINENAME\username
    5. ensure this domain user name or local user name does have sufficient permissions in Dynamics NAV

    If you apply build 32558 via KB article 2575205, the web services changes to EN-US. The reason for this is described below via an extract of the KB:

       (…)
    Assume that you use an application that communicates with the Microsoft Dynamics NAV web service. In this situation, the date format that is accepted by the web service is changed after you change the language in the RoleTailored client (RTC). It depends on the RoleTailored client language that you use in the last session. Therefore, if the current date format that you use differs from the date format that is accepted, you receive an error message in metadata.
    This problem occurs in the following products:  

    • Microsoft Dynamics NAV 2009 R2
    • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

    (…)

    This web service design change does break Outlook Synchronization and produces an error message like the one below taken from a German Dynamics NAV client:

    NST Asynch-Aufruf abgeschlossen. Fehler: A '=' is missing in TransferFormulaData. WHERE(Art=CONST(1),Verkäufercode=CONST(PS)); .

    There are currently two workarounds that will help you to resolve the issue:

    1. Configure Outlook Synch User Setup in English
    2. Apply a later hot fix that brings back the web service in the old state

    Ad. 1 Configure Outlook Synch User Setup in English
    1. Change application language to English United States
    2. Remove all lines from Outlook Synch User Setup
    3. Reset all entities to default values in order of entity:

    - Salespersons
    - Company contacts
    - Person contacts
    - Tasks
    - Appointments

    4. Add all lines in the Outlook Synch User Setup

    NOTE: the description and values of conditions, etc. are now in English

    5. Refresh Folders in the Outlook Add-In on the users workstation

    Ad. 2 Apply a later hot fix that brings back the web service in the old state
    Apply build 33137 via KB article 2667345

    This does bring the web service in it’s old state. The current recommendation is to bring back the web service to its old state when utilizing the web service for Outlook Synchronization. This issue will be readdressed in Dynamics NAV 2013.

    Outlook Synchronization via Application Server

    For implementation via application server, you need to do the following:
    1. start up Dynamics NAV CSIDE client and ensure language is set to the Dynamics NAV client language you are synchronizing with
    2. ensure Regional Settings are set to to the Dynamics NAV client language you are synchronizing with
    3. ensure entities were originally populated with language settings same as the Dynamics NAV client language you are synchronizing with
    4. ensure the application server service do start up with a domain user account or a user account in format MACHINENAME\username
    5. ensure this domain user name or local user name does have sufficient permissions in Dynamics NAV
    6. copy fin.stx from %programfiles%\Microsoft Dynamics NAV\60\Classic\xxx\ to %programfiles%\Microsoft Dynamics NAV\60\Application Server\
    7. copy cronus.flf rom %programfiles%\Microsoft Dynamics NAV\60\Classic\ to %programfiles%\Microsoft Dynamics NAV\60\Application Server\

    NOTE: on 64-bit systems 6. and 7. would have to be changed to:
    6. copy fin.stx from %programfiles(x86)%\Microsoft Dynamics NAV\60\classic\xxx\ to %programfiles(x86)%\Microsoft Dynamics NAV\60\Application Server\
    7. copy cronus.flf from %programfiles(x86)%\Microsoft Dynamics NAV\60\classic\ to %programfiles(x86)%\Microsoft Dynamics NAV\60\Application Server\

    NOTE: for some reasons it may be necessary to upload a different license -not matching the Dynamics NAV client language you are synchronizing with, to the SQL Server; at that point a language error could occur.

    8. ensure the Regional Settings are correct for the domain user account or local user account that starts up the application server service on the server or workstation that hosts the application server service responsible for Outlook Synchronization

    Regards,

    Marco Mels
    CSS EMEA 

    This posting is provided "AS IS" with no warranties, and confers no rights

  • Microsoft Dynamics NAV Team Blog

    Outlook Synchronization: Synchronization conflicts resolution

    • 0 Comments

    Resolving conflicts can be configured in the Outlook Add-In. There are four ways of doing this:

    1. Replace Outlook items with Microsoft Dynamics NAV records
    2. Replace Microsoft Dynamics NAV records with Outlook items
    3. Replace older entities with newer ones
    4. Replace conflicts manually

    image

     

    If you choose to Resolve conflicts manually, results could be presented to you as a conflict / error in the Outlook Add-In troubleshooting window:

     

    image

    In this scenario, the end user will have to decide what items he wants to keep. If the end user ignores to review the items in the Conflicts area of Troubleshooting part of the Outlook Add-In, no changes will be made. Furthermore, there is a difference in conflict handling when performing a Full Synchronization compared to a (normal) Synchronization.

    A change will only be interpreted as a conflict if there are changes on both the Outlook side and the Dynamics NAV side when the synchronization happens. Therefore, when utilizing normal synchronization, the change will not be interpreted as a conflict if there is only a data entry change in one of the systems. The full synchronization acts a bit differently - as it validates all entries as being changed - and if there then is a difference between the two entries - it will interpret it as a conflict. Hence an entry in the Conflicts area of Troubleshooting part of the Outlook Add-in will occur.

    Regards,

    Marco Mels
    CSS EMEA

    This posting is provided "AS IS" with no warranties, and confers no rights

  • Microsoft Dynamics NAV Team Blog

    Jet Reports Express for Microsoft Dynamics NAV is Now Available in 5 More Countries

    • 1 Comments

    We are pleased to announce that Jet Reports Express for Microsoft Dynamics NAV is now available for Czech, Finnish, Hungarian, Icelandic, and Greek languages.

    As of March 30th 2012, Jet Reports Express for Microsoft Dynamics NAV has been updated to include Czech, Finnish, Hungarian, Icelandic, and Greek languages and is now available in all countries having a Microsoft localized version of Microsoft Dynamics NAV. 

    This very popular Microsoft Excel add-in for ad-hoc reporting and analysis is available as a download on Customer Source and Partner Source for no additional costs for customers on an active Business Ready Enhancement Plan. 

  • Microsoft Dynamics NAV Team Blog

    NAV 3-tier troubleshooting with PowerShell

    • 0 Comments

     

    Whenever there is a problem with a NAV 3-tier setup, typically we check the same usual things to begin with (SPNs, Delegation, NAV Service account, etc).

    Below is a link to a PowerShell script that collects some of this information for you. So rather than logging on to a customer's NAV Server, then Domain Controller, then looking around in Services, ADSIEdit, Users and Computers, etc, just run the script and it collects most of the usual information in txt files.

    There is also the situation where you can't access the remote system that you need to troubleshoot. Then, explaining a local admin what information you want them to look up can easily become a very long email and/or phone call. Instead of that, just ask them to run the script and send the results back.

    The script collects AD-information specific to setting up NAV Server in 3-tier, which means SPNs, NAV Service information, Delegation permissions and more. In best cases (and with a bit of luck!) it collects enough information to pinpoint where a problem might be. In worst cases, at least it gives you an overview of what accounts and permissions are involved, so when you proceed to troubleshoot further, at least you have some ideas of the basic setup.

     

    How it works


    You must run the script from the machine where NAV Server is running.
    Copy the script from the link below into a new folder, for example C:\NAVCheck\.
    Open a PowerShell Command prompt and move into this folder (CD C:\NAVCheck).
    Give your PowerShell Command prompt access to execute scripts:
      Set-ExecutionPolicy Unrestricted
    Run the script.

    The user running the script must of course be allowed to log on the NAV Server, but they do not need to be Domain Admins.

     

    What it collects


    The script creates a subfolder called "Results". This folder contains the following:

    •   A subfolder for each NAV Server on the machine. This subfolder contains CustomSettings.config and a txt file with a file list of files and versions in that folder.
    •   A Txt file with an overview of what NAV Servers are installed as services on the machine, and which user account each service is running under.
    •   Two Txt files for each user that is identified as running a NAV Service. These files contains the following information for that user:
      •   SPNs
      •   UserAccountControl
      •   msDS-AllowedToDelegateTo
    •   SetSPNX.txt (check for duplicate SPNs on the domain).

     

    What to check


    Check "SetSPNX.txt" first. A common issue is that the domain has duplicate SPNs created for different accounts. This is also an easy check you can do by just running "SetSPN -x" from a command prompt from any machine on the domain. Any duplicate SPNs must be resolved.

    What SPNs are created for the user running the NAV Server (if any!).

    UserAccountControl is a hash value that shows the user account properties, including "TRUSTED_FOR_DELEGATION", "DONT_EXPIRE_PASSWORD", "PASSWORD_EXPIRED", and more which could prevent a NAV 3-tier setup from working. NB: "TRUSTED_FOR_DELEGATION" is set only if the user is set up for unconstrained delegation (allowed to delegate to any service). If the user is set up for constrained delegation, then check msDS-AllowedToDelegateTo. You can use this link to decode the UserAccountCcontrol value.

    msDS-AllowedToDelegateTo shows what services the user is allowed to delegate to. Check that at least SQL Server is allowed, and in case of any file shares, also the cifs service (see here for more details on managing network files in RTC).

     

    Get the script

    The script can be copied / downloaded from here:

    Script for NAV 3-tier troubleshooting (PowerShell).

    This link also has further instructions and links at the bottom to further resources.

     

     

    As usual this script is of course supplied "as is" with no support or warranties. If you think that the script could be improved and/or collect different / further information, then please do add comments below.

     

     

     

    Lars Lohndorf-Larsen
     
    Dynamics NAV Support EMEA

Page 1 of 1 (7 items)