Microsoft Dynamics NAV 2009 Outlook Synchronization Timeout

easton21jd

Outlook Synchronization Timeout Issue:

Running Microsoft Dynamics NAV 2009 SP1 in a three tier environmen:
- Application server
- SQL Database Server
- Clients

Outlook synchronization has been installed, NAS has been installed and running. In Outlook, Connection connects perfectly, but when I go to Synch I get the following error:

A Microsoft Dynamics NAV Synchronization Add-In Error Occurred
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. Please contact your system administrator.

Troubleshooting:
- Uninstalled/re-installed Outlook Synch
- Uninstalled/re-installed NAS
- Checked Microsoft Dynamics NAV Server is running -- it is!
- Increased the timeout value in the configuration file

I have literally tried everything that I can think of, looking for a little help. ](*,)

Thanks!

ara3n

Do you see any entry in table Job Queue Entry 472?

The way the integration works is that outlook using cfront or webservice to write a record into this table and has the xml data store in the xml table.

NAS is monitoring this table Job Queue Entry and when it finds the record it processes it and write back in Job Queue Response 473 table

I suggest to look and see that NAS is running with startup Parameter JOBQUEUE
and that it can processes and that records get inserted into this table.

Check event log as well on NAS.

easton21jd

Hi! And thank you for your help.

I checked Job Queue Entry (Table 472) and there is not a record in there.

I am currently using a startup parameter of OSYNCH, I will change to JOBQUEUE and try again.

I also do not see anything in the Event Log.

ara3n

what table are you synchronizing?

easton21jd

Please disregard the above post.

Update:
I switched over to the correct company #-o and took a look at Table 472 and yes I see a ton of records. I will switch my startup parameter from OSYNCH to JOBQUEUE and see if that works.

Thank you so much for your help.

Jesse

ara3n

It happens to all of us

easton21jd

HA!!

OK, so I changed the startup parameter to JOBQUEUE, tested the connection (Success!), clicked Synchronize and got the same message..

ara3n

can you clean up all the existing records?

easton21jd

Can do...just from table 472?

ara3n

473 and 472

easton21jd

OK....

So I cleaned out Tables 472 and 473 and still got the same error message.

If it helps - I click on the Synchronize button and what happens is that it goes through the Process Synchronization Schema sync just fine and then stalls once it gets to the Synchronizing Outlook Items. It does not move from that point and timesout.

Once again, thanks for you help!

Jesse

ara3n

this is what I suggest you should do to find out what is happening.
I'm assuming you have programming experince.

turn NAS off. Instead run the job queue codeunit from classic client.

I don't have NAV infront of me but the CU can be found if you design CU 1 and search for JOBQUEUE, You'll find the CU Variable that it run.

once you run the codeunit turn on the debugger and put a breakpoint where it finds a jobqueueentry record.

then try to synch from outlook. NAV will stop at the breakpoint and then follow through on what NAV is doing. and why it does not respond to outlook.

ara3n

THe CU is 448 Job Queue Dispacher

Put the breakpoint in function getnextrequest


IF Found THEN BEGIN
JobQueueEntry.CALCFIELDS(XML);
IF JobQueueEntry."Recurring Job" THEN BEGIN

shepardassoc

Hoping revive this post due to I'm having the same issues. I have a 5.00 SP1 client running on SQL 2005 sp3. We have a test environment in house that works great but on the client's live system I'm getting timeout message. It seems to be working and gets to the Outlook Items sync and times out. Whatever it is causes the NAS to hang to were I can't even restart the service, I have to manually end task on the nassql.exe and then restart. I'm using the OSYNCH parameter. From the look of CU 1 I'm not seeing any difference in OSYNCH and JOBQUE, so don't think that's an issue. I've got the SQL Remote Timeout set to 120s. Unfortunately it's so hard to trace where this is hanging up. Any help would be appreciated.

Thanks!!

ara3n

As mentioned above stop NAS.

make sure there are no records in the table JobQueueEntry table.

put breakpoints in CU 448

IF JobQueueEntry."Recurring Job" THEN BEGIN

turn on debuger.

run CU 448 from NAV client.

shepardassoc

I figured out the issue. I was getting ready to try your suggestion of trapping the code and thought let me check out the what it's trying to do real quick. After reviewing the code in CU "Outlook Synch. NAV Mgt." I noticed that it hits the Change Log Entry pretty hard to see what has been changed determining what needs to be sync'd. Makes sense the problem was the client had 4.5 million records in the change log entry table. 1.7 million on the contact table alone. I cleared out the change log entry and got it down to about 400K records, optimized the table, and rebuilt the SQL Statistics. It worked!!! I think the key here, because they 35 people actively hitting the contact table and it being set to record all contact table changes in the change log, will be to make sure the change log table is well maintained. Probably will need to be scrubbed every few months to keep it a reasonable size.

Thanks for the input!

ara3n

thanks for the update and glad you found the issue.