In the past, Agvance used a naming convention that included the server name in the path to the data (e.g. \server\drvc\data\avdata\agvance.mdf). However, this caused issues when network problems caused delays in resolving the server's name, causing Agvance to time out while trying to connect. To fix this, newer versions of Agvance use physical drive letters (e.g. c:\data\avdata\agvance.mdf) instead. Since workstations typically map to a shared folder on the server and not the root of the drive, Agvance needs a way to get from the workstation path to the physical path to the data on the server. The server path is the path on the server that corresponds to the workstation's mapped network drive.
Below are some important things to know about the server path.
What is it?
- The path to the data from the server's perspective.
- The meaning of the workstation's mapped drive letter.
- For example: If the data is stored on C:\Data\Avdata, and the workstations map M: to C:\Data\, then the server path is C:\Data\.
- Stored in AgvSec.mdb
When is it set?
- 4.0 to 4.1 conversion
- Database Activation (new install)
- Create Play Data Utility
- Restore Database Utility
- Attach Agvance Databases Utility
- Set Server Path Utility
How is it used?
- Used for reports, databases, and images.
- Agvance starts with the server path and appends AgvRep or AgvImage.
- A problem in the server path will prevent Agvance from finding the reports databases, so some or all users will be unable to log in (Device Activation Error).
What is important?
- It's best to set the server path from a workstation, not the server.
- When setting the server path on the server, be sure the data has been mapped the same way as the workstations, and only navigate to the data using that mapped drive.
- The server path must have a backslash (\) at the end.
- Sometimes it is necessary to try twice.
- Double-clicking in the Server Path box and selecting the path through that window is both easier and more reliable.
- If the server path is correct and Agvance will not accept it, try from a different workstation. There have been cases where one workstation cannot set the server path, but another one can.
