Troubleshooting Search Applet

QuestAgent comes with several integration samples. Although all samples have been tested and known to work with the most popular browsers, it’s not impossible that because of eventual changes in new versions of browsers or higher security restrictions in your environment something doesn’t work as expected.

First, make sure to review the list of supported browsers and known issues.

If search doesn’t work, first check whether your browser reported some JavaScript or Java error:

• In case of JavaScript error, please send us complete error report or message you’ve received.
• In case of Java error, we need not only error message but complete error log. If your browser uses Sun’s Java plug-in, you can find this in Java Console. When Java plug-in is running its icon is displayed in the Windows taskbar. Right click on the icon and select Java Console option. Copy and send us the complete console content as that will help us to track down the problem.

If you customized search scripts or samples and search suddenly doesn’t work any more, check does it still work with the original samples deployed. If it does, lookup for error in customized code. Notice that you may need to verify not only your code related to QuestAgent but also check validity of other page elements. In our experience, we’ve seen QuestAgent working strange or not working at all due to errors in client’s CSS files, which is not what would one expect.

If you’re experiencing a problem in JavaScript implementation, you may find debug log useful.

Reporting Problems

When reporting problems with QuestAgent software, please provide as many relevant details as possible. This may include:

• Operating system used
• Browser version
• Java version
• Version of QuestAgent
• Java error log
• JavaScript error
• Do you run QuestAgent from a local file system or web server?

That will help us identify the problem and may significantly shorten time needed to advice.