Dynamics GP Data Recovery Notes

Feb 16
08:36

2011

Andrew Karasev

Andrew Karasev

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

There might be several scenarios, where you need data fixing or recovery in Great Plains. Let’s review these scenarios, and please know that they reflect real cases in our consulting practice.

mediaimage

As excurse into the history of this Corporate ERP application – it was historically available on several database platforms: Microsoft SQL Server,Dynamics GP Data Recovery Notes Articles Pervasive SQL 2000, also known as Btrieve, and Ctree.  If you are on historical version, you need to understand what is database.   We can get the answer from Microsoft Business Solutions, but this would need some time.  Let’s begin with recent versions 2010/11.0, 10.0, 9.0, 8.0:

1. Microsoft SQL Server Recovery.  Since the version 8.0 this ERP application is available on MS SQL Server exclusively.  We believe that your consultant implemented or recommended to your IT department SQL Backup.  The simplest way is to create SQL maintenance job, where you backup all the databases, place backup files into separate folders and keep each file as long as server hard drive space permits.  Second strategy is to include these backup directories into tape backup.  There is also an option to do direct SQL DB tape backup, where you need to purchase special add-on from your backup application provider.  If you have backup tapes, you are in the safe zone.  Sometimes we see customer IT folks do not watch backup log and when disaster happens, they finally look and realized that SQL Server agent was not running, meaning that nothing was happening.  If this is your unhappy case, and your server crashed on the hardware level – you may try to remove hard drive, attach it to another server or mount it into USB enclosure and reconnect to your computer.  When you remount your old drive, find your SQL database files: GPSDynamicsDAT.MDF is the file of the Dynamics database, company files have similar naming convention.  On the new SQL Server you should be able to attach these databases and remap user computers to the new destination

2. Earlier versions: 7.5, 7.0, 6.0, 5.5, 5.0.  These were available on three platforms: MS SQL Server (2000, 7.0 and 6.5) as well as on Pervasive SQL 2000/Btrieve and Ctree.  If you are on SQL Server, the paragraph above should be still the guidelines.  For the rest of us – try to locate Dynamics folder on the server hard drive, Btrieve/Pervasive files have BTR and IDX extensions, while Ctree files have DAT extension.  To redeploy Pervasive environment, you need Pervasive SQL 2000 CD and license diskette (or file)

3. Great Plains Accounting for DOS, Windows or Macintosh.  It was Btrieve application, where the files had DAT extension.  To recover, look for GPS folder, where your first company resides in GPData subfolder and all the subsequent companies in the folders with their names abbreviation.  If you are looking forward to redeploy GPA on the new server or computer, please consider to do it on Pervasive SQL platform, and know that you have to stick to Windows 32 bit version.  It is possible to redeploy GPA on Windows 7, Vista, XP, Small Business Server 2008, assuming that OS is 32 bit one

4. FRx Reports.  Here you need to look at Sysdata directory and especially in catalog files, usually Frxrpts.f32, try to recover all the files with f32 extension

5. Integration Manager.  Usually integration metabase is hosted in IM.MDB file

6. Report Writer reporting.  This might be substantial part of your implementation, as here you modify such forms as SOP Blank Invoice, where you typically place your company logo, disclaimers.  Look for Reports.dic file

7. Dexterity customizations.  These are residing on the client computer, so we believe that the recovery is not a big issue

8. Modifier with VBA.  It is also client side add-on, the modification is stored in Forms.dic and scripts in Dynamics.VBA

9. Extender.  This is Dexterity add-on, you are covered, assuming that your user workstations are still in good shape

10. Data corruption, caused by buggy customization.  Typically when you hire Dexterity programmer, who is still in learning curve, or when you are trying to insert data into Great Plains via custom SQL stored procedures.  The first step is having users log off, make backup for all the companies and Dynamics DB and then try Check Links for all the tables in System and all the companies.  If this recommendation doesn’t help – you need help from professional Dynamics GP Technical Consultant

11. Small Business Financials Data Recovery.  This Small Business ERP was introduced as simplified version on the same Dexterity code base, available on MSDE (scaled down version of the SQL Server).  The recommendation in the paragraph #1 are for you

12. How data recovery works in real life?  With the advances of modern computer technology there is no need to travel to your office, the job could be done via web session or remote desktop connection

13. Support domestically in the USA, Canada, Mexico and internationally.  This option is possible via Web Sessions, Skype or Phone conferences and direct visits onsite (in the case of the large scale project).  Our consulting team speaks English, Chinese, Portuguese, Spanish, Russian, Filipino.  Feel free to call us 1-866-304-3265, 1-269-605-4904, or email help@efaru.com