jceo
asked on
ACT! Database Becomes Un-Shared and unable to sync remote databases
ACT! Premium 2009 V11.1.183.0 hotfix 4 becomes un-shared each night since last weekend. The database is running on Windows Server 2003 R2. I have to log into ACT on the server each morning and share the database. Accept incoming syncs also went down around Tuesday and I had to restart that. Any ideas why this would suddenly start happening?
I have also started having issues with "Accept Incoming Syncs" it becomes unchecked and when I check it, I get the error: "Could not start sync server. ACT! has encountered an error, please check that the sync server port is able to listen for incoming connections. Contact your administrator for assistance." Not sure if there are related or not. The database will not currently allow syncs... when I try to accept incoming syncs I get the error: "Could not start sync server. ACT! has encountered an error, please check that the sync server port is able to listen for incoming connections. Contact your administrator for assistance."
I have also started having issues with "Accept Incoming Syncs" it becomes unchecked and when I check it, I get the error: "Could not start sync server. ACT! has encountered an error, please check that the sync server port is able to listen for incoming connections. Contact your administrator for assistance." Not sure if there are related or not. The database will not currently allow syncs... when I try to accept incoming syncs I get the error: "Could not start sync server. ACT! has encountered an error, please check that the sync server port is able to listen for incoming connections. Contact your administrator for assistance."
ASKER
Thank you 50cal. Good info, I will try that.
As for the sync issue I got this error when I restarted the server: "Error occurred after logon in synchronization manager: Transaction (Process ID 68) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." Any ideas?
As for the sync issue I got this error when I restarted the server: "Error occurred after logon in synchronization manager: Transaction (Process ID 68) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." Any ideas?
If it doesn't remain shared, that will cause the other issues. Fix that first
ASKER
Thank You
I tried everything in the article and also in this article: http://kb.sagesoftwareonline.com/app/answers/detail/a_id/19876#s1 with the exception of changing the PAD to use the IP instead of the machine name.
The only interesting thing I encountered is with the multiple shares on the database files folder. I unshared the folders related to ACT. When I went into ACT Tools>Database Maintenance and Share Database the folder that became shared in My Computer>Manage>Shared folders was C:\ACT\ourdatabase-databas
I tried everything in the article and also in this article: http://kb.sagesoftwareonline.com/app/answers/detail/a_id/19876#s1 with the exception of changing the PAD to use the IP instead of the machine name.
The only interesting thing I encountered is with the multiple shares on the database files folder. I unshared the folders related to ACT. When I went into ACT Tools>Database Maintenance and Share Database the folder that became shared in My Computer>Manage>Shared folders was C:\ACT\ourdatabase-databas
If you can access the database from the client again ... is there anything you still can't do?
ASKER
Sometimes I cannot sync remote databases. When I select "Accept incoming syncs" I will usually get an error message and not be able to sync. Restarting the server typically gets the sync working again. Thanks
You said you have Premium ... why are you using "Accept incoming sync"?
That's only if using Application Sync and will get that error if the Network Sync service is running - which is what you should be using
When you next get problems with sync, try the tests listed here:
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/24341
Also, have a look in the Windows Event log for any errors.
That's only if using Application Sync and will get that error if the Network Sync service is running - which is what you should be using
When you next get problems with sync, try the tests listed here:
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/24341
Also, have a look in the Windows Event log for any errors.
ASKER
It seems to be working now I will keep you posted
Which change got it working?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Solved primarily on own
I've seen similar issues starting checking incoming syncs if the network sync service is installed and running (As the port will be in use), also this issue can occur if there is another windows profile logged in with ACT running and accept incoming syncs checked (Or again the sync service running under another profile).