Help → help! PopFile? won't start

help! PopFile? won't start

Windows 7, Outlook 2016 (part of office 365).
Yesterday PopFile? was running fine.
Today it won't start
- after runpopfile, nothing shows up in Task manager
- I reinstalled a fresh 1.1.3 (didn't uninstall before that as I was afraid to lose my database), no effect
- edited popfile.cfg, set logger_level 2: no popfile.log gets written
- ran pfidiag /full, everything seems to be ok (let me know if I should paste it below).

Guess I'll have to reconfigure outlook to receive without popmail, but I've been using it for spam protection for 5-6 years now and can't live without it!

  • Message #2117

    I read http://getpopfile.org/discussion/1/530 and ran manually popfileb.
    - this works: it filters email, and the html UI is available
    - but it doesn't show a try icon
    - I also tried popfileif, popfilei (don't work), and popfileib (works but leaves a console window around)
    - a log file is written (grew to 26Mb within minutes)

    I checked the problem described in the above-quoted discussion. I don't have that problem: "set popfile" shows proper short-file-name paths, and these show the appropriate dir content:

    dir %POPFILE_ROOT%
    dir %POPFILE_USER%

    Is popfileib the most appropriate file to start?
    Can I recover the try icon somehow?
    Thanks for your help!

  • Message #2118

    It sounds like POPFile is shutting down (or crashing) as soon as it tries to start. The easiest way to check if this is happening is to run the Message Capture utility. This will display some information in a scrollable window and then start POPFile using a mode that displays some startup messages which are normally hidden. This window will stay open after POPFile shuts down or crashes - this will let you copy and paste the report into a reply. The installer creates a Start Menu shortcut for this utility:

    Start -- All Programs -- POPFile -- Support -- Message Capture utility


    - ran pfidiag /full, everything seems to be ok (let me know if I should paste it below).

    This might be useful as the report includes the locations used by your installation and this information will make it easier to provide detailed advice.

    • Message #2120

      popfileb (which I started manually) has crashed.

      Output of Message Capture utility

      ------------------------------------------------------------
      POPFile Message Capture Utility v0.2.0
      ------------------------------------------------------------
      POPFILE_ROOT   = C:\PROGRA~2\POPFile
      POPFILE_USER   = C:\Users\VLADIM~1.ALE\AppData\Roaming\PopFile
      Using 'popfileif.exe' to run POPFile
      ------------------------------------------------------------
      (report started 14-Feb-2016 @ 17:04:58)
      ------------------------------------------------------------
      Can't call method "parameter" without a package or object reference at C:\PROGRA~2\POPFile/POPFile/Module.pm line 453.
      Compilation failed in require at C:\PROGRA~2\POPFile/POPFile/History.pm line 35.
      Can't call method "parameter" without a package or object reference at C:\PROGRA~2\POPFile/POPFile/Module.pm line 453.
      Can't call method "parameter" without a package or object reference at C:\PROGRA~2\POPFile/POPFile/Module.pm line 453.
      BEGIN failed--compilation aborted at C:\PROGRA~2\POPFile/POPFile/History.pm line 35.
      Can't call method "parameter" without a package or object reference at C:\PROGRA~2\POPFile/POPFile/Module.pm line 453.
      Compilation failed in require at C:\PROGRA~2\POPFile/POPFile/Loader.pm line 484.
      Can't call method "parameter" without a package or object reference at C:\PROGRA~2\POPFile/POPFile/Module.pm line 453.
      
      POPFile Engine loading
      
          Loading... 
               {core: windows}
               {core: config
      
      ------------------------------------------------------------
      Status code: 2
      ------------------------------------------------------------
      (report finished 14-Feb-2016 @ 17:04:59)
      ------------------------------------------------------------
      

      Output of pfdiag:

      ------------------------------------------------------------
      POPFile PFI Diagnostic Utility v0.3.0 (full mode)
      ------------------------------------------------------------
      String data report format (not used for numeric data)
      
      string not found              :  ><
      empty string found            :  <  >
      string with 'xyz' value found :  < xyz >
      ------------------------------------------------------------
      
      Current UserName  = vladimir.alexiev (Admin)
      
      Operating System  = Windows 7 Professional (64-bit)
      IsNT return code  = 1
      Internet Explorer = 8.0
      
      ------------------------------------------------------------
      Location used to store temporary files
      ------------------------------------------------------------
      
      $TEMP folder path = < c:\tmp >
      
      ------------------------------------------------------------
      Start Menu Locations
      ------------------------------------------------------------
      
      AU: $SMPROGRAMS   = < C:\ProgramData\Microsoft\Windows\Start Menu\Programs >
      AU: $SMSTARTUP    = < C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup >
      
      Search results for the "AU: $SMSTARTUP" folder:
      
      *.lnk files found = 0
      POPFile shortcuts = 0
      
      CU: $SMPROGRAMS   = < C:\Users\vladimir.alexiev\AppData\Roaming\Microsoft\Windows\Start Menu\Programs >
      CU: $SMSTARTUP    = < C:\Users\vladimir.alexiev\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup >
      
      Search results for the "CU: $SMSTARTUP" folder:
      
      Shortcut name     = < Run POPFile.lnk >
      Shortcut start in = < C:\Program Files (x86)\POPFile >
      Shortcut target   = < C:\Program Files (x86)\POPFile\runpopfile.exe >
      Shortcut argument = < /startup >
      Target status     = found
      
      *.lnk files found = 6
      POPFile shortcuts = 1
      
      ------------------------------------------------------------
      Obsolete/testbed Registry Entries
      ------------------------------------------------------------
      
      [1] Pre-0.21 Data:
      
      Pre-0.21 POPFile  = ><
      Pre-0.21 Testbed  = ><
      
      [2] 0.21 Test Installer Data:
      
      HKLM: RootDir_LFN = ><
      HKLM: RootDir_SFN = ><
      
      HKCU: RootDir_LFN = ><
      HKCU: RootDir_SFN = ><
      HKCU: UserDir_LFN = ><
      HKCU: UserDir_SFN = ><
      
      [3] Current PFI Testbed Data:
      
      MRI PFI Testbed   = ><
      MRI PFI Testdata  = ><
      
      ------------------------------------------------------------
      POPFile Registry Data
      ------------------------------------------------------------
      
      NTFS SFN Disabled = < 2 >
      
      HKLM: MRI Version = < 1.1.3 >
      
      HKLM: NewParser   = ><
      
      HKLM: InstallPath = < C:\Program Files (x86)\POPFile >
      HKLM: RootDir_LFN = < C:\Program Files (x86)\POPFile >
      HKLM: RootDir_SFN = < C:\PROGRA~2\POPFile >
      
      HKLM: *.exe count = 6 (this is OK)
      
      HKCU: Data Owner  = < vladimir.alexiev >
      HKCU: MRI Version = < 1.1.3 >
      HKCU: RootDir_LFN = < C:\Program Files (x86)\POPFile >
      HKCU: RootDir_SFN = < C:\PROGRA~2\POPFile >
      
      HKCU: UserDir_LFN = < C:\Users\vladimir.alexiev\AppData\Roaming\POPFile >
      HKCU: UserDir_SFN = < C:\Users\VLADIM~1.ALE\AppData\Roaming\PopFile >
      
      HKCU: popfile.pl  = found
      HKCU: popfile.cfg = found
      
      HKCU: *.exe count = 6 (this is OK)
      
      ------------------------------------------------------------
      POPFile Logger Settings
      ------------------------------------------------------------
      
      Logger output     = < 1 > (To File)
      Logger format     = < default >
      Logger level      = < 2 >
      Logger directory  = < ./ > (C:\Users\vladimir.alexiev\AppData\Roaming\POPFile)
      
      ------------------------------------------------------------
      POPFile Environment Variables
      ------------------------------------------------------------
      
      'POPFILE_ROOT'    = < C:\PROGRA~2\POPFile >
      'POPFILE_USER'    = < C:\Users\VLADIM~1.ALE\AppData\Roaming\PopFile >
      
      Env: popfile.pl   = found
      Env: popfile.cfg  = found
      
      ROOT: *.exe count = 6 (this is OK)
      
      'ITAIJIDICTPATH'  = ><   (this is OK)
      'KANWADICTPATH'   = ><   (this is OK)
      
      'MECABRC'         = ><   (this is OK)
      
      ------------------------------------------------------------
      POPFile Configuration Settings (subset)
      ------------------------------------------------------------
      
      POPFile UI port   = < 8081 >
      POP3 Listen port  = < 110 >
      Concurrent POP3   = < 0 >
      
      ------------------------------------------------------------
      (report created 13-Feb-2016 @ 16:00:49)
      ------------------------------------------------------------
      

      I restarted popfileb and can get mail (but it may crash again). Message Capture still tries to run popfileib, doesn't use the existing process instance.

      Thanks for your help!!

      • Message #2126

        I've just found that runpopfile doesn't seem to work any more on my Windows 10. When I run it, what looks like a CMD window appears for a fraction of a second and disappears. I can run popfileib and the Message Capture Window starts without error.

        Windows 10 did some sort of significant upgrade this morning, which has tweaked a few elements of the Windows UI for me, so I wonder if this is related...

        • Message #2127

          I now start popfileb (put a shortcut in AppData?\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\). It's worked for a month with no problem

          • Message #2128

            That's how I'm starting it too, but I was just wondering why it's failed. I thought it might be related to the problems when first installing Win10, but the environment variables are present and correct. I could try reinstalling again, I suppose...