Help → Error: Compatible version of POPFile not found !

Error: Compatible version of POPFile not found !

HELP!

I cannot launch POPFile, I get the message:

title : "Run POPfile (enchanced)"
Message: "Error: Compatible version of POPFile not found !"

I'm trying to run a May/10/2008 version of popfile.

What should I do?
I've tried a reboot, no help.

I don't know if this will help,
but below is the ouput from the Database Status Check:

------------------------------------------------------------
POPFile SQLite Database Status Check (integrated) v0.1.8
------------------------------------------------------------

Current user  : Mark
Current folder: C:\Program Files\POPFile
Command line  : /REGISTRY

Trying to find database using registry data (HKCU)... found it!

POPFile database found (C:\Users\Mark\AppData\Roaming\POPFile\popfile.db)

SQLite v2.8.17 utility found in C:\Program Files\POPFile

Database is in SQLite 2.x format, uses schema version 3 and its size is 13,625 KB

Result of running the 'pragma integrity_check;' command:
ok

The POPFile database has passed the SQLite integrity check!

------------------------------------------------------------
(report finished 06-Jun-2008 @ 11:08:40)
------------------------------------------------------------

Thanks in advance,
Mark

P.S. I am a software developer, albeit with close to zero experience in Perl. My point is that I'm comfortable with pretty technical responses.

  • Message #182

    The POPFile installer creates some registry entries and some environment variables (a mixture of system-wide and user-specific entries is used). The "Run POPFile" shortcuts created by the installer use a small program to read these registry entries and environment variables before trying to start POPFile.

    The "Error: Compatible version of POPFile not found !" message means that the small program (runpopfile.exe) was unable to determine the appropriate data to be used so it did not try to start POPFile.

    The database status report shows that your user data is stored in "C:\Users\Mark\AppData\Roaming\POPFile" and that the POPFile program is stored in "C:\Program Files\POPFile". You should be able to confirm this by using the Start Menu:

    Start -- All Programs -- POPFile -- Support -- PFI Diagnostic utility (simple)

    The easiest way to fix this problem is to run the "Add POPFile User" wizard

    C:\Program Files\POPFile\adduser.exe

    and make sure the "Choose POPFile Data Location for 'Mark'" page is set to use the folder "C:\Users\Mark\AppData\Roaming\POPFile". This will reset the registry data and environment variables to the correct values for the user 'Mark'.

    When the wizard gets to the email stuff just click the "Skip All" button to bypass all of the email pages. Once the wizard finishes you should be able to start POPFile.

    Brian

    • Message #183

      Hi Brian,

      Thank you for the quick response.
      I did as you said, however it didn't help.

      C:\Program Files\POPFile\adduser.exe

      and make sure the "Choose POPFile Data Location for 'Mark'" page is set to use the folder "C:\Users\Mark\AppData\Roaming\POPFile". This will reset the registry data and environment variables to the correct values for the user 'Mark'.

      While AddUser?.exe was still running, I received this message:

      ---------------------------
      Add POPFile User v0.4.3
      ---------------------------
      An error occurred when the installer tried to start POPFile.  
      Please use 'Start -> Programs -> POPFile -> Run POPFile' now.  
      Click 'OK' once POPFile has been started.
      ---------------------------
      OK   
      ---------------------------
      

      Then the installer (adduser) tried to bring up http://localhost:8080/buckets
      which resulted in "Internet Explorer cannot display the webpage"
      I then tried to launch PopFile? via it's shortcut, and received the same error message that I reported earlier today.

      FYI: I've been using the newer version of PopFile? for several weeks. I first saw this error this morning when I was trying to relaunch PopFile? after a popfile shutdown. I've been finding that PopFile? seems to require shutdown/relaunches on a regular basis, especially when I'm getting heavy spam. Regular spam levels for me are 2000 messages a day, heavy can be 6000 a day.

      TIA,
      Mark

      • Message #184

        While AddUser.exe was still running, I received this message

        I think you are the first user to report seeing that message. I had to look at the code to see what makes it appear :-)

        The installer creates some debugging shortcuts that might help me work out what's going wrong if you post the results here:

        Start -- All Programs -- POPFile -- Support -- PFI Diagnostic utility (full)

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

        Which OS are you using?

        Brian

        • Message #185

          While AddUser.exe was still running, I received this message


          I think you are the first user to report seeing that message. I had to look at the code to see what makes it appear :-)

          The installer creates some debugging shortcuts that might help me work out what's going wrong if you post the results here:

          Start -- All Programs -- POPFile -- Support -- PFI Diagnostic utility (full)

          ------------------------------------------------------------
          POPFile PFI Diagnostic Utility v0.1.11 (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  = Mark (User)
          
          IsNT return code  = 1
          Internet Explorer = 7.0
          
          ------------------------------------------------------------
          Location used to store temporary files
          ------------------------------------------------------------
          
          $TEMP folder path = < C:\Users\Mark\AppData\Local\Temp >
          
          ------------------------------------------------------------
          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 = 3
          POPFile shortcuts = 0
          
          CU: $SMPROGRAMS   = < C:\Users\Mark\AppData\Roaming\Microsoft\Windows\Start Menu\Programs >
          CU: $SMSTARTUP    = < C:\Users\Mark\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\POPFile >
          Shortcut target   = < C:\Program Files\POPFile\runpopfile.exe >
          Shortcut argument = < /startup >
          Target status     = found
          
          *.lnk files found = 1
          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 = < 0 >
          
          HKLM: MRI Version = < 1.0.1 >
          
          HKLM: NewParser   = ><
          
          HKLM: InstallPath = < C:\Program Files\POPFile >
          HKLM: RootDir_LFN = < C:\Program Files\POPFile >
          HKLM: RootDir_SFN = < C:\PROGRA~1\POPFile >
          
          HKCU: Data Owner  = < Mark >
          HKCU: MRI Version = < 1.0.1 >
          HKCU: RootDir_LFN = < C:\Program Files\POPFile >
          HKCU: RootDir_SFN = < C:\PROGRA~1\POPFile >
          
          HKCU: UserDir_LFN = < C:\Users\Mark\AppData\Roaming\POPFile >
          HKCU: UserDir_SFN = < C:\Users\Mark\AppData\Roaming\POPFile >
          
          HKCU: popfile.pl  = found
          HKCU: popfile.cfg = found
          
          ------------------------------------------------------------
          POPFile Environment Variables
          ------------------------------------------------------------
          
          'POPFILE_ROOT'    = < C:\PROGRA~1\POPFile >
          'POPFILE_USER'    = < C:\Users\Mark\AppData\Roaming\POPFile >
          
          Env: popfile.pl   = found
          Env: popfile.cfg  = found
          
          'ITAIJIDICTPATH'  = ><   (this is OK)
          'KANWADICTPATH'   = ><   (this is OK)
          
          'MECABRC'         = ><   (this is OK)
          
          ------------------------------------------------------------
          (report created 06-Jun-2008 @ 13:48:56)
          ------------------------------------------------------------
          
          


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

          Failed to run,

          ---------------------------
          Run POPFile (enhanced)
          ---------------------------
          Error: Compatible version of POPFile not found !
          ---------------------------
          OK   
          ---------------------------
          


          Which OS are you using?

          Vista Ultimate

          We could _try_ a gotomeeting, https://www2.gotomeeting.com/join/846480876
          This account is used for tech support, so we could be bumped at any moment.
          I'm near my machine, but not at it today, so if you join, try to make some noise ;-)

          Mark

          • Message #186

            The diagnostic report does not show any unexpected data; it looks OK to me.

            I'd forgotten that the "Message Capture utility" shortcut relied upon the runpopfile.exe program. Sorry about that!

            As you are using Vista you can simply run the Message Capture utility directly:

            C:\Program Files\POPFile\msgcapture.exe

            The utility should display something like this before it tries to start POPFile:

            ------------------------------------------------------------
            POPFile Message Capture Utility v0.1.8
            ------------------------------------------------------------
            POPFILE_ROOT = C:\PROGRA~1\POPFile
            POPFILE_USER = C:\Users\Mark\AppData\Roaming\POPFile
            

            The next line in the report will mention either popfileif.exe or popfilef.exe, depending upon whether or not you use POPFile's system tray icon.

            I think there are only three reasons why runpopfile.exe displays that error message:

            (1) it could not read the HKCU RootDir_LFN entry for POPFile
            (2) it could not read the HKLM RootDir_LFN entry for POPFile
            (3) it could not find popfile.exe in the folder specified in the registry

            Given that the diagnostic utility was able to handle (1) and (2) without any trouble, could you check that the following five programs still exist in the C:\Program Files\POPFile folder:

            popfile.exe
            popfileb.exe
            popfilef.exe
            popfileib.exe
            popfileif.exe

            Brian

            • Message #187

              Hi Brian,

              I think we just found something significant....

              ------------------------------------------------------------
              POPFile Message Capture Utility v0.1.8
              ------------------------------------------------------------
              POPFILE_ROOT = C:\PROGRA~1\POPFile
              POPFILE_USER = C:\Users\Mark\AppData\Roaming\POPFile
              
              Fatal error: cannot find POPFile program
              
              (C:\PROGRA~1\POPFile\popfilef.exe does not exist)
              
              C:\Program Files\POPFile>dir p*.exe
              <redacted>
              Directory of C:\Program Files\POPFile
              
              07/31/2007  03:35 PM            45,137 perl.exe
              05/10/2008  11:14 AM            79,968 pfidbstatus.exe
              05/10/2008  11:14 AM            67,258 pfidiag.exe
              04/18/2008  05:40 PM           122,965 popfile-service.exe
              04/18/2008  05:41 PM           155,735 popfileib.exe
              04/18/2008  05:41 PM           155,735 popfileif.exe
                             6 File(s)        626,798 bytes
                             0 Dir(s)   9,899,151,360 bytes free
              
              C:\Program Files\POPFile>
              

              So, why am I suddenly missing some .EXE's?

              What should I do next? Just re-install over my existing Popfile?

              FYI: I did recently turn off system tray support, hoping that would enhance stability. But I'm pretty sure that I had restarted a few times with that setting.

              P.S. That gotomeeting link is still active.

              Thanks again,
              Mark

              • Message #188

                The problem is solved.

                It turns out that AVG decided that Popfile was a threat and moved some of the .EXEs to it's vault.
                Brian helped me work around that problem.
                Later an AVG update corrected the false positive.

                THANK YOU SO MUCH BRIAN

                • Message #216

                  I received this error too, at startup, but all the files were present and the diagnostics ran normally. Oddly, if I ran runpopfile.exe after the startup was done, it worked fine.

                  My problem was the use of SUBST drives (e.g., P:\=C:\Program Files). At startup, I create the SUBST drives, but the user startup program menu items run before the "All Users" program menu items, so POPFile ran before the SUBST batch commands. Generally SUBST drives should be avoided, because Windows doesn't handle them truly transparently, but I have so much legacy stuff that expects different drives that I just make it work. Probably, the registry somewhere points to P:\POPFile instead of C:\Program Files\POPFile and that is the cause. I fixed it the lazy way, by running POPFile as part of my Eudora startup instead of Windows startup.

                  I must agree that the error message is not that informative, but with a good web site and open code, I was able to figure it out. That cannot be said for most programs that generate error messages.

                  • Message #217

                    My problem was the use of SUBST drives (e.g., P:\=C:\Program Files) ... Probably, the registry somewhere points to P:\POPFile

                    Yes, this is what caused the cryptic error message (the registry and/or an environment variable supplied an invalid path for POPFile's program or data folders).

                    I must admit I had not considered the case where the referenced drive is not available. It looks as though the new code should check if the drive is available instead of just complaining that it cannot find the file.

                    All I've done so far is update the diagnostic utility to check that the popfile*.exe files are all present (ticket:56). There are some big changes coming in the 1.1.0 release so I may not get around to improving that cryptic error message in time.

                    Brian