Inmagic® Content Server Version 1.3
README File

Copyright © 2003–2004 Inmagic, Inc. All rights reserved.


Contents

About Inmagic Content Server

About this Document

What's New in this Version?

Important Upgrade Information

Issues Resolved

Documentation Resources

Troubleshooting

Contacting Inmagic, Inc. and Communicating with Others

About Inmagic Content Server

Inmagic® Content Server is an enterprise-wide scalable content management system. It combines the advantages of a robust and flexible database management environment with high speed search and categorization, making finding relevant information fast, easy, and precise. Web publishing capabilities are built into Inmagic Content Server, offering a better way to publish, access, and maintain information on corporate intranets and the Internet.

Content Server is built on industry standard architecture, incorporating Microsoft SQL Server 2000 as its data store. Content Server makes extensive use of open standards and technologies, the most obvious being Extensible Markup Language (XML), which forms the basis for much of its Web publishing functionality.

Content Server is made up of three components:

CS/TextWorks also provides you with access to Inmagic.net™, which gives you the ability to connect to the Inmagic server from within a CS/TextWorks session to accomplish various tasks related to acquiring, cataloging, indexing, and disseminating information throughout an organization. For more information about Inmagic.net, see the online help.

About this Document

Except where noted, everything in this document applies to all editions of the Content Server software:

What's New in this Version?

Each new and enhanced feature for CS/TextWorks, CS/WebPublisher PRO, and the CS/Importer is discussed briefly here. Where applicable, you are directed to documentation containing more information.

CS/TextWorks

CS/WebPublisher PRO

CS/Importer

Important Upgrade Information

The following topics are relevant to customers who already have a Content Server system and are upgrading to version 1.3.

Upgrading Menu Screens to Content Server Version 1.3

Before you can use your existing Content Server menu screens with the new version, you must use the new Update Menu Screens command (located on the Manage Upgrades menu of the Content Server Administration window) to update your menu screen (.CBM) files for use with the new version. For more information, see the Inmagic Content Server Installation Notes or the online help.



Upgrading Between Content Server Product Levels

If you are upgrading between Content Server product levels or you are changing SQL Servers, you must back up and restore each textbase you plan to use with the new product level.
  1. Start the Inmagic Content Server Administration program (INMCSADMIN.EXE).
     
  2. Choose Back Up & Restore>Back Up Textbase to open the Back Up Textbase Options dialog box and do the following:
     
    1. In the Textbase box, specify the textbase you want back up (that is, the textbase you want to move to the new SQL Server).
       
    2. In the Backup path box, specify the path for the backup file set. If the machine from which you are running the Content Server Administration program is different from the one on which the SQL Server resides, you must use a Universal Naming Convention (UNC) file path.
       
    3. Click OK.
       
  3. Depending on the product level of Content Server you are using, do one of the following:
     
    • If you are using Content Server Standard or Content Server Workgroup, choose Set Up SQL>Select SQL Instance and specify the new SQL Server you plan to use with your upgrade. If you are upgrading from the Workgroup to the Standard configuration, you may have been pointing to an instance of MSDE. Use the Select SQL Instance dialog box to specify the instance of SQL Server 2000 that you plan to use with Content Server Standard.
       
    • If you are using Content Server Enterprise, continue with step 4. You will be prompted to select a SQL Server when you restore the textbase.
       
  4. Choose Back Up & Restore>Restore Textbase to open the Restore Textbase Options dialog box and do the following:
     
    1. In the Backup set box, specify the name and location of the textbase backup file set. If the machine from which you are running the Content Server Administration program is different from the one on which the SQL Server resides, you must use a Universal Naming Convention (UNC) file path.
       
    2. In the Restore path box, specify the location of the folder where the textbase should be restored.
       
    3. From the Restore options group, select the Restore and rename textbase option button, then, in the New name box, type a name for the textbase.

      Important! Do not use the Typical restore option button when restoring a textbase to a different SQL Server. Typical restore should only be used when restoring a textbase to the same location (that is, a textbase with the same name and path on the same SQL Server instance).
       
    4. Click OK.
       
  5. If you are using Content Server Enterprise, the Select SQL Instance dialog box opens so that you can select the SQL Server onto which you want to restore the textbase. You will not see this dialog box if you are using Content Server Standard or Content Server Workgroup.
     
  6. Repeat steps 2-5 for each textbase you plan to use with the new product level.
     

