Known issues

These issues apply to the most recent release of SDL Contenta. If available, workarounds are provided.

Table 1. Installation and Upgrade
Issue numberDescription
CAS-7111Tomcat 8.5 directory is reported as invalid or version is not supported error

During installation, an error message similar to the following may be encountered.

Tomcat Home directory is invalid or Tomcat version is not supported.

Explanation/Resolution: To work around this issue, copy the Tomcat_home\bin\tomcat8*.exe file to Tomcat_home\bin\tomcat8.exe.

CC-2705Standalone Dynamic Import does not use the specified server and database.

When installed as a standalone module, Dynamic Import may not connect to the server and database specified for your map file (e.g. play.map) in the Server and Database fields of the Dynamic Import window.

Explanation/Resolution: To work around this issue, use a text editor to manually enter the database name, server, and port in your map file. Save the file and restart Dynamic Import.

CC-1987During installation or uninstallation of CE on Windows 10, you may be prompted to install the .NET Framework 3.5.

Explanation/Resolution: You are prompted to install .NET Framework 3.5 because Contenta Explorer installer tries to register .NET libraries, which are only required if the user is planning to develop a Contenta application using Contenta .NET Libraries. To work around this issue, skip the .NET install when prompted (close the prompted .NET dialog) and the install/uninstall will proceed.

CC-1981After installing XPP, Contenta portal fails to start, with the following error:

Windows could not start the XyEnterprise Contenta Server service on Local computer.

Explanation/Resolution: The XPP installation modifies the Path environment variable to, which may make it invalid for Contenta on some Windows systems. Verify that the value for the Path environment variable is correct after installing XPP.

CC-1769If you change the name of the Tomcat service from Tomcat8 while installing CW, the installer fails to locate the service.

Explanation/Resolution: Uninstall the Tomcat service and reinstall it with the name Tomcat8.

CC-1725When upgrading Contenta server on Windows 2012 all-in-one server, you may encounter a Windows error message stating that .Net Framework 3.5 could not be installed.

Explanation/Resolution: Disregard this message; it displays even though the framework has been installed properly.

CC-1704On some Windows systems, when you install or upgrade Contenta, you may encounter an error such as the following when the Contenta installer tries to register DLLs:

Error registering Contenta_Install_Location\system\PCMtoolsAPI.dll - regsvr returned exit code 3.

Alternatively, when Contenta Explorer is launched for the first time you may encounter a Contenta Explorer has stopped working error with a DLL as the Fault Module Name.

Explanation/Resolution: These errors are due to missing low-level dependencies that are part of the Visual C++ redistributable package. If the Contenta installation program fails to register some Contenta DLLs, you must download the required redistributable packages and manually register the Contenta DLLs that couldn't be registered before. You should manually register DLLs from a command window opened as an Administrator.

CC-1662Under certain conditions with Oracle 11g, you may get errors similar to the following when exporting a Contenta database:
 . . exporting table COMPOUNDBINARY
				       EXP-00003: no storage definition found for segment(0, 0)
				       . . exporting table COMPOUNDDOC 
           EXP-00003: no storage definition found for segment(0, 0)
				

Or you may get errors similar to the following when upgrading a database:

*****Error creating routing history field on Document: SQL Error Code -942

Explanation/Resolution: This could be because of the Oracle settings specified for deferred segments when the database was imported or exported. Please contact customer support for guidance on how to resolve this issue.

CC-1660During the installation, an inactive and un-refreshed database settings window entitled Contenta Server Setup with a header Contenta Database Settings may appear in the background. You can ignore this window.
42875In Linux and UNIX environments, the SDL Contenta Web installation hangs for over an hour while searching for the Java Virtual Machine.
Explanation/Resolution: The workaround is to specify the full path to the java executable when running the setup.jar file, rather than letting the operating system find the java executable. For example:
/usr/jdk1.7/bin/java -Dis.debug=1 -cp setup.jar run
42825On some UNIX and Linux environments, the installation CD cannot be mounted in a DVD drive.
Explanation/Resolution: When mounting the drive for the installation CD, specify that the drive is to read the content as a cdrom. For example:
mount -F hsfs -o ro,nomaplcase /vol/dev/dsk/c1t0d0/681366 /cdrom/681366
42527The ‘_uninstall SDL Contenta Editor Extensions’ folder is not visible after doing a new SDL Contenta Editor Extensions installation when editors are installed after the SDL Contenta installation.

