Next Topic

Previous Topic

Book Contents

Some Traverse services do not remain running on Windows installations

If you open the Traverse Service Controller and find that some services are unchecked and do not start even after a manual restart, perform the following steps:

Note: By default, the BVE API is not started automatically (you have to start it manually) since it is normally not needed.

  1. Shut down all Traverse components. Then start each service one by one with a 15 second delay between starting each service. If this resolves the issue, it means that your server does not have sufficient memory (256M to 512M is recommended). However, you can continue the trial to evaluate Traverse.
  2. If the web application aborts, it is most likely because you have IIS running on your machine already. Please follow the instructions below to shut down IIS.
  3. If the WMI query daemon aborts, see troubleshooting below.
  4. Check to see if you have the personal firewall enabled (default in XP SP2) which is preventing access to the database (the SP2 firewall blocks all incoming connections by default).

If the problem still persists, please zip the <TRAVERSE_HOME>\logs directory and contact Kaseya Customer Support.