Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. BlackBerry AtHoc Integrations
  4. American Signal Giant Voice System Installation and Configuration Guide
  5. Configure IIM IP connectivity
  6. 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://<domain-name>/client/default.asp is available on Internet Explorer on a local workstation, then the indexURL should also be available. Enter the indexURL in the browser. For example, https://<domain-name>-syndication/cap_amsig_v2/2060799/capindex.
  2. If there are items in the feed, an XML similar to the following image should be displayed: 
    <capIndex xmlns="http://www.incident.com/cap_index/1.0">
    <title>Current CAP Messages</title>
    <updated>2015-10-01T14:09:39.2519688-07:00</updated>
    -<item xmlns="http://www.incident.com/cap_index/1.0">
        <id>B8205FAC-CF2C-4B2D-A3D2-D012D04F3785</id>
        <identifier>B8205FAC-CF2C-4B2D-A3D2-D012D04F3785
        </identifier>
        <sender>AtHoc Admin</sender>
        <status>System</status>
        <msgType>Alert</msgType>
        <firstEffective>2015-10-01T14:09:10.71</firstEffective>
        <lastExpires>2015-10-01T14:24:10.71</lastExpires>
        <url>https://<Domain Name>/Syndication/CAP_AMSIG_V2_    
        2060799/CapIim
        /1012642</url>
        <bounds />
        <format>http://<Domain Name>/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 have 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 
    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.