I haven't read the release notes, but am guessing it's a much easier way for users to locate resources on the network (forms, reports) without having to navigate a UNC path or fuss with a mapped drive.

This folder is not for the convenience of users.  It contains the Sage 300 programs (only).  Cannot find any documentation on it, but we get a 40960 error message when it is not there.  Obviously, this is very confusing, as that error should be indicative of a DSN connection issue, but in this case, it is not.  Sometimes when running workstation setup, that local folder gets created and everything works fine. We did not even notice it at first. But other times, that folder does not get created and the 40960 error is returned upon attempting to open a company.  The only recourse we have found so far is to install programs locally (to C:\Sage300Local), leaving the SharedData path to the server, selecting System Manager with no options (since they are on the server) and applications used (but not number changers, sample data, etc.). 

Hi Jim - the error 40960 indicates an issue connecting to the database.

Sounds like you may have ambiguous references to more than one version.

Please confirm the following:
1. Path - only one reference to the production Runtime folder
2. Registry - Ensure the Shared Data and Programs are pointing to the correct folders
3. Shortcuts - ensure shortcuts are pointing to the correct share
4. Regacc.exe - Run as administrator from the correct Runtime folder
5. ODBC DSN - Ensure that a 32 bit server-centric DSN has been created in the Machine section of the ODBC Admin screen
6. Permissions - Try running Sage 300 as administrator

Good luck,

Shane

As I stated, this is not an ODBC issue.  Yes, I understand that 40960 has always meant a DSN connection issue. In this case, it had to do with the absence of the C:\Sage300Local folder.  We spent an inordinate amount of time checking, double-checking, triple-checking the DSN connection, the registry, the path, shortcuts, rights, etc.  Once we finally discovered the local programs folder on working workstations and the absence on 40960 workstations, an install of programs to that folder, with no other changes, resolved the issue. 

An additional item of interest regarding this:  The Sage300Local folder appears to be a folder of symbolic links, not actual programs, though at first glance, it appears that all of the programs are there.  It would have been nice had Sage deigned to put something about this in the documentation. 

If you are installing to that folder on the local drive, do you also have to then install product updates on that workstation? Defies the concept of server-client install.

Yes, you're right.  But having to re-run workstation setup every time a product update is installed also defies the concept.  In that light, just installing the product update may actually be faster. 

We ran into this issue when upgrading to the 2019 version on a couple of workstations; for whatever reason the C:\sage300local folder wasn't created by the installer.  IMO, a better workaround than installing the folder locally is to manually create a symbolic link to the network folder.

From an elevated command prompt in the root of C:, run:

mklink /d Sage300local [path to sage programs]

This will create a symbolic link (NOT a shortcut) to the proper location and everything seems to work after that. Note that the link target must exist in the elevated environment for the command to succeed; if you're using mapped drives you may need to net use [DL]: \\uncpath-to-sage-files before attempting to create the link.

We ran into this issue when upgrading to the 2019 version on a couple of workstations; for whatever reason the C:\sage300local folder wasn't created by the installer.  IMO, a better workaround than installing the folder locally is to manually create a symbolic link to the network folder.

From an elevated command prompt in the root of C:, run:

mklink /d Sage300local [path to sage programs]

This will create a symbolic link (NOT a shortcut) to the proper location and everything seems to work after that. Note that the link target must exist in the elevated environment for the command to succeed; if you're using mapped drives you may need to net use [DL]: \\uncpath-to-sage-files before attempting to create the link.

Cool!  Thank you.