The Gateway Manager ETL isn't importing any Visualizer files from a Windows console and the says that it is detecting 0 runs in TrueSight Capacity Optimization (TSCO)

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Capacity Optimization


    APPLIES TO:

    BMC TrueSIght Capacity Optimization 20.02, 11.x, 10.x ; BMC Performance Assurance 9.5



    PROBLEM:

    The TrueSight Capacity Optimization (TSCO) Gateway Manager ETL isn't importing any Visualizer files from a Windows console and the says that it is detecting 0 runs.

    The Log Level 10 ETL logs look like this:

    [2016-04-26 15:06:58]  INFO  Listing finished manager runs...
    [2016-04-26 15:06:58]  INFO  [listAllFinishedManagerRuns] GM response status: 1 - status line: 200 OK - content: <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:BMCGM="urn:GeneralManager"><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><BMCGM:listAllFinishedManagerRunsResponse><runList></runList></BMCGM:listAllFinishedManagerRunsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope> - HTTP/1.1 200 OK
    Connection: close
    Server: gSOAP/2.7
    Content-Length: 565
    Content-Type: text/xml; charset=utf-8
    Client-Date: Tue, 26 Apr 2016 20:06:58 GMT
    Client-Peer: 10.178.51.210:10129
    Client-Response-Num: 1

    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:BMCGM="urn:GeneralManager"><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><BMCGM:listAllFinishedManagerRunsResponse><runList></runList></BMCGM:listAllFinishedManagerRunsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

    [2016-04-26 15:06:58]  INFO  listAllFinishedManagerRuns -- [<?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:BMCGM="urn:GeneralManager"><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><BMCGM:listAllFinishedManagerRunsResponse><runList></runList></BMCGM:listAllFinishedManagerRunsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>]
    [2016-04-26 15:06:58]  INFO  listAllFinishedManagerRuns -- pre parse -- [<runList></runList>]
    [2016-04-26 15:06:58]  INFO  Skipping filtered manager run
    [2016-04-26 15:06:58]  INFO  Detected #1 policies - 0 runs - policies:
    [2016-04-26 15:06:58]  INFO  Importing #0 runs - run list:
    [2016-04-26 15:06:58] WARNING  No file found for extraction (based on provided last counter and manager runs filers).
    <-- cut -->


     


    SOLUTION:

     

    Debugging

    What do you get if you run the following commands on the Windows console machine:  
       
    •   "%BEST1_HOME%\bgs\bin\GeneralManagerClient.exe" -s localhost:10129 listAllFinishedManagerRuns
    •  
    •   "%BEST1_HOME%\bgs\bin\GeneralManagerClient.exe" -s localhost:10129 listRunningManagerRuns
      

    Solution

    If the output of the listAllFinishedManagrRuns says "Finished Manager Runs =0" this may be due to scheduler corruption. 

    For example, output like: 

    "%BEST1_HOME%\bgs\bin\GeneralManagerClient.exe" -s localhost:10129 listAllFinishedManagerRuns
    Info : you can specify an optional version : using 9.0.00
    Finished Manager Runs =0


    In the Windows console under Manager -> Schedule do you see runs in FINISHED status or do you only see runs in WAITING status? 

    If you only see runs in WAITING status that likely means that the %BEST1_HOME%\local\manager\BSched[HR].brf files have been corrupted on the machine. 

    The resolution process is to stop the scheduler, remove the *.brf files, and then use the RecoverCorruptManagerRuns command to rebuild the scheduled entries from the runs that had been scheduled before (using the run list from udrCollectMgr which is a component of Manager that manages the data collection and transfer for the Manager runs so it knows the complete list of scheduled runs).  

    Steps to fix BRF file corruption

    (1) Stop the Patrol_Scheduler 

       net stop Patrol_Scheduler

    (2) Back up the BSchedR.brf and BSchedH.brf files (rename to .bad or .orig or something else). (Files are location in %BEST1_HOME%\local\manager, by default, "C:\Program Files\BMC Software\Patrol3\BEST1\NTC\local\manager". 

      cd "%BEST1_HOME%\local\manager"
      rename BSchedR.brf BSchedR.brf.bad
      rename BSchedH.brf BSchedH.brf.bad


    (3) Restart the Patrol_Scheduler 

       net start Patrol_Scheduler

    (4) Rescheduled the Manager script or scripts 

    First, it may be possible to automatically recover previously scheduled Manager runs via the following command: 
      "%BEST1_HOME%\bgs\bin\RecoverCorruptManagerRuns.exe"

    The RecoverCorruptManagerRuns command uses the UDR Collection Manager (UCM) Manager Registration files to resubmit the previously active runs to the PATROL Scheduler.  This is useful if it has been necessary to delete the current scheduler *.brf files due to coruption. 

    If the RecoverCorruptManagerRuns.exe command is not able to recover the runs it will generally be necessary to manually reschedule each Manager run via the TSCO Gateway Manager UI or via another supported methodology. 

    (5) Validate the Manager runs are now scheduled via the TSCO Gateway Manager UI or via another supported methdology. 
      

     


    Article Number:

    000225009


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles