• A file location in Company Settings is pointing to a path on an invalid server.
• Windows update is blocking Pervasive/Actian.
• A mapped drive for file locations has quit working.
• UNC paths in the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Timberline\General were referencing an IP address instead of the server's name.

Note: If everything was previously working and suddenly everyone is receiving this error, the Local Area Network (LAN) settings may have been incorrectly changed to Public from Domain, Private, or Work. There have been reported cases of Windows updates changing this setting. When the value is set to Public, Windows Firewall will behave entirely differently and start blocking all sorts of Pervasive/Actian connection attempts. It has also been found that this error occurs when you are using mapped drives for File Locations.

WARNING: Once File Locations are set and used in production (with or without a location specified in the Data Folder field), do not change these settings without working with a Sage 300 CRE Consultant as it could result in loss of data.

See article 35405 DocLink: How do I change an existing file location? for warnings and considerations before changing File Locations.

Option I: Update paths to valid location on server:

Versions 15.1 and older:

1. Open Sage Desktop.
2. From Tasks, Sage 300 Construction and Real Estate, Common Tasks, File, Company Settings, File Locations.
3. Update the path for each File Location that may have an invalid path.
4. Click OK.

Versions 16.1 and newer:

1. Open Sage Desktop
2. From Applications, Common Tasks, File, Company Settings, File Locations.
3. Update the path for each File Location that may have an invalid path.
4. Click OK.

Note: It is recommended that you use a UNC path for data files.

Option II: Replace mapped drive with UNC path

Replace the mapped drive portion of the File Location with the UNC path.