Windows NT RDO failed to connect to SQL server

  • Thread starter Thread starter himshah
  • Start date Start date
H

himshah

We have application that runs with RDO/ODBC connection. The application works
fine in client/server environment in LAN. We know that other locaiton has
same applicaiton running with TS client.

Our location, it failes to open the SQL database. It seems that RDO is not
working in TS environment. There must be some fix but I can't find. If anyone
has any knowledge, please help
 
Looks like Microsoft people are clueless about TS and RDO/ODBC.

"himshah" wrote:

> We have application that runs with RDO/ODBC connection. The application works
> fine in client/server environment in LAN. We know that other locaiton has
> same applicaiton running with TS client.
>
> Our location, it failes to open the SQL database. It seems that RDO is not
> working in TS environment. There must be some fix but I can't find. If anyone
> has any knowledge, please help
 
Most people posting in this newsgroup are not MS employees, but people
like myself who are doing it in their spare time, voluntarily and free
of charge.

Please keep this in mind when posting to newsgroups. And be a bit more
specific about your problem.

Helge

On 18 Jul., 17:00, himshah <hims...@discussions.microsoft.com> wrote:
> Looks like Microsoft people are clueless about TS and RDO/ODBC.
>
> "himshah" wrote:
> > We have application that runs with RDO/ODBC connection. The application works
> > fine in client/server environment in LAN. We know that other locaiton has
> > same applicaiton running with TS client.
>
> > Our location, it failes to open the SQL database. It seems that RDO is not
> > working in TS environment. There must be some fix but I can't find. If anyone
> > has any knowledge, please help
 
Thanks for ??

"Helge Klein" wrote:

> Most people posting in this newsgroup are not MS employees, but people
> like myself who are doing it in their spare time, voluntarily and free
> of charge.
>
> Please keep this in mind when posting to newsgroups. And be a bit more
> specific about your problem.
>
> Helge
>
> On 18 Jul., 17:00, himshah <hims...@discussions.microsoft.com> wrote:
> > Looks like Microsoft people are clueless about TS and RDO/ODBC.
> >
> > "himshah" wrote:
> > > We have application that runs with RDO/ODBC connection. The application works
> > > fine in client/server environment in LAN. We know that other locaiton has
> > > same applicaiton running with TS client.
> >
> > > Our location, it failes to open the SQL database. It seems that RDO is not
> > > working in TS environment. There must be some fix but I can't find. If anyone
> > > has any knowledge, please help
>
>
>
 
Did I say volunteer is clueless? No I said Microsoft is clueless. Microsoft
is also watching this news group. Microsoft manges the group and has link to
their website for support. They benefit from us the volunteer. I think they
should be looking to non responsive post.

I am not sure what part of my questions you did not understood.

"Helge Klein" wrote:

> Most people posting in this newsgroup are not MS employees, but people
> like myself who are doing it in their spare time, voluntarily and free
> of charge.
>
> Please keep this in mind when posting to newsgroups. And be a bit more
> specific about your problem.
>
> Helge
>
> On 18 Jul., 17:00, himshah <hims...@discussions.microsoft.com> wrote:
> > Looks like Microsoft people are clueless about TS and RDO/ODBC.
> >
> > "himshah" wrote:
> > > We have application that runs with RDO/ODBC connection. The application works
> > > fine in client/server environment in LAN. We know that other locaiton has
> > > same applicaiton running with TS client.
> >
> > > Our location, it failes to open the SQL database. It seems that RDO is not
> > > working in TS environment. There must be some fix but I can't find. If anyone
> > > has any knowledge, please help
>
>
>
 
Like Helge, I didn't reply to your post because of the lack of
information to go on.
In what way does your application "fail to open the SQL database"?
Is there any error message? On the TS or on the SQL server?
Are there any errors or warnings in the EventLog / SQL log?
Did you enable tracing in the ODBC manager?
Anything in the ODBC logfile?
Is this a homegrown application, or a commercial one? If
commercial, have you contacted the vendor? Can you give us a
website for the application / vendor?
Was the Terminal Server put into "install mode" before installing
the application and all it's components?
Does it fail for all users, or does it work for Administrators?
Does it work when you run the application on the console of the
Terminal Server?
_________________________________________________________
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?aGltc2hhaA==?= <himshah@discussions.microsoft.com> wrote
on 19 jul 2007 in microsoft.public.windows.terminal_services:

