Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 10063 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can not schedule a scan

ASRV

I have SAV all setup and when I try to schedule a scan I get this error - "Incorrect password or the password does not adhere to security policy"  I have created a SAV Admin account  just for scanning and have logged in with this account, so I know the passowrd is correct.  I have uninstalled and reinstalled but still have the same issue.  This is on windows 7 home.  Not sure what else to try.

:52006


This thread was automatically locked due to age.
Parents
  • 0

    The user is a admin, and I logged in with this user, installed SAV and had it update.  It would not create the scheduled task in task manager, BUT would start is I told it to start. 

    I did not change any rights for this user ie:  Logon as a batch job right (or has an explicit Deny) either.

    I managed to get this to work, with another uninstall and clean-up ( of Sophos)  and a reinstall using the same user and password.

    I have to wonder if the tamper protection had anything to do with this.  I usually setup the san last after enabeling tamper protection.  This time I setup the scan first then the last thing I did was tamper protection.

    I have ran into this error several times, and have not been able to figure out how to not run into it. 

    :52096
Reply
  • 0

    The user is a admin, and I logged in with this user, installed SAV and had it update.  It would not create the scheduled task in task manager, BUT would start is I told it to start. 

    I did not change any rights for this user ie:  Logon as a batch job right (or has an explicit Deny) either.

    I managed to get this to work, with another uninstall and clean-up ( of Sophos)  and a reinstall using the same user and password.

    I have to wonder if the tamper protection had anything to do with this.  I usually setup the san last after enabeling tamper protection.  This time I setup the scan first then the last thing I did was tamper protection.

    I have ran into this error several times, and have not been able to figure out how to not run into it. 

    :52096
Children
No Data