Page 1 of 2 12 LastLast
Results 1 to 15 of 19

Thread: Can't access server via remote desktop connection

  1. #1
    Mark Christensen Guest

    Can't access server via remote desktop connection

    I have an XP machine that I use to remote into our server that's located in
    another part of the building. The server is running Server 2003 R2
    Enterprise Edition SP2. The server is set up to accept remote connections.
    Usually I can get in to it fine, but then every so often when I open the
    Remote log on box on my PC and click connect (after entering the log on info
    like normal), the Remote log on box just refreshes and won't let me connect
    to the server. Our fix for this has always been to reboot the server, then I
    can log in fine, but this doesn't seem right.

    Is there something wrong with our server?
    Or a setting that needs to be changed on it so I can reliable remote in to
    it?

    Thanks.

    Mark



  2. #2
    John Z Guest

    RE: Can't access server via remote desktop connection

    HI, Mark,

    I have exactly the same problem with one of our server (Server 2003 std,
    DC). A reboot will fix the issue, then the issue will come again, and reboot
    again.

    I cannot seem to find the reason, but was wondering if any folks here have
    any clue?

    John

    "Mark Christensen" wrote:

    > I have an XP machine that I use to remote into our server that's located in
    > another part of the building. The server is running Server 2003 R2
    > Enterprise Edition SP2. The server is set up to accept remote connections.
    > Usually I can get in to it fine, but then every so often when I open the
    > Remote log on box on my PC and click connect (after entering the log on info
    > like normal), the Remote log on box just refreshes and won't let me connect
    > to the server. Our fix for this has always been to reboot the server, then I
    > can log in fine, but this doesn't seem right.
    >
    > Is there something wrong with our server?
    > Or a setting that needs to be changed on it so I can reliable remote in to
    > it?
    >
    > Thanks.
    >
    > Mark
    >
    >
    >


  3. #3
    Mark Christensen Guest

    Re: Can't access server via remote desktop connection

    Yes exactly - a reboot will fix the issue for awhile, but then it stops
    working and you have to reboot to get it to work again.


    "John Z" <JohnZ@discussions.microsoft.com> wrote in message
    news:D98EC4C2-C7F0-4590-870A-35DCB8C59F4F@microsoft.com...
    > HI, Mark,
    >
    > I have exactly the same problem with one of our server (Server 2003 std,
    > DC). A reboot will fix the issue, then the issue will come again, and
    > reboot
    > again.
    >
    > I cannot seem to find the reason, but was wondering if any folks here have
    > any clue?
    >
    > John
    >
    > "Mark Christensen" wrote:
    >
    >> I have an XP machine that I use to remote into our server that's located
    >> in
    >> another part of the building. The server is running Server 2003 R2
    >> Enterprise Edition SP2. The server is set up to accept remote
    >> connections.
    >> Usually I can get in to it fine, but then every so often when I open the
    >> Remote log on box on my PC and click connect (after entering the log on
    >> info
    >> like normal), the Remote log on box just refreshes and won't let me
    >> connect
    >> to the server. Our fix for this has always been to reboot the server,
    >> then I
    >> can log in fine, but this doesn't seem right.
    >>
    >> Is there something wrong with our server?
    >> Or a setting that needs to be changed on it so I can reliable remote in
    >> to
    >> it?
    >>
    >> Thanks.
    >>
    >> Mark
    >>
    >>
    >>




  4. #4
    Jeremy Rossi Guest

    Re: Can't access server via remote desktop connection

    Have you tried killing any existing sessions (other than console) from
    terminal service manager? I have to do this on occasion, if I ever get
    around to finding a solution rather then this work around I'll try to
    remember to post it here.


    "John Z" <JohnZ@discussions.microsoft.com> wrote in message
    news:D98EC4C2-C7F0-4590-870A-35DCB8C59F4F@microsoft.com...
    > HI, Mark,
    >
    > I have exactly the same problem with one of our server (Server 2003 std,
    > DC). A reboot will fix the issue, then the issue will come again, and
    > reboot
    > again.
    >
    > I cannot seem to find the reason, but was wondering if any folks here have
    > any clue?
    >
    > John
    >
    > "Mark Christensen" wrote:
    >
    >> I have an XP machine that I use to remote into our server that's located
    >> in
    >> another part of the building. The server is running Server 2003 R2
    >> Enterprise Edition SP2. The server is set up to accept remote
    >> connections.
    >> Usually I can get in to it fine, but then every so often when I open the
    >> Remote log on box on my PC and click connect (after entering the log on
    >> info
    >> like normal), the Remote log on box just refreshes and won't let me
    >> connect
    >> to the server. Our fix for this has always been to reboot the server,
    >> then I
    >> can log in fine, but this doesn't seem right.
    >>
    >> Is there something wrong with our server?
    >> Or a setting that needs to be changed on it so I can reliable remote in
    >> to
    >> it?
    >>
    >> Thanks.
    >>
    >> Mark
    >>
    >>
    >>



  5. #5
    Lanwench [MVP - Exchange] Guest

    Re: Can't access server via remote desktop connection

    Mark Christensen <markc@ssbrakes.com> wrote:
    > I have an XP machine that I use to remote into our server that's
    > located in another part of the building. The server is running Server
    > 2003 R2 Enterprise Edition SP2. The server is set up to accept remote
    > connections. Usually I can get in to it fine, but then every so often
    > when I open the Remote log on box on my PC and click connect (after
    > entering the log on info like normal), the Remote log on box just
    > refreshes and won't let me connect to the server. Our fix for this
    > has always been to reboot the server, then I can log in fine, but
    > this doesn't seem right.
    > Is there something wrong with our server?
    > Or a setting that needs to be changed on it so I can reliable remote
    > in to it?
    >
    > Thanks.
    >
    > Mark



    One thing to note - always try to connect to the console session directly
    (start | run | mstsc /console is the easiest way).


    If it works sometimes but not others, it isn't a configuration problem -
    you'd need to check the event logs and possibly have physical access to the
    server when this is happening to troubleshoot it.



  6. #6
    Mark Christensen Guest

    Re: Can't access server via remote desktop connection

    How would I kill existing sessions?

    I'm not a trained IT professional, but I'm the closest we have here. Thanks.


    "Jeremy Rossi" <JLRossi@MFS.tld> wrote in message
    news:778E168C-878A-4E87-9D08-3A4571A9E266@microsoft.com...
    > Have you tried killing any existing sessions (other than console) from
    > terminal service manager? I have to do this on occasion, if I ever get
    > around to finding a solution rather then this work around I'll try to
    > remember to post it here.
    >
    >
    > "John Z" <JohnZ@discussions.microsoft.com> wrote in message
    > news:D98EC4C2-C7F0-4590-870A-35DCB8C59F4F@microsoft.com...
    >> HI, Mark,
    >>
    >> I have exactly the same problem with one of our server (Server 2003 std,
    >> DC). A reboot will fix the issue, then the issue will come again, and
    >> reboot
    >> again.
    >>
    >> I cannot seem to find the reason, but was wondering if any folks here
    >> have
    >> any clue?
    >>
    >> John
    >>
    >> "Mark Christensen" wrote:
    >>
    >>> I have an XP machine that I use to remote into our server that's located
    >>> in
    >>> another part of the building. The server is running Server 2003 R2
    >>> Enterprise Edition SP2. The server is set up to accept remote
    >>> connections.
    >>> Usually I can get in to it fine, but then every so often when I open the
    >>> Remote log on box on my PC and click connect (after entering the log on
    >>> info
    >>> like normal), the Remote log on box just refreshes and won't let me
    >>> connect
    >>> to the server. Our fix for this has always been to reboot the server,
    >>> then I
    >>> can log in fine, but this doesn't seem right.
    >>>
    >>> Is there something wrong with our server?
    >>> Or a setting that needs to be changed on it so I can reliable remote in
    >>> to
    >>> it?
    >>>
    >>> Thanks.
    >>>
    >>> Mark
    >>>
    >>>
    >>>

    >




  7. #7
    Mark Christensen Guest

    Re: Can't access server via remote desktop connection

    What would I look for in the event logs?

    "Lanwench [MVP - Exchange]"
    <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
    news:eElUpci0IHA.2384@TK2MSFTNGP02.phx.gbl...
    > Mark Christensen <markc@ssbrakes.com> wrote:
    >> I have an XP machine that I use to remote into our server that's
    >> located in another part of the building. The server is running Server
    >> 2003 R2 Enterprise Edition SP2. The server is set up to accept remote
    >> connections. Usually I can get in to it fine, but then every so often
    >> when I open the Remote log on box on my PC and click connect (after
    >> entering the log on info like normal), the Remote log on box just
    >> refreshes and won't let me connect to the server. Our fix for this
    >> has always been to reboot the server, then I can log in fine, but
    >> this doesn't seem right.
    >> Is there something wrong with our server?
    >> Or a setting that needs to be changed on it so I can reliable remote
    >> in to it?
    >>
    >> Thanks.
    >>
    >> Mark

    >
    >
    > One thing to note - always try to connect to the console session directly
    > (start | run | mstsc /console is the easiest way).
    >
    >
    > If it works sometimes but not others, it isn't a configuration problem -
    > you'd need to check the event logs and possibly have physical access to
    > the server when this is happening to troubleshoot it.
    >
    >




  8. #8
    John Z Guest

    Re: Can't access server via remote desktop connection

    Hi, Lanwench,

    I actually checked the error logs, but i could not find anything directly
    related the problem for RDP. But i did noticed a pattern here. Whenever i
    found i was not able to RDP into this server, i noticed out Backup Exec also
    failed with the similar VSS error (failed to backup System State and Shadow
    Copy Components). I then reboot the server which usually can fix those VSS
    writers errors. So does the RDP problem. It seems this RDP problem is
    directly related to those VSS issues. I don't know if Mark Christensen has
    the similar situation. I even called BackExec support, the support guy asked
    me to reload the sp2 for server 2003 plus some microsoft VSS patches, I
    helped and the worked for a while but the problem will come back again.

    John

    "Lanwench [MVP - Exchange]" wrote:

    > Mark Christensen <markc@ssbrakes.com> wrote:
    > > I have an XP machine that I use to remote into our server that's
    > > located in another part of the building. The server is running Server
    > > 2003 R2 Enterprise Edition SP2. The server is set up to accept remote
    > > connections. Usually I can get in to it fine, but then every so often
    > > when I open the Remote log on box on my PC and click connect (after
    > > entering the log on info like normal), the Remote log on box just
    > > refreshes and won't let me connect to the server. Our fix for this
    > > has always been to reboot the server, then I can log in fine, but
    > > this doesn't seem right.
    > > Is there something wrong with our server?
    > > Or a setting that needs to be changed on it so I can reliable remote
    > > in to it?
    > >
    > > Thanks.
    > >
    > > Mark

    >
    >
    > One thing to note - always try to connect to the console session directly
    > (start | run | mstsc /console is the easiest way).
    >
    >
    > If it works sometimes but not others, it isn't a configuration problem -
    > you'd need to check the event logs and possibly have physical access to the
    > server when this is happening to troubleshoot it.
    >
    >
    >


  9. #9
    Jer_ Guest

    Re: Can't access server via remote desktop connection

    The easiest way while at the server is probably - Click the 'Start' button,
    Settings, Control Panel, Administrative Tools, Terminal Services Manager.
    Select the server in the left hand pane and right click the session/s in the
    right hand pane and choose logoff. The session 'Console' is what you are
    using while sitting at the server so leave that one as is.

    "Mark Christensen" <markc@ssbrakes.com> wrote in message
    news:eg9Hyui0IHA.4416@TK2MSFTNGP05.phx.gbl...
    > How would I kill existing sessions?
    >
    > I'm not a trained IT professional, but I'm the closest we have here.
    > Thanks.
    >
    >
    > "Jeremy Rossi" <JLRossi@MFS.tld> wrote in message
    > news:778E168C-878A-4E87-9D08-3A4571A9E266@microsoft.com...
    >> Have you tried killing any existing sessions (other than console) from
    >> terminal service manager? I have to do this on occasion, if I ever get
    >> around to finding a solution rather then this work around I'll try to
    >> remember to post it here.
    >>
    >>
    >> "John Z" <JohnZ@discussions.microsoft.com> wrote in message
    >> news:D98EC4C2-C7F0-4590-870A-35DCB8C59F4F@microsoft.com...
    >>> HI, Mark,
    >>>
    >>> I have exactly the same problem with one of our server (Server 2003 std,
    >>> DC). A reboot will fix the issue, then the issue will come again, and
    >>> reboot
    >>> again.
    >>>
    >>> I cannot seem to find the reason, but was wondering if any folks here
    >>> have
    >>> any clue?
    >>>
    >>> John
    >>>
    >>> "Mark Christensen" wrote:
    >>>
    >>>> I have an XP machine that I use to remote into our server that's
    >>>> located in
    >>>> another part of the building. The server is running Server 2003 R2
    >>>> Enterprise Edition SP2. The server is set up to accept remote
    >>>> connections.
    >>>> Usually I can get in to it fine, but then every so often when I open
    >>>> the
    >>>> Remote log on box on my PC and click connect (after entering the log on
    >>>> info
    >>>> like normal), the Remote log on box just refreshes and won't let me
    >>>> connect
    >>>> to the server. Our fix for this has always been to reboot the server,
    >>>> then I
    >>>> can log in fine, but this doesn't seem right.
    >>>>
    >>>> Is there something wrong with our server?
    >>>> Or a setting that needs to be changed on it so I can reliable remote in
    >>>> to
    >>>> it?
    >>>>
    >>>> Thanks.
    >>>>
    >>>> Mark
    >>>>
    >>>>
    >>>>

    >>

    >
    >



  10. #10
    Hank Arnold (MVP) Guest

    Re: Can't access server via remote desktop connection

    Mark Christensen wrote:
    > I have an XP machine that I use to remote into our server that's located in
    > another part of the building. The server is running Server 2003 R2
    > Enterprise Edition SP2. The server is set up to accept remote connections.
    > Usually I can get in to it fine, but then every so often when I open the
    > Remote log on box on my PC and click connect (after entering the log on info
    > like normal), the Remote log on box just refreshes and won't let me connect
    > to the server. Our fix for this has always been to reboot the server, then I
    > can log in fine, but this doesn't seem right.
    >
    > Is there something wrong with our server?
    > Or a setting that needs to be changed on it so I can reliable remote in to
    > it?
    >
    > Thanks.
    >
    > Mark
    >
    >

    Standard Diagnostics Question #1:
    ---------------------------------
    "Anything showing up in the Event Logs?"

    --

    Regards,
    Hank Arnold
    Microsoft MVP
    Windows Server - Directory Services

  11. #11
    Hank Arnold (MVP) Guest

    Re: Can't access server via remote desktop connection

    Mark Christensen wrote:
    > How would I kill existing sessions?
    >
    > I'm not a trained IT professional, but I'm the closest we have here. Thanks.
    >
    >
    > "Jeremy Rossi" <JLRossi@MFS.tld> wrote in message
    > news:778E168C-878A-4E87-9D08-3A4571A9E266@microsoft.com...
    >> Have you tried killing any existing sessions (other than console) from
    >> terminal service manager? I have to do this on occasion, if I ever get
    >> around to finding a solution rather then this work around I'll try to
    >> remember to post it here.
    >>
    >>
    >> "John Z" <JohnZ@discussions.microsoft.com> wrote in message
    >> news:D98EC4C2-C7F0-4590-870A-35DCB8C59F4F@microsoft.com...
    >>> HI, Mark,
    >>>
    >>> I have exactly the same problem with one of our server (Server 2003 std,
    >>> DC). A reboot will fix the issue, then the issue will come again, and
    >>> reboot
    >>> again.
    >>>
    >>> I cannot seem to find the reason, but was wondering if any folks here
    >>> have
    >>> any clue?
    >>>
    >>> John
    >>>
    >>> "Mark Christensen" wrote:
    >>>
    >>>> I have an XP machine that I use to remote into our server that's located
    >>>> in
    >>>> another part of the building. The server is running Server 2003 R2
    >>>> Enterprise Edition SP2. The server is set up to accept remote
    >>>> connections.
    >>>> Usually I can get in to it fine, but then every so often when I open the
    >>>> Remote log on box on my PC and click connect (after entering the log on
    >>>> info
    >>>> like normal), the Remote log on box just refreshes and won't let me
    >>>> connect
    >>>> to the server. Our fix for this has always been to reboot the server,
    >>>> then I
    >>>> can log in fine, but this doesn't seem right.
    >>>>
    >>>> Is there something wrong with our server?
    >>>> Or a setting that needs to be changed on it so I can reliable remote in
    >>>> to
    >>>> it?
    >>>>
    >>>> Thanks.
    >>>>
    >>>> Mark
    >>>>
    >>>>
    >>>>

    >
    >


    Open up the Terminal Server Manager console and log the user session
    off........

    --

    Regards,
    Hank Arnold
    Microsoft MVP
    Windows Server - Directory Services

  12. #12
    Hank Arnold (MVP) Guest

    Re: Can't access server via remote desktop connection

    Mark Christensen wrote:
    > What would I look for in the event logs?
    >
    > "Lanwench [MVP - Exchange]"
    > <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
    > news:eElUpci0IHA.2384@TK2MSFTNGP02.phx.gbl...
    >> Mark Christensen <markc@ssbrakes.com> wrote:
    >>> I have an XP machine that I use to remote into our server that's
    >>> located in another part of the building. The server is running Server
    >>> 2003 R2 Enterprise Edition SP2. The server is set up to accept remote
    >>> connections. Usually I can get in to it fine, but then every so often
    >>> when I open the Remote log on box on my PC and click connect (after
    >>> entering the log on info like normal), the Remote log on box just
    >>> refreshes and won't let me connect to the server. Our fix for this
    >>> has always been to reboot the server, then I can log in fine, but
    >>> this doesn't seem right.
    >>> Is there something wrong with our server?
    >>> Or a setting that needs to be changed on it so I can reliable remote
    >>> in to it?
    >>>
    >>> Thanks.
    >>>
    >>> Mark

    >>
    >> One thing to note - always try to connect to the console session directly
    >> (start | run | mstsc /console is the easiest way).
    >>
    >>
    >> If it works sometimes but not others, it isn't a configuration problem -
    >> you'd need to check the event logs and possibly have physical access to
    >> the server when this is happening to troubleshoot it.
    >>
    >>

    >
    >

    Any errors o warnings that occurred just before the loss of
    connectivity. Then go to http:\\eventid.net to diagnose...

    --

    Regards,
    Hank Arnold
    Microsoft MVP
    Windows Server - Directory Services

  13. #13
    Hank Arnold (MVP) Guest

    Re: Can't access server via remote desktop connection

    John Z wrote:
    > Hi, Lanwench,
    >
    > I actually checked the error logs, but i could not find anything directly
    > related the problem for RDP. But i did noticed a pattern here. Whenever i
    > found i was not able to RDP into this server, i noticed out Backup Exec also
    > failed with the similar VSS error (failed to backup System State and Shadow
    > Copy Components). I then reboot the server which usually can fix those VSS
    > writers errors. So does the RDP problem. It seems this RDP problem is
    > directly related to those VSS issues. I don't know if Mark Christensen has
    > the similar situation. I even called BackExec support, the support guy asked
    > me to reload the sp2 for server 2003 plus some microsoft VSS patches, I
    > helped and the worked for a while but the problem will come back again.
    >
    > John
    >
    > "Lanwench [MVP - Exchange]" wrote:
    >
    >> Mark Christensen <markc@ssbrakes.com> wrote:
    >>> I have an XP machine that I use to remote into our server that's
    >>> located in another part of the building. The server is running Server
    >>> 2003 R2 Enterprise Edition SP2. The server is set up to accept remote
    >>> connections. Usually I can get in to it fine, but then every so often
    >>> when I open the Remote log on box on my PC and click connect (after
    >>> entering the log on info like normal), the Remote log on box just
    >>> refreshes and won't let me connect to the server. Our fix for this
    >>> has always been to reboot the server, then I can log in fine, but
    >>> this doesn't seem right.
    >>> Is there something wrong with our server?
    >>> Or a setting that needs to be changed on it so I can reliable remote
    >>> in to it?
    >>>
    >>> Thanks.
    >>>
    >>> Mark

    >>
    >> One thing to note - always try to connect to the console session directly
    >> (start | run | mstsc /console is the easiest way).
    >>
    >>
    >> If it works sometimes but not others, it isn't a configuration problem -
    >> you'd need to check the event logs and possibly have physical access to the
    >> server when this is happening to troubleshoot it.
    >>
    >>
    >>

    What are the exact messages? Have you looked at http:\\eventid.net for
    some help in analyzing the errors and/or warnings?

    --

    Regards,
    Hank Arnold
    Microsoft MVP
    Windows Server - Directory Services

  14. #14
    Join Date
    Jun 2008
    Posts
    10
    Hi

    I have found a very simple solution to these problems by installing "VNC Server". This gives me a prefect access to any of my systems in the network using a password protection. I can see the desktop of the desired system without any hassles and can log into any machine using LAN or WAN.

    Try it if it suits your need.

    Thanks

    Quote Originally Posted by Mark Christensen View Post
    I have an XP machine that I use to remote into our server that's located in
    another part of the building. The server is running Server 2003 R2
    Enterprise Edition SP2. The server is set up to accept remote connections.
    Usually I can get in to it fine, but then every so often when I open the
    Remote log on box on my PC and click connect (after entering the log on info
    like normal), the Remote log on box just refreshes and won't let me connect
    to the server. Our fix for this has always been to reboot the server, then I
    can log in fine, but this doesn't seem right.

    Is there something wrong with our server?
    Or a setting that needs to be changed on it so I can reliable remote in to
    it?

    Thanks.

    Mark

  15. #15
    John Z Guest

    Re: Can't access server via remote desktop connection


    Hi, Hank,

    Sorry for my late response. I reboot the server. The vss error(id 12293) is
    gone after the reboot. But the other errors are still there. However, RDP
    seems to be working fine. Thank you.

    Most of the error are somting like below.
    Event Type: Error
    Event Source: VSS
    Event Category: None
    Event ID: 12293
    Date: 6/18/2008
    Time: 8:53:42 PM
    User: N/A
    Computer: S10095
    Description:
    Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy
    Provider {f5dbcc43-b847-494e-8083-f030501da611}. Routine details
    BeginPrepareSnapshot({f5dbcc43-b847-494e-8083-f030501da611},\\?\Volume{30f3c473-5221-11da-8c41-806e6f6e6963}\) [hr = 0x80070002].

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 2d 20 43 6f 64 65 3a 20 - Code:
    0008: 43 4f 52 48 57 50 57 43 CORHWPWC
    0010: 30 30 30 30 30 35 34 33 00000543
    0018: 2d 20 43 61 6c 6c 3a 20 - Call:
    0020: 43 4f 52 48 57 50 57 43 CORHWPWC
    0028: 30 30 30 30 30 34 32 35 00000425
    0030: 2d 20 50 49 44 3a 20 20 - PID:
    0038: 30 30 30 30 35 39 33 32 00005932
    0040: 2d 20 54 49 44 3a 20 20 - TID:
    0048: 30 30 30 30 31 31 33 36 00001136
    0050: 2d 20 43 4d 44 3a 20 20 - CMD:
    0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
    0060: 57 53 5c 53 79 73 74 65 WS\Syste
    0068: 6d 33 32 5c 76 73 73 76 m32\vssv
    0070: 63 2e 65 78 65 20 20 20 c.exe
    0078: 2d 20 55 73 65 72 3a 20 - User:
    0080: 4e 54 20 41 55 54 48 4f NT AUTHO
    0088: 52 49 54 59 5c 53 59 53 RITY\SYS
    0090: 54 45 4d 20 20 20 20 20 TEM
    0098: 2d 20 53 69 64 3a 20 20 - Sid:
    00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18

    Event Type: Error
    Event Source: SQLWRITER
    Event Category: None
    Event ID: 24583
    Date: 6/18/2008
    Time: 8:30:48 PM
    User: N/A
    Computer: S10095
    Description:
    Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr =
    0x80040e14. SQLSTATE: 42000, Native Error: 3013
    Error state: 1, Severity: 16
    Source: Microsoft SQL Native Client
    Error message: BACKUP DATABASE is terminating abnormally.
    SQLSTATE: 42000, Native Error: 3271
    Error state: 1, Severity: 16
    Source: Microsoft SQL Native Client
    Error message: A nonrecoverable I/O error occurred on file
    "{FB3F0D6D-D98B-4C3D-AE1B-AFA0D3F2210F}1:" 995(The I/O operation has been
    aborted because of either a thread exit or an application request.).
    SQLSTATE: 01000, Native Error: 4035
    Error state: 1, Severity: 0
    Source: Microsoft SQL Native Client
    Error message: Processed 0 pages for database 'model', file 'modeldev' on
    file 1.


    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
    0008: 39 36 30 00 00 00 00 00 960.....
    0010: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
    0018: 39 32 35 00 00 00 00 00 925.....

    Event Type: Error
    Event Source: SQLVDI
    Event Category: None
    Event ID: 1
    Date: 6/18/2008
    Time: 8:30:48 PM
    User: N/A
    Computer: S10095
    Description:
    SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2640.
    Thread=4760. Server. Instance=SQLEXPRESS.
    VD=Global\{FB3F0D6D-D98B-4C3D-AE1B-AFA0D3F2210F}1.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: MSSQL$SQLEXPRESS
    Event Category: (6)
    Event ID: 3041
    Date: 6/18/2008
    Time: 8:30:48 PM
    User: NT AUTHORITY\SYSTEM
    Computer: S10095
    Description:
    BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup
    application log for detailed messages.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: e1 0b 00 00 10 00 00 00 รก.......
    0008: 12 00 00 00 53 00 31 00 ....S.1.
    0010: 30 00 30 00 39 00 35 00 0.0.9.5.
    0018: 5c 00 53 00 51 00 4c 00 \.S.Q.L.
    0020: 45 00 58 00 50 00 52 00 E.X.P.R.
    0028: 45 00 53 00 53 00 00 00 E.S.S...
    0030: 00 00 00 00 ....





    "Hank Arnold (MVP)" wrote:

    > Mark Christensen wrote:
    > > I have an XP machine that I use to remote into our server that's located in
    > > another part of the building. The server is running Server 2003 R2
    > > Enterprise Edition SP2. The server is set up to accept remote connections.
    > > Usually I can get in to it fine, but then every so often when I open the
    > > Remote log on box on my PC and click connect (after entering the log on info
    > > like normal), the Remote log on box just refreshes and won't let me connect
    > > to the server. Our fix for this has always been to reboot the server, then I
    > > can log in fine, but this doesn't seem right.
    > >
    > > Is there something wrong with our server?
    > > Or a setting that needs to be changed on it so I can reliable remote in to
    > > it?
    > >
    > > Thanks.
    > >
    > > Mark
    > >
    > >

    > Standard Diagnostics Question #1:
    > ---------------------------------
    > "Anything showing up in the Event Logs?"
    >
    > --
    >
    > Regards,
    > Hank Arnold
    > Microsoft MVP
    > Windows Server - Directory Services
    >


Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 4
    Last Post: 03-05-2012, 07:58 PM
  2. Access to Remote Desktop local server with external IP
    By ktric2121 in forum Windows Server Help
    Replies: 2
    Last Post: 30-12-2011, 02:52 AM
  3. Replies: 4
    Last Post: 23-12-2010, 09:15 AM
  4. unable to access server with remote desktop after server restart
    By inenewbl in forum Windows Server Help
    Replies: 2
    Last Post: 24-11-2008, 08:53 PM
  5. No sound over Remote Desktop Connection to SBS server
    By Billie in forum Small Business Server
    Replies: 2
    Last Post: 31-03-2008, 07:37 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •