build487 service is not running

By blueadmin7 | January 21st, 2009 | 12:50 pm

I’ve been trying build build 486\487 on my Vista64 Home premium (partially vlited) , upgrading from builf 484.

Some how the eBoostr service refuse to start. Try to start manual via service but with no success.

I’m wondering if anyone experiencing similar symptom. In evenviewer I get:

“System Exception -529697949 in eBoostr Service.” – EventID 6

Does eboostr require specific service to be running in vista?

With build484, it was working rather seamlessly and it started to happen when I tried 486 and also with 487.

Any idea would be appreciated.

12 Responses to “build487 service is not running”

  1. Colonel ONeill
    Jan 21, 2009

    It happens to me on some installs, but I just reinstall over it, then it works.


  2. blueadmin7
    Jan 22, 2009

    Strange…
    I tried to install/re-install for about 10 times with no success. :(


  3. Ilya Elenik
    Jan 22, 2009

    Can you please look on adjacent eventlog records?
    Service should create memory dump in case of exception.


  4. blueadmin7
    Jan 22, 2009

  5. Ilya Elenik
    Jan 22, 2009

    blueadmin7, unfortunately something wrong with synchronization of dump and debug info, so I see only what there is some error in sqlite database. Please try to rename filestat.dat file, so eBoostr service will recreate it on startup. Also check free space on system disk. If it does not help please drop me a letter to [email removed], I will try to determinate what is happen.


  6. blueadmin7
    Jan 22, 2009

    Hi again,

    Appreciate the tip. I think I found something that may be a cause. I’ve been using the same settings.ini since build 484 and I have filestat.dat to be located here.

    ; eBoostr config file
    [eBoostr]
    maxfilesize=62914560
    showpartitions=1
    MinIdleValue=80
    StatPath=D:\Users <– causes fail to star
    —–
    StatPath=D:\ <– It works.

    It seems like the service refuse to run when it’s in pointed to Users directory, even though filestat.dat is created.

    However when I set it to just root “D:\” it works. Does filestat.dat need to be located in root, when it’s not on default location?


  7. Ilya Elenik
    Jan 22, 2009

    No, there is no such restriction.
    It works for me (XP) for any existent folder.
    May be the problem is in access rights for this location.


  8. blueadmin7
    Jan 22, 2009

    My testing tells me that eboostr doesn’t like the folder property to be altered.

    I haven’t changed any access rights on these folder except that I do change icons for important folders/directories.

    One thing is that even though I revert back to default icon, once the setting has been altered, the folder seems to cause problem for eboostr.

    Maybe it’s one of those strange Vista thing but a problematic things to be aware of I guess. At least now I know what was the cause. Thanks for the concern.


  9. Ilya Elenik
    Jan 22, 2009

    I have reproduced this behavior on Vista64 computer. For some reason SQL unable to use USERS as storage for temp files. I do not understand why it happen, but have inserted some additional checks, so this location should work at next build.


  10. blueadmin7
    Jan 22, 2009

    Great~, I’ll look forward for the next build and thanks for the research. Keep it up! :)


  11. Andrey Zarudnev
    Jan 23, 2009

    Here goes the new build that should fix your issue:
    http://www.eboostr.com/closedbeta/feedback/build-490/


  12. blueadmin7
    Jan 23, 2009

    Ah, thanks so much for follow up.
    Installed it today and it’s working flawless.
    Great job!:D