01-08-2018 07:54 AM
We recently upgraded our computers to Windows 10 Pro. We have Act! Pro Version 18.104.22.168, Update 6 installed on 6 office computers. The database is on one computer and is shared by everyone else.
However, almost once a week, the database randomly unshares itself!! Very frustrating. Every time it happens we go to the file menu within ACT on the computer that holds the database and click on the "open/share database.." option to open the dialog box. The blue box has always changed to "Share" in front of our database and we have to choose to share it again!
Can anyone tell me why this is happening and if there's a way to stop it? When we were on Windows 7 it worked just fine.
Thanks for your help,
01-08-2018 11:18 AM
Maybe Microsoft SQL is cutting out
01-17-2018 11:24 AM
I have followed your instructions and so far the database has not unshared itself. However, I am waiting for a Windows 10 update to "automatically" restart my computer. I think it happens every time that goes through as well. Windows 10 automatic updates has been a problem with multiple programs. Wishing I could turn them off and manually update on a regular basis!
06-19-2020 12:18 PM - edited 06-23-2020 05:51 AM
For me the Act database un-shares itself randomly, every few weeks I would say. For example it happened Wednesday afternoon at 4:50pm. On this server the Act Scheduler backup runs at 8pm and it completes after 20-30 minutes. I also run a Windows Server Backup of the Act data location to capture attachments, templates, etc., and this runs at 9pm. I spoke to Act phone support and they said it was possibly a user with admin rights who unchecked 'share database', but that wasn't it. Act admins were not in the office.
In services.msc, looking at the Act SQL service, it is set to start manually, rather than automatic with delayed start. I believe my predecessor set it this way because our Act data is on a disk partition with BitLocker, so you have to start the service manually once you manually unlock the BitLocker drive after a reboot.
Once I figure out if BitLocker is the reason for the manual service start, I will try your service restart settings. THANKS!!!