Skip Navigation

Troubleshooting

If the CapCon System Activity console indicates anything other than a total number of items in the index and a number, or if the CapCon System Errors/Exceptions/Warnings console has content in red, this indicates that the configuration has not been executed correctly.
  1. If the BlackBerry AtHoc management system, for example, https://integration7.athoc.com/athoc-iws is available on Microsoft Internet Explorer on a local workstation, then the indexURL should also be available. Enter the indexURL in the browser. For example, https://integration7.athoc.com/syndication/cap_Monaco_2050363/capindex.
    If there are no items in the syndication feed, an XML similar to the following image should be displayed: 
    Cap Index with no items in the syndication feed
  2. If connectivity is still not good, try commenting out the 
    proxyServer
     and 
    proxyPort
     variables.
  3. If an HTTP or HTTPS error is displayed instead of XML, this may indicate a firewall or certificate issue or a configuration problem with the BlackBerry AtHoc server syndication folder or subfolders.
  4. Check the indexURL and proxy settings in the 
    system_private.config
     file for any misspellings. If any line have been misspelled, repeat the configuration steps.
  5. Check the 
    capnodelog
     file for errors. Open Windows Explorer by right-clicking on the IIM Start button and navigate to 
    C:/Program Files/capnode/capnodelogs
     and open the 
    capnode.log
     file with Notepad. Browse the file to find the time that the indexURL was changed and the CapCon service restarted.
  6. Contact BlackBerry AtHoc technical support. Be prepared to provide the 
    system_private.config
     and 
    capnode.log
     files and screen shots of the console screen and the BlackBerry AtHoc management console pages.