Configure the Ledger Data Folder Structure

Configure the Ledger Data Folder Structure

Ledger Data Folder Configuration

UNC Paths / Mapped Drives

We strongly recommend UNC paths be used throughout the application. 

There are a number of websites that contain detailed instructions on how to set these up.

If mapped drives are to be used, these MUST be replicated on the SQL Server and Application Server, as when a backup is initiated from within the Argos application on their workstation the backup instruction is actually passed onto the SQL Server to be actioned. Therefore if the mapping does not exist on the SQL server, the backup will fail as the server will not be able to find the location to store the backup file.

Another issue can occur when a drive mapping exists on the server but the underlying folder location is different to the equivalent mapped drive on the workstation. This can cause confusion as SQL Server will undertake the backup and save the file to the mapped location as instructed, however this may not be the location the user expected. 

Permissions to access and write to the ArgosData files are required for all users.

Folder Structure Required

Each ledger will have a separate root folder under ‘ArgosData’ for data files.  For each ledger the following folder structure should be created:
<<Argos Data>>
<<LedgerCode>> - This is the name of the database 

               

    • Related Articles

    • Install the Vault client

      Workstation Access to Argos These tasks need to be completed for each workstation that will be using the Argos application. Install the prerequisites Create an ODBC DSN Create the Desktop shortcut with database connection information If a new ...

    • Installation Instructions

      Summary This set of documents details the initial setup requirements for the Argos software. It is recommended that the installation checklist from the appendices is printed as a step by step guideline for the installation task being undertaken. The ...

    • Installing Argos Internal API

      The Argos Internal API is used to power the Vault and Bailment applications. Note, this is available from Argos v6.0 onwards Installation Types The installer can be used to install a production instance of the Argos Internal API. Instructions to ...

    • Installing Argos Bailment

      Argos Bailment Installing the Bailment Module Application Note: Argos Bailment is a licenced module that is run independently of Argos Vault. If you are not licenced for this module, then this section can be disregarded. New Installations Double ...

    • Installation Prerequisites

      Prerequisites The following section outlines the third-party applications required to successfully run Argos. The below applications are not provided as part of the Argos application and it is the responsibility of the client to purchase/licence, ...