Help → Upgrade problem (winXP)

Upgrade problem (winXP)

Hi - I just tried updating a windows install to 1.0 and popfile crashes soon after starting.

Nothing useful in log so looked at the cfg and discovered windows_console, so set to 1 to see messages but console vanishes too fast. Went into cmd window and ran popfilef from there and found message

install_driver(SQLite) failed: Can't locate DBD/SQLite.pm in @INC (@INC contains: C:\PROGRA~1\POPFile C:\Program Files\POPFile C:/Program Files/POPFile/lib .) at (eval 112) line 3.
Perhaps the DBD::SQLite perl module hasn't been fully installed.

p.s. Noticed odd mixture of / and \ in this message.

lib only contains SQLite2.pm

Uninstalled popfile and re-installed previous version (0.22.5) and still doesn't work.

Background details - I run a limited user account (no admin authority) for email but all install etc done on separate admin account. This has always worked ok in the past. No popfile files in local Application data area have been touched by the install/failed run except the logfile. I have a good backup of these but not the original contents of Program Files.

I will check against another similar system but in the meantime would appreciate assistance. Thanks.

renowden
04/19/08 14:02:15
Tree View Flat View (newer first) Flat View (older first)
  • Message #124

    Nothing useful in log so looked at the cfg and discovered windows_console, so set to 1 to see messages but console vanishes too fast.

    If POPFile crashes as soon as it tries to start then the easiest way to see the console messages is to use the special Start Menu shortcut created by the installer:

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

    Another diagnostic shortcut created by the installer is:

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

    This one reports on a lot of the things the installer is supposed to have done and performs some simple validity checks.

    POPFile 0.22.5 (or later) defaults to using SQLite2 instead of SQLite. Since you appear to have used the 1.0.0 installer to upgrade an existing 0.22.5 installation, POPFile's configuration file should be specifying SQLite2 (either because the existing 0.22.5 data was already set to this or because the 1.0.0 installer changed the setting from SQLite to SQLite2).

    Background details - I run a limited user account (no admin authority) for email but all install etc done on separate admin account. This has always worked ok in the past. No popfile files in local Application data area have been touched by the install/failed run except the logfile.

    The 1.0.0 installer should have updated some files in the User Data area for the limited user. Perhaps you selected the "wrong" User Data folder when upgrading to 1.0.0 (or, more likely, did not notice that the installer had defaulted to the "wrong" User Data folder).

    If you use the limited user account to run the adduser.exe program found in the POPFile program folder you can make POPFile 1.0.0 use the correct User Data folder. If you check the timestamps in that folder after running adduser.exe you should find some changes there (e.g. adduser.exe always re-writes the pfi-run.bat file).

    For a quick confirmation, check that the correct User Data folder is listed when you use this shortcut:

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

    brian
    04/19/08 17:18:56
    • Message #125

      Thank you very much Brian. I think I may have misled you (and myself). This is my wife's laptop and I can't have updated it as recently as I thought. The key bit I had forgotten was adduser.exe which fixed everything just as you said it would. There is no opportunity during the main install to select an account it just assumes the current one and I always abort at that point. It was fortunate because I realised when I got to it that my own machine no longer had popfile or any email system installed on it so I had nothing to compare it against.

      I have recently switched my own work to Mac and have written a basic install script for OS X Leopard to make things easier but that is off topic for this post so I will create another one.

      renowden
      04/19/08 19:30:33
      • Message #126

        There is no opportunity during the main install to select an account it just assumes the current one and I always abort at that point.

        If you run the 1.0.0 installer from a limited user account it will configure POPFile for that limited user account, even though the installer asks for the administrator's password.

        The 1.0.0 installer uses the administrator's account to install the POPFile program and create some registry entries, etc but it will switch back to the current limited user's account to create the User Data and reconfigure the email client.

        adduser.exe is in fact the second part of the installer, the part that does all of the User Data stuff.

        Glad to hear you got things sorted out!

        brian
        04/19/08 20:39:16
        • Message #127

          Somehow I never expect a windows installer to do things right - but if there was one it had to be for a great product like this. Many thanks all round.

          renowden
          04/19/08 23:45:33
Tree View Flat View (newer first) Flat View (older first)