1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Timed out sending notification error message

Discussion in 'Windows Home Server' started by Clowntrigger, Apr 8, 2009.

  1. Clowntrigger

    Clowntrigger Guest

    I have 2 BDC servers at remote locations that are generating the following
    error every 2 minutes.

    Event ID 257
    Timed out sending notification of target device change to window of
    "C:\WINDOWS\Explorer.EXE"

    I did a search on the internet, but could not find anything that would
    resolve this issue. Any idea on what may be causing the problem?
     
  2. Hello Clowntrigger,

    See here:
    http://support.microsoft.com/kb/924390

    If you use on google:
    event id 257

    you get roundabout 398.000 hits. What do you search for?

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


    > I have 2 BDC servers at remote locations that are generating the
    > following error every 2 minutes.
    >
    > Event ID 257
    > Timed out sending notification of target device change to window of
    > "C:\WINDOWS\Explorer.EXE"
    > I did a search on the internet, but could not find anything that would
    > resolve this issue. Any idea on what may be causing the problem?
    >
     
  3. Clowntrigger

    Clowntrigger Guest

    I didn't think the hotfix would apply. I'm not using a Net Appliance backup
    app and I haven't added any disks to the server.
     
  4. Clowntrigger

    Clowntrigger Guest

    I applied the hot fix and rebooted last night. That did resolve my issue.
    Thanks.

    "Meinolf Weber [MVP-DS]" wrote:

    > Hello Clowntrigger,
    >
    > See here:
    > http://support.microsoft.com/kb/924390
    >
    > If you use on google:
    > event id 257
    >
    > you get roundabout 398.000 hits. What do you search for?
    >
    > Best regards
    >
    > Meinolf Weber
    > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    > no rights.
    > ** Please do NOT email, only reply to Newsgroups
    > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >
    >
    > > I have 2 BDC servers at remote locations that are generating the
    > > following error every 2 minutes.
    > >
    > > Event ID 257
    > > Timed out sending notification of target device change to window of
    > > "C:\WINDOWS\Explorer.EXE"
    > > I did a search on the internet, but could not find anything that would
    > > resolve this issue. Any idea on what may be causing the problem?
    > >

    >
    >
    >
     
  5. Hello Clowntrigger,

    Nice to hear that it helps.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


    > I applied the hot fix and rebooted last night. That did resolve my
    > issue. Thanks.
    >
    > "Meinolf Weber [MVP-DS]" wrote:
    >
    >> Hello Clowntrigger,
    >>
    >> See here:
    >> http://support.microsoft.com/kb/924390
    >> If you use on google:
    >> event id 257
    >> you get roundabout 398.000 hits. What do you search for?
    >>
    >> Best regards
    >>
    >> Meinolf Weber
    >> Disclaimer: This posting is provided "AS IS" with no warranties, and
    >> confers
    >> no rights.
    >> ** Please do NOT email, only reply to Newsgroups
    >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >>> I have 2 BDC servers at remote locations that are generating the
    >>> following error every 2 minutes.
    >>>
    >>> Event ID 257
    >>> Timed out sending notification of target device change to window of
    >>> "C:\WINDOWS\Explorer.EXE"
    >>> I did a search on the internet, but could not find anything that
    >>> would
    >>> resolve this issue. Any idea on what may be causing the problem?
     

Share This Page