[THIN] Re: Stop 0x00000050 - FIXED (so far)
- From: "Pardee, Michael" <MPardee@xxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Mon, 7 Oct 2002 08:47:39 -0400
Thought I'd update the list on this one.
Doing research turned up Q262956, which looked like it could be our problem.
While getting ready to test it on our test wts box, one of our engineers
noticed that q267896, which we were testing to eliminate an issue with
Acrobat printing garbage characters, updates the same files, yet they were
nearly 1 year newer than the same files from the original hotfix. We used
the profile from our bad users and our test server crashed. We then applied
Q262956 on the server and tried logging in as the user again and everything
is working fine. We will run throughout the day like this and if all goes
well we will start to add this hotfix to all of our servers.
I hope none of you ever have to go through this. It is a sickening feeling
when server after server after server after (you get the idea) crashed and
you can't even get on them long enough to diagnose.
Hope this helps someone else out there. I'll let the list know how we are
doing with the hotfix later on as well.
-----Original Message-----
From: Pardee, Michael
Sent: Friday, October 04, 2002 11:40 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Stop 0x00000050
Hello list. Haven't had to bug you guys in a LONG time, but here it goes.
I have always known that the majority of the stop 0x00000050 errors were
printer drivers. We make it a policy to restrict the printer drivers that
are available for use on our systems because of this. The last couple of
days have been particularly bad with the 0x50 BSODs but the pattern is that
they only occur when a certain user logs on to the system. The fix is to
disable that user's account, wipe out their profile and then they can login
again. We are currently on the phone with MS about this and have sent them
the ntuser.dat from the user's registry from this instance.
I realize that I don't have enough of the error code after the 0x50 message
yet, and apologize for that, but we're trying to dig it up. This happens to
us randomly. We have gone months with no issues and then bam, 4,5,or more
servers crashing within minutes of each other and it's because the user
keeps trying to login and the load balancing keeps sending her to the next
available server, as it should. Makes for quite an interesting report to
senior management though.
We are running WTS 4.0 with SP6 and the browser hotfix. Our audits of the
servers do not turn up an "bad" printer drivers.
Any help is appreciated.
Thanks,
> Michael Pardee
Mailto:mpardee@xxxxxxxx
**********************************************
This weeks sponsor 99Point9.com
99Point9 helps solve your unresolved technical
server-based questions, issues and incidents. http://www.99point9.com
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
**********************************************
This weeks sponsor 99Point9.com
99Point9 helps solve your unresolved technical
server-based questions, issues and incidents.
http://www.99point9.com
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
Other related posts:
- » [THIN] Re: Stop 0x00000050 - FIXED (so far)
