Skip to content
logo Knowledgebase

Sage 200 CRM - How to restore data off site into a test environment

Created on  | Last modified on 

Description

NOTE: Sage 200 CRM has stopped being sold as of 1st April 2021. The classic integration for Sage 200 CRM is now in extended support until 30th September 2021. For any new integrations, the Qmulus Qnect Connector must be used. For further information on this, please see this article

How to restore data off site into a test environment.

Resolution

Requirements

To take integrated CRM data offsite, you will need:

  • CRM Data Backup



  • Sage 200 Data Backup



  • WWWRoot folder (C:\Program Files\Sage\CRM\CRM)


When restoring customer's data into another environment, you will not be able to use the integration or certain areas of functionality until some configuration has been carried out.

Guidance and Recommendations

You must ensure you’re using the same version and build as your customer. So, if the customer is using 7.1.f-S and you have 7.1.d.1 installed on your test system, you must either:

  • Install the relevant patch for Sage 200 CRM on your own test system before restoring the data. Remember you will need to do the same for Sage 200 to ensure version compatibility. The reason for this is that your program files will otherwise be out of date, as when a patch/ service pack/ hotfix is run, it can update both the program files and the database.



  • If the customer data is an earlier version of the test, you should either completely uninstall and reinstall Sage 200 CRM to the relevant version and patch or restore the customer data and re-run the relevant patch against the dataset after restoring it. 


Customisations

To ensure you are able to use any customisations they have, you should stop IIS, rename your own WWWRoot folder (so it can be easily reinstated) and replace it with the customer’s. You can then restart IIS. Note: If the WWWRoot folder is substantial and getting it will be problematic, just request the CustomPages folder from within here instead.

Integration between Sage 200 and Sage 200 CRM

To be able to use the integration, you must amend the URL in the ERPIntegrations table in the CRM database as it will refer to your client's server name rather than that of your test PC. This cannot be overtyped and must be amended using a simple script (this example assumes you are restoring a 7.1 database)...

UPDATE ERPIntegrations
SET ERPI_ERPURL = 'https://machinename:10443/Sage200WebServices/SageCRM.asmx’ --(http or https depends on the version, as does the port number requirement)
WHERE ERPI_IntegrationID = 2 (ID will vary, check first although if you only have one integration, you can simply omit the WHERE clause).

You will then need to go to the integration settings screen in CRM and amend the CRM/ERP user details and Company name information as required.
NOTE: If when saving these you get an error saying ERP credentials are invalid, first of all check the Integration.log file and if this doesn’t show any further information reset IIS and try again
.

Bear in mind that the Admin user will likely have a password on the account. This can be amended to NULL in the Users table so you can easily log in.

You may also experience errors when accessing Account tabs such as Quotes, Orders, Sage 200 Accounts Data / Forms and Relationships or when running reports, such as ‘File does not exist: C:\CRM\CRM2\CustomDotNet\Sage200CRM.dll’.

These errors occur as the customer’s data will be configured to look at particular paths for CRM dll files, reports etc. Unless you have an identical installation path and name, you will more than likely see these errors at some point when using CRM.

There are several paths in the table ‘Custom_SysParams’ in the CRM database which you’ll need to amend. For each ‘Parm_Name’ listed, the corresponding ‘Parm_Value’ should be edited as required.

UPDATE Custom_SysParams

SET Parm_Value = 'NET03'

WHERE Parm_Name = 'ServerNames'


UPDATE Custom_SysParams

SET Parm_Value = 'C:\Program Files\Sage\CRM\CRM\Library\'

WHERE Parm_Name = 'DocTemplates'


UPDATE Custom_SysParams

SET Parm_Value = '/CRM/Library/'

WHERE Parm_Name = 'HTTPDocStore'


UPDATE Custom_SysParams

SET Parm_Value = 'C:\Program Files\Sage\CRM\CRM\WWWRoot\Reports\'

WHERE Parm_Name = 'ReportsRootDir'


UPDATE Custom_SysParams

SET Parm_Value = 'C:\Program Files\fop\fop.bat'

WHERE Parm_Name = 'AdobeConverterExe'


UPDATE Custom_SysParams

SET Parm_Value = '\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones'

WHERE Parm_Name = 'TimeZoneReg'


UPDATE Custom_SysParams

SET Parm_Value = 'C:\Program Files\Sage\CRM\CRM\Library\'

WHERE Parm_Name = 'DocStore'


UPDATE Custom_SysParams

SET Parm_Value = 'C:\Program Files\Sage\CRM\CRM\CustomDotNet\'

WHERE Parm_Name = 'DotNetDllDirectory'


UPDATE Custom_SysParams

SET Parm_Value = 'C:\Program Files\fop\fop.bat'

WHERE Parm_Name = 'SoloClientAdobeConverterExe'

Note: After editing these paths, a metadata refresh should be carried out.

 


Sage Business Partners can now log new cases online!

If you're unable to find the help you require from our online resources, log a new case with us without having to use phone or email. Simply select 'Manage your cases' from the dashboard or visit my.sage.co.uk/cases.