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 PortProtector Error at Logoff

A number of our users are experiencing the following error at logoff.

The top of the box says 'SProtector.exe' - The message says 'The (?) at 0x0012a7c0 referenced the memory at 0x0000000. The memory could not be "written".

Our environment is:

OS - WinXP SP2
SafeGuard Enterprise client 5.40.0.152
SafeGuard Port Protector client 5.40
SafeGuard Client Configuration 5.40

This is happening only occassionally on a couple of machines and is more or an annoyance than a problem. Anyone out there have any ideas?

Cheers

Matt

This thread was automatically locked due to age.

Parents

0 DSchwartzberg over 15 years ago

Hello again Matt!
While there is a SafeGuard PortProtector, so you mean SGN Configuration Protection (CP)? While they do the same things, they are designed differently.
If you mean SGN CP, can you enable a trace file and try to cause the error to occur again? If you are not sure how to enable a trace file, click here -> here.
When receiving error messages that reference memory space which is 0x0000000, it would be my suggestion to contact Sophos Support so the issue can be escalated for deeper analysis.
:1432
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 DSchwartzberg over 15 years ago

Hello again Matt!
While there is a SafeGuard PortProtector, so you mean SGN Configuration Protection (CP)? While they do the same things, they are designed differently.
If you mean SGN CP, can you enable a trace file and try to cause the error to occur again? If you are not sure how to enable a trace file, click here -> here.
When receiving error messages that reference memory space which is 0x0000000, it would be my suggestion to contact Sophos Support so the issue can be escalated for deeper analysis.
:1432
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data