Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
- Troubleshooting: Common database errors
- Messages: Cannot Find SQL Server, Error Connecting to servername
- Message: Corresponding Join Not Defined
- Messages: Error opening the Core.ir file in read mode
- Troubleshooting: Database debug
- Troubleshooting: Interpreting debugdbquery output
- Troubleshooting: Power outages and hardware failure
- Troubleshooting: Slow execution of queries
- Troubleshooting lister
- Troubleshooting: ODBC error when running Crystal Reports
Messages: Cannot Find SQL Server, Error Connecting to servername
Message: Cannot Find SQL Server and Error Connecting to servername
These generic connection failure messages indicate that the Run-time Environment (RTE) attempted to log in to Service Manager and either failed or received no reply. See the following list for common causes and possible solutions.
- The Service Manager server is not running.
Ensure that the server is running and then attempt to connect using the Service Manager client. - Your login information is incorrect.
On failure, Service Manager prompts you to re-enter your login information. Ensure that you enter the correct case-sensitive login and password. For future login attempts, you can optionally modify program options to automatically set them to the correct information. - The number of valid Service Manager licenses are already in use.
Service Manager accepts a set number of concurrent users, depending on your license agreement. If all available licenses are in use, Service Manager rejects your login. Contact your Service Manager administrator to confirm the number of licenses available.
Troubleshooting: Common database errors
