Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 38 replies
  • Subscribers 3 subscribers
  • Views 67693 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

A Windows API call returned error 1909 [0x00000070]

KAR AAR

 Hi Experts :) ,

 

I am facing an issue with the following ESC. We have Windows 7 and 10 OS installed in our environment. Below is the error I am getting.

Actually the Update is failing with the below error, and sometimes it updates successfully but next moment if I check it says Failed and the reason shows account locked. Whereas I've also checked the account in local machines its not locked. 

Would highly appreciative if I get quick response and support in solving this issue.

 

Please find error attached.

 

Thanks

Best Regards

Faisal



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

    Hello Faisal,

    this is strange as the accounts mentioned are apparently the local SophosSAU accounts created by the installer (with User cannot change password and Password never expires set). Does this affect all endpoints and when did this start?

    the account in local machines its not locked
    As only AutoUpdate uses this account and should "know" the correct password I can't see why the lockout should occur in the first place. The lockout time is set with the Account Security Policy (minimum one minute) so they might get unlocked automatically.
    AFAIK AutoUpdate nevertheless tries to make the connection and updates should succeed if there is no other issue. Are the endpoints shown as up to date in the Console? 

    Christian

  • 0 in reply to QC

    Hello QC,

     

    This is not affecting all users at same time but its affecting most of the users timely. The account gets locked out itself and throws an error. With some users its working fine with the default installer created.

    This is strange why the account works sometimes and then gets locked itself. Is there any policy modification required through GPO ?

     

    Regards

    Faisal

Reply
  • 0 in reply to QC

    Hello QC,

     

    This is not affecting all users at same time but its affecting most of the users timely. The account gets locked out itself and throws an error. With some users its working fine with the default installer created.

    This is strange why the account works sometimes and then gets locked itself. Is there any policy modification required through GPO ?

     

    Regards

    Faisal

Children
No Data
Unfiltered HTML