By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,638 Members | 2,204 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,638 IT Pros & Developers. It's quick & easy.

ODBC -- call failed Error

P: n/a
I have an Access 2000 database that links several tables from Oracle 9.
For some reason or another, one of our user repeatedly gets the
following error when accessing queries within this database:
************************************************** **********************************
ODBC -call failed.

[Oracle][ODBC]ORA-01017: invalid username/password; logon denied
(#1017)[Microsoft][ODBC Driver Manger] Driver's SQLSetConnectAttr
failed IM006 0 [Microsoft][ODBC Driver Manager] Driver's
SQLSetConnectAttr failed (#0)

************************************************** **********************************
I can access this database with no problems. When I try to recreate a
new database for her and re-link these table it seems to work okay for
several try and the error would pop-up again. It looks like this error
is specific to her machine. Anyone know why or how to fix this
problem? She's had problem with this error for all of her access
databases that are connecting to an Oracle server. Any information
would be appreciated.

Jan 12 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a

alegria4ever wrote:
I have an Access 2000 database that links several tables from Oracle 9.
For some reason or another, one of our user repeatedly gets the
following error when accessing queries within this database:
************************************************** **********************************
ODBC -call failed.

[Oracle][ODBC]ORA-01017: invalid username/password; logon denied
(#1017)[Microsoft][ODBC Driver Manger] Driver's SQLSetConnectAttr
failed IM006 0 [Microsoft][ODBC Driver Manager] Driver's
SQLSetConnectAttr failed (#0)
I have had similar problems with connecting to an MS SQL database. I
found that I had to create a login for the user in sql.

>
************************************************** **********************************
I can access this database with no problems. When I try to recreate a
new database for her and re-link these table it seems to work okay for
several try and the error would pop-up again. It looks like this error
is specific to her machine. Anyone know why or how to fix this
problem? She's had problem with this error for all of her access
databases that are connecting to an Oracle server. Any information
would be appreciated.
Another issue could be that you do not have the ODBC setup under system
dsn.

Jan 12 '07 #2

P: n/a
alegria4ever wrote:
[Oracle][ODBC]ORA-01017: invalid username/password; logon denied
(#1017)[Microsoft][ODBC Driver Manger] Driver's SQLSetConnectAttr
failed IM006 0 [Microsoft][ODBC Driver Manager] Driver's
SQLSetConnectAttr failed (#0)
Looks like you're using the MS Oracle driver. Try the Oracle driver.

The error message seems to indicate that the password for the Oracle
user is not correct. Have you examined the DSN she is using? Most
important, does tnsnames.ora have the correctnet service name set up on
the machine for her user name?
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Jan 14 '07 #3

P: n/a
Yes, I have examed her DSN and even replicated the one on my machine to
hers. That didn't fix the problem either. The password she's using is
correct, we've tested that many times. I think the tnsnames.ora file
is correct because she was able to access the database with no problems
for several times.

Tim Marshall wrote:
alegria4ever wrote:
[Oracle][ODBC]ORA-01017: invalid username/password; logon denied
(#1017)[Microsoft][ODBC Driver Manger] Driver's SQLSetConnectAttr
failed IM006 0 [Microsoft][ODBC Driver Manager] Driver's
SQLSetConnectAttr failed (#0)

Looks like you're using the MS Oracle driver. Try the Oracle driver.

The error message seems to indicate that the password for the Oracle
user is not correct. Have you examined the DSN she is using? Most
important, does tnsnames.ora have the correctnet service name set up on
the machine for her user name?
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Jan 16 '07 #4

P: n/a
alegria4ever wrote:
Yes, I have examed her DSN and even replicated the one on my machine to
hers. That didn't fix the problem either. The password she's using is
correct, we've tested that many times. I think the tnsnames.ora file
is correct because she was able to access the database with no problems
for several times.
What I would do next then, is repeat the problem on her machine, ie,
relink the tables and then work the app for several tries until the
ora-01017 error occurs again. As soon as it does, on her machine, open
SQL Plus (I always make sure I install this on my users' machines along
with the Oracle net client and the Oracle ODBC driver - if you don't
have it on her machine, it can be installed from the Oracle set up cd)
using the same user name used by the DSN and the password. If this
latter action causes problems, then it's something to do with the net
client installation, a conflict or something and you're into Oracle
territory I don't usually tread (or troubleshoot, at least). Another
possible alternative to testing with SQL Plus is tnsping (but I haven't
done this since it used to be done at the command prompt in Oracle
7.3.4, so I don't remember how to do it).

Anyway, if SQL Plus connects to the database/user name successfully,
then there's something screwy with Access 2000 and again, I'm sorry, I'm
out of my area of expertise (I went from A97 to A2003 and didn't use
either 2000 or 2002).

Hope this is of some help, at least for further trouble shooting. 8)
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me
Jan 16 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.