Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. BlackBerry AtHoc Integrations
  4. ATI Giant Voice System Installation and Configuration Guide
  5. Configure IIM IP connectivity
  6. Verify the CapCon system activity console (GUI)
  7. Troubleshooting

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 IE 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_ATI/2086867/capindex.
  2. If there are items in the feed, an XML similar to the following image should be displayed: 
    - <?xml version="1.0"?>
<capIndex xmlns="http://www.incident.com/cap_index/1.0">
    <title>Current CAP Messages</title>
    <updated>2018-03-26T08:51:11.2144241-07:00</updated>
- <item xmlns="http://www.incident.com/cap_index/1.0">
    <id>31998A16-210C-4B07-92B8-4E6873C91BE4</id>
    <identifier>31998A16-210C-4B07-92B8-E6873C91BE4</identifier>
    <sender>AtHoc Admin</sender>
    <status>System</status>
    <msgType>Alert</msgType>
    <firstEffective>2018-03-26T11:51:03.067</firstEffective>
    <lastExpires>2018-03-26T11:55:03.067</lastExpires>
    <url>https://integration7.athoc.com/Syndication/
    CAP_ATI_2086867/CapIim/1142288</url>
    <bounds />
    <format>http://www.incident.com/cap/1.1</format>
  </item>
</capIndex>
  3. If connectivity is still not good, try commenting out the 
    proxyServer
     and 
    proxyPort
     variables.
  4. 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.
  5. Check the indexURL and proxy settings in the 
    system_private.config
     file for any misspellings. If any line has been misspelled, repeat the configuration steps.
  6. 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 newest 
    capnode.log
     file with Notepad. Browse the file to find the time that the indexURL was changed and the CapCon service restarted.
  7. 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.