Baseline implementation utilizing Outlook Synchronization in Dynamics NAV 2009 R2

Baseline implementation utilizing Outlook Synchronization in Dynamics NAV 2009 R2

Rate This
  • Comments 0

 

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

Leave a Comment
  • Please add 1 and 5 and type the answer here:
  • Post