Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > No CDR\CMR data being collected due to old Job ID in database

No CDR\CMR data being collected due to old Job ID in database

Created by Matthew Lamb, last modified by MindTouch on Jun 16, 2016

Views: 1,227 Votes: 0 Revisions: 3


This article discusses an issue that can occur when VNQM is not pulling any of the Call Detail Records (CDR) or Call Management Records (CMR) data for Cisco Unified Call Managers from the FTP\SFTP server even when the files are present on the server and the FTP\SFTP server shows VNQM logging into the client. The steps in this article only pertain to when the Job ID is not refreshing for CDR\CMR collection.


VNQM 4.0 and later


The issue occurs because the registered Job ID in the database has been corrupted or invalid and is constantly being recycled through the job engine. The Job ID will remain in the voipccmftpconnectioninfo table and not be purged out when the next poll interval comes through.


  1. Verify the following:
    • The CDR\CMR files are on the FTP\SFTP server and 
    • VNQM has the correct credentials and can connect to the FTP\SFTP server.
    • The CDR\CMR sequence is correct based off the flat file sequences on the FTP\SFTP server.
  2. Run this query to verify if the Job ID is being refreshed correctly: 
    select currentjobid, currentjobstarttimeutc from voipccmftpconnectioninfo
  3. If the job id is being refreshed correctly every new polling cycle, troubleshoot CDR\CMR collection normally.
  4. If the job id is not being refreshed and remains the same through several polling cycles, stop all services.
  5. Run the following queries:
    update voipccmftpconnectioninfo set currentjobid = null
    update voipccmftpconnectioninfo set currentjobstarttimeutc = null
  6. ​Reinstall the Collector service
  7. Reinstall the Job Engine and Job Engine v2 services. The job should now refresh correctly.


Last modified