Inmagic® DB/Text® WebPublisher Lite version 6.0
Error Messages

DB/Text WebPublisher Lite is the single textbase version of DB/Text WebPublisher.
DB/Text WebPublisher is the search and retrieval engine used with the DB/Text Intranet Spider.


Cannot create temporary storage file for query sets. Contact the webmaster for this site.

Cause The directory where temporary DB/Text WebPublisher sets are stored is write protected or does not exist.
Solution The webmaster for the site where the textbase resides needs to verify that the "qsets" subdirectory under the WebPublisher installation directory exists and is visible to the HTTP server, and that the Internet user account has full (read, write, create) access to this directory.


Cannot find field '<field name>'.

Cause The field indicated in the message does not exist. The field may have been renamed or deleted since the query screen was created.
Solution

Contact the webmaster for the site where the textbase resides, and provide the exact text of the message. The webmaster will probably need to modify the query screen or edit the textbase structure to correct the problem.



Cannot find or load set '<set name>'.

Cause You clicked a link which includes the named set as part of its query criteria. The query set indicated in the message does not exist. The set may have been renamed or deleted since the page was created.
Solution

Contact the webmaster for the site, and provide the exact text of the message, the URL for the page and the text of the link you clicked. The webmaster will probably need to modify the page or recreate the set to correct the problem.



Cannot search unindexed field '<field name>'.

Cause The field indicated in the message has neither a Term index, nor a Word index. DB/Text WebPublisher cannot search unindexed fields.

The indexes were removed after the query screen was designed.

Solution The webmaster for the site where the textbase resides needs to use Edit Textbase Structure to add either a Term index or a Word index or both to this field.


Could not access XML conversion facility.

Cause You shouldn't normally see this message. It indicates that WebPublisher could not access the XML conversion facility.
Solution The webmaster for the site where the textbase resides will need to ensure that the Microsoft XML program files are properly installed and accessible to WebPublisher.


DB/Text WebPublisher Lite cannot access textbase '<textbase name>'.

Cause The textbase name specified in the query or menu screen (and shown in the message) does not match the textbase name specified in the [WebPubLite] section of the DBTWPUB.INI file.
Solution The webmaster for the site needs to see the READMEWP.HTM file for instructions. To search multiple textbases, upgrade to DB/Text WebPublisher.


DB/Text WebPublisher Lite cannot be accessed in this way.

Cause You accessed DB/Text WebPublisher by specifying the DLL/EXE name. For example, this can happen if you attempt to bookmark a report page (or add it to your favorites) then use that bookmark.
Solution You cannot bookmark the results of a WebPublisher query. Aside from this issue, temporary query sets expire periodically. Instead, bookmark the query or menu screen and repeat the search.


The DB/Text WebPublisher Lite DLL has not been properly serialized.

Cause The serial number is not a valid DB/Text WebPublisher serial number. The most likely cause for this is that the DBTWPUB.DLL file has been damaged or the installation process failed prior to completion.
Solution The webmaster for the site where the textbase resides needs to reinstall DB/Text WebPublisher from the original disks using the SETUP program.


The DB/Text WebPublisher Lite textbase path or name is not initialized.

Cause The textbase name or path is not specified in the [WebPubLite] section of the DBTWPUB.INI file.
Solution The webmaster for the site needs to see the READMEWP.HTM file for instructions.


DB/Text WebPublisher Lite Trial Version cannot open a textbase containing more than 50 records.

Cause The site where the textbase resides is using a trial version of DB/Text WebPublisher.
Solution The webmaster for the site where the textbase resides needs to (purchase and) install a full version of DB/Text WebPublisher.

If the textbase is strictly for demonstration/testing purposes, they can delete enough records so the textbase has fewer than 50 records.



The DB/Text WebPublisher XML output feature has been disabled.

Cause The webmaster for the site where the textbase resides has disabled XML output for WebPublisher.
Solution Contact the webmaster for the site about enabling XML.


Error loading XML stream - <reason>. <line number>

Cause The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. WebPublisher encountered an error when attempting to load the XML generated by WebPublisher before transforming it. The message normally includes the reason for the error and the line number in the XML stream on which the problem occurs.

Solution The webmaster for the site must correct the problem. If using a Web browser which can transform XML output (e.g., IE5.x or later), one can temporarily stop using the XSL file, and display raw XML in the Web browser, to get more information about the line which is causing the error.


Error reading XSL file '<XSL value>' - <reason> line <line number>
Error reading XSL file '<XSL value>' (from '<URL>').


Cause The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The <XSL value> shown in the message indicates the value of the XSL= parameter specified in the query screen.

WebPublisher encountered an error reading the specified XSL file. The message includes the reason for the error and the line number in the XSL file on which the problem occurs. If no reason or line number is given, WebPublisher cannot find the XSL file (the '<URL>' shows the complete URL to which any relative URL was translated), or the XSL file is too unreadable to report a specific problem.

Solution The webmaster for the site must either fix the problem in the XSL file, or specify the correct location of the XSL file.


Error trying to initialize the XML conversion facility.