Explanation/Resolution: This is because we are circumventing the usual installation process and installation is to be done by hand, so uninstallation must be done by hand.

42523Contenta uninstaller on UNIX: The SDL Contenta uninstaller on Solaris and Linux removes the /pdm link.

Explanation/Resolution: Recreate the /pdm link.

39823Windows Only: Client and server installs, when installed or upgraded by Administrator: Administrator user takes ownership of the Dynamic Import, Checkout, Logs, and temp directories.

Explanation/Resolution: Refer to the SDL Contenta installation guide for post-installation steps to correct this issue.

Table 2. Contenta Explorer
Issue numberDescription
CC-2811Dynamic Import File Import does not allow selection of a folder with ISO-8859-1 characters in its name.

Explanation/Resolution: To work around this issue, select only parent folders with only ASCII or Unicode characters in their names.

CC-2706Dynamic Import fails to launch on Contenta Explorer or from the command line for a user without administrator privileges. The following error message is displayed.A system error occurred while converting "distribution config file".

Explanation/Resolution: To work around this issue, remove the Read-only attribute from the Contenta_home directory, including its sub-directories.

CC-1719Attempting to copy and paste a folder containing objects into a ContentRoutingProject results in a server-side portal error.
42512SDL Contenta Explorer crashes when trying to create a CompoundAscii object.

In Oracle 11gR2, a new deferred segment creation feature was added. This feature enables you to defer creation of the initial segment until the first row of data is inserted into the database table.

To check whether the database is compatible with Oracle 11gR2, run this command as database administrator:
SQL> show parameter compatible
The results should be in this format:
compatible string 11.2.0.0.0
To check whether the deferred segment creation feature is enabled, run this command as database administrator:
SQL> show parameter def
The results should be in this format:
deferred_segment_creation   boolean   TRUE
Disable the deferred segment creation feature by running this command as database administrator:
SQL> alter system set deferred_segment_creation=false scope=both;

If you have problems importing a database because the deferred segment creation feature was enabled when the original database was created, please contact SDL Customer Support.

40183Upgrade customers only: Creation of a WordHybrid object fails.

Explanation/Resolution: The WordHybrid object is not a valid SDL Contenta object in this release. It will be removed from the New Object menu in a future release.

38828When creating a user desktop with a long name and the login name is longer than 49 characters, if the user accepts the default (that is, the login name), the desktop creation process reports errors.

Explanation/Resolution: The login name may not be longer than 49 characters. Change the default login name to be shorter.

38827If a Long Names field in Contenta Explorer contains a backslash (\), it is removed from the property field. For example, C:\graphics\gif is saved as C:graphicsgif.

Explanation/Resolution: Enter a backslash as \\. For example, C:\\graphics\\gif is saved as C:\graphics\gif.

Table 3. Editor Tools
Issue numberDescription
CRQ-13423fm version error when launching FrameMaker
When opening a document in FrameMaker, the following error message may be displayed:
The file's fm version (13.0) does not match the version of this product.
Explanation/Resolution: To work around this issue, perform the following steps.
  1. Back up the FrameMaker_home\Structure\xml\default.rw file.
  2. Open the FrameMaker_home\Structure\xml\default.rw file in a text editor.
  3. Change the FrameMaker version in the file to 7.0.
  4. Save and close the file.
CRQ-10444Contenta menu did not appear after installing the editor extension

The Contenta menu may not appear after installing the editor extension if the name of the menu file has been changed from .Help, for example, when the menu is translated from English. This issue may occur because the EpicEditCatMain.acl ACL file, which adds the menu looks for a menu named .Help.

Explanation/Resolution: If the name of the Contenta menu file has been changed, edit the EpicEditCatMain.acl file to refer to the current name of the menu file. For example, if the menu file is translated into German and its name changed to .Hilfe, change each instance of .Help in the ACL file to .Hilfe.

43064XML Fetch/View: Parsing errors may occur when using XML Fetch or XML View on content that contains Arbortext Editor change tracking.
42526Intermittent XMetaL issue that seems to be caused by a bug in the XMetaL installation that only affects vendors with custom code such as ours. Symptoms: The document doesn’t open and XMetaL won’t stay closed when you exit because it is stuck in an initialization loop. Or, you may see an “automation error” or the following error message: ActiveX Component can’t create object XyeXmCatXMCat.
Explanation/Resolution: Manually register XMetaL as follows:
cd XMetaL_home\Author
xmetalnn.exe/RegServer
where nn is the version (for example, xmetal60.exe).
38961When creating an object-mapped element in the editor that contains no data, the inheritance for the ElementType attribute field is set to inherited (that is, inherited from parent) rather than local (that is, defined in the object itself). In addition, the inheritance is lost when the object is reused to a Project. This default cannot be edited since it is disabled, so you cannot change it to local.

Explanation/Resolution: Delete the entry and manually create it with inheritance set to local.

38829If the checkout path length is greater than 100 characters, the checkout directory is not created.

Explanation/Resolution: Change the checkout directory path to be shorter.

Table 4. Contenta Web
Issue numberDescription
CC-2710The Workflow Template editor sometimes fails to save a template.

Explanation/Resolution: This issue occurs because the Contenta Web Workflow editor does not place a lock on the template when it is opened. If a Contenta Explorer subsequently opens and locks the template, the Workflow editor will fail to save the template with a server-side portal error.

CC-2709The Workflow and Workflow Template editors do not warn that edits will be lost when the user closes the editor window by clicking the X.

Explanation/Resolution: Always save the changes before closing the editor window.

CC-2708On login, Contenta Web sometimes does not expand the tree view to display the location saved at the end of the previous session.

Explanation/Resolution: This issue occurs on Microsoft Internet Explorer 11 and Firefox browsers. To work around this issue, expand the root object (the configuration) immediately after logging in. The tree view then continues to expand to display the appropriate object.

CC-2563When using Dynamic Import from Contenta Web on Windows and using long paths, Dynamic Import does not always correctly import a file or directory.

Explanation/Resolution: This issue occurs in Contenta Web because a Perl method incorrectly applies security to the file or directory.

To work around this issue, in the Registry editor:
  1. Change all Contenta temporary paths from C:\Program Files (x86)\XyEnterprise\Contenta\temp to C:\Windows\TEMP.
  2. Change the docBase setting from C:\Program Files (x86)\Apache Software Foundation\Tomcat 8.0\conf\Catalina\localhost\cw_tmp.xml to C:\Windows\TEMP.
An alternative workaround is to complete the following steps:
  1. In Services, right-click Tomcat to display Tomcat settings.
  2. On the Log On tab, select This account.
  3. Enter administrator credentials.
  4. Save the settings and exit Services.
N/AThe Java file transfer applet used by several CW tools hangs or pops up an error "The applet parameter 'url1' is missing or invalid" when the version of Firefox is 3.6.14.

Explanation/Resolution: This issue is fixed by Firefox in version 3.6.15. This should be a very rare problem since it only affects Firefox users who are on version Firefox 3.6.14, which was soon superseded by 3.6.15. The CW tools that use the affected applet are Dynamic Import and the structured editor tools (Epic/Arbortext, FrameMaker, FrameBook and XMetaL).

CC-787Delivered delete trigger fails to delete the project.

Add the "delete" trigger to a routing task that's going to "End." Forward the project to end. It forwards with no errors but fails to delete the project.

CAS-6997Contenta Web displays an HTTP-400 error on IE11 when data is non-ANSI

In some versions of Microsoft Internet Explorer 11, you may see an HTTP-400 error (The webpage cannot be found) when data contains non-ANSI characters.

Explanation/Resolution: This error occurs because two IE11 advanced options are turned off by default. Turn on these options by performing the following steps.
  1. In Internet Explorer Settings, select Internet Options.
  2. On the Advanced tab, in the International section, select the following options.
    • Send UTF-8 query string for Intranet URLs
    • Send UTF-8 query string for non-Intranet URLs
  3. Click Apply.
  4. Restart Internet Explorer.
CAS-6789Object incorrectly appears locked preventing Arbortext Editor checkout.

In some cases, a user will be prompted to update Java when attempting to check out an object with Arbortext Editor. After the user responds to this prompt, the checkout fails with an error message incorrectly indicating that the object is locked.

Explanation/Resolution: To avoid this issue, either turn off automatic updates in the Java Control Panel or ensure that the latest Java update has been installed before using Arbortext Editor checkout.

42816, 43374In the SDL Contenta Web list view, actions on multiple objects are limited to 200 or fewer selections.

Explanation/Resolution: When selecting multiple objects for processing actions in the list view of SDL Contenta Web, do not select more than 200 objects for each action.

43386Contenta Web: login fails if files in the Contenta Web tree view start with a numeric character (for example, 1PublishConfiguration.xml).

Explanation/Resolution: Objects in the Contenta Web tree view should not be named or renamed with a filename that starts with a number.

43064Under some circumstances, Arbortext Editor Change Tracking markup can cause parsing errors with SDL Contenta Web XML Fetch or XML View functionality.

For example, while working in Arbortext Editor with change tracking enabled, delete an element that is mapped to a checked-out object and then check in that object. If you access that object through the SDL Contenta Web XML Fetch or View tools, you will encounter parsing errors like this:

Error on line 119 in file C:\temp\webcheckouts\cas\epiccat\ACT_II147226_022503778\ACT II#147#226_022503778.xml:

[A11052] Unknown element in start tag.

There is no such element as '_xsipt'.

*** Error on line 123 in file C:\temp\webcheckouts\cas\epiccat\ACT_II147226_022503778\ACT II#147#226_022503778.xml:

[A11051] Unknown element in end tag.

There is no such element as '_xsipt'.

42673At the time of object creation in SDL Contenta Web, edits to nested property sheets and property lists are not saved.

Explanation/Resolution: As a workaround, complete the creation of the object in SDL Contenta Web then edit nested property sheets and property lists as a separate operation.

42672If select lists are not set up correctly (for example, the property list for a select list is not on sysadmin’s desktop), property list edits in Contenta Web are not saved.

Explanation/Resolution: Correct the select list setup, and then try the property list edit again.

42530SDL Contenta Web has shown some performance degradation with IIS7 and Tomcat as opposed to Tomcat only.
42529The XML View web tool fails to launch in an environment where the Contenta application and web server is the same server and is a UNIX server.

Explanation/Resolution: If SDL Contenta Web was installed after installing SDL Contenta Server on the same UNIX server, you must create a directory named “tmp” under the /pdm/clients directory on the Contenta Web server. If Contenta Web was installed first, this manual step is not required.

Table 5. Search
Issue numberDescription
CC-2583Crawler fails to index objects created or modified under a newly added desktop with a reused configuration.

Explanation/Resolution: Stop and restart Crawler immediately after the new desktop is added.

CC-1518Searching for special characters can fail.

Explanation/Resolution: Character entities are not yet supported with Search. Wildcard searches can be used as an alternative.

CC-1449The Crawler does not index property lists and secondary property sheets.

Explanation/Resolution: Only top-level property sheet (metadata) is currenty indexed by the Crawler.

CC-1289The Crawler does not index referenced objects.
CC-794The Java crawler does not strip markup from the "CONTENT" field if DATATYPE field has 'SGML' value.

Explanation/Resolution: The CONTENT can still be searched, but the data returned includes the markup.

CC-1121Hidden fields are not indexed by the crawler (such as access level).

Explanation/Resolution: If required in the index field, this should be made visible, or a custom solution can be implemented.

Table 6. Administration Tools
Issue numberDescription
CC-1581Need support of UNC pathing and mapped drives.

Explanation/Resolution: Contenta does not support UNC paths or mapped drives for directories paths (such as checkout, encaps, temp, or icons) that can be set by the user or the administrator.

CC-1087Issues with Controlling containers with many objects with the same name. This issue occurs for databases which have controlling containers with numerous objects with the same name and tools which do a select by namepath on one of the objects which has the same name in the controlling container.

Explanation/Resolution: If you are impacted by this issue, please contact customer support for guidance.

CC-796Server tool exit code not recevied by client tool.

Explanation/Resolution: When a Contenta server tool written in Perl exits with an exit like this: exit(2); the exit code is not returned by the call to RunTool() in the client Perl tool. The call to RunTool() returns -1 no matter what code is returned by the server tool.

39036The pcmsessions utility fails to find the database when the database has a custom password.
Explanation/Resolution: Specify the ODBC DSN with the database name when issuing the command. For example:
pcmsessions –dbase certain@xyentDNS
35585Compiled utilities (for example, dumpobj, fixblob, killobj, pcm_stats, pltrim, reap_report, showobj, checkblobs, unmark_checkpoints) fail if Contenta Server and Contenta Explorer are on separate machines and you have a database with a custom password. The problem does not occur when using the default password.

Explanation/Resolution: Set two environment variables, XYV_PDM_ROOT and XYE_PRTL_DATABASE_SID, before executing the utility.