10-10-2013 10:43 AM - last edited on 11-14-2013 05:24 AM by dpark
We've been using ACT2011 without issue shared with multiple users. Recently we had an IT employee leave so we rolled passwords for everyone's computers and the server which is hosting the ACT! database.
The .pad files used by all before the roll over is still working for everyone on the domain. However, two users who are logging in from outside the domain (via VPN) can no longer access the file using that same .pad file. Again, that common file is what worked prior to the passwords change.
All the recommendation in http://kb.swiftpage.com/app/answers/detail/a_id/19876 seem to apply if everyone can't get in. In this case it appears the database files had permission prior to the change and don't know that the password changes and are now blocking visibility. We've scrubbed the file permission to ensure everyone has full access, and that didn't resolve the issues.
Can anyone point us in the right direction?
(edited to update kb link)
10-10-2013 02:29 PM
You could try checking to see if the VPN users are part of a special/unique group - if so, check the permissions for that group. It could be affecting those 2 users access.
10-11-2013 09:03 AM
We have full admin rights and server sharing options. Still no luck.
The system does see the .pad file, and brings up the user name and password (which work on domain computers, so that's not the issue). The "Cannot find database supplemental files folder" error comes up after that as if the main file is visible and sharable but something else isn't allowing this to go through.
The only thing we changed was computer passwords for the users and the server. No permissions were changed, no groups were changed, no names were changed. I agree it seems to be a file permissions issue, but it also appears as if ACT isn't recognizing the remote computer with the new password and is acting as a firewall to block it. Yes, we checked the actual firewalls. SInce there was no name changes they had no impact.
Any other suggestions?
10-11-2013 10:04 AM
There are two places involving shares that present a permission problem. The first is the folder that is being shared and the second (the one most people don't know about) is that the share itself has permissions. Check the permissions on the share and see if that person has permissions to the share as well as the folder.