This article applies to Microsoft Dynamics NAV for all countries and all language locales.
When the Outlook Synchronization process is run from Microsoft Office Outlook to synchronize with Microsoft Dynamics NAV 5.0 with Service Pack 1 (SP1), with Microsoft Dynamics NAV 2009 or with Microsoft Dynamics NAV 2009 with SP1, the Microsoft Dynamics NAV Application Server (NAS) produces the following error message:
The response from Microsoft Dynamics NAV has not been received because of connection timeout. Please check if the Microsoft Dynamics NAV server is running and try again later. If the problem persists increase the timeout value in the configuration file.
This problem occurs if the Change Log Entry table (405) contains a large number of records.
This problem occurs because of one of the following reasons:
The last synchronization attempt was not successful.
If the synchronization process has not been run recently, a full table scan is performed to verify the changes in the Change Log Entry table (405). This causes a time-out error when the Change Log Entry table contains a large number of records.
A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV service pack or the next version that contains this hotfix.
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.
To implement this hotfix, you must have a developer license.
We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
The Modify permission for the object that you will be changing.
The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.
Note You do not have to have rights to the data stores unless you have to perform data repair.
Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To install this hotfix, change the code in the RemoveChangeLogDuplicates function of the Outlook Synch. NAV Mgt codeunit (5301) as follows: Existing code
...ChangeLogEntry.SETCURRENTKEY("Table No.","Date and Time");TempChangeLogEntry.RESET;TempChangeLogEntry.DELETEALL;IF ChangeLogEntry.FIND('+') THEN REPEAT IF ChangeLogEntry."Primary Key" <>TempChangeLogEntry."Primary Key" THEN BEGIN TempChangeLogEntry.SETRANGE("Primary Key",ChangeLogEntry."Primary Key"); IF NOT TempChangeLogEntry.FIND('-') THEN BEGIN TempChangeLogEntry.INIT; TempChangeLogEntry := ChangeLogEntry; TempChangeLogEntry.INSERT; END; END; UNTIL ChangeLogEntry.NEXT(-1) = 0;TempChangeLogEntry.RESET;...
...ChangeLogEntry.SETCURRENTKEY("Table No.","Date and Time");ChangeLogEntry.SETFILTER("Date and Time" , '>=%1', OSynchUserSetup."Last Synch. Time"); // Add this line. TempChangeLogEntry.RESET;TempChangeLogEntry.DELETEALL;IF ChangeLogEntry.FIND('+') THEN REPEAT IF ChangeLogEntry."Primary Key" <>TempChangeLogEntry."Primary Key" THEN BEGIN TempChangeLogEntry.SETRANGE("Primary Key",ChangeLogEntry."Primary Key"); IF NOT TempChangeLogEntry.FIND('-') THEN BEGIN TempChangeLogEntry.INIT; TempChangeLogEntry := ChangeLogEntry; TempChangeLogEntry.INSERT; END; END; UNTIL ChangeLogEntry.NEXT(-1) = 0;TempChangeLogEntry.RESET;...
You must have one of the following products installed to apply this hotfix:
Microsoft Dynamics NAV 2009 SP1
Microsoft Dynamics NAV 2009
Microsoft Dynamics NAV 5.0 SP1
You cannot remove this hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.