Andrew Karasev

Great Plains Tech Support: Before You Call Dynamics GP Consultant

Microsoft Dynamics GP could be supported by external Great Plains consultant, especially if you just implemented this ERP and you have strong support from your Great Plains Reseller, Technology Partner or ISV (in the case, when you are relaying on one of the third party Dynamics GP Add-Ons).  

However, as the time goes, especially if you are upper mid-size or large organization, you may decide to support Dynamics GP internally through your IT department.  We would like to give you orientation in internal Dynamics GP Technical support:

1.       Dynamics GP Customer Source.  If you are currently enrolled in GP annual enhancement program (this program is required if you plan to be current with Dynamics GP software upgrades), please request from Microsoft Business Solutions login to your Great Plains Customer Source.  There you should find Techknowledge base with all known issues and resolution procedures.  If you are not current with Great Plains annual enhancement program, then you normally lose access to Dynamics GP Customer Source, in this situation you should contact Microsoft Dynamics subdivision or call your Dynamics GP VAR, if you are not sure who is your Great Plains VAR, feel free to call our office

2.       Great Plains Batch Recovery.  If your Dynamics GP users report you that they cannot post one of the batches, you should go to Tools->Routines->Batch Recovery, there if you see Transaction Error – Edit Required, then there is no way to force posting this batch, you need to review Transactions with errors.  Simply open this batch, and print Batch Edit List report.  This report will indicate your which transactions should be corrected, typically lack of GL distribution account.  If your error message is different, simply mark the batch and click Continue, ask user to post the batch one more time

3.       If you have “strange” error messages.  Again, please take into consideration the fact that Great Plains was coded for larger organization, where you have client server environment (Microsoft SQL Server Database platform and GP Dexterity coded user workstation).  The first rule is not to install new programs on Dynamics GP Workstation computers spontaneously (preferably take away computer administrator rights from the user).  If you are getting annoying errors from Dynamics GP, consider this scenario.  Find Dex.ini file, open it for editing and change

SQLLogSQLStmt=FALSE

SQLLogODBCMessages=FALSE

SQLLogAllODBCMessages=FALSE

False to True

This change will begin Dynamics GP Dexterity, ODBC and SQL actions logging.  When you get error message, simply open Dexsql.log file and review its content

Article Tags: Great Plains

Source: Free Articles from ArticlesFactory.com

ABOUT THE AUTHOR