winlogon.exe error causes bluescreen after FR1/SP1to FR3/SP3 upgrade.. 1

[chjinmind]

Hi!

My servers are bluescreening after upgrading to SP3/FR3.
Setup is 2 XPa SP1/FR1 servers on w2k adv. server SP2.
Server 1 holds Datastore and is Data Collector.

Right now I'm trying toupgrade Server 2 first with no luck at all. Installation routine works fine, all is good, sever works fine after upgrade, checked with Management Console and even connecting with ICA client.
Licenses for FR3 are added to the farm.

Problem:
After reboot the server hangs at logon;
winlogon.exe, application error.
The exeption unknown software exception (oxc00000fd) occured in the application at location 0x67de1828.
OK or Cancel

Etither choice causes a bluescreen and server reboots and results in an endless bluescreening loop.

Safe mode without networking works, but no tries with recovery console or applying windows SP will fix this.
Tried to apply FR3 with all win SP but none works...
Funny thing is that server works in background, I can map drives, connect a mmc to the server even make ICA connections to the server, but at user credential point the error msg appears again...

Event log on failing server says nothing but logs the application popup, identical to the error msg.

Anyone seen this?

Adding a fresh server to the farm by installing MetaFrame with SP3/FR3 slipstreamed will not work, errormsg is, "no Server with FR3 detected".

Do I have to upgrade the DS machine first to make the farm a SP3/FR3 farm???

Can SP3/FR3 amke the winlogon.exe file make the server that corrupt?

Please any input would be very helpful!

 

[CitrixEngineer]

It's easy for me to say, but this should have been done on a test server first.

The server acting as the farm's Data Collector MUST be upgraded first, as per the MetaFrame XP Admin guide included with FR3 (Page 129).

I'm not sure if that will fix this problem, as I have never seen it before - but it may well do, as I believe there are updates to ctxgina.dll - the file that replaces msgina.dll (Microsoft Graphical Identification and Authentication), which is the graphical part of the login process. If there is a GINA related problem, then the sort of issue you are seeing is a common symptom.

I hope this helps




CitrixEngineer@yahoo.co.uk

 

[lengoo]

Hi Chjcomit
I also upgrade to FP3/SP3 yesterday and got the blue screen of death when I tried to run the console manager..
I had to uninstall it completely and revert back to FP2

 

[chjinmind]

Hi!
Hehe... it was tested on a testserver first. However before doing it in real environment I mirrord the disk array completely so to roll back fast I just changed the physical disks in the array.


I will try the suggestion to update the DC first in this environment. In my tests I only had 1 server so pointing out a DC was not that big of a task...

Will post results later,
cheers!

/Chris

 

[garyl29]

Hello,

I also upgrade to FP3/SP3 yesterday and got the blue screen of death when I tried to run the console manager. All I had to do is uninstall and reinstall console manager to get rid of the Blue Screen

 

[chjinmind]

Cause found!

MF SP3/FR3 does not work under NT domains.

The MF servers I currently work on are in a NT resource domain (not yet migrated to AD).
Users accounts has been migrated to AD so the whole MS solution is in mixed mode.

The cause on the bluescreening MetaFrame servers were that MFXP SP3 servers cannot be part of a NT domain, it has to be in AD envorinment to work properly
SP2/FR2 servers are still OK.

The crash was a WlxNegotiate function the winlogon.exe uses. Address dump showed that the crash was in the memory area ctxgina.dll uses. Obviously MFXP SP3/FR3 with the updated ctxgina.dll is not compatible with NT4 authentication.

DO NOT UPGRADE METAFRAME XP TO SP3 IF SERVERS ARE MEMBERS OF NT DOMAIN, STAY WITH SP2/FR2.

//Chris

 

[CitrixEngineer]

That's news to me, Chris - thanks for spotting that!

CitrixEngineer@yahoo.co.uk

 

[androute]

I think I solved it, using the information in the post above.
I figured that if ctxgina.dll was indeed the culprit, then maybe reinstalling the version that comes with Metaframe SP2 FR2 would to the trick.
So, after the server crashed again after upgrading, I did not click OK nor Cancel, so that the dialog box stayed on screen.
At that time I could still reach the server from the network.
I made a NET USE connection to this server, renamed CTGINA.DLL to CTXGINA.NEW in the %SYSTEMROOT%\SYSTEM32 folder, then copied the Metaframe SP2FR2 version to that folder, and rebooted.
Bingo !
But I have no idea what this means, if this would cause any problems for the upgrade.
Is this still fully SP3FR3 or will this give problems in the future ?
The interface appears to be SP3FR3 anyway.