LSASS.exe terminated unexpectedly with status code 1073741819
From: Adrian (adrian.gardiner_at_ccsit.co.uk)
Date: 05/10/03
- Next message: ivan: "problem with deleting files"
- Previous message: jim camel: "help"
- In reply to: opti_mystic: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Next in thread: Opti_mystic: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Reply: Opti_mystic: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 10 May 2003 13:34:08 -0700
Thanks Opti_mystic for your reply and suggestion. My
preference would definitely be to go with something other
than Ghost but my boss decided otherwise (he's the MD!).
SMS would be No.1, closely followed by WinInstall of
which I have some experience. However, the problem that
I've encountered, although triggered by Ghost software,
looks to be down to a W2K bug that's fixed by SP3
(article Q306497), if only I could get SP3 to make its
way past the 'inspecting your environment phase!'. The
Symantec site is unfortunately, pretty useless.
Thanks again,
Adrian.
>-----Original Message-----
>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: ivan: "problem with deleting files"
- Previous message: jim camel: "help"
- In reply to: opti_mystic: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Next in thread: Opti_mystic: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Reply: Opti_mystic: "LSASS.exe terminated unexpectedly with status code 1073741819"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
