Dynamics GP under the Hood: Setup in Dex.ini File

This setup file could be found in versions 2010/11.0 or 10.0 in Data subfolder of the client application main folder in Program Files.  For earlier versions it could be found directly in the client application folder.  Traditionally this file is known to Great Plains consultants and large number of technical support cases requires your consultant to capture logs (SQL, ODBC) in DEXSQL.LOG.  Let’s review some of the settings and how they could be deployed in various practical situations.  This publication is not intended to technical consultants; it is rather for IT department, assuming that you are trying to do as much self-support as possible in-house:

1. Dex.ini could be opened in Notepad or similar low profile text processor.  As this is unprotected setting, please consider making reserve copy before changing parameters.  In case when you got it screwed, you may copy it from another user workstation, where it is connecting top the same server

2. DEXSQL.log file.  Normally you do not need logs to be collected, as it causes some performance degradation, plus consumes hard drive space.  However, when you have encountered error messages with error number and code shown in details – the easiest way to trap the cause is to enable logging.  In new versions, starting from 7.5 most of the parameters is already in the Dex.ini and marked as FALSE.  In earlier versions, such as 6.0, 5.5, 5.0, 4.0 you would have to manually typing parameter name and its settings

3. Enabling logging.  In order to enable, please change the following parameters to true: SQLLogSQLStmt=TRUE, SQLLogODBCMessages=TRUE, SQLLogAllODBCMessages=TRUE.  DEXSQL.log file will be created on the next login to GP workstation.  Try to repeat the steps where you got error message, and having it popup, stop using Great Plains interface and make a copy of DEXSQL.log file.  Then open it in Notepad or Write, go all the way down to the last page and analyze its content.  There are chances that you will get some ideas about error cause.  In older versions of GP errors were often attributed to service pack applied on the server and user workstation mismatch.  If you cannot resolve the issue on your own and have to place a call to Microsoft Business Solutions technical support – it is always a good idea to have log file ready, as in the case of strange error message MBS tech support engineer often request you to send him or her DEXSQL.log file

4. OLE Notes.  When you are entering notes to the document or master record, there is an option to enter OLE note, where you can attach documents in OLE compliant format, for example, PDF, Excel, Word, PowerPoint.  Default installation of GP workstation places OLE Notes folder into Data\Notes.  If you would like to share your OLE Notes or in other words attached documents with other users, consider creating shared folder on the Server and then come through each user workstation and change settings for OLEPath parameter accordingly (UNC Path is OK, or you can use mapped drivers).  If you already have some OLE notes stored on local computers, you can copy the files over to the server Notes dedicated folder (in the case of conflict you can always decide which user OLE attachment has privilege)

5. Synchronize parameter.  When you install GP client interface two parameters set to TRUE, as following: Initial=TRUE, Synchronize=TRUE.  Initial means that Utilities must be launched and Synchronize means that Dynamics.dic Dexterity dictionary is not synchronized on the matter of Account Segment structure.  If you changed your account format via SQL statements and now you need to update all the user Dynamics.dic file, the simplest way is to open Dex.ini file and change Synchronize from False to True

6. There are other parameters that might seem like interesting, but in our opinion those are for consulting professionals, who have access to Partner Source with information documented there.  If you have specific question, we recommend you to contact your Dynamics GP Reseller, or feel free to call our office

7. Please call us 1-866-304-3265, 1-269-605-4904. help@efaru.com We have local presence in Chicagoland, Southern California, South West Michigan, Houston and Dallas areas of Texas. We serve customers USA, Canada, Mexico nationwide and internationally via web sessions and phone conferences (Skype is welcomed). Our consultants speak English, Spanish, Portuguese, Russian, Chinese