Sync timeouts with ACT 2011 SP1 HF6
We're experiencing a sync issue that sounds a lot like KB28293, which has this description:
"Large Number of Files in Synchronization After Upgrading to Sage ACT! 2011 SP1 Hot Fix 5 or Sage ACT! 2012 Results in Synchronization Timing Out or 'Out of Memory' Error"
However, we have ACT! 2011 SP1 Hot Fix 6 on all four machines.
In particular, the two of us who sync via a VPN are timing out during the database updates phase. The one user who is on the LAN with the server can sync successfully.
Could the VPN be an issue if there are delays to/from the server?
Is it possible that that the HotFix 5 problem that caused escalating sync times is causing our issues even though we have HF 6 installed? Or should we look somewhere else for cause?
"Large Number of Files in Synchronization After Upgrading to Sage ACT! 2011 SP1 Hot Fix 5 or Sage ACT! 2012 Results in Synchronization Timing Out or 'Out of Memory' Error"
However, we have ACT! 2011 SP1 Hot Fix 6 on all four machines.
In particular, the two of us who sync via a VPN are timing out during the database updates phase. The one user who is on the LAN with the server can sync successfully.
Could the VPN be an issue if there are delays to/from the server?
Is it possible that that the HotFix 5 problem that caused escalating sync times is causing our issues even though we have HF 6 installed? Or should we look somewhere else for cause?
Mike Lazarus
Can you post the sync log?
ASKER
I'll turn the option on and try again later today...
Also ... what tye of sync: Application, Network Service or Internet Service?
ASKER
Here are the logs from the server for several recent attempts.
Re the type of sync, I don't recall selecting one of the three options you mentioned, Mike. We are simply synchronizing across the network (LAN or VPN) from remote databases to a central database.
Re the type of sync, I don't recall selecting one of the three options you mentioned, Mike. We are simply synchronizing across the network (LAN or VPN) from remote databases to a central database.
======== SYNC SESSION - 6/18/2012 2:50:22 PM ========
[ Info | 6/18/2012 2:50:22 PM ]Message: Synchronization started.
[ Info | 6/18/2012 2:50:23 PM ]Message: Server object created.
[ Info | 6/18/2012 2:50:23 PM ]Message: Checking if schema changes are available for sync.
[ Info | 6/18/2012 2:50:30 PM ]Message: Server establishing synchronization with remote database: HELMERS8_2011
[ Info | 6/18/2012 2:50:30 PM ]Message: Server generated remote sync session identifier: 17f716ad-0f64-4750-b7d9-2d992c242c55:<Helmers8_2011>
[ Info | 6/18/2012 2:50:37 PM ]Message: Checking if data changes are available for sync.
[ Info | 6/18/2012 2:50:58 PM ]Message: Server initialized database send session: 24
[ Error | 6/18/2012 3:51:00 PM ]Message: Server initialization failed. Synchronization timed out.
======== SYNC SESSION - 6/14/2012 6:07:40 PM ========
[ Info | 6/14/2012 6:07:40 PM ]Message: Synchronization started.
[ Info | 6/14/2012 6:07:40 PM ]Message: Server object created.
[ Info | 6/14/2012 6:07:41 PM ]Message: Server establishing synchronization with remote database: HELMERS8_2011
[ Info | 6/14/2012 6:07:41 PM ]Message: Server generated remote sync session identifier: 7e546f60-b57d-4091-9508-6c7bbeca39c4:<Helmers8_2011>
[ Info | 6/14/2012 6:07:44 PM ]Message: Checking if data changes are available for sync.
[ Info | 6/14/2012 6:07:54 PM ]Message: Server initialized database send session: 24
[ Error | 6/14/2012 7:07:54 PM ]Message: Server initialization failed. Synchronization timed out.
======== SYNC SESSION - 6/14/2012 5:43:33 PM ========
[ Info | 6/14/2012 5:43:33 PM ]Message: Synchronization started.
[ Info | 6/14/2012 5:43:33 PM ]Message: Server object created.
[ Info | 6/14/2012 5:43:34 PM ]Message: Checking if schema changes are available for sync.
[ Info | 6/14/2012 5:43:36 PM ]Message: Server establishing synchronization with remote database: HELMERS8_2011
[ Info | 6/14/2012 5:43:36 PM ]Message: Server generated remote sync session identifier: 98afff11-4819-4c9b-a9ba-d62c878d6c92:<Helmers8_2011>
[ Info | 6/14/2012 5:43:39 PM ]Message: Checking if data changes are available for sync.
[ Info | 6/14/2012 5:44:00 PM ]Message: Server initialized database send session: 24
[ Error | 6/14/2012 6:44:00 PM ]Message: Server initialization failed. Synchronization timed out.
======== SYNC SESSION - 6/14/2012 3:30:06 PM ========
[ Info | 6/14/2012 3:30:06 PM ]Message: Synchronization started.
[ Info | 6/14/2012 3:30:06 PM ]Message: Server object created.
[ Info | 6/14/2012 3:30:06 PM ]Message: Checking if schema changes are available for sync.
[ Info | 6/14/2012 3:30:10 PM ]Message: Server establishing synchronization with remote database: RYANC_06_01_2012
[ Info | 6/14/2012 3:30:10 PM ]Message: Server generated remote sync session identifier: 604ada8e-b7a5-4f52-aedd-66558208fdee:<ryanc_06_01_2012>
[ Info | 6/14/2012 3:30:14 PM ]Message: Checking if data changes are available for sync.
======== SYNC SESSION - 6/13/2012 4:45:52 PM ========
[ Info | 6/13/2012 4:45:52 PM ]Message: Synchronization started.
[ Info | 6/13/2012 4:45:52 PM ]Message: Server object created.
[ Info | 6/13/2012 4:45:52 PM ]Message: Checking if schema changes are available for sync.
[ Info | 6/13/2012 4:46:00 PM ]Message: Server establishing synchronization with remote database: HELMERS8_2011
[ Info | 6/13/2012 4:46:00 PM ]Message: Server generated remote sync session identifier: 2d050e9f-14ad-4396-952c-04937e71e243:<Helmers8_2011>
[ Info | 6/13/2012 4:46:04 PM ]Message: Checking if data changes are available for sync.
[ Info | 6/13/2012 4:46:30 PM ]Message: Server initialized database send session: 24
[ Error | 6/13/2012 5:46:30 PM ]Message: Server initialization failed. Synchronization timed out. ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'll try increasing the sync timeouts.
Re your question about sync type: I'm only offered one choice: "Network (Inside firewall)", which makes it sound like I'm doing Network syncs. But when I read through various KB articles, it sounds as though Network sync is only available with ACT Premium.
Because I'm using ACT Pro, can I assume that I'm using Application sync despite seeing "Network (Inside firewall)" during sync setup?
Re your question about sync type: I'm only offered one choice: "Network (Inside firewall)", which makes it sound like I'm doing Network syncs. But when I read through various KB articles, it sounds as though Network sync is only available with ACT Premium.
Because I'm using ACT Pro, can I assume that I'm using Application sync despite seeing "Network (Inside firewall)" during sync setup?
Application sync is the only option for Pro, yes
ASKER
I bumped
DatabaseCommandTimeOut.Lon
from 3600 to 5000 because the logs I posted above show a timeout at one hour. The new result is simply a timeout that occurs after one hour 23 minutes instead of one hour (see last two sync attempts below).
Is it reasonable to just try a larger number?? If everything is working properly, the Database Modifications phase normally just takes a couple of minutes.
Anything else I should try? Thanks...
DatabaseCommandTimeOut.Lon
from 3600 to 5000 because the logs I posted above show a timeout at one hour. The new result is simply a timeout that occurs after one hour 23 minutes instead of one hour (see last two sync attempts below).
Is it reasonable to just try a larger number?? If everything is working properly, the Database Modifications phase normally just takes a couple of minutes.
Anything else I should try? Thanks...
======== SYNC SESSION - 6/21/2012 1:26:38 PM ========
[ Info | 6/21/2012 1:26:38 PM ]Message: Sync remote client created.
[ Info | 6/21/2012 1:26:39 PM ]Message: Checking if schema changes are available for sync.
[ Info | 6/21/2012 1:26:59 PM ]Message: Client establishing synchronization with server database: HCG_PRIMARY_2011
[ Info | 6/21/2012 1:27:03 PM ]Message: Initial Handshake completed.
[ Info | 6/21/2012 1:27:03 PM ]Message: Checking if data changes are available for sync.
[ Info | 6/21/2012 1:27:06 PM ]Message: Client initialized database send session: 23
[ Info | 6/21/2012 1:27:16 PM ]Message: Client initialized.
[ Info | 6/21/2012 1:27:16 PM ]Message: Client schema synchronized.
[ Error | 6/21/2012 2:50:49 PM ]Message: Synchronization has failed. Server Error Description: Synchronization timed out.
======== SYNC SESSION - 6/18/2012 2:50:12 PM ========
[ Info | 6/18/2012 2:50:12 PM ]Message: Sync remote client created.
[ Info | 6/18/2012 2:50:21 PM ]Message: Checking if schema changes are available for sync.
[ Info | 6/18/2012 2:50:26 PM ]Message: Client establishing synchronization with server database: HCG_PRIMARY_2011
[ Info | 6/18/2012 2:50:35 PM ]Message: Initial Handshake completed.
[ Info | 6/18/2012 2:50:35 PM ]Message: Checking if data changes are available for sync.
[ Info | 6/18/2012 2:50:37 PM ]Message: Client initialized database send session: 23
[ Info | 6/18/2012 2:50:46 PM ]Message: Client initialized.
[ Info | 6/18/2012 2:50:47 PM ]Message: Client schema synchronized.
[ Error | 6/18/2012 3:50:58 PM ]Message: Synchronization has failed. Server Error Description: Synchronization timed out. ASKER
BTW, the timeout values on both the server and remote ends are:
<add key="DatabaseCommandTimeOu
<add key="DatabaseConnectionTim
<add key="DatabaseCommandTimeOu
<add key="DatabaseCommandTimeOu
<add key="DatabaseConnectionTim
<add key="DatabaseCommandTimeOu
Bump them all up and give it one go ...
ASKER
Tried these values with no change:
<add key="DatabaseCommandTimeOu
<add key="DatabaseConnectionTim
<add key="DatabaseCommandTimeOu
I've reverted to merging databases and creating new remotes. The problem I foresee is that I merged and created new remotes two months ago. Syncing worked for a while -- then the timeouts began. If the situation repeats yet again, then there has to be an underlying database or sync issue -- something like the one that is allegedly fixed in HF6 per KB28293.
<add key="DatabaseCommandTimeOu
<add key="DatabaseConnectionTim
<add key="DatabaseCommandTimeOu
I've reverted to merging databases and creating new remotes. The problem I foresee is that I merged and created new remotes two months ago. Syncing worked for a while -- then the timeouts began. If the situation repeats yet again, then there has to be an underlying database or sync issue -- something like the one that is allegedly fixed in HF6 per KB28293.
Keep the timeouts high ... if might have damaged the remotes with a previous failed sync and this might prevent it happening
ASKER
OK, will do. BTW, no surprise but syncing is working fine since merging and creating new remotes.
Question: do you know what timeout applies if the specific values on the server and a remote are different?
Question: do you know what timeout applies if the specific values on the server and a remote are different?
Both ... in different ways.
Not sure of the specific spots they kick in - if it happens again, I'll do some tests and find out.
Not sure of the specific spots they kick in - if it happens again, I'll do some tests and find out.