Known Issues
The following are known issues in this version.
- Web/App/DB Servers
-
- We strongly advise to redirect your custom integration to
DocumentObj25/PublicationOutput25instead of using deprecated classesDocumentObj20/Publication20/PublicationOutput20. When throughput is important you might receive time out errors on the 2.0 code base with error looking like:Trisoft.InfoShare.API25.InfoShareException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.If you mix this up with 2.5 code, you might also see errors like:System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed outThe main reason for this is that the COM+ based 2.0 calls forceSerializableon the transaction potentially making all calls wait. This problem is resolved when you switch your custom code to the 2.5 API calls; this is also what we did for all of our clients (e.g. Publication Manager, AuthoringBridge, DITA2Trisoft, etc). [TS-8739] - Failed transactions block any further update on locked content objects (DocumentObj) or publication outputs (PublicationOutput) requiring manual actions to roll back the transaction. The following characteristics identify the problem:
ORA-01591: lock held by in-doubt distributed transaction trans_idorORA-02049: time-out: distributed transaction waiting for lockin the log files.- The Microsoft Component Services panel holds entries marked with
(only failed to notify)in the . For exampleISAuthor.CPublicationOutput (only failed to notify)orISAuthor.CDocument (only failed to notify).
isource. Usually near expiration time you'll see the messages appear likeORA-28001: the password has expiredorORA-28002: the password will expire within x days. We advise you to contact your DBA on this, the following statements are provided for convenience only:- First check which profile
ISOURCEis using:SELECT profile FROM dba_users WHERE username='ISOURCE'; - Optional query to show all the limit settings of this profile:
SELECT resource_name,limit FROM dba_profiles WHERE profile='DEFAULT'; - Change the default profile to set the password lifetime to unlimited:
ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED; - After setting the password lifetime you have to reset the password again. You can set it to the same password as it was:
ALTER USER isource IDENTIFIED BY isource; - We advise you to restart the database and any web/app server.
- In case of network stability or connection problems (like
ORA-03113 end-of-file on communication channel) we advise you to setup the "Oracle Microsoft Transaction Server (MTS) Recovery Service" as documented on http://docs.oracle.com/cd/E11882_01/win.112/e26104/recovery.htm#NTMTS003. This service resolves in-doubt Microsoft Transaction Server transactions. [TS-7822] - The EventMonitor logging system potentially shows the wrong final status
FAILEDin the overview; although it was actually aSUCCESS. A failure is logged, but then the generic or the PublishService retry mechanism is started that potentially results in a success. The EventMonitor logging system thenCALCULATEs the result in the overview. [TS-8560] - Upgrading from SDL Trisoft 3.8.X to SDL LiveContent Architect 10.0.X using an Oracle 10 database can cause problems with the isource.i script. The difference between scripts is:
revoke ALTER USER from ISOURCE / revoke CREATE USER from ISOURCE / revoke DROP USER from ISOURCE / GRANT CREATE SYNONYM TO ISOURCE / GRANT CREATE JOB TO ISOURCE/ - At installation time, it is important to note for InfoShareSTS usage that
hostname,baseurlandlocalservicehostnamecan not be the same. It is not allowed to have the same value in the hostname ofbaseurlandlocalservicehostname. InfoShareSTS fails because it creates two sets of relying parties with same identifier. [TS-4693] - The automated shut down of the
Trisoft-InfoShare-AuthorIsofailed application sometimes results inInvalid syntax. You may ignore this message. - Renaming languages in settings area will not adapt @xml:lang and language combinations [TS-6472]. Avoid changing the label of a language (for example, from en to EN or en-us) when it is in use, because the following problems can occur:
- When changing the label of the language, the existing files in that language are not automatically adapted therefore they become invalid. This happens because the xml:lang attribute and the processing-instruction no longer match the label of the language. In this case, you would have to resubmit each file.
- The publication outputs that have a language combination containing the modified language become invalid and must be recreated.
- We strongly advise to redirect your custom integration to
- Non-Western Language Searches
-
- Solr uses the Boolean
ORoperator when multiple words are detected in a search. Note also that for non-Western languages, Solr uses language analysis features to break down terms into smaller components, so if you enter a Japanese search for リンク解析 Solr breaks it into two words: リンク and 解析. In this case, the default behavior is to search for リンク OR 解析. This may not return the expected results. - Therefore, when you search in non-Western languages such as Japanese, Solr can be configured to use the Boolean
ANDoperator between words instead of the defaultORoperator. - To specify the Boolean
ANDoperator in these instances, add<str name="q.op">AND</str>in the<lst name="invariants">part of therequestHandlersection in the \TrisoftSolrLucene\SolrLuceneCatalog\conf\solrconfig.xml file. - If this is done, when Solr uses its language analysis features to break down a term into smaller components, the Boolean
ANDoperator is applied instead of theORoperator. However note that this does not affect words entered with a space between them as the search criteria. A whitespace between words assumes use of the default BooleanORoperator. [TS-6497]
- Solr uses the Boolean
- Client Tools
-
- You cannot connect with a second user to the same data source if the first user was already connected to the same data source. You can have two accounts, so two usernames, pointing to the same repository. You just cannot be connected at the same time. Switching accounts requires a client tools restart. [TS-8656]
- When using the
<stylesheet>element in StyleSheets.xml at<download>time, you are actually forcing an XSLT processor to handle the file from the repository. The XSLT processor will always add default attributes - like@class,@domains,@ishlabelxpath, etc - to the resulting XML file. Our typically configured Filters/Dita11ToDita12.xsl which takes care of automated@navtitleattribute to<navtitle>element conversion immediately removes these unwanted default attributes again. Stripping does not happen for the@processing-roleattribute on the<keydef>element. You can either disable the<stylesheet>or tweak the XSLT file to your needs. [TS-8692] - Although multiple third-party XML editors are supported in this release of SDL LiveContent Architect, use of a single third-party editor is recommended. SDL is not responsible for how the third-party editors handle XML and DITA and the behavior might differ for each XML editor. As a result, if you use more than one, you may find cross-compatibility issues with the way the different editors handle DITA. If you decide to use multiple third-party XML editors and find cross-compatibility issues with DITA, SDL recommends that you work with the vendor of the XML editor to resolve the issue. [ TS-4957|TS-5260]
- Only 32 bit versions of the xml editors are supported.
- Uninstalling the Authoring Bridge for XMetaL on Windows 7 causes a problem when you then try to upgrade to the new installation. You must first uninstall XMetaL then you can uninstall Authoring Bridge.Reinstall XMetaL then upgrade or reinstall the Authoring Bridge. [SCTS-380]
- Although not supported, when installing Client Tools 10.0.3 on a Server 10.0.0/10.0.1/10.0.2 you might run into a compatibility issue. Reason is that the Trisoft.Utilities.ServiceReferences.dll assembly has been extended with a new class to do WCF http compression in the .NET 3.5 world. The Client Tools MSIs are not always allowed to overwrite the server-side's older version of the assembly. This results in messages like "Unable to establish a connection with the web services on" or "Could not load type 'Trisoft.Utilities.ServiceReferences.WebClients.CompressibleHttpRequestCreator'" [TS-7169]
- Client Tools 2013 (10.1.x) can currently not be installed next to existing 2011R2 (9.3.x) ones - versions of the Authoring Bridge fight over resources in the XML Editors. You must uninstall all prior versions of the Authoring Bridge (as noted in the installation document) before installing a new version. [SCTS-167]
- Translations to Japanese are missing: [TS-4696]
- Search options in the find dialog; match case, search up, match whole word
- cut/copy/paste in the standard toolbar
- ; searching on a version is always done on AllVersions [TS-4222]
- Only references to DITA topics and DITA maps are supported. References to images and other formats (for example, PDF, DOC) are not properly supported or not supported at all. [TS-5731]
- Although Microsoft Windows 8 is not supported for the SDL LiveContent Architect Client Tools,
Microsoft .NET Framework 3.5 Featuresmust be enabled on your system before installation. [TS-6428] - In ServiceReferences there is no check about the ability of a user to enter the application. So the authentication works but Architect or Reach might still block authorization by a ProfileMismatchException. [TS-4292]
- Client Tools using SSL might crash when using a Url that doesn’t match the certificate. [TS-571]
- Client Tools cannot handle Architect accounts that contain a slash (/) or back slash (\) because it confuses them while handling other authentication requests coming from Secure Token Services or Proxies that potentially require NTLM/Windows authentication. [TS-8312]
- When using a secured proxy, the client tools browser component could popup an extra authentication dialog. [TS-4680]
- Avoid opening multiple instances of editors (so there is only one process of the editor running) to prevent possible locking of files in the profile folder of the Gecko renderer component. [TS-4682]
- Where Used Report [TS-7037] known issues. When doing a where used on an object in the client tools, beware that the shown publications are determined by performing a PublicationOutput25.Containing API method which means:
- The
PublicationOutput25.Containingfirst calculates the baselines in which the logical object is present (seeBaseline.Containing). These baselines are used to retrieve the publication versions (seePublicationOutput.UsingBaseline). Consequently, when the baseline is shared between multiple publications, the result can contain publications in which the topic is not used. - Selecting a specific version of a map forces version selection for all referenced topics. Changing the version of a map can give less referenced topics, but those topics could still be in the baseline. This can result in publications shown in the report where the topic is no longer used.
- If a library contains @conrefs with illustrations or links to other topics, all referenced objects will be returned as part of the publication, even if they are not used.
- If a library contains variable definitions with illustrations or links to other topics, all referenced objects will be returned as part of the publication, even if they are not used.
- Conditional filtering is ignored!
- The
- The current list of elements explicitly resulting in resolved link text in the Client Tools preview are: <xref>, <link>, <topicref> and their basic @class attribute based specializations. Many other elements like the <mapref>, <topicsetref>, <anchorref>, <topicgroup>, <topicset> elements or <navref> will not be resolved while previewing. [TS-8298]
- When creating a folder you can assign a UserGroup where the current user has no access to. The folder will be created, but any refresh action afterwards will not show you that folder and potentially can trigger an error message like
The object does not exist. [c:"894969"][TS-8652]
- Adobe FrameMaker 9/10
-
- FrameMaker +DITA-FMx only: Cannot insert a conref to a row element. After inserting a conref to the row element, an error is displayed: Could not insert element row. [TS-6555]
- After SDL LiveContent Architect synchronization, I see a structapps.fm file opening and closing again. Working as designed. This is done when synchronizing the FM templates. It can happen after the first synchronization or when a template changes for the FrameMaker authoring tool.
- Arbortext Editor 6.0
-
- The SDL LiveContent menu and the Insert Markup action to insert elements works and will trigger the necessary Authoring Bridge dialogs. All other functionality such as the direct Insert menu items cannot properly be redirected to the RepositoryAdapter and pops-up with Arbortext Editor's file system integration.
- Conrefend attribute is not displaying in the Modify attributes window.
The conref attribute was removed from the Modify Attributes dialog. Use menu option, in the editor to insert a conref or a conref range. [TS-5593]
- The conref attribute was removed from the Modify Attributes dialog when you have an SDL LiveContent Architect document opened in the Arbortext 6.0 editor. Users must use the menu item, , to insert a conref or a conref range in their document.
- JustSystems XMetaL 8.0/9.0
-
- Publishing from within XMetaL is not supported; the following menu items are not fully supported (may not work):
- File > Generate Output for DITA Map...
- File > Generate Output for DITA Topic...
- File > View Output Log...
- File > Preview in Browser...
- Local Publish with a Topic/task etc. which has an xref inside does not work. [TS-5182|TS-5184]
- The Page Preview view is not supported (may not work). [TS-5526]
- Page Preview error
null is null or not an objectwhen xref topic contains unresolved references. [TS-4438] - Do remember that like in SDL LiveContent Architect 2013 when installing the Authoring Bridge for XMetaL on Windows Vista/7 machines you have to have full access to folders C:\Program Files (x86)\Common Files\XMetaL Shared and C:\Program Files (x86)\XMetaL 6.0 before doing the installation.
- Starting from version 10.0.3 we support XMetaL version 8 in English and Japanese. However when inserting an image you will experience that the
@widthand@heightattributes are persisted potentially causing roundtripping problems if your image resolutions/renditions vary in dimensions. This issue is communicated to JustSystems. [TS-7120] - XMetaL will show the value of an
ishconditionattribute that contains the following special characters ", <, >, & in the Tags On View and Normal View with their corresponding XML character entities ", <, >, &. Note that all other characters should not be shown as XML character entities.For example the following
ishconditionvalue:Department='R&D' and version > 3.1.1will show up as:Department='R&D' and version > 3.1.1. [TS-8004] - Inserting a @conref to a multimedia object is not always resolved corrected. Either it shows you the object twice or it shows a blue outlined diamond. [TS-8458|TS-8663]
- Publishing from within XMetaL is not supported; the following menu items are not fully supported (may not work):
- <oXygen/> XML Author/Editor 15.2/16.0
-
- Issues with Find and Replace when used on a DITA map. A common error made when doing a find/replace on map is setting the wrong filter in the Include Files field of the UI. When performing a find/replace on a map, users should change the filter to the asterisk wildcard character, *. The default is *.*. (Only on 15.2)
- Add account window does not disappear after pressing Cancel. This is a known issue when using remote desktop technologies. [TS-5654]
- <oXygen/> XML Author/Editor does a save operation on all your open files when you access an AuthoringBridge menu, which allows you to CheckIn or CheckOut. The issue is caused by a different threading paradigm between the JAVA based xml editor and the .NET based AuthoringBridge SDK components.
- <oXygen/> XML Author/Editor is only available on a Microsoft Windows platform because the AuthoringBridge SDK is comprised of .NET libraries
- <oXygen/> XML Author/Editor menu items and buttons do not get disabled when a document is visible in the editor but not checked out. The user can still access the dialogs and perform actions which can be confusing because the document is locked and cannot be edited. [TS-5140]
- SDL LiveContent Create
-
- Selecting a range of contiguous conref targets is not supported in SDL LiveContent Create. [LCDE-385|LCD-2229]
- Publication Manager
-
- When a conref is made to an image in the same topic, an erroneous message is displayed for circular references:
Warning: The object <x> is mentioned within the object itself, creating a circular reference. [TS-3449] - When you change the Review End Date of a publication output in Publication Manager or Web Client after the output was already published, the status is changed to Out of date .
Working as designed. Note that when any metadata field is changed on the publication output, the status of the publication output is changed to
Out of date. This happens because the metadata (in this example, theReview End Date) may have been used in the publication, for instance, on the front page, therefore the published result can now be out of date. [TS-3093] - Find option (CTRL+F) in Publication Manager for the current document no longer has the option to "Match whole word".
The find on a whole word functionality was dropped; it is not supported by the new browser component (Gecko). [SCTS-469]
- After checking in topics, there is a delay before the changes can be found by the search. When using the scope 'Current Publication' it will be asked to check in the topics, but even then changes might not be part of the search results.
There is a delay between checking in and the indexing into the full text index. A refresh of the search result pane will resolve the problem after the index is generated for the checked in topics. [TS-8322]
- There is no cursor when adding or replying to a comment in the Publication Manager. Typically happens when you switch to another application and then move back to Publication Manager. The issue is a bug in the Gecko renderer component.
- Comments pane title in Publication Manager does not resize correctly. For screen resolution settings 1024x768 and lower, the Comments pane display in Publication Manager may have display problems. [SCTS-168]
- Inbox gives an error when one of the files in the list has a conref - conrefend pair that don't refer to the same document. The error is:
Begin and end id require to be in the same document when a bookmark is given. [TS-2207]
- When a conref is made to an image in the same topic, an erroneous message is displayed for circular references:
- Web Client
-
- You can create a logical id with spaces however when you try to use a template to create the initial document, it errors. For example: The object "JIRA TS 2031" contains invalid XML. Multiple names found in attribute value when only one was expected. The OASIS DITA document types specify the @id attribute as a true identifier blocking spaces in the identifier. In a future version we will completely block usage of spaces in identifiers. [TS-2110]
- Sort on Inbox items not correct; uppercased letters come before lowercased ones which is the typically ASCII sort based on their numerical (not alpha) representation. [TS-2933]
- New Slide-Out Navigation pane and Dashboard page is not supported in Microsoft Internet Explorer 8 (IE8) and earlier.
- Actions triggered through the web client don't allow to update baseline entries. A web client triggered will reuse any existing baseline and trigger an auto complete action when required. For example, creating a publication in the web client and trying to get it to status Released will not work as at no point in time the baseline received version entries. [TS-8633]
- Preview
-
- Web client preview of SVGZ results in an XML parsing error. The XML parsing error is caused by the mimetype. The mimetype for both SVGZ is text/xml+svg. The text/xml portion of the mimetype enables SDL product components to process the content as XML. However, the SVGZ content is actually a zip archive of SVG content. That is, the format is not XML, but a zip archive of XML text. The zip archive of XML content causes the parsing or loading error. [SCTS-532]
- WMF and TIFF files are not displayed in the preview. They cannot be rendered by any client tool or the web client.
- Other
-
- When conrefing a
glossentrywhich is part of aglossgrouptopic, aglossentryis created with an incorrect value in theconrefattribute. Publish warns that there is an unresolvable conref during publish because the conref value is incorrect. [TS-4630]
- When conrefing a