Salesforce

Ad-hoc scoping in WorldServer 11.3.x leads to inconsistent Total wordcount and error 'Word counts of some assets are inconsistent:' and 'Errors were found in the scoping information'

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentSDL WorldServer 11.3.0, 11.3.1., 11.3.2., 11.3.3, 11.3.4
Symptoms/Context
After upgrading to WorldServer 11.3., when I want to
  • scope my files using the Get Scoping and Estimates link at the last step of the project creation
  • create a Quote and clicking on the Get Scoping and Estimates button or
  • scope one or more files ad-hoc action in Explorer
I see an error in my scoping result window

Word counts of some assets are inconsistent:

or

Errors were found in the scoping information


and a list of the inconsistencies. ​This behavior is not dependent on file format scoping configuration, locale or TM. It happens under every scenario. Below is a screenshot of the issue. As you can see, in all cases the total wordcount is 0, which is incorrect:

User-added image

User-added image

In other cases, the wordcount error happens because the ICE matches that were calculated after segmentation disappear after import of a Return package, hence the total wordcount is incorrect.


 
Resolution
This defect is fixed in WorldServer 11.3.5 and through a Hotfix for 11.3.1.

A more robust fix is now available. This fix is included in two deliverables:
  • In a hotfix for WorldServer 11.3.1.
  • In WorldServer 11.3.5. + Hotfix CRQ-14034. Please make sure you install Hotfix CRQ-14034 for version 11.3.5 as it addresses yet another version of the issue.
Important! All customers who are currently running WorldServer in one of the affected versions must upgrade to WorldServer 11.3.5 as soon as possible and also install Hotfix CRQ-14034.

You can find announcements with link to SDL FTP about new updates in our Community page here.

The specific announcement for the WorldServer 11.3.1. Hotfix can be found here.
The announcement for the WorldServer 11.3.5. Release (which includes the Hotfix as well), can be found here.






 
Root Cause
This incorrect behavior has been filed as defects ID CRQ-9801 and CRQ-14034.
Reference
You can find announcements about new updates here.
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by