Cannot load illegal module Term Service event id 1014
Hi,
We have a number of citrix servers running windows 2003 SP2 and Citrix Xenapp5. We patched them on the weekend with the latest windows updates and now after the servers reboot we randomly we get the following message:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
Date: 15/05/2012
Time: 08:30:37
User: N/A
Computer: CITRIXXN46
Description:
Cannot load illegal module: C:\WINDOWS\system32\vdtw30.DLL.
(Note that the illegal module can sometimes be different.)
Sometimes a reboot fixes the problem, but other times it does not.
When we get this issue, users cannot connect to the citrix server as the ICA and RDP listeners are down.
Any help would be appreciated.
May 15th, 2012 4:42am
Hello,
Please go through below hotfix link once:
http://support.microsoft.com/kb/958476
Regards, Ravikumar P
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 4:55am
I have found the answer. I did plenty of searches but one came up trumps and I found a citrix article that described the problem (http://support.citrix.com/article/CTX133141).
Essentially it seems that is is a known problem on a windows 2003 server with RDP and ICA protocols.
See MS Article http://support.microsoft.com/kb/2653956 and the hotfix that needs to be installed
http://support.microsoft.com/kb/958476
Note we did not have to remove the original 2653956 hotfix before applying the hotfix 958476
May 15th, 2012 4:56am
Hi Ravikumar,
Thanks for the post, I got there eventually although it wasn;t easy to find at first.
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 4:57am
Thank goodness I found this! We've had a busy time with our XenApp gold image over the last month and we had installed the same set of updates and started getting the same error each morning (we reboot XenApp overnight).
I'd spent weeks releasing new gold images adding bits in one at a time and had got down to "Ohh dear, it's Windows updates".
It's a long time since a Windows update has broken something else.
Cheers, Rob.
June 7th, 2012 4:24am