Thread Info
  • State Not Answered
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 7 subscribers
  • Views 17606 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

SafeGuard shutting down computer

slewis

Hello,

I am using SafeGuard 5.50.8.13 on Windows 7 Professional. I logged into SafeGuard successfully, pressed Ctr+Alt+Del and then OK to get to my Windows desktop, which displayed sucessfully, but then Windows just started shutting down. I had to start the machine up again and when I did it said I was locked out of SafeGuard and had to Challenge/Response with HelpDesk to get back in. This is the second time in 2 weeks I've had to do this.

My system log shows the following: The process C:\Program Files (x86)\Sophos\SafeGuard Enterprise\Client\SGNAuthServicen.exe (mycomputername) has initiated the shutdown of computer mycomputername on behalf of user NT AUTHORITY\SYSTEM for the following reason: Legacy API shutdown Reason Code: 0x80070000 Shutdown Type: shutdown Comment: SessionManager::LCCorruptedReceived LC was corrupted.

Can anyone give me any insight into what may be causing this and how to stop this from happening?

Thanks,

   slewis

:36535


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

    Hi slewis,

    a corruption of the SafeGuard Local Cache can occur if the Local Cache directory itself is being modified either manually or automatically. We recommend to exclude the SafeGuard Local Cache directory from Indexing, Backup and Anti-Virus applications.

    For details, please see Knowledge Base Article “108531 - SafeGuard Enterprise: Considerations when installing with other applications”

    The Challenge/Response that is required after a LocalCache corruption occured is optional and can be enabled/disabled via a policy in the SafeGuard Management Center (General Settings policy | Logon Recovery | Activate logon recovery after Windows LocalCache corruption - Yes / No)

    Regards,

    ChrisD

    :36543
Reply
  • 0

    Hi slewis,

    a corruption of the SafeGuard Local Cache can occur if the Local Cache directory itself is being modified either manually or automatically. We recommend to exclude the SafeGuard Local Cache directory from Indexing, Backup and Anti-Virus applications.

    For details, please see Knowledge Base Article “108531 - SafeGuard Enterprise: Considerations when installing with other applications”

    The Challenge/Response that is required after a LocalCache corruption occured is optional and can be enabled/disabled via a policy in the SafeGuard Management Center (General Settings policy | Logon Recovery | Activate logon recovery after Windows LocalCache corruption - Yes / No)

    Regards,

    ChrisD

    :36543
Children
No Data
Unfiltered HTML