Re: Can't connect error
From: JeffO (anonymous_at_discussions.microsoft.com)
Date: 03/03/04
- Next message: Tian Min Huang: "RE: MS SQL Server 2000 ODBC driver crash"
- Previous message: Jason Hinsperger: "MS SQL Server 2000 ODBC driver crash"
- In reply to: Frank Hickman: "Re: Can't connect error"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 3 Mar 2004 13:58:57 -0800
Yes, our machines not only have the Oracle client, in
order to work with our JDE, they have to have the
full "Programmer" install of Oracle. So they have far
more Oracle than necessary for the ODBC stuff.
Although we have JDE available through terminal server,
the user in question has the "Fat client" production
package installed and running from his PC. (The same
package everyone else has.)
I'm beginning to think this is caused by the way the JDE
people have the ODBC stuff set up. Maybe something has
changed. They don't always tell us when they change
things.
As for trying different drivers, we've tried that.
Outside of Denver Water, we're advised that we should be
able to connect with Oracle, MS, or JDE drivers. But our
JDE admins tell us that's not true. So I think they've
done something that makes this different.
Our Oracle database admin told me "there's no such thing
as an expert in ODBC's". This is a mess.
>-----Original Message-----
>You might try using the Oracle ODBC driver, not the
Microsoft one.
>Something else, even with those drivers, if you do not
have the Oracle
>client software on the machine, it will not work...at
least for us. If you
>do not have the Oracle ODBC driver then install the
Oracle Client on the
>machine. Then change the DSN to that driver.
>
>HTH
>--
>============
>Frank Hickman
>NobleSoft, Inc.
>============
>Replace the _nosp@m_ with @ to reply.
>
>
>"JeffO" <anonymous@discussions.microsoft.com> wrote in
message
>news:30f701c400ad$5f1a0720$a601280a@phx.gbl...
>> I have a situation where, in addition to all the
hardware
>> and software I have to support, I also have to get all
>> the ODBC's set up for my area. (Hard to be good at
>> something when you don't use things like that.)
>> The problem started with a program called ACL. It asks
>> JDEdwards for data. JDE asks Oracle for data. Somewhere
>> in there the "Microsoft for Oracle" ODBC driver gets
>> called. ACL gave the error "Can't connect ot JDE".
>>
>> Tried to use Excel to test. When attempting to "Get
>> external", Excel also says, "Can't connect to JDE". So
>> the problem isn't ACL. The JDE people say that if you
can
>> log onto JDE, JDE isn't the problem. They say if you
>> can't connect in Excel, Windows has something wrong.
>>
>> Oracle SQLPLUS has no trouble connecting to JDE, and
the
>> JDE application has no trouble connecting from that
>> machine. Other people have no trouble connecting from
>> their machines.
>>
>> There are no errors in the Event Logs.
>> There are no Dr Watsons.
>> The performance of the machine and all indicators are
>> that it is in top operational condition.
>> But there must be something wrong or missing if other
>> machines connect just fine. The other machines have the
>> exact same ODBCs. The spelling and case of each ODBC is
>> exact.
>>
>> Windows 2000 SP4 (with ALL the patches)
>> MDAC2.8
>> Office XP (with all Office updates)
>>
>> Any help anyone could give would be appreciated.
>
>
>.
>
- Next message: Tian Min Huang: "RE: MS SQL Server 2000 ODBC driver crash"
- Previous message: Jason Hinsperger: "MS SQL Server 2000 ODBC driver crash"
- In reply to: Frank Hickman: "Re: Can't connect error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
