Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The server was not able to initialize the Client Management virtual driver (Error 13)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a virtual driver?
|Our approach: This information is only available to subscribers. An example of Our approach|
From a newsgroup post this error: "Citrix tends to start dying around a 700 ms latency (RDP is around 600ms), even at this latency, it starts to become unusable. Although it is not ideal, measure the latency using ping from his client machine to the Citrix server. If the latency is around 1000 ms, then almost certianly the session will die if data is streaming to the client at the time (high latency is OK, just so long as no data is being send to and from the server at the time of the hight latency).
Future release 1 for MF 1.8 has a "high latency" workaround which is essentially a local echo on the client of mouse and keystrokes - which makes most applications usable even at 700 ms latency - but it does not prevent the session from dying completely when the latency is 1000 ms or more. You will find that cable users will generally have 1/2 to 2/3 the latency compared to an equivalent DSL user. Note that to make the session stable, you only need to get the latency below 650 ms, rather than reduce it to a really low value.
Generally, there is not much you can do to lower the latency for the user - in these instances you need to look at the viability of shifting them to another medium such as cable, ISDN or even modems (we have had an office of 3 users running Citrix sessions concurrently very successfully on a 33.6k connection in the past - yes, we were suprised it worked at all)."
Another newsgroup post: "Solution: If the group Everyone is given Read access to the Mfc42u.dll file, the errors no longer appear during logon."
See Citrix document CTX891099 - This event is usually associated with a connection that gets disconnected early in the logon process. It usually occurs during the time that cltmgr queries the local client to determine what client devices are attached to the local client.
From a newsgroup post: "We finally narrowed it down to IBM8235 software loaded on an individuals' PC which had Citrix Client loaded. Seems Citrix wanted to try to map or attached to the modem pool we no longer had. I got rid of 8235 software and the problem was solved."
From another newsgroup post: "Uninstall Citrix client and reinstall it will fix the problem."
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated