Fixed issues in 13.0.0 Web/App/Db server

The following issues are fixed in Content Manager 13.0.0 compared to 12.0.0.

Secure Token Service - Authentication and Authorization

  • Improved error messaging/handling for ISHSTS, ISHCM and ISHWS when the certificate thumbprint is not found avoiding generic errors Exception type: InvalidOperationException and Exception message: Sequence contains no elements. [TS-11468|TS-10632]

Installing and Upgrading

  • In some situations, the command line InstallTool ended with an interactive mode Press any key to continue message. [TS-10910]
  • Admin.XMLBackgroundTaskConfiguration.xml configuration for ISHSYNCHRONIZETOLIVECONTENT event will now only synchronize Low resolution images out-of-the-box, matching the OutputFormat configuration. So in Settings > Background Task Xml the entry <plugin name="ISHSYNCHRONIZETOLIVECONTENT" handler="SynchronizeToLiveContent"> is advised to be tuned to <plugin name="ISHSYNCHRONIZETOLIVECONTENT" handler="SynchronizeToLiveContent" ishcondition="FRESOLUTION='VRESLOW'"> which in turn means less objects will be synchronized which increases throughput. [TS-11478|TS-11046|SRQ-4709]

PublishService

  • By default PublishService retrieves metadata over API20 which does not handle IMetadataBinding (so taxonomy integration), toggling TRISOFT_INFOSHARE_PublishService_UseMinimalRequestedMetadata does, but the registry key was not used for the Publication and publicationOutput metadata retrieval which is now corrected. [TS-12361|SRQ-6428]
  • When publishing the metadata is retrieved over API20 by default. Unless TRISOFT_INFOSHARE_PublishService_UseMinimalRequestedMetadata is enabled because then API25 is used. There is a difference in behavior between API25 and API20 RetrieveMetadata file (fields not present on a card type are not returned with API25) no longer cause publish to DITA XML to fail. [TS-12407|TS-12464]
  • When a publication was published to PDF with the Compare functionality activated, any failure in a comparison (either engine or result is not xml well-formed) between versions of specific objects made the whole publish process fail. Now only that specific comparison is skipped and the specific object is displayed in the final result as having been entirely changed. The publication itself completes. [TS-11365|SRQ-5060|SRQ-4837]
  • PublishService PrepareForExport function didn't always receive a properly wrapped xml validation error when the origin type was System.Xml.Schema.XmlSchemaException. [TS-10917|TS-10862]
  • The length of publication titles can lead to exceeding Windows file path length limitations. Long titles are now truncated instead of failing the publication with errors like Following error occured: 76 - ???????????. [TS-10639|TS-11474|SRQ-4340]
  • More extensive handling of the DITA-OT log file makes potential errors and warning visible through EventMonitor, so without server access. The end result of publish is still the same, so when DITA-OT.log contains a BUILD FAILED, the status of the publish becomes Failed. More log file content will become available through EventMonitor. Everything starting from the first [Fatal Error] or XML document structures must start and end within the same entity. message - so more than the last 20 lines of DITA-OT.log. Unfortunately, the errors generated by the various DITA-OT versions are not consistent enough to generically fine tune the publish status result of Release Candidate or Draft - it is different per type like CHM, PDF, etc. [TS-10788|TS-11475|SRQ-4972|SRQ-4201|TS-11601]
  • The internal EDT conflict that made some PDF publish fail whenever Content Manager was upgraded from 10.0.X or earlier to 12.0.X has been solved by code changes in PublishService, ISHPublUtil.vbs and publish.wsf. [TS-11317|TS-11419|SRQ-5249]

TranslationOrganizer

  • Translation Organizer: for jobs involving external systems, the job information in the log file now specifies the result of steps that completed successfully. [TS-10565]
  • Translation Organizer: The file system export for translation no longer creates empty archives. [TS-11504]
  • When the Translation Organizer is killed during an export, it no longer resets the exported file counter. [TS-10281]
  • TranslationOrganizer now has a more precise reporting of issues caused by files sent back by WorldServer. The RetrieveTranslationJobItems API now includes two new fields that help finding the exact files containing DTD-invalid XML: The ERROR and EXTERNALSTATUS fields [TS-10304|TS-10305|TS-11557|TS-11558|SRQ-4069].
  • The log files now contain the precise statuses that are dynamically detected by TranslationOrganizer during the run. The statuses are printed at the beginning of the log [TS-12057].
  • Translation Organizer is now more resilient regarding imperfect network setups causing the occasional HTTP status 502: Bad Gateway error. In the past this caused Translation Jobs to move to a manual recovery status requiring user action. Now safe (idempotent) calls like retrieving items or status moves will be retried; but for example an actual second submit of a job to the translation management system could incur double costs which is a conflict that still requires manual handling. [TS-11096|TS-10422|TS-11090|SRQ-4195|SRQ-4714]
  • Some transmission issues have also been fixed, such as the processing of Logical Identifiers having GUIDs with dots (.) as separators. An issue which was introduced on 2016/12.0.0. [TS-11273|TS-11269|SRQ-4960]
  • Added example uri of SDL WorldServer and SDL TMS into the TranslationOrganizer.exe.config. [TS-11473|TS-10789|SRQ-4464]

BackgroundTask

  • Reducing the size of logs for BackgroundTask.exe and BackgroundTaskIso.exe by raising the default NLog.config level from Debug to Info. In practice the spinning wheel polling log entry will be avoided. [TS-10911|TS-11477|SRQ-4584].

Other

  • For the ExportObjects BackgroundTask handler implementation of events like INBOXEXPORT or PUBLICATIONEXPORT. The algorithm for reducing the size of titles for exported files has been modified to adapt to cases when the file extensions have different sizes. For example, .met files that are created when .ai files are exported have a title longer by one character. This no longer generates errors. [TS-12500|SRQ-6677]
  • We don't log method enter/exit or anything from Trisoft.InfoShare.COMAPI in order to avoid NLOG.config changes causing deadlocks [TS-12034|SRQ-5807].
  • Improved recovery for IIS Application Pools that failed to re-initialize because the database was unavailable during their first initialize attempt [TS-12134|TS-12157|SRQ-6051].
  • In some upload and prepare situations, cancelling a publish process from Content Manager failed to unlock the publication in Collaborative Review. This has been fixed. [TS-11398|TS-11399|SRQ-5088].
  • Duplicate values are now removed from the FISHLINKS and FISHFRAGMENTLINKS fields of the ISHSYSFRAGMENTLINKSTOMETADATA write plugin whenever a topic contains the same conref multiple times or contains multiple conrefs from the same library. [SCTCM-83|SRQ-7227]