B – Installation {appendix}


On each workstation you must have configured MYOB Exo Business to successfully run. You may not intend MYOB Exo to be in common use on that station but because DUO is an extender product it lives in the same environment.  This means that:

·         The Microsoft OLE DB SQL Client is installed (MSOLEDBSQL exists)

·         A computer profile has been created / allocated to this workstation by running an MYOB Exo application

·         A suitable staff record has been created for application login

For evaluation purposes Dyameta Technology also provides, as an SQL backup file, an updated copy of the demonstration Motopartz database with all DUO modules and additional metadata pre-installed. DUO licence codes are not required to run this demo.

Assisted install

An installer program is supplied which acts as both an installer and a database upgrade tool (altering metadata for newer versions).  This is a typical wizard style installer and is not documented here.

Manually Installing the DUO distributables

DUO can be installed manually as described in this section or you can use the installer program.

For manual install DUO ships as a series of files in exoDUO.zip which can be extracted to a folder of your choice. We recommend putting these in the same folder as your exonet.exe preferably on a network drive. It is common practice to map the MYOB Exo network folder to X: therefore the default settings are set accordingly.

The exoDUO.zip contains the following files:




The application executable


This is the default version of exoDUO.xml. Only needed if you don’t want to use connections stored in registry.

As we don’t want to overwrite your custom settings in exoDUO.xml during an upgrade we provide this file with an altered name.


This document in PDF format


SQL script to add metadata for the Common Module


SQL script to add metadata for the Warehouse Module


SQL script to add metadata for the Purchasing Module


SQL script to add metadata for the Sales Module


SQL script to add metadata for the Production Module


SQL script to add metadata for the Admin Module


SQL script to add metadata for the Designer Module


SQL script to add metadata for the Help Desk Module


You must have accessed the database at least once per workstation using an MYOB Exo application. This ensures:

·         A connection has been defined in registry for the database. DUO does not have its own connection editor because by default it uses the MYOB Exo parameters.

·         The MYOB Exo application has created a record in the COMPUTERS table for this workstation.

If this is the first time this workstation has accede this database using DUO then DUO will prompt for the SQL server password.  This is because DUO cannot decipher MYOB’s encrypted copy of this password. And must store its own encrypted copy.

Identifying your machine

DUO recognises your machine by the same rules as MYOB Exo and therefore also works in virtual workspaces such as Terminal Services. For computer level profile settings, it has the same requirements as Exo.

 If there is no computer record yet established for the current workspace then MYOB Exo Business must first be run in that workspace to automatically create one.  In such case the user is advised...

Appendix - Installation - Identifying Your Machine

Login Windows shortcut

DUO can be launched with login credentials on the command line therefore a shortcut can be set up on your desktop to automatically log in.  The parameters are the same as for MYOB Exo.


Appendix - Installation - Windows Application Shortcut

A fourth parameter may be optionally supplied to specify the Role required.

First time run

Before you can log in to your database with DUO the DUO Essentials module must be installed.  If you have used the installer program then this will have already been done. If not installed then the following message will appear

Appendix - Installation – DUO Essentials module not installed

Ether rerun the installer program or run the script DuoDBupdateEssentials.sql

Installation checklist

For a manual install

ü  Obtain DUO licences from Dyameta Technology Ltd

ü  Unzip exoDUO.zip into the same folder as your exonet.exe

ü  Copy (not rename) exoDUOBack.xml to exoDUO.xml

ü  Launch exoDUO.exe and provide the SQL password

ü  The system will automatically run the required epDBupdate scripts

ü  Open MYOB Exo Config (Exocfg.exe) and navigate to the Profiles tab

ü  Change the All Programs combo box to DUO

ü   Ensure all profile settings are set correctly, especially Folder location for XML files

ü  In DUO, navigate to the Help > About screen

ü  Click the Get Licences button

TODO: Red items not implemented yet. We are considering putting epDBupdate and Get Licences in a separate executable so that they are not available to all staff. This might also include a Wizard for first time setup.

Upgrade checklist

To upgrade your DUO version

ü  Unzip exoDUO.zip into the same folder as your previous DUO install

ü  Login to your database

ü  The system will automatically run the required epDBupdate scripts

Troubleshooting Operating Environment

Invalid Connection Attribute

Symptom: If the system cannot connect to your database then it will display a screen similar to this.

Appendix - Installation – Invalid Connection Attribute


·         Check that you have all the correct settings in the Configurator.

·         If using MSSQL connection type (default) then check that ntwdblib.dll is in the path specified (as displayed under Driver Above).

msvcr71.dll not found

Symptom: The system displays a message saying it can’t find msvcr71.dll

Appendix - Installation – Microsoft MSVCR71.DLL Missing

This is part of the Microsoft Visual Studio .NET.  It is installed on your server when installing Microsoft SQL but DUO might not be able to find it, perhaps because of Windows security settings.


·         On a workstation it should have been installed with .NET which is present by default on newer operating systems.  On older Operating systems, download .Net and install it.

·         As a last resort msvrc.dll can be found on your SQL server in path

C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn

o   On a 16 bit operating system copy this to \Windows\System32

o   On a 32 bit operating system copy this to \Windows\SysWOW64

Ribbon does not display correctly in Terminal Services

Symptom: Some border drawing is incomplete (corners missing).

The ribbon component used was designed to work with 24 bit colour depth and you are operating with 16 bit colour depth.

Note: This is common in a Terminal Services session as the T/S default settings on the server are often set to a maximum of 16 bit colour depth. Attempting to set a higher colour depth in the RDP client won’t help.

For modern workstations the colour depth will usually default to 32 bit and you won’t have this issue when running DUO locally (unless it has been reduced for some reason). 

Remedy: Use as is or get your systems administrator to increase the Terminal Services maximum colour depth from 16 to 24 bit. This setting is found in the Server Manager under Roles > Remote Desktop Services > RD Session Host Config.

 Appendix - Installation –Ribbon Display in Terminal Services

Changing from Ribbon to Classic mode displays wrong tab

Symptom: When switching from Ribbon mode to Classic mode (Tabbed PageControl). The highlighted tab is always the first one and may not correspond to the screen body contents.

This is a known issue which seems to be a bug in the Windows PageControl component.

Remedy: After swapping back to Classic toolbar mode, just click another tab to restore the correlation between tab highlighted and the screen content.

DUO for EXO     DUO for EXO     © Dyameta Technology Ltd                     Previous Topic           Next Topic           Home