06-06-2008 02:37 PM
06-07-2008 12:48 PM
Are these all new records are updates to current records? You might try using itImport. The Pro edition has a setting to reduce the amount of transactions for sync users
How big is the ADF file in GB (both Publisher and Subscriber)? Remember, when running on a non-server operating system, SQL Server 2005 is limited to 4GB
You could try increasing the TimeOutLong value in ACTDIAG as per this ACT! Knowledge Base article - http://tinyurl.com/4nsog5
06-07-2008 01:35 PM
06-07-2008 01:48 PM
The Pro version of itImport has an option to only log fields that are changed... this reduces the amount of data to sync.
SQL 2005 Express is always used if the operating system is not Windows 2003
I'd bump the 3600 much bigger - both server and remote
The only other option would be to do the imports 2500 at a time, then a sync, then the next lot
06-09-2008 09:12 AM
Increasing timeout values for syncing in actdiag on the server will only affect application sync. To increase timeout with network sync, you will need to modify the Act.Framework.Syncrhonization.Service.exe.config file located where you've installed the service (default: C:\Program Files\ACT\Act for Windows\ACT Network Sync).
First stop and close ACT! Network Sync Service. Open the config file in notepad and add these triggers between </runtime> and </configuration>
<!-- Database Timout values are in seconds so a value of 30 will be 30 seconds -->
<add key="DatabaseCommandTimeOut.Default" value="360"/>
<add key="DatabaseConnectionTimeOut.Default" value="360"/>
<add key="DatabaseCommandTimeOut.Long" value="3600"/>
As you can see, timeout values have already been increased from the default value 30.