Cannot connect to company file on file server

Question

I have the connection manager installed on the server, users in question have full control access to the directory (NTFS) where the company file exists, they even have local admin access on their workstations. 
 Everyone has FC on the share permission. 
 I can get it to work by running AS the domain administrator on the workstations..but that's it. Even if I 'run as administrator' without credentials (IE 'using' the users admin privileges, but not the domain admin credentials) it still fails with the error: 
 'Sage 50 cannot open the database because the database engine reported an error. Please see error log for more information' 
 Sage 50, 2013 u2 
 Works fine with company file local on the workstation 
 Thoughts?

RandyW · Accepted Answer

The log files are in ghe company.SAJ folder. i.e. if the company 'file' is MyCompany.SAI, the folder is MyCompany.SAJ. 
 It's significant that it works when you are the domain administrator. As you say, you've pretty well eliminated the firewall or any local rights, as an issue. 
 Has the server has been restarted? (to eliminate a possible difference in what rights the Services start with on boot, vs. after installation without reboot, make sure there's no files held open that shouldn't be, etc.) 
 Seriously, has the server been restarted? 
 The process goes more or less like this: 
 - Workstation client opens MyCompany.SAI using an SMB file connection. 
 - Workstation client figures out server name from the file connection info, and attempts to make a TCP/IP connection to the Connection Manager on port 13531 
 - Connection Manager verifies that it is a valid Sage 50 Client makiing the connection, and 
 - starts the MySQL database engine, which 
 - opens the 'real' data files in the .SAJ folder.. 
 - Connection Information for the server database daemon's TCP/IP port is passed to the Client (the first one is usually 13540, second is 13541, etc.) 
 So... the process is going wrong about where the database engine is opening the file. If the database engine reported an error, then the communication all the way up to the database is working. If the only user account that can start the database server is the domain admin, then it might not be starting as a system process?

EdPro · Answer

I have traced this problem to sync off-line files on the client machine. My fix was to open Sync Center from the control panel and clear files that were associated with mapped drives. I also disable disabled offline files syncing. 
 What was happening is that the '~PVSW~.loc' file was being cached from the company directory on the server. This causes a problem when the offline version of the file is read instead of the file on the server. This file contains the server machine name and the local copy fails as it is is not the server. Sage needs to read the file from the server and not a cached offline copy.

Sage 50 Canada

Cannot connect to company file on file server

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING