We received the followng email from Sage Developer Support on Monday 19th January 2015 with regards a possible issue with 3rd party SDO applications (like ConnectIt-Sage50) after installing Sage 50 Accounts 2015 (v21) Service Update 1. We do not expect ConnectIt-Sage50 to be affected by this issue or for any changes to be required to ConnectIt-Sage50 or your Sage 50 Accounts system based on this, but the article is being provided ‘for information’.
From Sage Developer Support Mon 19th Jan 2015:
In the scenarios detailed below, the automatic installation of Data Service Update 1 can cause issues for 3rd party SDO applications. Please note that only a few clients will have been affected by this update.
Scenario
The issue can occur if your applications environmental setup matches the below:
- A 3rd party SDO application is on a computer that doesn't have Sage 50 Accounts installed
- The data is on different computer to your 3rd party application computer
- The SDO file version that your 3rd party application is using is 21.1.5.51
- The Data Service file version is 21.0.3.296/21.0.3.297
These are the effects when using a higher SDO version to post to a Data Service that is a lower version (This will only occur in the above scenario).
Effects when using a higher SDO version than that of the Data Service Version on the data location:
- The SDO reports a successful posting when it is not been
- Posted Invoices are not posted and contain corruption ‘Number # has bad Pointer’
- Ledger transactions (SI,PI,BR...) do not commit to the database.
How to check if your application is affected
We believe a very few 3rd party applications have been affected by this and we are working on a resolution of this issue. If you would like to check if your applications have been affected you can check the file versions of these files below.
| SDOV21 (Sg50SDOEngine210.dll) | 21.1.5.51 | Installed where the 3rd party application is posting from |
| Sage 50 Accounts Service (Sg50svc.exe) | 21.0.3.296 /21.0.3.297 | Installed and running as a service where the data is located |
If you do identify different file versions, you can fix the issue by installing the update from www.sage.co.uk/au.
These updates do not fix postings that have happened retrospectively so you will need to run a check data and repost any missing transactions if there is no corruption.
|
