[THIN] Re: Event log stops logging and a while later the server is not able to be logged into PS 4.0 W2K3
- From: Adam Thompson <adwulf@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Fri, 28 Jun 2013 11:22:44 +0100
I've had this on Server 2003 with PS4/4.5. It happens when the system log
get spammed with event ID 333. Eventually, the server hangs and the log
gets corrupted.
Installing KB970054 helps prevent the eventlog spamming/corruption, but
does not resolve the server hang. Analysis of an NMI hangdump does not show
pool depletion.
I found that clearing up user profiles has helped. Also - UPHClean v2 (if
you're not too fussy about it being described as beta software).
On 26 June 2013 13:10, Raffensberger, Stephen D <sraffens@xxxxxxxxxxx>wrote:
> Not the same but similar. Event logs keep going corrupt. Then, the
> server becomes non-functional.
>
> Excluding .EVT files from virus checking helped but it still happens
> occasionally.
>
>
>
> [image: Logo Produban]
>
> *Steve Raffensberger***
>
> Citrix Administrator
>
> Produban US
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Dean Cunningham
> *Sent:* Wednesday, June 26, 2013 12:53 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Event log stops logging and a while later the server is
> not able to be logged into PS 4.0 W2K3
>
>
>
> I have a weird one:
>
>
>
> Citrix Presentation Server 4.0
>
> Window Server 2003 Enterprise Edition, Physical Address Extension 8GB RAM
>
>
>
> Two of the server farm (all at hotfix level PSE400W2K3R06) have
> occasional events where "all" the logs in the event viewer stop logging
> items and hours or days later the server stops accepting requests and
> "grinds" to a halt (console is non responsive, new sessions (via RDC) hang
> before the login prompt. )
>
>
>
> The result is the server has to be powered off
>
>
>
> Does this jog anyones memory?
>
>
>
> And no, upgrading citrix is not an option and yes, I know it is going off
> support :)
>
>
>
> cheers
>
> Dean
> This message contains information which may be confidential and
> privileged. Unless you are the addressee (or authorized to receive for the
> addressee), you may not use, copy or disclose to anyone the message or any
> information contained in the message. If you have received the message in
> error, please advise the sender by reply e-mail, and delete or destroy the
> message. Thank you.
>
--
AdamT
Novus Ordo Mundi
Other related posts:
