Great Plains Tech Support: Typical Issues and Fixes

Apr 24
07:45

2009

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

Based on our 20 years old consulting practice, supporting Great Plains Accounting, GP Dynamics and other ERP applications we would like to share with you typical issues.

mediaimage

If you are experiencing serious Dynamics GP,Great Plains Tech Support: Typical Issues and Fixes  Articles GPA for DOS and Windows, Great Plains Dynamics on Pervasive SQL/Ctree/Faircom, hurting your business operability, consider give us a call or email us

 

1.       Batch is locked in posting.  This is especially hurting when you are printing PM Computer Checks.  You already tried to open batch recovery screen, and it doesn’t help.  If you are DBA, feel free to review batch unlocking procedure: SY00500 and SY00800 tables

 

2.       User is showing as logged in, however you know that it is “ghost”.  Try System->Routines->Delete User.  If you are on older versions of GP on SQL Server, try to delete user directly from Activity table, it resides in Dynamics database.  If you are on Pervasive/Ctree, in your Dynamics->System folder delete Activity.btr or Activity.dat file (please, be sure that all the users are logged off GP before this fix)

 

3.       Customization upgrade.  If historically you have implemented Dexterity add-on, coded specially for your unique business logic – in order to update this modification to new version you should possess Dex source code (either Dynamics.dic or Extract.dic with the code)

 

4.       Report is not found, problem opening report – this issue is associated with GP security.  Each user (unique for each company) or user class (unique across the system, the same for each company).  Please, verify your Dynamics.set file to identify where your Reports.dic is stored.  You can either try centralized location or each workstation could have its local dictionary.  Great Plains stores user access to modified reports in Dynamics database

 

5.       FRx errors.  These are typically associated with G32 extension files or Sysdata path

Article "tagged" as:

Categories: