The following notes describe known problems or critical information for this release. Where applicable, each note includes the associated Failure Report (FR) number for reference and tracking purposes.
Installation and Upgrade Issues
Added a topic about support for Windows 2003 Server.
Added FR 49922
Configuration and Operation Issues
Added FR 39142
Added FR 43918
Added FR 46504
Added FR 49572
Moved the corrected procedure (previously in this Current Notices document) for restoring a storage repository to the topic "Administration Guide > Restoring Repositories > Restoring a Storage Repository".
Incorporated FR 42880 into step 4 of the procedure in the topic "Administration Guide > Content Search Repositories > Adding a Content Search Repository".
Added FR 49232
Added FR49114
Installation and Upgrade Issues
Added FR 43091
Configuration and Operation Issues
Added FR 45554
Added FR 46316
Added FR 47352
Installation and Upgrade Issues
Added FR 46684
Configuration and Operation Issues
Added FR 42880
Added FR 46504
Installation and Upgrade Issues
Added a note about support for Windows 2000 Service Pack 3.
Added FR 43436
Configuration and Operation Issues
Added FR 37433
Added FR 43918
Added FR 42528.
Configuration and Operation Issues
Added FR 39417
Added FR 20642.
Added FR 39770
Note There have been changes to the Content Services Application Program Interface (API). If you are creating custom applications using this API, refer to the latest Panagon Content Services Toolkit Readme on the FileNET Worldwide Support web site for details.
Installation and Upgrade Issues
Added a notice about retirement of Windows NT 4.0.
Added a note indicating the presence of a file, update.exe, that should not be in the Content Services 5.2 distribution media.
Revised the entry calling for installation of Microsoft Hot Fix 8.00.277. This patch is no longer needed if you have installed SQL Server 2000 Service Pack 1.
Configuration and Operation Issues
Added FR 32597
Added FR 34026
Added FR 35520
Added FR 35614
Added FR 36377
Added a note in regarding the absence of preview-file support for LDAP User Import.
Added FR 37544
Added FR 37798
Added FR 36399
Archive to Image Services Issues
Added FR 35078
Added FR 35638
Added FR 35669
Added FR 35907
Added FR 35914
Added FR 35988
Added FR 36120
Added FR 36248
Added FR 36877
Added FR 36916
Added FR 38009
Configuration and Operation Issues
Removed FR 14530
Configuration and Operation Issues
Added FR 3381
Content Services 5.2 now supports Windows 2000 Service Pack 3.
The Content Services 5.2 distribution media contains a file, update.exe, in the \IDMDS\update folder that you must not execute, as it launches the IDMDS 5.1.1 service pack installation and will corrupt your CS 5.2 installation.
As of January 1, 2003 Microsoft will begin to phase out product support for the Windows NT Server 4.0 family of operating systems. As of January 1, 2005, online support for Windows NT 4.0 will no longer be available. Refer to http://www.microsoft.com/ntserver/ProductInfo/Availability/Retiring.asp for the specific schedule of the phaseout.
Because Windows NT 4.0 support is ending, FileNET recommends that you migrate your Content Services software from Windows NT 4.0 to Windows 2000 at your earliest convenience. FileNET expect to end support for Windows NT as of the Content Services 6.0.0 release, scheduled for late 2002. See the "Migrating to Windows 2000" topic in the Windows SQL edition of the Content Services 5.2 documentation for details.
If you install Content Services on a machine with an incorrect OEM code page, you will receive a warning message informing you which code page to use for proper support of accented characters. This warning will not otherwise affect completion of the setup, however, using the wrong code page can lead to improper storage of accented characters in the library system. This, in turn, can adversely affect users' ability to retrieve data and documents. (FR 6285)
The Dsuninst program does not delete the subfolder for the library system from the Repl folder. (FR 8064)
If you interrupt a property server installation but want to redo it later, first check to see that the database tablespace is populated with the library system objects. If it is, we recommend that you do the following:
Delete everything on the property server related to the interrupted installation, including the library-system configuration files and binary files located in the installation directory (%IDMDS_HOME% by default).
Drop the library system user, using the following SQL command:
drop user librarysystem
If you fail to take these steps prior to rerunning the property server installation, the default Document Class may not be created as expected.
As an alternative, if the CS executables and the database tablespace are already installed as expected, but the default Document Class and Workflow Class objects are not yet created, you can simply create these Class objects manually to complete the installation. Contact FileNET Worldwide Support before you attempt this alternative. (FR 11537)
Only one top-level installation directory per server (property server or remote storage server) is allowed. The default name for this directory is Drive:\Idmds. You can assign a different name during Setup if you wish, but if you install multiple library systems using different top-level directory names, there is potential for serious problems in your registry if you do not follow these rules: you must either (1) be sure to use the same top-level directory name on ALL servers, or (2) NEVER install/re-install library system services with different top-level directory names on the same machine. (FR 12003 and FR 12142)
Examples of what NOT to do:
On a remote storage server, DO NOT install two Storage Managers that reference two different property servers, each of which has a library system installed in a top-level directory of a different name. In other words, if multiple property servers have remote Storage Managers installed on the same remote server, the top-level directory must be named the same on ALL of the servers.
DO NOT restore a library system that was originally installed with one top-level directory name (for example, \Idmds) onto a different server that already has existing library system components installed in a different top-level directory (for example \Filenet).
DO NOT install a library system using one top-level directory name (for example, \Idmds), then uninstall it and install a different library system (different database) on that server using a different top-level directory name (for example, \Filenet), and then re-install the first library system with the top-level directory name \Idmds.
The Dssetup installer will fail if you put a space in the top-level installation directory name. Dssetup should produce an error message saying that spaces are not allowed. For example, if you attempt to use 'IDM DS' as the top-level directory name Dssetup installation will fail. (If you were to attempt this with IDMDS Setup, an error message would be displayed and the name would not be accepted.) (FR 12379)
Reinstalling a library system does not create the SSLibrarySystem ODBC Data Source correctly if the content search repository is on a drive other than C: (FR 13708)
On a system with English Windows NT, with regional settings of Czech and enabled Czech keyboard, you are unable to type uniquely Latin2 characters into the dialog boxes during IDMDS installation. For example, if you try to enter a uniquely Latin2 character into a name such as Admin, Administrators group, Default Document Class, the character is displayed in the dialog box as a completely different character. (FR 15101)
If there are more than two users still logged in to a library system when you run the UPDATE program to install Hot Fix Packs, the program cannot load the database correctly. The fact that the Storage Manager is shut down and logons are disabled does not preclude the possibility that multiple user sessions could still be open. Be sure that ALL users are logged off the system before you run UPDATE. (FR 23187)
If you attempt to move a Content Services component (such as a Storage Manager) from one Windows server to another, and you export the Registry from the old server and imported it to the new server, the Content Services installer on the new server will suffer a fatal error if the installation-drive letters for the component on the old and new servers are different. ( FR 26650)
Here is a scenario to illustrate this failure:
Assume that the Storage Manager is installed on the D: drive of the old server.
Export the Registry from the old server and import it to the new server. (You would do this, for example, if you wanted to carry over your custom configurations from the old server to the new server)
Launch the Content Services installer on the new server.
Specify C: as the installation drive for the Storage Manager on the new server (perhaps because the D: drive on the new server is already assigned to a CD-ROM device).
When the Content Services installer displays the Select Directory and Drives dialog box, you will notice that the drive letter for the Storage Manager is missing.
When you click Next in the dialog box, a Severe error message appears: "An error occurred while attempting to create directory D:\idmds. Setup is now being terminated."
Click OK, and the installation aborts.
To prevent this fatal error, perform the following Registry modification on the new server immediately after step 2 above:
Find the HKEY_LOCAL_MACHINE > SOFTWARE > FileNET > FileNET Content Services > InstallDrive key and change its value from what it was on the old server (D: in the scenario above) to what it will be on the new server (C: in the scenario above).
Then continue with steps 3 through 7 of the Content Services installation as above.
If you specified a non-default device location for CS Client Library Files when you installed Replication Services on an additional storage server, you will encounter a ComponentMoveData error message if you reboot the server, start Replication Services, and then run the CS Setup program to install additional components. This message will appear when the installer tries to copy installation files to the server. To avoid this error, stop all the CS services on the server before running the CS Setup program to install additional components. (FR 26884)
If you have Replication Services installed as part of Content Services when Content Services is not collocated with the database server, Content Services must be able to connect to the database (via ODBC Driver) before you start the uninstall procedure. Otherwise, the uninstall will fail. (FR 26892)
If the value of the Content Searches Enabled? parameter is set to 'No' for a library, reinstalling the library will change the parameter value to 'Yes'. After the reinstall is complete, use CS Admin Tools to restore the parameter to its previous value. (FR 43091)
The topic Installation Guide > Upgrading Content Services > Upgrading (Additional or Replication) Storage Servers incorrectly states that indexes are rebuilt if a Content Search Manager is upgraded. The indexes are not rebuilt during an upgrade. (FR 43436)
If during the installation of Content Services 5.2 you change the default location where the CS shared files are to be installed, you will see an error message at the end of the installation indicating that the installer is unable to locate the file srs***.dll. This error message is benign and does not indicate that the installation failed. (FR 46684)
On a server whose RAM exceeds 2 GB, the Content Services 5.2 installer may fail with an insufficient-memory error. If this happens, configure the server to support at most 2 GB of its RAM, install Content Services, and then reconfigure the server to support all of its RAM. (FR49922)
Content Services now supports Service Pack 1 for Microsoft SQL 2000, which supersedes the previously documented Microsoft hotfix 8.00.277.
If your library system's display language is either French or German, the string "Content Search Threshold" in the User object are displayed in English. (FR 2883)
A CVL, which you create using the Doc Class & CVL tool, can contain at most 10,000 values. If you try to create a CVL with more than 10,000 values, it will contain only the first 10,000 that you specify; the excess values will be ignored. (FR 3381)
The value range for integer custom properties is -2,147,483,648 to +2,147,483,647. Entering a value outside this range will cause an error. The '+' sign is assumed unless an explicit '-' is entered. Positive values are allowed 10 characters; negative values 11 (to accommodate the '-' sign). (FR 3485)
Running the REPCHECK utility in fix mode or the CSADMIN utility in rebuild mode has the potential to fill your transaction log. Refer to the REPCHECK and CSADMIN utilities in the Content Services 5.2 documentation for information on how you can avoid this problem. (FR 5194)
A bug in the FrameMaker filter file causes indexing to fail for FrameMaker 5.5 documents. (FR 5669)
Because of limitations imposed by Windows NT 4 on the number of files that can be efficiently stored in a single folder or directory, Microsoft recommends not to add more than 10,000 documents to a single storage repository. Severe operating system performance problems will arise if you exceed 15,000, either through normal usage or while doing a bulk add. Therefore, before performing a bulk add operation, you should verify that no more than 10,000 documents will be added. Windows 2000 does not have this limitation. (FR 6035)
Do not use the Euro character or other non-alphanumeric or special characters, such as `~!@#$%^&*()_+-=[]\{}|;':",./<>? in IDMDS database (library system) names. Also, do not use these characters in IDMDS object names, such as group names, user names, search names, etc. (FR 9389)
An item search with an OR on keyword returns invalid results. For example, a search with the following criteria: "Item ID=valid_ID OR Keyword = valid_keywd" only returns items containing a keyword. Note that if the item searched for with the Item ID happens to contain a keyword, it IS also returned. (FR 9451)
If the maxRows parameter is set to a value greater than 1000, a content search that returns more than 1000 hits will cause a General Protection Fault. (FR 18443)
When you delete a source document that has more than 100 published source-dependent documents created via Rendition Services, the system does not delete all of the published documents as expected. (FR 18549)
Under Windows 2000, DSSTATUS fails to display the correct Replication Service status. Users can start and stop Replication Services on a local system, but on remote systems in the Windows 2000 domain, DSSTATUS will erroneously indicate that the service is not installed by displaying an "X" instead of a start/stop indicator. (FR 20636)
If you rename or move the proc.dat file for CAT_PROC, it will return a message saying it failed to open the file proc.dat, but the restore was performed successfully. This message is wrong; the restore was not performed. (FR 21977)
If you set the DB Threshold value in the CS Configuration Tool Storage Manager Tab to 0, restarting the Storage Manager for that system will result in a Dr. Watson error. (FR 22666)
The User Import tool will not add a group to a library if the group name contains more than 32 characters. The group will simply remain in the Selected Groups field of the User Import tab. (FR 22706)
Under Windows 2000, if you add a group using the User Import Tool (DIRSYNC) and then manually delete the group from the domain controller, the User Import Tool will not function properly. The group and its users will remain in the IDMDS system. (FR 22710)
Using the NOT LIKE operator to search on properties that contain null (empty) values may return incomplete results. (FR 23035)
Uninstalling IDM Desktop 3.1 from an IDMDS 5.1.1 server will remove the ODBC data source used by IDMDS 5.1.1. If you uninstall IDM Desktop 3.1, use the ODBC Data Source Administrator tool (available from the Windows NT Control Panel) to add another data source for the IDMDS server. Select the System DNS tab, click Add, select the SQL Server driver, and then click Finish. This will start the "Create a New Data Source to SQL Server" wizard which you can use to add the data source. (FR 23755)
If the value you assign to a User or Group object property is undefined in the library system, the User Import tool will not add the object to the library system. (FR 25597)
Because only a few letters in the Arabic alphabet are recognized by the Content Services indexer, Arabic-language documents (MS Word, for example) are not correctly indexed for content searches. (FR 26109)
The CAT_INDX utility is unable to re-create table index on the destination database server if the current table indexes are not present. Be sure your database backups and/or export utility has these indexes intact. (FR 26755)
If the library-system administrator adds a Document Class containing the Is Replica Item? property, subsequent logins to the library from IDM Desktop or IDM Web Services will fail with the following error message: "Library (libname) does not have any document classes installed. Please contact your system administrator." ( FR 26850)
When running DSSTATUS while logged in to a domain, be aware that CPU usage is sensitive to the number of Content Services libraries in the domain. In a domain with many libraries, CPU usage may climb to 50 - 70 %, as indicated by the Task Manager. CPU usage will return to a more normal level when DSSTATUS exits. To avoid excess CPU usage when running DSSTATUS, do not be logged in to the domain if the library whose status you are interested in shares the domain with many other libraries. (FR 29069)
Although the Title property in the Item object accepts a value as long as 254 characters, the CS API currently has a maximum length of 80 characters defined for searchable values (via the SPI_MAXLEN_QUERY_VALUE define). As a result, if you use the IDM Find application in IDM Desktop to search for documents based on the Title property, an error is displayed if any of the retrieved documents have titles longer than 80 characters. (FR 32597)
If you log on to a Novell network and enter the LDAP Server, BaseDN, BindDN and BindDN Password in the Novell NDS/Ldap User Import tab of the Content Services 5.2 Configuration tool, no organizational units will appear in the Available Organizational Units list box. (FR 34026)
The Outside In™ Technology Version 7.0 content-search indexing filters do not index words within an XML element specified by a tag with the same name as an HTML tag. For example, words within the XML element <title>...</title> will not be indexed. (FR 35520)
The Windows Control Panel applet CS Configuration does not let you choose OUs/Group for LDAP directories, which means you cannot choose any group defaults either. One of those group defaults is the "Add Items?" property for the group. Thus, if you use CSIMPORT to import users into a library system, you will get all the groups in the iPlanet directory with no group defaults.
As a workaround, after the groups are imported into the library system, perform a CS Admin Tools search for all User objects whose Imported User? property value is Yes. Then select all the User objects found by this search, right-click, select Properties from the pop-up menu, and set the Add Items? property value to Yes. (FR 35614)
LDAP_EXP does not correctly process users and groups whose names contain the special character '<' or '&'. Although these characters are acceptable for user/group names in iPlanet, they are not supported in Content Services 5.2. (FR 36377)
In the CS 5.2 topic Administration Guide > Creating Reports Using the Database > Database Schemas, the U_DIR_SYNC property in the USR table should be documented as the U_SYNC property (FR 37433).
The topic "Backing Up Content Search Repositories" needs to say that a scheduled CSMERGE execution will run only if CSMERGE has not been run within the last 24 hours (FR 39142).
The "Localized Stopword Files" section of the "Content Search Stopwords" topic in the CS 5.2 documentation incorrectly states that localized stopword files for supported languages are provided in the same directory as the English stopword file. These localized files are not provided.
To enable content searching to use localized stopwords, create your own stopword file (one stopword per line), name the file fultext.stp, and place the file in the directory Drive:\Idmds\LibrarySystem\content\data\. The library system will use fultext.stp for the language you have installed. (FR 39417).
Contrary to step 3 of the procedure in the topic "Restoring a Content Search Repository", content search repository directories residing on the same drive as their associated Content Search Manager may not be re-created when you restart library system services on the storage server. In which case, you must manually re-create the directory structure. (FR 43918)
If dirsync imports a group and its member users from a directory server into a library system, and a user's membership in the group on the directory server is subsequently removed, dirsync is supposed to remove that membership in the imported CS group. If the imported user is a member of exactly one imported group in the library, then dirsync works as it should.
If, however, the imported user is a member of more than one imported group then, because of a bug, the imported user remains in the imported group after the user's membership in the group on the directory server has been removed. In this case, the library system administrator must manually remove the CS membership from the imported group. (FR 45554)
The initial and additional (remote) Storage Managers of a library system are each separately configurable with respect to secure deletes. Whether an item (document) is securely deleted depends on the secure-delete setting of all the Storage Managers that govern the storage repositories where the versions of the item are stored.
When an item is added to a library, it is given a Storage Category, which is associated with the storage repository where the versions of the item will be stored. If the Storage Category is modified to change the assigned storage repository, versions of the item may be stored in different storage repositories which may be located on different servers.
To ensure that an item is securely deleted, make sure all versions of the item are stored in storage repositories where the Storage Manager is configured for secure deletes. Beware that if even one of the storage repositories in which a version of the item is stored is on a server whose Storage Manager is not configured for secure deletes, then any versions of the item that are stored on that server will not be securely deleted. (FR 46316)
Windows User Import supports Windows 2000 mixed-mode, but not native-mode, domains. (FR 46504)
If your workstation is running Novell Client for Windows and you attempt to logon to a Content Services 5.2 library system as a user that was previously imported (as DOMAIN;username) to the library from a Windows domain, your workstation logon to the library will fail (see FR 47452) if you cancel the NDS logon and try to logon to the Windows domain instead. (FR 47452)
As a workaround to enable successful logons to the library through a Windows domain, add the following system environment variable on the workstation:
sni_network_type = 1
When a Content Services Storage Manager starts up on a server, it may assign to itself one or more ports intended for another application that is installed, but not currently running, on the same server. A subsequent attempt to start the other application will then fail. If this happens, shut down the Storage Manager, start the other application, and then restart the Storage Manager. (FR 49572)
For increased performance on Windows SQL 2000, you may want to enable Connection Pooling on any CS server where a Storage Manager service resides. To enable Connection Pooling, insert the Panagon Content Services Admin Tools CD and click the util\regfiles\ConnectionPoolingON.reg file. To disable Connection Pooling, click the util\regfiles\ConnectionPoolingOFF.reg file.
The procedure in the "Using LDAP User Import" topic suggests that you generate and review a preview transaction file before you import users and groups to your library system. However, in CS-5.2.0-002, no preview transaction file can be generated. You should therefore ignore the steps that refer to the preview file. As an alternative, use the CS Explorer Admin Tools to view the users, groups, and group memberships that have been imported.
The DSINFO utility does not report the status of Replication Services when Replication Services are installed an a standalone machine. Replication status will only be reported if the associated Storage Manager is installed on the same server as Replication Services. (FR 14746)
Do not place IDM Desktop stored searches in Replication folders. Stored Searches and/or Templates do not replicate.
The Title value of a replica document is supposed to be blank if it is blank in the source document. Sometimes, however, you will see the target Item ID in place of a blank Title value in the replica document. This happens intermittently, depending on when the Replication Daemon runs while you are adding the source document. (FR 18856)
You cannot copy a parent compound document into a replication folder. (FR 19607)
If you want to uninstall just Replication Services, you must do it from the command line. Type:
drive:\idmds\Repl\util\inst_rep -U
Use the -h flag to get command line help for inst_rep. (FR 20944)
The USGRPCHK and USGRPMIG utilities do not correctly map non-default names for the Admin user, Administrators group, and General Users group created during IDMDS setup. For example, suppose you have two library systems that are members of a replication administrative domain. On one of these systems you accepted the default name of General Users, on the other you assigned the name Universal Users. You run USRGRPCHK and discover that "CORRUPT REPLICA" messages are logged for perfectly valid replica users and "DUP MASTER" messages stating that "the two masters differ" are logged for otherwise identical users. You can safely disregard these messages. For more information about these utilities and the messages they generate, see the USGRPCHK and USGRPMIG utilities in the Content Services 5.2 documentation. (FR 22273)
The DTCVLCHK utility may produce spurious messages about CVLs differing on upgraded library systems. If you modify CVL data (via the CS Document Class and CVL Admin) on a library system that has been upgraded from IDMDS 4.3 to 5.1, DTCVLCHK may produce a message indicating a difference with a seemingly identical CVL on another library system. This is a benign error message caused by internal database issues; you can safely ignore it. For more information, see the DTCVLCHK utility in the Content Services 5.2 documentation. (FR 22342)
Even if you have configured the Index Replicas setting to be ITEM, current behavior is that manual index/de-index operations you perform on a source version of a replicated document do not cause CS to perform the same operations on the replicas in the other replication library systems. Such replicated behavior occurs only if you do the indexing/de-indexing while adding a new document or checking in a version. (FR 22940)
If you replicate a tree of folders all at once from a source library system to one or more target library systems, the following erroneous behavior will occur: If a child folder in the tree on the source library has a folder ID less than that of its parent folder, then no replica of an item in the child folder will be associated with a replica of the child folder on any target library.
To avoid losing the replica item-folder association on target libraries, you can choose either of two workarounds:
If your folder tree already contains items or is empty, replicate the folder tree one level at a time, as follows:
Add the root folder of the tree to the Replication folder.
Wait until the replica root folder appears in all the target libraries.
Go down one level in the tree, select only the folders at that level, and add them the Replication folder.
Wait until all the replicated folders appear on the target libraries.
Repeat steps 3 and 4 until you have replicated all the folders in the folder tree.
If your folder tree is empty, replicate the entire tree before adding items to the folders, as follows:
Add the entire tree to the Replication folder.
Wait until the entire tree replicates to all the target libraries.
Add items to the folders in the tree within the Replication folder.
You can safely add more folders to a folder tree that has already been replicated (by either workaround) as follows:
If the folder to be added does not contain subfolders, simply add the folder to the tree in the Replication folder and wait for it to replicate to the target libraries. The added folder may or may not contain items when you add it to the tree.
If the folder to be added is itself a subtree (that is, it does contain subfolders), then follow the procedure described in the appropriate workaround described above. In other words, if the subtree already contains items, apply the first workaround; if the subtree is empty, apply either workaround.
(FR 25787)
Items added to a library system that was originally installed with IDMDS 5.0 or earlier may replicate erratically if the library had 19 or more item custom properties before being upgraded to IDMDS 5.1 or later.
Items added to a library will replicate properly if either of the following conditions holds:
The library was installed new with IDMDS 5.1 or later.
The upgraded library had 18 or fewer item custom properties before the upgrade to IDMDS 5.1. (Custom properties added after the upgrade to IDMDS 5.1 do not matter.)
To determine whether items in a library may replicate erratically, run the following SQL query:
select INA_ID from libraryname .INA_INFO where INA_NAME = 'idmSearch';
(FR 29718)
In Content Services 5.2.0, folders and items placed in the Replication folder of a library system whose name has more than 11 characters will not replicate to other libraries.
After installing CS-5.2.0-003, folders placed in the Replication folder will replicate to the other libraries; items will not. As a workaround, dereplicate the replicated folders and replicate them again. Now the folders and items will all be replicated. (FR 37544)
kPublisher 1.1.1 fails to render files produced with PageMaker 6.5. As a workaround, upgrade to PageMaker 6.52 from the Adobe patch (pm652upd.exe) located in "PageMaker 6.5 or 6.51 to 6.52 Update -- English" on Adobe Downloads web site. Do not upgrade from the PageMaker 6.52 CD. With a later release of kPublisher, PageMaker files should be correctly rendered. (FR 20642)
The Title property must be included in the current DocClass when publishing a document. Otherwise, the document ID is used as the title, even when publishing a document to replace an existing rendition. (FR 26252)
kPublisher 1.1.1 intermittently fails to render Excel documents. When the rendering failure occurs, kPublisher displays an error message indicating that it has exceeded its timeout period. The error message also indicates an error in "ESPS Plugin Messages Resource DLL" and that the job is being canceled. (FR 26666)
The kPublisher 1.1.1 slave server application will stop responding if a plug-in causes a timeout. The timeout occurs intermittently when the Excel plug-in is rendering Excel files (see FR 26666).
To recover from an Excel plug-in timeout, you must re-boot the Renditions Services server. When kPublisher restarts, it will abandon the current document and then run normally, rendering more documents until another timeout occurs. If you only kill and restart kPublisher following a timeout, without re-booting the slave server, the kPublisher slave server application will erroneously mark every document sent to it by the master server as being "in error".
kPublisher 1.1.1 will process plug-in timeouts correctly if only one server is used to render documents. We recommend using only a single server per Content Services library when using kPublisher 1.1.1 to render documents to PDF. (FR 26672)
Due to incompatibilities between Windows 2000 and kPublisher, do not install kPublisher on Windows 2000 if you need to render Excel or AutoCAD files. Windows 2000 is supported if you do not render these file types. (FR 26964)
The kPublisher 1.1.1 documentation mentions watermarks among the features you can add to a document during publishing. However, watermarks are available only with the kPublisher client, not the kPublisher server that is shipped with Content Services 5.2. (FR 31406)
If you are running Microsoft Print Spooler on Windows 2000 Server or Advanced Server, and you attempt to publish a large document via kPublisher, you may find that kPublisher will publish less than 100 pages of the document. This is due to a bug in the Print Spooler software (see Q272114 in the Microsoft Knowledge Base at the Microsoft Support site for details).
As a workaround, open the Printer Properties dialog box of the kPublisher printer, select the Advanced tab, and check the "Print directly to the printer" checkbox. This will bypass the print spooler and allow all the pages in a large document to be correctly printed. (FR 37798)
"MS Internet Explorer 5.0 or later" should be in the Supported Software Versions list in the Rendition Services topic "Installing Source Programs". (FR 42528)
Rendition Services 5.3.0, which contains the Liquent engine for creating PDF renditions of documents in CS 5.3.0 libraries, can also run on Content Services 5.2. Refer to the CS 5.3.0 media and associated Rendition Services documentation for information on installation and configuration. (FR 49232)
The kPublisher "watched folder" feature mentioned in the CS Rendition Services documentation is available as a preview feature only; it is not fully supported for CS 5.2.x. Documents in a watched folder will be rendered to PDF and stored in the library system as expected, but the system will not assign them to a folder in the library nor establish a relationship with their parent documents. This makes these PDFs difficult to locate for users of IDM Desktop or Panagon Web Services. Users will have to build (or be provided) searches to find these PDFs and, if necessary, drag them manually into the library's folder structure.
In the CS Document Class and CVL Admin, the DocClass name DOCTYPE_CONTROL_OBJECT doesn't fit within its list box unless you resize the list box. (FR 3189)
If you use the CS Explorer to add a new multivalue custom property while Replication Services is running, new values for that property will not start replicating immediately on all the associated library systems. You must either (1) stop and restart Replication Services on all the library systems or (2) expect to wait up to 6 hours to use the property (because the replication daemon checks for any new multivalue custom properties every 6 hours). (FR 22523)
If you use the Datasheet Export function of the Bulk Process tool to export a datasheet to Paradox 7 or Paradox 8 format, the Microsoft JET Database Engine will display an "Invalid operation" error message. (FR 25395)
If you use the Datasheet Export function of the Bulk Process tool to export a datasheet to a file in dBase III or dBase IV format, you will encounter errors when using the Datasheet Import function to import the same file. If you export datasheet to a file in dBase V format, you will not encounter errors when importing the same file. (FR 25396)
You can import a database table using the Datasheet Import function of the Bulk Process tool only if the table was previously exported using the Datasheet Export function. (FR 25426)
It may take several minutes to log in to a Content Services library system from CS Explorer if more than 100 such libraries are listed in the Windows 2000 Active Directory. To shorten the login time, CS Explorer users should either log in to a Windows 2000 domain that has fewer Content Services libraries or else log in to the local machine account. (FR 27734)
In CS Explorer, the Online Help and the Properties tab of the System - Content Services - Item dialog box incorrectly display the values of the "Is Replica Item?" property as "1" or "0". These values should be displayed as "Yes" or "No". (FR 36399)
If you run CS Web Admin Tools on a machine where McAfee Virus Scanner is also running, you are likely to experience noticeable performance slowdowns. This degradation occurs with both McAfee client and McAfee server versions. (FR 39770)
Before installing CS Admin Tools from FileNet Software Patch CS-5.2.0-1035 on a machine, run the CS Admin Tools uninstaller that comes with the base CS 5.2 product to uninstall any existing CS Admin Tools on that machine. (The CS Admin Tools uninstaller that comes with CS 5.2 Hotfix Pack 3 fails to delete some files.) Otherwise, you will encounter multiple error messages when launching IDM Desktop or CS Explorer on the machine. (FR49114)
Importing data via the Bulk Process tool of CS Admin Tools from a SQL Server database into a Content Services library system succeeds only if the import operation is performed on the server where the database is installed. (FR 49286)
When installing the AIS Admin Console, the paths from the Start menu items to their respective executables are incorrect. The installer creates paths "\filenet\AIS", but the paths should be "\filenet\AIS\bin". After installing the software, edit the properties of these menu items and correct the paths. (FR 35078)
After adding an IS Alias (by entering the information, then clicking OK), the newly added alias is invisible on the list. To make it visible, click on the location where it should appear, and it will appear. (FR 35638)
When creating a retention rule with a filter property, the values for the filter property will not appear in the list initially. You must save the rule, then click Edit to edit the rule. See also FR 36248. (FR 35669)
When configuring parameters in the "Other Section Parameters" dialog box, the parameters for the AISArchive section are initially set up to have two comma-separated values (e.g., 20,21). This is incorrect but does not affect functionality. If you wish, you may edit these parameters to remove the comma and the second value. (FR 35907)
When configuring parameters in the "Other Section Parameters" dialog box, if you set a parameter's value to null (or blank) the parameter will disappear as soon as you Apply the new value. Do not set parameters to null values. (FR 35914)
If an index map is deleted, and then in the same session the user attempts to create an index map with the same ID, a DBI duplicate-key error is generated. If you exit the index map creation dialog and then open it again, and then try to create a new index map, the old index map's ID will be skipped over. To work around this problem, exit the AIS Admin Console completely if you have to delete an index map. (FR 35988)
Uninstall does not remove all values from the "custom" table. After uninstalling, you must use SQL Server to remove these values manually. To see the values, "select * from custom where co_object_type=AIS". To remove the values, "delete from custom where co_object_type=AIS". (FR 36120)
When creating a retention rule with a filter property, the dropdown list for the filter property's values is created from the quicklist instead of the CVL data, which causes only those values currently being used to be displayed. You can still type the full set of values into the entry box, but not all values will appear automatically for selection. See also FR 35669. (FR 36248)
If only one CS system is installed on a node, Archive to IS can only access one IS alias when creating an index map. If two or more CS systems are installed, Archive to IS can access up to five IS aliases. See also FR 36916. (FR 36877)
If multiple CS libraries exist on each node, then each AIS IS Alias List must contain the same servers. If they do not, attempts to create a CS-to-IS index map will cause the error "AISISalias.GetISAliasbyISDomain) Error: 20008 (0x4E28) : Can't connect to custom object." The workaround to this problem is to require that each CS library per node/gateway contain the same list of IS aliases. Note that this limits the number of IS systems to 5 total, rather than 5 per CS library. (FR 36916)
Content-based search from UNIX client applications is currently broken. For example, running content searches from a customized HP-UX client application causes a memory fault and resulting core dump. (FR 38009)