>
> Did I say volunteer is clueless? No I said Microsoft is
> clueless. Microsoft is also watching this news group. Microsoft
> manges the group and has link to their website for support. They
> benefit from us the volunteer. I think they should be looking to
> non responsive post.
>
> I am not sure what part of my questions you did not understood.
>
> "Helge Klein" wrote:
>
>> Most people posting in this newsgroup are not MS employees, but
>> people like myself who are doing it in their spare time,
>> voluntarily and free of charge.
>>
>> Please keep this in mind when posting to newsgroups. And be a
>> bit more specific about your problem.
>>
>> Helge
>>
>> On 18 Jul., 17:00, himshah <hims...@discussions.microsoft.com>
>> wrote:
>> > Looks like Microsoft people are clueless about TS and
>> > RDO/ODBC.
>> >
>> > "himshah" wrote:
>> > > We have application that runs with RDO/ODBC connection. The
>> > > application works fine in client/server environment in LAN.
>> > > We know that other locaiton has same applicaiton running
>> > > with TS client.
>> >
>> > > Our location, it failes to open the SQL database. It seems
>> > > that RDO is not working in TS environment. There must be
>> > > some fix but I can't find. If anyone has any knowledge,
>> > > please help
 
Thanks for your question. I can try to answer.
Error is on TS client but no message. If I go to ODBC setup, I connect to
database. When I run the apps that uses the ODBC, it fails. What I was told
by app provider that they use RDO with ODBC. ODBC connection is fine but RDO
fails. This works perfectly fine in Client server environment on Local LAN.

No error on SQL server

ODBC trace - I cannot locate but I will try that today.

No error/warning in event log

Application is custom apps provided by software vendor. It is not homegrown
and it works for us in CS environment and many other locaiton. We know that
another client has this working on TS setup so there is something with our
setup.

It fails for all TS clients. We are just setting up TS now. It works fine in
our LAN.

It fails on TS console

I will report to you ODBC tracer report if I can find where to run it. I am
assuming that it is located in ODBC setup option.

Thanks for your guidance. I was not upset with all volunteer but more upset
with MS for not having any info on technet/msdn and not looking at the post
here.



"Vera Noest [MVP]" wrote:

> Like Helge, I didn't reply to your post because of the lack of
> information to go on.
> In what way does your application "fail to open the SQL database"?
> Is there any error message? On the TS or on the SQL server?
> Are there any errors or warnings in the EventLog / SQL log?
> Did you enable tracing in the ODBC manager?
> Anything in the ODBC logfile?
> Is this a homegrown application, or a commercial one? If
> commercial, have you contacted the vendor? Can you give us a
> website for the application / vendor?
> Was the Terminal Server put into "install mode" before installing
> the application and all it's components?
> Does it fail for all users, or does it work for Administrators?
> Does it work when you run the application on the console of the
> Terminal Server?
> _________________________________________________________
> 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?aGltc2hhaA==?= <himshah@discussions.microsoft.com> wrote
> on 19 jul 2007 in microsoft.public.windows.terminal_services:
>
> >
> > Did I say volunteer is clueless? No I said Microsoft is
> > clueless. Microsoft is also watching this news group. Microsoft
> > manges the group and has link to their website for support. They
> > benefit from us the volunteer. I think they should be looking to
> > non responsive post.
> >
> > I am not sure what part of my questions you did not understood.
> >
> > "Helge Klein" wrote:
> >
> >> Most people posting in this newsgroup are not MS employees, but
> >> people like myself who are doing it in their spare time,
> >> voluntarily and free of charge.
> >>
> >> Please keep this in mind when posting to newsgroups. And be a
> >> bit more specific about your problem.
> >>
> >> Helge
> >>
> >> On 18 Jul., 17:00, himshah <hims...@discussions.microsoft.com>
> >> wrote:
> >> > Looks like Microsoft people are clueless about TS and
> >> > RDO/ODBC.
> >> >
> >> > "himshah" wrote:
> >> > > We have application that runs with RDO/ODBC connection. The
> >> > > application works fine in client/server environment in LAN.
> >> > > We know that other locaiton has same applicaiton running
> >> > > with TS client.
> >> >
> >> > > Our location, it failes to open the SQL database. It seems
> >> > > that RDO is not working in TS environment. There must be
> >> > > some fix but I can't find. If anyone has any knowledge,
> >> > > please help
>
 
