LSASS.exe terminated unexpectedly with status code 1073741819
From: opti_mystic (opti_mystic_69_at_NOSPAMyahoo.com)
Date: 05/10/03
- Next message: jim camel: "help"
- Previous message: Matt Foster: "Re: Limiting access to Windows Explorer"
- In reply to: Adrian: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Next in thread: Adrian: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Reply: Adrian: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 10 May 2003 12:58:52 -0700
Adrian,
Have you tried the Symantec support site? Issues related
to Ghost are not supported by Microsoft.
It is precisely for these types of issues that Microsoft
supports installation and distribution of software via SMS
with .msi packages, not Ghost. Have you tried SMS?
Opti_mystic
>-----Original Message-----
>We just sent out a Symantec Ghost v7.0 AI (autoinstall)
>package executable (via email) to update Word templates
>for our users and now have 6 staff with unusable
>machines. After running the package the machines started
>to experience problems and had to be rebooted. On
>restarting, each user saw a window pop up at logon
>saying 'System Shutdown', 'The system process
>c:\winnt\system32\lsass.exe terminated unexpectedly with
>status code: 1073741819. The system will now shutdown
and
>restart'. Unfortunately, this happens every time at
>logon, meaning it's now impossible to logon with the
>machines stuck in this restart loop.
>
>All attempts to fix this have failed. Uninstalling the
>package did not work. Conducting a repair via the W2K CD
>failed.
>
>SP3 looks to be the best bet as there are a number of
>LSASS.exe related fixes included. Unfortunately, every
>time we try to run it we get a problem during the
>inspecting your environment stage because files are
>supposedly in use (e.g. iuengine.dll or samsrv.dll) and
>cannot proceed with the update. We were installing the
>update whilst in safe mode so surprised to see that these
>key files were in use.
>
>Any help at all that anyone can provide on this would be
>very gratefully received as our only other option would
be
>to rebuild said machines, with possible loss of developer
>code on some.
>
>Yours hopefully,
>
>Adrian.
>
>PS. The machines are all W2K Pro boxes running SP2. The
>package was tested prior to deployment, but obviously not
>enough!
>.
>
- Next message: jim camel: "help"
- Previous message: Matt Foster: "Re: Limiting access to Windows Explorer"
- In reply to: Adrian: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Next in thread: Adrian: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Reply: Adrian: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
