E2S Error Codes
(To enter and find your error use CTRL+F from your desktop or the search bar below)
E11 – Incorrect Sage version set. Cannot process further. Please set correct version of Sage for this computer.
| Code | Recommended Solution |
| S2 | Click Configuration tab – Select Sage Version – Click Save Configuration button |
| S4 | Check Datapath within E2S Company Control is correct – How to check my datapath? |
E10 – Finished loading Customers to Sage with errors. Processing stopped at record 0 – .Net Error: Conversion from type ‘DBNull’ to type ‘String’ is not valid.
| Code | Recommended Solution |
| S6 | Check all the mandatory columns (highlighted in red) have been populated with data on each of the rows |
E9 – Could not read Setup.dta file to see if Foreign Trader Wizard has been run
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
| S4 | Check Datapath within E2S Company Control is correct – How to check my datapath? |
| S5 | Check within Sage that Foreign Trader has been enabled under Tools > Activation > Enable Foreign Trader |
E8 – Sales Order Quote Post Failed, no customer Not connected to Data Source – Connect or Logon failed
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
| S4 | Check Datapath within E2S Company Control is correct – How to check my datapath? |
E7 – Sales Order Post Failed, no customer Not connected to Data Source – Connect or Logon failed
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
| S4 | Check Datapath within E2S Company Control is correct – How to check my datapath? |
E6 – Finished loading Customers to Sage with errors. Processing stopped at record 0 – .Net Error: Not connected to Data Source – Connect or Logon failed
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
| S4 | Check Datapath within E2S Company Control is correct – How to check my datapath? |
E5 – Finished loading Customers to Sage with errors. Processing stopped at record 0 – Sage Error: Not connected to Data Source – Connect or Logon failed
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
| S4 | Check Datapath within E2S Company Control is correct – How to check my datapath? |
E4 – Sage error returned (if any) = Invalid or incorrect username or password
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
E3 – Error connecting to Sage – Invalid or incorrect username or password
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
E2 – You have not yet selected a Sage Version, please select a Sage version on the Configuration tab, save using the ‘Save Config’ button, and finally restart E2S before using the system.
| Code | Recommended Solution |
| S2 | Click Configuration tab – Select Sage Version – Click Save Configuration button |
E1 – Processing stopped at record 0 – Not connected to Data Source – Connect or Logon failed
| Code | Recommended Solution |
| S1 | Check SDO is enabled within Sage – Open Sage – Click Tools – Click Activation – Click Enable 3rd Party Integration – How to enable 3rd Party Integration |
| S3 | Check to ensure the Username & Password chosen in the E2S Configuration tab (usually connector) exists within Sage under Settings > Access Rights in the Sage company you’re trying to import to |
| S4 | Check Datapath within E2S Company Control is correct – How to check my datapath? |
Get in touch
Red IT Solutions Limited
Red IT Lodge
PO Box 40
Rottingdean
Sussex
BN2 8WH
Telephone Options:-
1 – Sales
2 – Sage 200 & CRM Support
3 – Sage 500 & 1000 Support
4 – Red IT Product Support
Opening Hours
09:00 – 17:00 Monday
09:00 – 17:00 Tuesday
09:00 – 17:00 Wednesday
09:00 – 17:00 Thursday
09:00 – 13:00 Friday