Problem with Windows 2003 TS and SQL connection

[Guest A. Koch]

Hello,

 

sorry for my bad English. I hope you will understand me.

 

My customer have two servers. One Fileserver (Windows 2003 SB) and one

Terminal Server (Windows 2003 Standard).

 

The installed applications on the terminal server uses a SQL-server (on the

fileserver).

 

The problem:

 

When the users don't work for 20 minutes (ore more) and the session is still

active, the connection between the applications and the sql-server will be

lost.

 

drivers and windows updates are on both server up to date. In the event

viewer is nothing protocolled..

 

Any idea?

 

Thanks!

[Guest Vera Noest [MVP]]

Re: Problem with Windows 2003 TS and SQL connection

 

That sounds to me like a time-out built into the application.

If the remote session is still active, it's not a problem with the

TS.

Does the same happen when you run the application directly from a

client?

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?QS4gS29jaA==?= <A. Koch@discussions.microsoft.com> wrote

on 12 mar 2008 in microsoft.public.windows.terminal_services:

> Hello,

>

> sorry for my bad English. I hope you will understand me.

>

> My customer have two servers. One Fileserver (Windows 2003 SB)

> and one Terminal Server (Windows 2003 Standard).

>

> The installed applications on the terminal server uses a

> SQL-server (on the fileserver).

>

> The problem:

>

> When the users don't work for 20 minutes (ore more) and the

> session is still active, the connection between the applications

> and the sql-server will be lost.

>

> drivers and windows updates are on both server up to date. In

> the event viewer is nothing protocolled..

>

> Any idea?

>

> Thanks!

[Guest A. Koch]

Re: Problem with Windows 2003 TS and SQL connection

 

Hello,

 

thanks for the quick reply.

 

the session is still active, just the connection from application to the sql

server is down.

there is no problem when the application is directly started on the

client... :-(

 

 

"Vera Noest [MVP]" wrote:

> That sounds to me like a time-out built into the application.

> If the remote session is still active, it's not a problem with the

> TS.

> Does the same happen when you run the application directly from a

> client?

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?QS4gS29jaA==?= <A. Koch@discussions.microsoft.com> wrote

> on 12 mar 2008 in microsoft.public.windows.terminal_services:

>

> > Hello,

> >

> > sorry for my bad English. I hope you will understand me.

> >

> > My customer have two servers. One Fileserver (Windows 2003 SB)

> > and one Terminal Server (Windows 2003 Standard).

> >

> > The installed applications on the terminal server uses a

> > SQL-server (on the fileserver).

> >

> > The problem:

> >

> > When the users don't work for 20 minutes (ore more) and the

> > session is still active, the connection between the applications

> > and the sql-server will be lost.

> >

> > drivers and windows updates are on both server up to date. In

> > the event viewer is nothing protocolled..

> >

> > Any idea?

> >

> > Thanks!

>

[Guest Vera Noest [MVP]]

Re: Problem with Windows 2003 TS and SQL connection

 

Mmm, difficult.

Do you get any message on the screen when the connection is lost?

Does the application have a log file?

When the connection is lost, can you ping the SQL server from

within the session? And connect to a file share on the SQL server?

Are you able to reconnect immediately to the SQL server, without

ending the TS session? Maybe by just closing the application and

starting it again? Or do you need to end the TS session to regain a

connection?

I would also check the SQL logfiles and post to a sql newsgroup.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?QS4gS29jaA==?= <AKoch@discussions.microsoft.com> wrote

on 12 mar 2008 in microsoft.public.windows.terminal_services:

> Hello,

>

> thanks for the quick reply.

>

> the session is still active, just the connection from

> application to the sql server is down.

> there is no problem when the application is directly started on

> the client... :-(

>

>

> "Vera Noest [MVP]" wrote:

>

>> That sounds to me like a time-out built into the application.

>> If the remote session is still active, it's not a problem with

>> the TS.

>> Does the same happen when you run the application directly from

>> a client?

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?QS4gS29jaA==?= <A. Koch@discussions.microsoft.com>

>> wrote on 12 mar 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > Hello,

>> >

>> > sorry for my bad English. I hope you will understand me.

>> >

>> > My customer have two servers. One Fileserver (Windows 2003

>> > SB) and one Terminal Server (Windows 2003 Standard).

>> >

>> > The installed applications on the terminal server uses a

>> > SQL-server (on the fileserver).

>> >

>> > The problem:

>> >

>> > When the users don't work for 20 minutes (ore more) and the

>> > session is still active, the connection between the

>> > applications and the sql-server will be lost.

>> >

>> > drivers and windows updates are on both server up to date. In

>> > the event viewer is nothing protocolled..

>> >

>> > Any idea?

>> >

>> > Thanks!