Upgrading Web Edit Pages from Version 1.0 to a Later Release

If you have upgraded Content Server from version 1.0 to version 1.1 or later, edit screens you exported to HTML in version 1.0 will continue to work. However, because version 1.1 and later provide better formatting on the Web, you may want to export each edit form to HTML again. If you do that, you can delete the copy of ICSW-EDIT.ASP and ICSW-EDIT.CSS in the same folder as the exported HTML edit form.

Note that in version 1.0, a copy of this .ASP file was required in each folder containing an exported edit form. With version 1.1 and later, this is not necessary. Only one copy of this file is needed—an updated version is installed in the ASP subfolder of the CS/WebPublisher PRO installation folder.

Issues Resolved

Content Server version 1.3 addressed the following issues. The applicable Inmagic Software Problem Report (SPR) number follows each item listed.

  • The confirmation message that appears when you use the Copy Textbase, Recover Textbase, or Update Textbases command no longer includes the amount of disk space needed. [2]
     
  • Network drops and machine crashes no longer risk damaging textbases. Because Content Server uses SQL Server as its back end, safeguards are in place against textbase corruption. This means users will no longer see the following error message when opening a textbase: "The textbase files are in an inconsistent state because an abort occurred during an update. We recommend you recover from this problem before using the textbase. Consult manual or Help." [5]
     
  • The LargeHitsOption= parameter can now be used to suppress hit counts on the Inmagic Choices Browser and the Word Wheel. When LargeHitsOption=4, the number of hits will not be displayed for any fields. [10, 18]
     
  • When you click a validation list link on a Web edit page for a field that uses a thesaurus as a validation list, the validation list will be empty if the thesaurus is missing or not available. It no longer returns a Runtime Error. [21]
     
  • If you have a field with a validation list that permits users to update and override the validation list, the list no longer includes blank entries for entries consisting entirely of a carriage return. [22]
     
  • If you are using an accent-insensitive SQL Server, validation lists now handle diacritics properly. On edit pages, either term is accepted, but the term you enter is changed to match the way it appears in the validation list. [23, 134]
     
  • If you have two terms in the validation list for a Code field that differ only by case, the validation list no longer incorrectly shows the two terms multiple times. [24]
     
  • The "Error writing record" message is now included in the CSENGMSG.INI file so that it can be modified or translated. [25]
     
  • If you search for records on the Web and someone deletes one of the records in your set while you are viewing them, CS/WebPublisher PRO now provides a message. The message lets you know that the record has been deleted since the search was performed. [45]
     
  • If a record in a set being viewed on the Web is deleted from the textbase, that record will not be included in the sorted set when you change forms on the Web. Previously, the deleted record was sorted first. [46]
     
  • When you recover a textbase using the Recover Textbase command, any Content Server roles assigned to users/groups of that textbase are now retained. [50]
     
  • If a textbase in the Textbases to Service list does not exist when you click the Import Profile Wizard button or the Start Importer button, the CS/Importer service now displays a message telling you that the textbase does not exist and returns you to the Inmagic CS/Importer Settings dialog box. Previously, an error message displayed and the Inmagic CS/Importer Settings dialog box closed. [60]
     
  • If there is a problem starting the CS/Importer service, the error message now includes an explanation of the problem. This information is also written to the CS/Importer log file. [62, 74]
     
  • SQL Server transactions relative to Content Server now require a single database connection instead of two. [69]
     
  • The Recover Textbase, Copy Textbase, and Rename Textbase commands on the Content Server Administration window now display an error message if the textbase is Read-only. [75]
     
  • If you submit XML to CS/WebPublisher PRO and request that results be returned unsorted (that is, you include <SortFields sort="unsorted"> in the XML input), the software now correctly returns unsorted records. [78]
     
  • Query screens and edit forms that are exported to HTML now correctly handle the MF= parameter (which specifies the message file) if it is included in their source. [81]
     
  • When you click the Submit button on a Web edit page that has navigational controls at the top and bottom, both sets of controls are now disabled while the record is being updated. Previously, only the top controls were disabled. [84]
     
  • When using the CS/Importer service to import a document using IFilters, the .TMP file containing the extracted text is now deleted from the TEMP folder if the record is rejected (for example, because a required field was not populated). [92]
     
  • When submitting XML input, the <XE> and <XS> elements (if any) are read before the rest of the XML is validated. [94]
     
  • CS/WebPublisher PRO now supports the use of Basic authentication when referencing XSL style sheets in XML input. Previously, if you referenced any XSL files in the XML input, only Anonymous access was supported. [96, 129]
     
  • A problem with record level security has been corrected. In order to add terms to an Access Control field, the password you are using must have Full Access to the record class. [97]
     
  • The Find box on the Inmagic Choices Browser on query screens now correctly jumps to the correct item in the list. [100]
     
  • The way CS/WebPublisher PRO locates a textbase has been improved to reduce the occurrence of the "Unable to access the textbase" error message. [101]
     
  • You can now use a mouse scroll wheel with the Query Choices Browser for sets boxes. Previously, this caused CS/TextWorks to crash. [105]
     
  • CS/WebPublisher PRO now always writes identifying fields to the textbase log file when there is an error modifying a record. [123]
     
  • A problem with the background color of a CS/WebPublisher PRO error message has been corrected. When you submit a canned query that is not in the appropriate format for the software, the message now uses the Web browser's default background and text colors. [133]
     
  • Word indexes are now handled properly when you use the Load New Textbase command on an accent-insensitive SQL Server. [135]
     
  • If the same color is specified for both the background color and foreground color on a form or screen that is used on the Web, CS/WebPublisher PRO now automatically detects this and only uses the color set for the background; the foreground color will not be changed to your specification so that users can view the page. This also applies to error message pages on the Web. [186]
     
  • When loading a new textbase, the software now detects the size of the import file before loading it and displays a message if it is larger than 2 gigabytes. [190]
     
  • Temporary query boxes added "on-the-fly" to query screens now behave appropriately when you use the Change Order buttons (for example, to list a different field's index first in the Query Choices Browser). Previously, if you used the Change Order buttons, the field names were added to the box contents. [206]
     
  • Advanced users can now add their own form elements to Web search screens without specifying name parameters for them. Previously, adding additional form elements without name parameters caused some Web search screens to halt with a Runtime error. [211]
     
  • CS/TextWorks no longer crashes when displaying records containing words longer than 465 characters when search highlighting is on. [230]
     
  • The width specified in <div> statements in Raw HTML is no longer retained when screens and forms are exported to HTML for use with CS/WebPublisher PRO. [242]
     
  • While specifying Import Options (for the CS/Importer service or when you choose File>Import or File>Import Document in CS/TextWorks), the correct controls display after dismissing an error message. Previously, the correct tab was selected, but it contained the wrong controls. [257]
     
  • The validation list for an Access control field now prohibits all entries that start with a number. Previously, it incorrectly accepted entries that started with a number, if they exceeded 10 characters. [319]
     
  • CS/WebPublisher PRO now correctly recognizes when you do not specify any search criteria on query screens that have been modified to include check boxes. Previously, an error message page would appear stating that the software was "Unable to recognize as a correctly formed query." [330]
     
  • When using Content Server to import XML, if you select the Specify XSL Transform in File option button, but do not specify an XSL file, you now get a message letting you know that you need to specify one. [335]
     
  • When restoring a textbase (choose Back Up & Restore>Restore Textbase), you now get an error message if you select a backup set that is missing any of the required files (.DAT, .CBS, .CBA, .CAC). [352]
     
  • After installing Content Server, when you choose Set Up SQL>Create Control Database but do not specify a SQL Server, you now get a message that says: "A SQL Server is required". If you are using Content Server Enterprise, you will also see this message whenever you click OK on the Select SQL Instance dialog box without having specified an instance. [355]
     
  • In the Content Server Administration window, if you choose Set Up SQL>Create Control Database and the control database already exists, you now get a message letting you know that it already exists. [356]
     
  • When editing the textbase structure, if you remove indexes, the resulting status message now correctly says "Removing field index. Please wait…" Previously, it said "Removing field. Please wait…" [367]
     
  • If you try to add a new record over the Web by submitting XML and the record is not added because of an error, the XML no longer shows an empty <KeyField> tag. [413]
     
  • When using the CS/Importer, if you are importing records using the Append Fields matching option, consecutive matching records will now be appended appropriately to the existing record. Previously, the first record that matched did not have its information appended to the existing record. [427]
     
  • The Next Value setting for Automatic Numbers now resides within the SQL database. Previously, it was stored in the .CBS file. [460]
     
  • If you delete the only record on a report page on the Web, the screen is now automatically refreshed and a message appears to tell you that there are no records left to display on the page. [463]
     
  • If you specify an XSL file with the XS= parameter and the HTTP reference you use does not exist, the message that appears now indicates that the problem is an HTTP 404 (for example, file not found). [486]
     
  • Web reports generated using a Web Multiple Textbase Query screen no longer incorrectly display a "Record has been deleted" message when a user tries to expand a record that is located in one of the search textbases. Previously, this happened sporadically. [499]

Documentation Resources

The following resources are available for CS/TextWorks, CS/WebPublisher PRO, and the CS/Importer:

Resource Explanation
Inmagic Content Server Installation Notes This booklet, which comes with the software, explains how to install the software. It is also available as a PDF file. Note that the CS/Importer service is installed by default with CS/TextWorks.
Inmagic Content Server User’s Manual A user’s manual that covers CS/TextWorks and CS/WebPublisher PRO and is available as a PDF file, which is included with the installation of the software.
Content Server
online help		 The help file, which covers CS/TextWorks, CS/WebPublisher PRO, and the CS/Importer service, contains the most up-to-date information and includes more details than the Inmagic Content Server User’s Manual. To open the help file:
  • Start CS/TextWorks and press F1, or choose Help>Help Topics from the CS/TextWorks menu bar.
     
  • Start CS/Importer and press the Help button.
Inmagic Content Server Administrator’s Guide This guide, available as a PDF file, describes ongoing administrative and maintenance tasks for the Content Server system that should be performed by the Content Server Administrator (for example, how to back up and restore a textbase). It is located on the Inmagic Web site at http://support.inmagic.com/web.
Upgrading to the Inmagic Content Server Platform This guide, available as a PDF file, explains how to upgrade from Inmagic DB/TextWorks and Inmagic DB/Text WebPublisher PRO to CS/TextWorks and CS/WebPublisher PRO. It is installed with your Content Server software and is available on the Inmagic Web site at http://support.inmagic.com/web.
Inmagic Web Products Schema Documentation This file contains information about each element you can submit in XML to CS/WebPublisher PRO. It is located on the Inmagic Web site at http://support.inmagic.com/web.
Knowledgebase and Web site Provides information via the Web. With the software open and a Web browser available:
  • To search for solutions to common problems, choose Help>Inmagic on the Web>Knowledgebase to go to the Inmagic Product Support knowledgebase.
  • To visit the Inmagic Web site, choose Help>Inmagic on the Web>Home Page or Help>Inmagic on the Web>Support Page.
HTML help pages for CS/WebPublisher PRO These files provide help topics for the Web component. See the online help for descriptions of WEB_BEGIN.HTM, WEB_ICHOICES.HTM, WEB_MSG.HTM, and WEB_WW.HTM, which are in the HELP subfolder of the folder in which you installed CS/WebPublisher PRO.

Troubleshooting

The following sections include errors you may experience as you familiarize yourself with your Content Server system.

Critical Errors for CS/TextWorks

There are a number of messages that may prevent you from starting CS/TextWorks or opening any textbase. Each is documented below. Messages are listed in alphabetic order.

Error message: "Cannot create directory '<directory>'."

Reason: Either this is the first time you have run CS/TextWorks on this machine using this login account, or the UserFilePath setting has been removed from your registry.

You typed a directory that does not already exist in the User File Path dialog box, and responded Yes to the Directory does not exist. Create it? question. However, CS/TextWorks encountered an error when trying to create the directory.

When you click OK, you return to the User File Path dialog box so you can try again.

Solution: Verify that:

  • You typed a path (that is, a drive and directory), not a file name.
     
  • The drive you specified, if any, exists (and if you are on a network, that you are connected to it or logged in).
     
  • You have the necessary rights to create a directory on that drive.
     
  • The directory name is a valid directory name.
     
  • If you typed multiple directory levels, all directories above the specified directory already exist (for example, if you typed C:\USER\TEMP\CONTENTSERVER, verify that C:\USER\TEMP already exists).
     
  • No file exists with the directory name you specified.

Try creating the directory manually by choosing File>New>Folder in Windows Explorer.

If all else fails, accept the default that CS/TextWorks supplies (for example, C:\PROGRAM FILES\INMAGIC).

Error message: "Cannot read 'inmcsrv.cmx'"

Reason: This message can appear if the INMCSRV.CMX file is missing or damaged.

Solution: If the INMCSRV.CMX file is missing or damaged, re-install the software.

Error message: "Directory does not exist. Create it?"

Reason: Either this is the first time you have run CS/TextWorks on this machine using this login account, or the UserFilePath setting has been removed from your registry.

You typed a folder that does not already exist in the User File Path dialog box.

Solution: If this is the first time you have run CS/TextWorks and you want to create the new folder, click Yes.

If you already have existing user files, or you made a mistake when typing the folder name, click No to return to the User File Path dialog box. Then, specify the folder where your user files (extension .CBU) are already located.

Error message: "File '<file name>', and possibly other textbase files, no longer exist. The textbase cannot be opened.
Note: The Recover Textbase command may help you recover from this problem."

Reason: You tried to open a textbase using one of the following methods:

  • You clicked on a textbase box in a menu screen.
     
  • You chose one of the "last-used" textbases from the bottom of the File menu.
     
  • You chose File>Open.
     
  • You used Dump Textbase, Load New Textbase, Check Textbase, or one of the other commands on the Manage Textbases menu. (Note that the Check Textbase command is only accessible from the Content Server Administration window.)

Content Server cannot find the file name shown in the message.

Solution: If you used one of the first two methods, the problem may be that you have moved or renamed the textbase or you are not connected to the network drive where the textbase is located. Or, the textbase may have been a temporary textbase that you have deleted because you no longer need it.

If you used one of the last two methods, the problem is probably more serious. The .CBA file exists, but other files are missing. The Recover Textbase command on the Manage Textbases menu of the Content Server Administration window will only be useful if all of the textbase files with the following extensions do still exist: .CBA, .CBS, and .CAC. If not, your only recourse is to restore the textbase from a healthy backup. Contact your Content Server Administrator.

Error message: "File '<file name>' cannot be read. It is possible that the file is corrupted."

Reason: The file name shown in the message exists, but Content Server cannot read essential information in it. The file may be corrupted.

Solution: If the file is one of the files installed with Content Server (for example, INMCSRV.EXE, INMCSRV.CMX, or a .DLL file), you can re-install Content Server from the original CD-ROM.

Error message: "File '<file name>' is missing, and CS/TextWorks cannot run. Please reinstall."

Reason: CS/TextWorks checks for several files on startup, including INMCSRV.CMX and certain DLL files. The file name shown in the message is missing. (Note that you may also get a similar message when using the Content Server Administration program. If you do, the same solution applies.)

Solution: Contact your Content Server Administrator to re-install the software from the original CD-ROM using the SETUP program. Or restore the missing file from a healthy backup.

Error message: "The textbase is not available because someone else has exclusive access. Please try again later."

Reason: You tried to open a textbase when someone else already has the textbase open with exclusive access. This can happen when:

  • The other person used the File>Set Exclusive Textbase Access command.
     
  • The other person used one of the commands on the Manage Textbases menu, for example, Dump Textbase, Load New Textbase, or Check Textbase. All of these options require exclusive access to that textbase. (Note that the Check Textbase command is only accessible from the Content Server Administration window.)
     
  • The other person is using a command in the Content Server Administration program that requires exclusive access to that textbase.

Solution: Wait until the other person finishes using the textbase.

If this message appears frequently, you may want to:

  • Add a Master password to prevent unauthorized people from using the options on the Manage Textbases menu. You must know the Master password to use any of these options. You can enable a Silent password to provide default permissions to the textbase.
     
  • Add or change any passwords in use so that users cannot switch to exclusive access. Clear the Exclusive Access Permitted check box for each password.

Error message: "The user file path '<path>' specified in your user options does not exist."

Reason: The user file directory represented by <path> in the message does not exist, so CS/TextWorks cannot create a user file until you specify a new user file path.

Solution: When you click OK on the message, the User File Path dialog box appears, with your current user file path filled in.

To create the user file path shown, click OK. Otherwise, specify a different user file path. If you know where your user files are located, specify that folder. User files have the extension .CBU.

Error message: "You must run Setup Workstation on this machine before you can run CS/TextWorks. See the Installation Notes for more information."

Reason: You attempted to run CS/TextWorks when Setup Workstation has not been run on this machine. Setup Workstation does not simply create shortcuts; it installs files and registry entries necessary for CS/TextWorks to run.

Solution: Log in as Administrator. Then close down all other applications, including the Microsoft Office taskbar, and run SETUP.EXE from the folder where CS/TextWorks is installed. Follow the prompts.

JavaScript Errors with CS/WebPublisher PRO

Multiple JavaScript errors occur when you load an exported menu screen, query screen, or edit screen in a Web browser.

Solution: Consider the following:

  • The ICS-WPD virtual directory may not be mapped/aliased properly to the CS/WebPublisher PRO installation folder or does not have the necessary Read, Execute, and Scripts access. Some HTTP servers may also require explicit access to the ICS-WPD/EXEC virtual directory.
     
  • The screen may have been opened using file access (that is, the file was double-clicked to open it). The screen must be opened using HTTP access.

Contacting Inmagic, Inc. and Communicating with Other Users

For help, you can contact Inmagic, Inc. or your local Inmagic dealer. You can also communicate with other Inmagic users.

If you have a Product Support contract, please have the number ready, and try to be at your computer when you call. If that is not possible, note exactly what you were doing when you encountered the problem, the text of any error messages you received, and your software version and serial number (choose Help>About CS/TextWorks to look it up). If you do not have a Product Support contract, you can contact Inmagic Sales to purchase a support plan.

Inmagic, Inc.
200 Unicorn Park Drive
Fourth Floor
Woburn, MA 01801 U.S.A.
Tel: 781-938-4444 or 800-229-8398
Fax: 781-938-4446
http://www.inmagic.com

support@inmagic.com - product support questions
advantage@inmagic.com - for questions from current InmagicADVANTAGE customers
sales@inmagic.com - sales, product pricing, and custom solution questions
marketing@inmagic.com - marketing questions
partners@inmagic.com - new Business Partner inquiries
webmaster@inmagic.com - messages related to the Inmagic Web site
wishlist@inmagic.com - feature requests
inmagic@inmagic.com - other messages

If your message is intended for a particular person at Inmagic, Inc. (for example, a Product Support representative who is expecting the message or files), please include the name of that person in the subject and in the message.

Communicating with Other Users

You can communicate directly with other users by participating in one or more Inmagic Web forums. To do so, go to the Inmagic Web site (http://www.inmagic.com) and from the Support menu, click Forums.

0804