Error Initialization. Check dcsuserprot.exe

Discussion in 'ProcessGuard' started by Stefan12, Nov 28, 2004.

Thread Status:
Not open for further replies.
  1. Stefan12

    Stefan12 Registered Member

    Joined:
    Nov 28, 2004
    Posts:
    4
    As "Administrator" on Win 2000 SP 4: Install of PG 3.050 on system that has not had earlier PG versions goes fine. A-ok.

    PG autostarts and runs under "Administrator" profile. Ok.

    However, under "User" profile, PG does not autostart. Manual PG start has long delay, then gives, "Error Initialization. Check dcsuserprot.exe".

    TaskManager looks ok: shows dcsuserprot.exe and pgaccount.exe, then also shows procguard.exe after manual start.

    Might be a Win 2000 security priviledges issue. However, the ProcessGuard directory and ProcessGuard\logs directory do both have read/write access.

    What're the fixes: for "User" autostart of PG? For allowing "User" to run PG?

    Thanks,

    Stefan
     
  2. nick s

    nick s Registered Member

    Joined:
    Nov 20, 2002
    Posts:
    1,430
  3. Paranoid2000

    Paranoid2000 Registered Member

    Joined:
    May 2, 2004
    Posts:
    2,839
    Location:
    North West, United Kingdom
    The PG3 UI can only be run under an Administrator user - from another account you can use Run As (as Administrator) to access the PG3 UI but it will give an error message about pgaccount.exe not running (see the Pgaccount.exe thread for details). This error message can however be ignored - PG should work fully.
     
  4. Stefan12

    Stefan12 Registered Member

    Joined:
    Nov 28, 2004
    Posts:
    4
    Thanks for the references and details, I'll give it another shot.

    Stefan
     
Thread Status:
Not open for further replies.