You can enable ODBC tracing in Start - All programs -
Administrative tools - ODBC

Since the application also fails when run on the physical console
of the server, your problem has nothing to do with Terminal
Services.
Since the software seems commercial, your best source of
information and help is the vendor. And since the problem isn't
Terminal Services related at all, I think that you can get better
help in other newsgroups (I had to Google for RDO to see what it
means).

_________________________________________________________
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?aGltc2hhaA==?= <himshah@discussions.microsoft.com> wrote
on 20 jul 2007 in microsoft.public.windows.terminal_services:

> Thanks for your question. I can try to answer.
> Error is on TS client but no message. If I go to ODBC setup, I
> connect to database. When I run the apps that uses the ODBC, it
> fails. What I was told by app provider that they use RDO with
> ODBC. ODBC connection is fine but RDO fails. This works
> perfectly fine in Client server environment on Local LAN.
>
> No error on SQL server
>
> ODBC trace - I cannot locate but I will try that today.
>
> No error/warning in event log
>
> Application is custom apps provided by software vendor. It is
> not homegrown and it works for us in CS environment and many
> other locaiton. We know that another client has this working on
> TS setup so there is something with our setup.
>
> It fails for all TS clients. We are just setting up TS now. It
> works fine in our LAN.
>
> It fails on TS console
>
> I will report to you ODBC tracer report if I can find where to
> run it. I am assuming that it is located in ODBC setup option.
>
> Thanks for your guidance. I was not upset with all volunteer but
> more upset with MS for not having any info on technet/msdn and
> not looking at the post here.
>
>
>
> "Vera Noest [MVP]" wrote:
>
>> Like Helge, I didn't reply to your post because of the lack of
>> information to go on.
>> In what way does your application "fail to open the SQL
>> database"? Is there any error message? On the TS or on the SQL
>> server? Are there any errors or warnings in the EventLog / SQL
>> log? Did you enable tracing in the ODBC manager?
>> Anything in the ODBC logfile?
>> Is this a homegrown application, or a commercial one? If
>> commercial, have you contacted the vendor? Can you give us a
>> website for the application / vendor?
>> Was the Terminal Server put into "install mode" before
>> installing the application and all it's components?
>> Does it fail for all users, or does it work for Administrators?
>> Does it work when you run the application on the console of the
>> Terminal Server?
>> _________________________________________________________
>> 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?aGltc2hhaA==?= <himshah@discussions.microsoft.com>
>> wrote on 19 jul 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> >
>> > Did I say volunteer is clueless? No I said Microsoft is
>> > clueless. Microsoft is also watching this news group.
>> > Microsoft manges the group and has link to their website for
>> > support. They benefit from us the volunteer. I think they
>> > should be looking to non responsive post.
>> >
>> > I am not sure what part of my questions you did not
>> > understood.
>> >
>> > "Helge Klein" wrote:
>> >
>> >> Most people posting in this newsgroup are not MS employees,
>> >> but people like myself who are doing it in their spare time,
>> >> voluntarily and free of charge.
>> >>
>> >> Please keep this in mind when posting to newsgroups. And be
>> >> a bit more specific about your problem.
>> >>
>> >> Helge
>> >>
>> >> On 18 Jul., 17:00, himshah
>> >> <hims...@discussions.microsoft.com> wrote:
>> >> > Looks like Microsoft people are clueless about TS and
>> >> > RDO/ODBC.
>> >> >
>> >> > "himshah" wrote:
>> >> > > We have application that runs with RDO/ODBC connection.
>> >> > > The application works fine in client/server environment
>> >> > > in LAN. We know that other locaiton has same applicaiton
>> >> > > running with TS client.
>> >> >
>> >> > > Our location, it failes to open the SQL database. It
>> >> > > seems that RDO is not working in TS environment. There
>> >> > > must be some fix but I can't find. If anyone has any
>> >> > > knowledge, please help
 
