The Easy Way to Refresh Your Dynamics GP Test Company – Part Four

by | October 23, 2019 | Dynamics GP

In our last sessions, we created the SQL backup job and step, then the Restore step as well as our third step of running the company fix script.  In this session, we will test our job and troubleshoot any issues.

1) Go to the server where SQL Server is installed, and your Dynamics GP databases are located.

2) Launch SQL Server Management Studio and log in as SA or a user with System admin rights.

3) Expand SQL Server Agent and then Jobs. Look for the job you created in our last session.  In this case, it is:  “Back Up Database – TWO and Restore to Test.”

4) Right-click the job and click to select “Start Job at Step”

5) You should get a window that looks like this one below.  Click on start to run the job.

6) If the job starts and runs correctly, you should see this window

7) If the job and all steps complete successfully you should see this window:

8) Next, launch Dynamics GP and login to the test company

9) If all goes well, you will be able to log in. If not, then the fix company script most likely did not complete correctly.

10) If you are not sure if the restore to the test company completed properly:

  • You can go into the test company and create a customer or vendor that is not in your live company.
  • I like to create a customer called: Test Company restore.
  • I create this customer in the test company.
  • I then go and run the restore job as noted above.
  • I then go back into the test company and look for the user I just created.
  • If the user is now gone I know the live data has overwritten the test database.

11) To troubleshoot a job that is failed the best way is to review the logs for that job.

  • Expand SQL Server Agent and then the Jobs.
  • Select your job and right-click
  • Now select View History

12) When viewing the Log File Viewer, you will be able to see the jobs and steps that succeeded and also the ones that failed.  In this view below you can see that the job ran but step three failed.  In this case the script was incorrectly pasted into the job step window.

13) To see more info on why a step failed, you can copy the exact script from the job step and paste it into a new query window and execute it there to see more of why the script failed.

This concludes our series on Easy Test Company restore. If you have any other questions or are looking for more information, reach out to the team at Stoneridge Software.

Related Posts


Submit a Comment

Your email address will not be published. Required fields are marked *

Upcoming Events


02dec11:00 am12:00 pmConfab LIVE with Stoneridge - Let’s Talk Dynamics – Open Q&A Session

09dec12:00 pm12:45 pmHow to Become a Dynamics 365 Consultant

15dec1:00 pm4:00 pmOnline Workshop - Dynamics GP Year-End Close


19jan10:00 am11:00 amTax Compliance and Coffee – a Virtual Discussion

26jan2:00 pm2:45 pmKeep Your Data Secure and Move to the Cloud with GP

About Stoneridge
Stoneridge Software is a unique Microsoft Gold Partner, with emphasis on partner. With specialties in Microsoft Dynamics 365, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics GP and Microsoft Dynamics CRM, we focus on attracting the most knowledgeable experts in the field to our team, and prioritize delivering stellar solutions with maximum impact for your business. At Stoneridge, we are deeply committed to your results. Each engagement is met with a dedicated team, ready to provide thorough, tailored, and expert service. Based in Minnesota, we intentionally “step into your shoes,” wherever you are. We focus on what you care about, and develop trusting, long-term relationships with our clients.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!