Cause There is a problem with the Microsoft XML4 program file installation. The MSXML4 DLLs either are not properly installed, are damaged, or are not accessible to WebPublisher. The WebPublisher install puts these files in the Windows System directory.
Solution The webmaster for the site must ensure that the Microsoft XML4 DLLs are properly installed, and that the account used by WebPublisher has sufficient rights to use these files.


Field '<field name>' is not a Link field.

Cause The DB/Text WebPublisher search screen you are using is not compatible with the textbase it searches. The textbase structure has been changed since the search screen was created.

A box searches a secondary textbase field (e.g., Title@Catalog). The message indicates that 'Catalog' is a field in the current primary textbase but it is not a Link field.

Solution The webmaster for the site where the textbase resides needs to create a new search screen for this textbase.

For now, you can only search the textbase if you don't use that box.



Field(s) not indexed for comparison searching (no term index).

Cause Your search includes an operation which requires a Term index (e.g., a range search {indicated by a colon}, or a =, >, >=, <, or <= search). The field searched by the box where you typed the comparison search doesn't have Term index.
Solution Change your search so it doesn't use any of the comparison operators. For example, if you searched for =Accounting, search for Accounting instead.

If you're searching for text which includes any of these symbols, enclose the search text in quotes or replace the symbol with a space.

You can also contact the webmaster for the site where this textbase resides and ask them to use Edit Textbase Structure to add a Term index to the field.



Field(s) not indexed for proximity searching (no word index).

Cause The search criteria include a proximity search (e.g., "bugs p2 bunny") on a field which doesn't have a word index. Proximity searches require a word index.
Solution Examine the contents of your search screen for a string like "w3" or "p5". Then change your search so it doesn't do a proximity search in that query box.

If you are trying to find a term which includes a word like "P73", precede the search item with an equal sign or enclose the search item in quotes:
=P73 NL1
"P73 NL1"

You can contact the webmaster for the site where the textbase resides and ask them to use Edit Textbase Structure to add a word index for that field.



Incorrect password entered.

Cause The DB/Text WebPublisher search screen contains an "Enter password:" box. You typed a password which is not in use for this textbase.
Solution Return to the search screen and type a valid password.

The textbase may have a Silent password. If you don't know a password, try leaving the "Enter password:" box blank.



Link '<field name>' not valid or not available.

Cause You typed a search which attempted to search a field from a secondary textbase. You cannot search secondary textbase fields until the problem is corrected.
Solution If the textbase has passwords, the password you are using may hide the linked information. Return to the search screen and specify a password gives you access to the linked information.

Otherwise, contact the webmaster for the site where the textbase resides, and provide the exact text of the message. The webmaster will probably need to use Edit Textbase Structure to correct the problem. For example, the secondary textbase may not have a Silent password.



No query criteria specified.

Cause You pressed the Submit Query button without specifying any query criteria, either by:

- typing words and/or phrases in the query boxes
- selecting choices from droplists

Solution Specify what you want to search for before pressing the Submit Query button.


No records found by latest query.

Cause You did one of the following:
1. Performed a search which didn't retrieve any records.
2. Clicked on a hypertext link which automatically performs a search.
Solution Return to the DB/Text WebPublisher search screen and click the Help icon to review the instructions for searching. If you believe the search should have retrieved records, here are some things to check:

- If the search screen includes Word Wheel buttons, use the word wheel to paste words and/or terms into the search screen.

- If the search screen includes an "Enter password:" box, be sure you used a password which provides access to the fields you are searching.

- Examine the contents of the search screen (especially if it is longer than the screen) to verify that you don't have query criteria left over from a previous search.

- You must use symbols (&/!) not words (and,or,not) for Boolean operators.

- If your search includes any Boolean operators (/ & !) or range searches (:), put spaces around the symbol.

- Remember that range searches involving partial dates start from the beginning of the range. For example: <1993 will not retrieve 1-Jan-93, but >1993 will.

If you got this message when you clicked on a hypertext link, contact the webmaster for the site where the textbase resides. The query criteria for the stored set may need to be corrected.



Proximity search available only for words, not phrases.

Cause Proximity only works between two words, not between multiple words or phrases. The box contents which contain the problem search string are shown in the message.

Permitted proximity searches: jelly p2 beans, govern* w5 contract*
Invalid searches: licorice p2 jelly beans, licorice p2 jelly w5 beans

Solution Examine the contents of your search screen for the string shown in the message. Then change your search so proximity operators are used only between two single words.

If you are trying to find a term or phrase which includes a word like "W2", precede the search item with an equal sign or enclose the search item in quotes:

=Employee copy W2 form <-- term search
"Employee copy W2 form" <-- phrase search



Range operation is incorrect because '<beginning of range>' is not less than '<end of range>'.

Cause Your query criteria include a range search but the beginning of the range you specified is larger than the end of the range.
Solution Look for the range search. It will have a colon in it. If the search criteria are complex or your query screen is taller than the screen, you can use the Find option in your web browser to search for ':'. Then change the range search so the start of the range is to the left of the colon. For example, search for 20:50.

