The description for Event ID ( 54 ) in Source ( rdpdr ) cannot be found.

We have an Event ID 54 that keeps appearing our System event logs on almost all of our windows 2003 terminal servers. I have googled it but can’t find very useful information.

Event Type:      Warning
Event Source:      rdpdr
Event Category:      None
Event ID:      54
The description for Event ID ( 54 ) in Source ( rdpdr ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\RdpDrDvMgr.
0000: 00 00 00 00 01 00 54 00   ......T.
0008: 00 00 00 00 36 00 04 80   ....6..¿
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Based on what I have found:

\Device\RdpDrDvMgr - is the RDP/Terminal server device redirector

Error 54 seems to be a generic "something went wrong trying to redirect a device."  What I can't tell is was the device on the server or the client.

Do you have any unusual devices on either the server or the client, like say a finger print reader?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
smith9069Author Commented:
Thank you for the tip. Is there is any tool or log that can help us to find it?
From what I have read it seems that these errors come in pairs.  One will have \Device\RdpDrDvMgr as part of the event information and the other will have something else.  The something else is supposed to be directly related to whatever is causing the problem.
smith9069Author Commented:
I opened a case with MIcrosoft. The case can be found this link:
smith9069Author Commented:
opened a case with Microsoft
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.