Summary

If a customer is experiencing issues with their SPIR environment, it is worth validating that the core SPIR prerequisites are configured correctly. 
 
 These settings are typically completed during the initial implementation but can be reviewed as part of troubleshooting to rule out configuration-related issues.

Symptoms

Customers may experience & report:

• Invoices not synchronising into SPIR
• Access or permission-related errors
• Issues communicating with Sage 200
• Missing companies within SPIR
• Unexpected processing failures

Resolution

Work through the following checklist to confirm the SPIR environment has been configured correctly.

1. Verify SDCServiceUser Exists

Confirm the SDCServiceUser account is present on the same server where Spindle Document Management is installed.

2. Verify the Account Type

Ensure the SDCServiceUser is configured as a Domain User Account and that the associated services are running under this domain account.

3. Confirm Account Credentials

Ensure the password for the SDCServiceUser account is known and available if changes or service updates are required.

4. Verify Sage 200 Remote User Configuration

The SDCServiceUser must be configured within Sage 200 System Administration as a Remote User.

This allows SPIR to communicate with Sage 200 without consuming a full Sage licence.

Related Article

• Sage 200 Remote User Setup: https://draycir.freshdesk.com/a/solutions/articles/24000051009

5. Verify SPIR Role Feature Access

Confirm the SPIR security role has access to the following Sage 200 modules:

• Purchase Ledger
• Purchase Order Processing

6. Verify User Grouping

Ensure the domain account used by SPIR has been added to the SPIR role.

7. Verify Company Access

Confirm all Sage companies that will be used with SPIR have been assigned to the SPIR role.

8. Verify SQL Permissions

Check the SDCServiceUser has the following SQL permissions:

• Read access to all Sage company databases used by SPIR.
• Read access to the Sage 200 Configuration database.
• Access to the Draycir Folder in (C:\ProgramData\Draycir)

Additional Information

When troubleshooting SPIR issues, permission-related problems are often caused by:

• The service account password being changed.
• Missing SQL permissions.
• Companies not being assigned to the SPIR role.
• The service account being removed from the SPIR role.
• The service not running as the correct domain account.

Reviewing the above prerequisites can quickly identify common configuration issues before further investigation is required.

Knowledge Base Article Details