Check Point: SmartView Tracker does not display any logs - Error: "Failed to open file fw.log"

With the last post of how to do a "migrate import", one problem I did have was this error message below.  I found I had to import the pointer files, etc to fix my problem of not being able to open the log files, since my customer did want the log files included in the import.  No worries, step 3 and 4 resolved my issue.  Below is the SK that we referred to when I couldnt open the log files in Tracker.
SK35401:
SmartView Tracker does not display any logs and a popup appears "Failed to open file fw.log"

SYMPTOMS

SmartView Tracker does not display any logs and a popup appears "Failed to open file fw.log" SmartView Tracker does not display logs correctly.

CAUSE

Possible reasons: Some temporary issues with SmartView Tracker daemon (cplmd). Some of the log pointers are missing or corrupted.

SOLUTION

Follow these steps: Restart Check Point services on the machine to which you connect with SmartView Tracker (Management Server / Log Server): [Expert@HostName]# cpstop [Expert@HostName]# cpstart If the issue is not resolved, then delete SmartConsole cache files: Close all SmartConsole windows (SmartDashboard, SmartView Tracker, SmartView Monitor, etc.). Stop Check Point services on the machine to which you connect with SmartView Tracker (Management Server / Log Server): On Security Management Server: [Expert@HostName]# cpstop On Multi-Domain Security Management Server: [Expert@HostName]# mdsstop_customer Domain_Name Backup/move the current cache files: On Security Management Server: [Expert@HostName]# mkdir $FWDIR/conf/Cache_BKP [Expert@HostName]# mv $FWDIR/conf/CPMIL*  $FWDIR/conf/Cache_BKP/ [Expert@HostName]# mv $FWDIR/conf/applications*  $FWDIR/conf/Cache_BKP/ On Multi-Domain Security Management Server: Notes: It is forbidden to remove any files from the MDS context. It is forbidden to remove $FWDIR/conf/applications.C* files from the context of Domain Management Server. [Expert@HostName]# mdsenv Domain_Name [Expert@HostName]# mcd conf [Expert@HostName]# mkdir $FWDIR/conf/Cache_BKP [Expert@HostName]# mv $FWDIR/conf/CPMIL*  $FWDIR/conf/Cache_BKP/ Start Check Point services on the machine to which you connect with SmartView Tracker (Management Server / Log Server): On Security Management Server: [Expert@HostName]# cpstart On Multi-Domain Security Management Server: [Expert@HostName]# mdsstart_customer Domain_Name If the issue is not resolved, then delete the current log pointers and rebuild them: Close all SmartConsole windows (SmartDashboard, SmartView Tracker, SmartView Monitor, etc.). Stop Check Point services on the machine to which you connect with SmartView Tracker (Management Server / Log Server): On Security Management Server: [Expert@HostName]# cpstop On Multi-Domain Security Management Server: [Expert@HostName]# mdsstop_customer Domain_Name Backup/move the current log pointer files: On Security Management Server: [Expert@HostName]# mkdir $FWDIR/log/Log_Pointers_BKP [Expert@HostName]# mv $FWDIR/log/fw.logLuuidDB  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.logaccount_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.loginitial_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.logptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.logtrack  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtlog.cnt  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtlogaccount_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtloginitial_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtlogptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.vlogaccount_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.vloginitial_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.vlogptr  $FWDIR/log/Log_Pointers_BKP/ On Multi-Domain Security Management Server: [Expert@HostName]# mdsenv Domain_Name [Expert@HostName]# mkdir $FWDIR/log/Log_Pointers_BKP [Expert@HostName]# mv $FWDIR/log/fw.logLuuidDB  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.logaccount_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.loginitial_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.logptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.logtrack  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtlog.cnt  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtlogaccount_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtloginitial_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.adtlogptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.vlogaccount_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.vloginitial_ptr  $FWDIR/log/Log_Pointers_BKP/ [Expert@HostName]# mv $FWDIR/log/fw.vlogptr  $FWDIR/log/Log_Pointers_BKP/ Rebuild the current log pointer files: On Security Management Server: [Expert@HostName]# fw repairlog fw.log [Expert@HostName]# fw repairlog fw.adtlog [Expert@HostName]# fw repairlog fw.vlog On Multi-Domain Security Management Server: [Expert@HostName]# mdsenv Domain_Name [Expert@HostName]# fw repairlog fw.log [Expert@HostName]# fw repairlog fw.adtlog [Expert@HostName]# fw repairlog fw.vlog Start Check Point services on the machine to which you connect with SmartView Tracker (Management Server / Log Server): On Security Management Server: [Expert@HostName]# cpstart On Multi-Domain Security Management Server: [Expert@HostName]# mdsstart_customer Domain_Name If the issue is not resolved, then contact Check Point Support for assistance.