When opening a client application, an unhandled error appears which looks like the below:
[User details]
Company :
Registered to :
Serial number :
Contact :
Unexpected problem has been detected in <Client name>
Description : Error checking if first time
Date : 24 September 2009
Time : 13:08:19
[Application Details]
Application : <Client>.exe
Full Path : C:\Program Files\DIP\<Product>\1.3.0.327\<Client>.exe
File Size : 380928
Created : 17/07/2008 14:11:12
File Ver : 1.1.0.28
[Client Operation System Details]
Operating System : Microsoft Windows NT 6.0.6001 Service Pack 1
.Net Framework : 2.0.50727.3074
[Di Stack Trace]
CLI1600E Error checking if first time
CFG050KE Could not load XML file
System.Xml Root element is missing.
This error is due to the client config file becoming corrupt and therefore Odex cannot read it.
The config files which are used by the client application vary between product and operating versions. A full list of them is below :
Darwin 4
All client config files are kept in :
C:\Documents and Settings\<Windows Username>\Local Settings\Application Data\dip\DARWIN\<Darwin version number>\
The various clients use the below config files :
Darwin Order Processing : DR3ORD.CFG
Darwin Administrator : DR3ADM.cfg
Darwin Invoices : DR3INV.cfg
Darwin 3
All client config files are kept in :
C:\Documents and Settings\<Windows Username>\Local Settings\Application Data\dip\Darwin3\<Darwin version number>\
The various clients use the below config files :
Darwin Order Processing : DR3ORD.CFG
Darwin Administrator : DR3ADM.cfg
Darwin Invoices : DR3INV.cfg
Odex Enterprise
All client config files are kept in :
C:\Documents and Settings\<Windows Username>\Local Settings\Application Data\dip\ Odex Enterprise\<Odex version number>\
The various clients use the below config files :
Odex Workstation : ODSWKS.CFG
Odex Administrator : ODSADM.cfg
Odex Comms Monitor : ODSCMR.cfg
BACS.IP
All client config files are kept in :
C:\Documents and Settings\<Windows Username>\Local Settings\Application Data\dip\ BACS.IP\<BACS.IP version number>\
The various clients use the below config files :
BACS.IP Submissions : BAXSUB.xml
BACS.IP Administrator : BAXEXP.xml
EPIC
All client config files are kept in :
C:\Documents and Settings\<Windows Username>\Local Settings\Application Data\dip\ EPIC\<EPIC version number>\
The various clients use the below config files :
EPIC Admin workstation: ODSWKS.cfg
EPIC Administrator : ODSADM.cfg
EPIC Postbag workstation : ODSPBG.cfg
EPIC comms Monitor : ODSCMR.cfg
Solution
If there is another computer which is running the client which is throwing the error, the config file from the working machine can be copied to the non-working machine. The config file will be in the same directory on both machines (apart from any username changes).
If there is not another machine with the client running on, there may be a file within the same directory as the corrupt config file which has a similar name, but with the extension of either .BAK or .tmp. If this file exists, the corrupt config file can be deleted and then the BAK or TMP file can be renamed, by taking of the BAK or TMP.
If the above cannot be found or this does not work, the corrupt config file will need to be sent into support, along with any other .cfg in that directory. The support email address is support@di-international.com |