Thanks. I am going to try tracing odbc. I am not sure where else I can post
but I will try in SQL newsgroup.

"Vera Noest [MVP]" wrote:

> You can enable ODBC tracing in Start - All programs -
> Administrative tools - ODBC
>
> Since the application also fails when run on the physical console
> of the server, your problem has nothing to do with Terminal
> Services.
> Since the software seems commercial, your best source of
> information and help is the vendor. And since the problem isn't
> Terminal Services related at all, I think that you can get better
> help in other newsgroups (I had to Google for RDO to see what it
> means).
>
> _________________________________________________________
> 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?aGltc2hhaA==?= <himshah@discussions.microsoft.com> wrote
> on 20 jul 2007 in microsoft.public.windows.terminal_services:
>
> > Thanks for your question. I can try to answer.
> > Error is on TS client but no message. If I go to ODBC setup, I
> > connect to database. When I run the apps that uses the ODBC, it
> > fails. What I was told by app provider that they use RDO with
> > ODBC. ODBC connection is fine but RDO fails. This works
> > perfectly fine in Client server environment on Local LAN.
> >
> > No error on SQL server
> >
> > ODBC trace - I cannot locate but I will try that today.
> >
> > No error/warning in event log
> >
> > Application is custom apps provided by software vendor. It is
> > not homegrown and it works for us in CS environment and many
> > other locaiton. We know that another client has this working on
> > TS setup so there is something with our setup.
> >
> > It fails for all TS clients. We are just setting up TS now. It
> > works fine in our LAN.
> >
> > It fails on TS console
> >
> > I will report to you ODBC tracer report if I can find where to
> > run it. I am assuming that it is located in ODBC setup option.
> >
> > Thanks for your guidance. I was not upset with all volunteer but
> > more upset with MS for not having any info on technet/msdn and
> > not looking at the post here.
> >
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Like Helge, I didn't reply to your post because of the lack of
> >> information to go on.
> >> In what way does your application "fail to open the SQL
> >> database"? Is there any error message? On the TS or on the SQL
> >> server? Are there any errors or warnings in the EventLog / SQL
> >> log? Did you enable tracing in the ODBC manager?
> >> Anything in the ODBC logfile?
> >> Is this a homegrown application, or a commercial one? If
> >> commercial, have you contacted the vendor? Can you give us a
> >> website for the application / vendor?
> >> Was the Terminal Server put into "install mode" before
> >> installing the application and all it's components?
> >> Does it fail for all users, or does it work for Administrators?
> >> Does it work when you run the application on the console of the
> >> Terminal Server?
> >> _________________________________________________________
> >> 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?aGltc2hhaA==?= <himshah@discussions.microsoft.com>
> >> wrote on 19 jul 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> >
> >> > Did I say volunteer is clueless? No I said Microsoft is
> >> > clueless. Microsoft is also watching this news group.
> >> > Microsoft manges the group and has link to their website for
> >> > support. They benefit from us the volunteer. I think they
> >> > should be looking to non responsive post.
> >> >
> >> > I am not sure what part of my questions you did not
> >> > understood.
> >> >
> >> > "Helge Klein" wrote:
> >> >
> >> >> Most people posting in this newsgroup are not MS employees,
> >> >> but people like myself who are doing it in their spare time,
> >> >> voluntarily and free of charge.
> >> >>
> >> >> Please keep this in mind when posting to newsgroups. And be
> >> >> a bit more specific about your problem.
> >> >>
> >> >> Helge
> >> >>
> >> >> On 18 Jul., 17:00, himshah
> >> >> <hims...@discussions.microsoft.com> wrote:
> >> >> > Looks like Microsoft people are clueless about TS and
> >> >> > RDO/ODBC.
> >> >> >
> >> >> > "himshah" wrote:
> >> >> > > We have application that runs with RDO/ODBC connection.
> >> >> > > The application works fine in client/server environment
> >> >> > > in LAN. We know that other locaiton has same applicaiton
> >> >> > > running with TS client.
> >> >> >
> >> >> > > Our location, it failes to open the SQL database. It
> >> >> > > seems that RDO is not working in TS environment. There
> >> >> > > must be some fix but I can't find. If anyone has any
> >> >> > > knowledge, please help
>
 
Back
Top