Connecting Tech Pros Worldwide Help | Site Map
 
 
LinkBack Thread Tools Search this Thread
  #1  
Old November 12th, 2005, 07:26 AM
Development at American Savings
Guest
 
Posts: n/a
Default connect db2 7.1 os/2 warp 3 connect to Win2k

I'm having some trouble being able to connect to my db2 server (it lives on
an os/2 warp 3 connect box) from my Windows2000 workstation using vs.net
2003. Any suggestions?

I have a local user account on the server "readonly", i have created a user
in the database of "readonly" and I can connect through the command line,
but from within visual studio .net 2003 I cannot make a connection. Better
stated: I can make a connection but I cannot create data adapters - I can't
get any data from that connection.

I can see it in my server explorer, I can browse the tables and fields, but
as soon as i try to drag some fields onto my form it asks for my username
and password, which I enter, and then I get the following error:
"ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
supplied is incorrect.
SQLSTATE=08004

ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr
failed."

I'm going crazy - what am i doing wrong?


  #2  
Old November 12th, 2005, 07:26 AM
Mark Yudkin
Guest
 
Posts: n/a
Default Re: connect db2 7.1 os/2 warp 3 connect to Win2k

"Development at American Savings" <dev@americansavingslife.com> wrote in
message news:10aikf73a1cq0a@corp.supernews.com...[color=blue]
> I'm having some trouble being able to connect to my db2 server (it lives[/color]
on[color=blue]
> an os/2 warp 3 connect box) from my Windows2000 workstation using vs.net
> 2003. Any suggestions?[/color]


AFAIK, this is not a supported combination; in any case, I would not expect
it to work. To start with, DB2 for OS/2 does not support ODBC V3 or later;
DB2's ODBC support is frozen at V2.5,. That at a minumum should be
sufficient to cause your second "error" (server doesn't support ODBC API).

You will need to use an API that is supported by DB2 for OS/2 V7.1, such as
native CLI. That means, ADO.NET is out. Alternatively, since DB2 for OS/2 is
frozen, it may be time to consider transitioning away from OS/2 to a
platform with DB2 V8 support, including support for the client API you wish
to use (see http://www.ibm.com/software/os/warp/strategy/).
[color=blue]
>
> I have a local user account on the server "readonly", i have created a[/color]
user[color=blue]
> in the database of "readonly" and I can connect through the command line,
> but from within visual studio .net 2003 I cannot make a connection.[/color]
Better[color=blue]
> stated: I can make a connection but I cannot create data adapters - I[/color]
can't[color=blue]
> get any data from that connection.
>
> I can see it in my server explorer, I can browse the tables and fields,[/color]
but[color=blue]
> as soon as i try to drag some fields onto my form it asks for my username
> and password, which I enter, and then I get the following error:
> "ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
> supplied is incorrect.
> SQLSTATE=08004
>
> ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr
> failed."
>
> I'm going crazy - what am i doing wrong?
>
>[/color]


  #3  
Old November 12th, 2005, 07:26 AM
Development at American Savings
Guest
 
Posts: n/a
Default Re: connect db2 7.1 os/2 warp 3 connect to Win2k

Isn't there some second opinion - some way to make it work??? Any types of
workarounds or anything?


"Mark Yudkin" <myudkinATcompuserveDOTcom@nospam.org> wrote in message
news:c8c8hs$mv3$1@ngspool-d02.news.aol.com...[color=blue]
> "Development at American Savings" <dev@americansavingslife.com> wrote in
> message news:10aikf73a1cq0a@corp.supernews.com...[color=green]
> > I'm having some trouble being able to connect to my db2 server (it lives[/color]
> on[color=green]
> > an os/2 warp 3 connect box) from my Windows2000 workstation using vs.net
> > 2003. Any suggestions?[/color]
>
>
> AFAIK, this is not a supported combination; in any case, I would not[/color]
expect[color=blue]
> it to work. To start with, DB2 for OS/2 does not support ODBC V3 or later;
> DB2's ODBC support is frozen at V2.5,. That at a minumum should be
> sufficient to cause your second "error" (server doesn't support ODBC API).
>
> You will need to use an API that is supported by DB2 for OS/2 V7.1, such[/color]
as[color=blue]
> native CLI. That means, ADO.NET is out. Alternatively, since DB2 for OS/2[/color]
is[color=blue]
> frozen, it may be time to consider transitioning away from OS/2 to a
> platform with DB2 V8 support, including support for the client API you[/color]
wish[color=blue]
> to use (see http://www.ibm.com/software/os/warp/strategy/).
>[color=green]
> >
> > I have a local user account on the server "readonly", i have created a[/color]
> user[color=green]
> > in the database of "readonly" and I can connect through the command[/color][/color]
line,[color=blue][color=green]
> > but from within visual studio .net 2003 I cannot make a connection.[/color]
> Better[color=green]
> > stated: I can make a connection but I cannot create data adapters - I[/color]
> can't[color=green]
> > get any data from that connection.
> >
> > I can see it in my server explorer, I can browse the tables and fields,[/color]
> but[color=green]
> > as soon as i try to drag some fields onto my form it asks for my[/color][/color]
username[color=blue][color=green]
> > and password, which I enter, and then I get the following error:
> > "ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
> > supplied is incorrect.
> > SQLSTATE=08004
> >
> > ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr
> > failed."
> >
> > I'm going crazy - what am i doing wrong?
> >
> >[/color]
>
>[/color]


  #4  
Old November 12th, 2005, 07:26 AM
Mark Yudkin
Guest
 
Posts: n/a
Default Re: connect db2 7.1 os/2 warp 3 connect to Win2k

Will the the IBM DD2 documentation serve as confirmation?

"The DB2 .NET Data Provider allows your .NET applications to access Version
8 DB2 Universal Database on Windows, UNIX, and Linux-based computers, and
Version 6 and Version 7 of DB2 Universal Database for OS/390 and z/OS via
DB2 Connect. "

You are using none of these servers

Full details are in the Application Development section of Concept, under
APIs - Windows - DB2 .NET.

The only "workaround" is to use a supported API. This means you cannot use
an API not supported by your DB2 for OS/2 V7 server.

"Development at American Savings" <dev@americansavingslife.com> wrote in
message news:10akk1spjfc7049@corp.supernews.com...[color=blue]
> Isn't there some second opinion - some way to make it work??? Any types[/color]
of[color=blue]
> workarounds or anything?
>
>
> "Mark Yudkin" <myudkinATcompuserveDOTcom@nospam.org> wrote in message
> news:c8c8hs$mv3$1@ngspool-d02.news.aol.com...[color=green]
> > "Development at American Savings" <dev@americansavingslife.com> wrote in
> > message news:10aikf73a1cq0a@corp.supernews.com...[color=darkred]
> > > I'm having some trouble being able to connect to my db2 server (it[/color][/color][/color]
lives[color=blue][color=green]
> > on[color=darkred]
> > > an os/2 warp 3 connect box) from my Windows2000 workstation using[/color][/color][/color]
vs.net[color=blue][color=green][color=darkred]
> > > 2003. Any suggestions?[/color]
> >
> >
> > AFAIK, this is not a supported combination; in any case, I would not[/color]
> expect[color=green]
> > it to work. To start with, DB2 for OS/2 does not support ODBC V3 or[/color][/color]
later;[color=blue][color=green]
> > DB2's ODBC support is frozen at V2.5,. That at a minumum should be
> > sufficient to cause your second "error" (server doesn't support ODBC[/color][/color]
API).[color=blue][color=green]
> >
> > You will need to use an API that is supported by DB2 for OS/2 V7.1, such[/color]
> as[color=green]
> > native CLI. That means, ADO.NET is out. Alternatively, since DB2 for[/color][/color]
OS/2[color=blue]
> is[color=green]
> > frozen, it may be time to consider transitioning away from OS/2 to a
> > platform with DB2 V8 support, including support for the client API you[/color]
> wish[color=green]
> > to use (see http://www.ibm.com/software/os/warp/strategy/).
> >[color=darkred]
> > >
> > > I have a local user account on the server "readonly", i have created a[/color]
> > user[color=darkred]
> > > in the database of "readonly" and I can connect through the command[/color][/color]
> line,[color=green][color=darkred]
> > > but from within visual studio .net 2003 I cannot make a connection.[/color]
> > Better[color=darkred]
> > > stated: I can make a connection but I cannot create data adapters - I[/color]
> > can't[color=darkred]
> > > get any data from that connection.
> > >
> > > I can see it in my server explorer, I can browse the tables and[/color][/color][/color]
fields,[color=blue][color=green]
> > but[color=darkred]
> > > as soon as i try to drag some fields onto my form it asks for my[/color][/color]
> username[color=green][color=darkred]
> > > and password, which I enter, and then I get the following error:
> > > "ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
> > > supplied is incorrect.
> > > SQLSTATE=08004
> > >
> > > ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's[/color][/color][/color]
SQLSetConnectAttr[color=blue][color=green][color=darkred]
> > > failed."
> > >
> > > I'm going crazy - what am i doing wrong?
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]


  #5  
Old November 12th, 2005, 07:27 AM
Development at American Savings
Guest
 
Posts: n/a
Default Re: connect db2 7.1 os/2 warp 3 connect to Win2k

Fair enough. I sure appreciate your help.


"Mark Yudkin" <myudkinATcompuserveDOTcom@nospam.org> wrote in message
news:c8f1ta$sm3$1@ngspool-d02.news.aol.com...[color=blue]
> Will the the IBM DD2 documentation serve as confirmation?
>
> "The DB2 .NET Data Provider allows your .NET applications to access[/color]
Version[color=blue]
> 8 DB2 Universal Database on Windows, UNIX, and Linux-based computers, and
> Version 6 and Version 7 of DB2 Universal Database for OS/390 and z/OS via
> DB2 Connect. "
>
> You are using none of these servers
>
> Full details are in the Application Development section of Concept, under
> APIs - Windows - DB2 .NET.
>
> The only "workaround" is to use a supported API. This means you cannot use
> an API not supported by your DB2 for OS/2 V7 server.
>
> "Development at American Savings" <dev@americansavingslife.com> wrote in
> message news:10akk1spjfc7049@corp.supernews.com...[color=green]
> > Isn't there some second opinion - some way to make it work??? Any types[/color]
> of[color=green]
> > workarounds or anything?
> >
> >
> > "Mark Yudkin" <myudkinATcompuserveDOTcom@nospam.org> wrote in message
> > news:c8c8hs$mv3$1@ngspool-d02.news.aol.com...[color=darkred]
> > > "Development at American Savings" <dev@americansavingslife.com> wrote[/color][/color][/color]
in[color=blue][color=green][color=darkred]
> > > message news:10aikf73a1cq0a@corp.supernews.com...
> > > > I'm having some trouble being able to connect to my db2 server (it[/color][/color]
> lives[color=green][color=darkred]
> > > on
> > > > an os/2 warp 3 connect box) from my Windows2000 workstation using[/color][/color]
> vs.net[color=green][color=darkred]
> > > > 2003. Any suggestions?
> > >
> > >
> > > AFAIK, this is not a supported combination; in any case, I would not[/color]
> > expect[color=darkred]
> > > it to work. To start with, DB2 for OS/2 does not support ODBC V3 or[/color][/color]
> later;[color=green][color=darkred]
> > > DB2's ODBC support is frozen at V2.5,. That at a minumum should be
> > > sufficient to cause your second "error" (server doesn't support ODBC[/color][/color]
> API).[color=green][color=darkred]
> > >
> > > You will need to use an API that is supported by DB2 for OS/2 V7.1,[/color][/color][/color]
such[color=blue][color=green]
> > as[color=darkred]
> > > native CLI. That means, ADO.NET is out. Alternatively, since DB2 for[/color][/color]
> OS/2[color=green]
> > is[color=darkred]
> > > frozen, it may be time to consider transitioning away from OS/2 to a
> > > platform with DB2 V8 support, including support for the client API you[/color]
> > wish[color=darkred]
> > > to use (see http://www.ibm.com/software/os/warp/strategy/).
> > >
> > > >
> > > > I have a local user account on the server "readonly", i have created[/color][/color][/color]
a[color=blue][color=green][color=darkred]
> > > user
> > > > in the database of "readonly" and I can connect through the command[/color]
> > line,[color=darkred]
> > > > but from within visual studio .net 2003 I cannot make a connection.
> > > Better
> > > > stated: I can make a connection but I cannot create data adapters -[/color][/color][/color]
I[color=blue][color=green][color=darkred]
> > > can't
> > > > get any data from that connection.
> > > >
> > > > I can see it in my server explorer, I can browse the tables and[/color][/color]
> fields,[color=green][color=darkred]
> > > but
> > > > as soon as i try to drag some fields onto my form it asks for my[/color]
> > username[color=darkred]
> > > > and password, which I enter, and then I get the following error:
> > > > "ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
> > > > supplied is incorrect.
> > > > SQLSTATE=08004
> > > >
> > > > ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's[/color][/color]
> SQLSetConnectAttr[color=green][color=darkred]
> > > > failed."
> > > >
> > > > I'm going crazy - what am i doing wrong?
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]


 

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Popular Articles

What is Bytes?

We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights. Get the best answers to your questions from over 205,248 network members.