Login/Register
  • Home
  • Community
  • Knowledge
  • Technical Docs
  • RWS Support Policy
  • Trados Studio Licensing Help
  • Login for Support
Back to Search Results

Tridion Docs: Various Large Publish Jobs Fail

000021305 |9/21/2023 2:18 AM
Scope/Environment
Content Manager
Knowledge Center
Tridion Docs 13x 14x
Symptoms/Context
The customer has multiple large publication jobs that they send for publishing in bulk. This issue does not occur every day, but whenever they send multiple tasks or large jobs to publish.

The publication will go through the process successfully until it gets to the “updating status” action where the status then shows “Failed” with “PUBLISH failed with error: The object is used by another user.” It goes through the retries and eventually continues with success.
User-added image
  • They have two batch servers with maxExecutions="3" on both servers for a total of “6”
  • Sometimes the jobs include the same Publication GUID but for different languages. But that is not always the case.
  • The errors are occurring on both batch servers at the same time.
  • The error messages in the logs of both batch servers are consistent. 
    • Trisoft.InfoShare.Configuration.ObjectInUseException: The object is used by another user. ---> System.Data.SqlClient.SqlException: Lock request time-out period exceeded.
    •  Trisoft.InfoShare.Plugins.Publish.PostProcess.Base.PluginBase.LogWarning ISHUPLOADCOMPRESSEDRESULTFILE failed with the message 'The object is used by another user. [140; ObjectInUse]'. The upload will retry after 300 seconds. Retries left: 2.
  • ​​​​​The COC and Database teams have reviewed the SQL server monitoring and logging but did not see anything relevant to resolve.

This looks like a database upload issue. It's a big issue when needing to manage large jobs on a regular basis. Since the system retries after all the other jobs have finished, the job never goes to the Fail log since the retry eventually succeeds. But could take up to 3 retries and slow down the progress of publishes within the queue. 
Resolution

Solution: set/update the following registry keys on batch servers only.

KeyValue 
HKLM\SOFTWARE\Wow6432Node\Trisoft\Tridk\TridkApp\InfoShareAuthor\Trisoft_InfoShare_ObjectLockWaitTimeQuery00:00:20
HKLM\SOFTWARE\Wow6432Node\Trisoft\Tridk\TridkApp\InfoShareBuilders\Trisoft_InfoShare_ObjectLockWaitTimeQuery00:00:20
HKLM\SOFTWARE\Wow6432Node\Trisoft\Tridk\TridkApp\InfoShareAuthor\Trisoft_InfoShare_ObjectLockWaitTimeMax00:01:02
HKLM\SOFTWARE\Wow6432Node\Trisoft\Tridk\TridkApp\InfoShareBuilders\Trisoft_InfoShare_ObjectLockWaitTimeMax00:01:02

Notes:

  • This should be done on the batch servers only.
  • These are system-wide settings.
  • These settings are still valid for Tridon Docs 14.0.4.
  • No need to restart any service after adding/updating the values.

Also please be informed that these keys are available in the public documentation:  Timeout Settings




 
Root Cause
Reference
Send Article Feedback
RWS Machine Translation Translation Software Language Services Content Management
All Contents Copyright © RWS.
COPYRIGHT PRIVACY POLICY COOKIE POLICY TERMS AND CONDITIONS