I have the following warning appearing in my system event log: Event Type: WarningEvent Source: PlugPlayManagerEvent Category: NoneEvent ID: 257Date: 1/5/2009Time: 12:18:39 AMUser: N/AComputer: THA-ABRAM Description: Timed out sending notification of target device change to window of "C:\WINDOWS\Explorer.EXE" For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.I'm not sure whatiscausing this error.Server Configuration:Dell PowerEdge 2900 (Dual Quad Xeon 2.0, 4GB RAM, Perc6i controller,4 x 146GB SCSI in two RAID 1's Windows 2003 SP2, Running Active Director, DNS, DHCP

hi there,this is caused by one of your driver, most possible causes would be your USB driver , hard disk is taking long time to pop up into explorer.or this would occur if high I/O operations are perfromed on disk have you attached any external device on to your system,from when is this issue occuring ?, what has changed ?sainath Windows Driver Development

This event is like clock work, I will get excalty six notices with the same exact time stamp to the second. So six events are show at the same exactt time. An hour later, six more event at the same exact time. I have two USB devices one is the USB adaptor, which converts a PS2 mouse and keyboard into a USB, that was supplied by Dell.The second is my UPS, which is connected to oura APC UPS.I have searched my event logs to see if something else was happening at the same or near the same time as that event, nothing, nothing at all.

Hello Philldmcc,Try this article which references a hotfix which sounds like what you are encountering:924390Event ID 257 is logged in the System event log several times on a Windows Server 2003-based computerhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;924390Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights

Hi all,So my suspicion was correct, dmadmin is not getting updated, i thought of it earlier , but as i did not have enough information , it was tough to predict.thanks darrell for the article. phil, i guess you can safely update the same, i thought there was someentry which is getting added to object manager, or might be PNP manager is not able to register itself appropriately.sainath Windows Driver Development

Well not sure that was or isthe problem.I was able to discover something new. Someone had terminaled in, twice under the same account that remained logged in. Once I logged off the remote sessions the error went away.Interesting at least.Phill