You may be searching for text which actually has a colon in it, rather than attempting to perform a range search. If this is the case, either omit the colon or enclose the text in quotes (e.g., "TX : Texas"). Depending on how the webmaster has configured DB/Text WebPublisher, another solution would be to remove the spaces around the colon (TX:Texas). Punctuation is not significant except in Code or UDC fields, so it's usually easier to omit punctuation in search text.

The box may search multiple fields which have different indexing settings. For example, one may treat numbers numerically, while the other may treat them alphabetically. In such a case, either "2:12" or "12:2" will cause this error. You must change your search; paste individual entries or use ">=2 & <=12" instead of "2:12". You might also want to contact the webmaster for this site about changing the query screen or indexing settings.



Severe error during transform using XSL file '<XSL value>'.

Cause The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The Microsoft XML DLLs which are used to perform the transform performed an illegal operation. The XSL file may be damaged. The problem is so severe that no line number can be given. <XSL value> represents the value of the XSL parameter.

Solution The webmaster for the site must address the problem with the XSL file.


Severe error loading XML stream. Insufficient memory?

Cause WebPublisher encountered an error creating the XML output stream. This message should rarely occur. If it does, the server running WebPublisher may be running low on memory.

Solution The webmaster for the site must address the problem with the server machine.


Severe error loading XSL file '<XSL value>'.

Cause The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The Microsoft XML DLLs which are used to perform the transform performed an illegal operation. The XSL file may be damaged. The problem is so severe that no line number can be given. <XSL value> represents the value of the XSL parameter.

Solution The webmaster for the site must address the problem with the XSL file.


There is a Boolean expression which is too deeply parenthesized.

Cause The search is too complex; there are too many levels of parentheses.
Solution If there are unnecessary parentheses, remove them.
Rearrange the order of the search items so fewer parentheses are necessary. Perform / searches before & and ! searches. For example, change "bugs & (rabbit / bunny)" to "rabbit / bunny & bugs"


This DB/Text WebPublisher Lite DLL has expired.

Cause The site is using a trial version of DB/Text WebPublisher, and the trial period is over.
Solution Contact the webmaster for the site and tell them you received this message.


This link does not have a valid destination (set no longer exists in textbase). Please contact the webmaster for this site.

Cause You clicked on a hypertext link which performs a search "under the covers". The query set referenced by the hypertext link has been deleted from the textbase or renamed. This message may also appear if one of the fields referenced by the set has been renamed.
Solution Contact the webmaster for the site about correcting the HTML page or restoring or recreating the query set.


Transform using XSL file '<XSL value>' produced no result.

Cause The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The result of the tranform is an empty page.
Solution The webmaster for the site must fix the problem with the XSL file.


Unable to access the textbase.

Cause There are several reasons why you might get this error.

- The textbase may be damaged.

- There may be too many people using the textbase.

- Someone else may have exclusive access to the textbase. For example: backup software, or someone using Check Textbase, Immediate Indexing, or editing the textbase structure.

Solution Contact the webmaster for the site and tell them you received this message. The webmaster may need to increase the maximum textbase users, or add passwords to prohibit exclusive access.


Unable to recognize as a correctly formed query.

Cause DB/Text WebPublisher cannot understand the search criteria typed in the search screen. This is a general error message which is often caused by typographical errors, or problems with the search screen.

If you received this message when clicking on a hypertext link, textbase fields or sets may have been renamed since the menu screen was created.

Solution Return to the search screen and click on the Help link to review the instructions for searching. Possible problems include:

- Mismatched quotes or parentheses
- Extra Boolean operators (e.g., you should have typed "car / auto" instead of "car / auto /")

If you cannot determine what caused the error, try a couple of simpler searches, e.g., just a word in a box, to see if they work. If the search screen includes Word Wheel buttons, use those to reconstruct the query.

If even simple searches don't work, contact the webmaster for the site, tell them you received this message, and describe what you typed in each box. The search screen may need to be edited and corrected. If there are multiple copies of the textbase with the same name, the webmaster may need to verify that the [WebPublisher Textbase Path] section of the DBTWPUB.INI file references the correct path.

If you received the message when clicking on a hypertext link, contact the webmaster for the site and tell them what link you clicked on. The hypertext link may need to be edited and corrected.



You must enter a password to access the textbase.

Cause The textbase has passwords. You must type a password to search the textbase.
Solution Return to the search screen and type a valid password in the "Enter password:" box.

If the search screen does not have an "Enter password:" box, contact the webmaster for the site. One will need to be added so that people can search the textbase.

If you got this message after clicking on a hypertext link, the link performs a search on the textbase. Contact the webmaster for the site. They will need to add a Silent password to the textbase.



Your current query has expired. Perform the search again.

Cause This error indicates that the slot occupied by a query set has been reused by someone else's query. This may indicate that too much time has passed since the query was first performed, or that many users are searching the textbase simultaneously.
Solution Contact the webmaster for the site. They may need to increase the maximum number of query sets that can be stored by increasing the WebSetMax= value specified in the [WebPublisher] section of the DBTWPUB.INI file in the Windows directory on the HTTP server.