Re: Windows XP Service Pack 2 SAS Application Error

Steven,

Thank you for the reply, in answer to your questions below:
- All the users are just "regular" users, not domain admins, not local
admins, not power users.
- There is nothing else unusual in the event log at that time. The user is
authenticated and nothing else error or success is related in the application
or system event log.

Thanks for the tip on the possible free support call - you're right - never
hurts to try!

Mike

"Steven L Umbach" wrote:

Offhand I don't know what is happening but is this happening only on SP2
computers? Is the problem users group membership any different than the
users that are not having the problem.for either local computer groups or
domain groups? Are there any related events in the application or system
logs on the computer they are trying to logon to? You might be entitled to a
free support call from Microsoft if it is service pack related. It never
hurts to ask them. --- Steve



"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:242162B4-60A7-4116-985A-869C4EE0C0A7@xxxxxxxxxxxxxxxx
Hello,

We are having some trouble on Windows XP Service Pack 2. We are in the
process of updating all our computers from Windows XP Service Pack 1 to
Service Pack 2 with all the latest updates from Microsoft Update, etc.

When certain users attempt to login, they receive an error after they
enter
their login information. Per the security event log, they are
successfully
authenticated, and they are logged in, however, the following error is
displayed and they are locked at a blue screen - not a blue screen of
death -
the Windows XP blue color. At that point, they cannot log in to any
machine
we have. Other people can login to that machine. We removed all
instances
of any local and roaming profiles, however the problem occurs even before
the
loading of the profile starts. The error we receive is below:

SAS window: winlogon.exe - Application Error
The exception unknown software exception (0xc0000409) occurred in the
application at location 0x75979eca.

All of the computers are brand new fresh images. They all have antivirus
software on them and it is not virual related. It almost seems that
something happens to the users SID or some association with active
directory
that doesn't allow them to login anywhere.

Any help would be greatly appreciated as we are at a loss for what else to
try.

Thanks
Mike



.

Relevant Pages

  • Re: Connecting to SQL from a Windows Service
    ... There is probably some way to debug this, but that's deeper Windows knowledge than I can dredge up right now. ... I looked into the Event Log and found that when my service ... 1st Login succeeds. ... You can try turning on login auditing in SQL Server and then check the ...
    (microsoft.public.sqlserver.connect)
  • Windows XP Pro and GPO computer deployment of Office 2000 SBE OEM
    ... event log, however when a user logs in windows protection ... Files that are required for Windows to run properly must ... The computers are running XP Pro SP1 with the latest ...
    (microsoft.public.office.setup)
  • Windows XP Pro and GPO computer deployment of Office 2000 SBE OEM
    ... event log, however when a user logs in windows protection ... Files that are required for Windows to run properly must ... The computers are running XP Pro SP1 with the latest ...
    (microsoft.public.windowsxp.general)
  • Re: Windows XP Service Pack 2 SAS Application Error
    ... We are having some trouble on Windows XP Service Pack 2. ... process of updating all our computers from Windows XP Service Pack 1 to ... When certain users attempt to login, they receive an error after they ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Error 1005 & 1030
    ... > into the event log, i see the same error everytime someone log in his ... > On the 2k computers i have always the error 1000 with still UserEnv as ... > the windows patches up to date. ... there is nothing out of the ordinary added, such as Zone Alarm, (and other ...
    (microsoft.public.windows.server.dns)