04-24-2018 11:47 AM
We have a subscription to Act Premium v20 with 3 offline clients. Each user is running his own database and none are shared. All users were upgraded to v20 at the same time last November, so should all have Act Premium v188.8.131.52 update 4, and SQL server 2014 express edition, though obviously I can't look at the problem offline database.
One user cannot sign in to his offline client today, but had no problem 2 days ago. After entering user name and password on login page he gets the error message: "The database (xxxxxx) could not be accessed. In order to access this database, check your network connection and verify that your database server is available.... "
No other users have issues on signing in to the offline client. He says nothing has been changed on his laptop, and there were no power outages. He is running the offline client on a Mac with Windows 7 installed using Parallels. He can sign in to his cloud database.
Looking through the list of possible solutions, most apply to older versions of Act, cloud access, problems after power outage, etc, none of which would seem to apply here.
Is a corrupted offline database the most likely problem, or something else?
04-25-2018 02:44 AM
04-25-2018 05:36 AM
Also check that SQL has started. Try a restart to check otherwise run services.msc to check.
04-25-2018 07:55 AM
I'm the Act admin but not an IT person...
So please tell me which you mean by the "host PC"? If this is the user's laptop, yes he has right to access files. And he could open his db a few days ago, and says he hasn't changed anything. None of the users is on a corporate network. I wouldn't think permissions are an issue.
First thing I had him do was reboot to make sure SQL Server was running, though in the past with that problem we've had an error message specifying it wasn't running which isn't the case here.
Corrupted db or is there another possibility we should look at?
05-02-2018 06:39 AM
Called Tech support and found that the ADP file was missing for some reason.
Restored database and synced.
The next time the user tried to open the offline client he got the same message, so I'm assuming the ADP file is missing again. (Will have the laptop in front of me later this morning.)
Any idea on why this would keep happening?
05-02-2018 06:48 AM
05-02-2018 09:44 AM
Webroot doesn't show that it quarantined or removed the ADF file.
Is it still worth adding all the exceptions for Act?