Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. BlackBerry AtHoc Integrations
  4. SiRcom Installation and Configuration Guide
  5. Configure IIM IP connectivity
  6. Troubleshoot the configuration

Troubleshoot the configuration

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 a red color, it indicates that the configuration has not been executed correctly.
  1. If the 
    BlackBerry AtHoc
     management system (for example, 
    https:/<
    domain-name
    >/athoc-iws
    ) is available on Internet Explorer on a local computer, then the 
    indexURL
     should also be available.
    1. Enter 
      SiRcom
       Giant Voice System Integration Guide's 
      indexURL
       in the browser. 
      For example, 
      https://<DomainName>/syndication/cap_ SERIALGV_2060520/capindex
      . If there are no items in the syndication feed, an XML message similar to the following image should be displayed:
      CAP-XML Message
  2. If there are items in the feed, an XML message similar to the following image should be displayed.
    a CapCon screenshot
  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 sub-folders.
  5. Check the 
    indexURL
     and proxy settings in the 
    system_private.config
     file for any misspellings.
  6. If any line have been misspelled, repeat the configuration steps above.
  7. Check the 
    capnodelog
     file for errors. Right-click 
    IIM
     to Open Windows Explorer.
  8. Click the 
    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.
  9. 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.