Introduction

When a Test server has been used during the process of upgrading Sage 200 a Test Licence is applied to the Test version of SDM and SPIR. When the Test Server is ready to be made Live, the Licence will need be updated to the existing Live licence that was previously activated on the old Live server.

The steps required are as follows:

1. Backup xml Files

All SDM/SPIR related xml configuration files should be backed up before the Live licence is activated, this means if any issues occur the files can be reverted back to the previous state. The xml files and their locations are:

File name - Configuration.xml 

Location - C:\ProgramData\Draycir\Spindle Document Capture\Server\Data

File name - RecognitionConfiguration.xml

Location - C:\ProgramData\Draycir\Spindle Document Capture\Server\Data 

File name - Configuration.xml 

Location - C:\ProgramData\Draycir\Recognition\Cloud Sync\Client 

File name - Configuration.xml 

Location - C:\ProgramData\Draycir\Recognition\Post Agent\Client 

2. Edit the xml Files

Each xml file has an entry within specific tags, i.e. <>. each tag will require editing to remove any reference to the old Activation code. This will force the activation code to be required to be entered again.

Open each of the Live XML files and open with notepad or similar to allow editing of the file.

Each xml file as listed above will have a section that contains an encrypted licence string. Each licence string is contained between a reference tag e.g. <SubscriptionVersion>, the value inbetween these two reference tags must be deleted. Edit each xml file as follows and then save the file with the information inbetween the tags removed: 

(C:\ProgramData\Draycir\Spindle Document Capture\Server\Data\Configuration.xml) 

Before editing the <SubscriptionVersion> reference tag:

(C:\ProgramData\Draycir\Spindle Document Capture\Server\Data\Configuration.xml) 

After editing the <SubscriptionVersion> reference tag:

(C:\ProgramData\Draycir\Spindle Document Capture\Server\Data\RecognitionConfiguration.xml)

Before editing the <RecognitionApiClientCredential> reference tag:

(C:\ProgramData\Draycir\Spindle Document Capture\Server\Data\RecognitionConfiguration.xml) 

After editing the <RecognitionApiClientCredential> reference tag:

(C:\ProgramData\Draycir\Recognition\Cloud Sync\Client\Configuration.xml) 

Before editing the <DraycirAccountCredential> reference tag: 

(C:\ProgramData\Draycir\Recognition\Cloud Sync\Client\Configuration.xml) 

After editing the <DraycirAccountCredential> reference tag: 

(C:\ProgramData\Draycir\Recognition\Post Agent\Client\Configuration.xml) 

Before editing the <DraycirAccountCredential> reference tag: 

(C:\ProgramData\Draycir\Recognition\Post Agent\Client\Configuration.xml)

After editing the <DraycirAccountCredential> reference tag: 

3. Restart the SDM Services

Open Spindle Document Management Server Administration Tool (Server Admin), select Manage Services and click Stop:

Once the Service is available to Start, click Start.

4. Re-Licence SDM & SPIR

Once the Services have been re-started the Test Activation code will be removed and the Live Activation code can be added:

Click the Licence button then the Activate Product button to prompt the Activation Window:

Input your details and the Customer's details for the SDM Activation. The Customer name and Activation code must be entered in the same format as provided by Draycir Licensing:

The SPIR Activation code also needs applying, select the Recognition button at the bottom of Server Admin:

Click the Activate button

Input your details and the Customer's details for the SPIR Activation. The Customer name and Activation code must be entered in the same format as provided by Draycir Licensing:

5. Run the Spindle Document Recognition Updater Tool

6. Re-configure the SPIR Tooling to point to the Live Sage 200 Companies

Once SDM and SPIR are re-activated check the Sage Companies in SPIR are pointing to the Live instances. 

Open SPIR Configuration from the Spindle Document Recogntion SA Window:

In the Companies tab check the companies listed are the correct Live Sage 200 companies.

If the companies listed are the Sage 200 companies used during testing delete them and add the correct Live Sage 200 companies that are used with SPIR, including all relevant Name Variations for each company.

7. Open the Document Portal to check that no errors occur

Open the document portal to confirm that invoices previously processed in the Live environment are available to be viewed. This confirms the Live environment is now accessible.

8. Uninstall SPIR Services
Once testing is confirmed as successful on the new Live environment, which may not be the same day, uninstall both the SPIR Services; Spindle Document Recognition Post Agent and Draycir Cloud Synchronisation Agent. This ensures there are no conflicts of services for Purchase Invoice Recognition. Failure to remove these services will cause problems with posting of invoices to Sage 200.

Knowledge Base Article Details