Link to home
Start Free TrialLog in
Avatar of Robert Hester
Robert Hester

asked on

ODBC Call Failed

Hello,

My enviroment:
- Win 2008 R2 64bits
-  Classic ASP application using Access 2003 database with linked tables on Oracle 11 database

I created a ODBC connection using the 32bits ODBC administrator.
When using these linked tables from within Access I can read/write fine on Oracle tables.
But when using the application, a ODBC Call Failed msg appears.
Where could the problem be?
a) with the aplication - which is created by ASPRunner code builder and works fine on several applications (including this one) using ODBC on a 32bits server ( as USER DSN). ASPRunner is said to be fully compatible with 64bits servers
b) with the 32bits ODBC issue on 64bits server
c) Permission related (when accessed by iusr?
d) Something else

I have no experience with 64bits servers so any help will be appreciated. My humble guess is that the OS is searching only for the 64bits ODBC connections. If so, where and how can I set this ? This is the only application to run on this server, so I don´t mind unabling 64bits connections if needed.
Thanks in advance,
Robert
ASKER CERTIFIED SOLUTION
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Robert Hester
Robert Hester

ASKER

Hi Jim,

1) ASP is running in 32bits....defined in App Pools of IIS
2) To create I used \sysWOW64. It works well when opening tables on Access user interface
3) I am the administrator to the server, but when I try accessing SYSTEM DSN on 32bits administrator, a msg appears saying I have non Admistraive privileges to create or modify System DSN. How do I get around this. What should I ask network Help Desk to workaround this?
4) Microsoft JET Dqatabase Engine error 80004005
ODBC - connection to 'ROBERT' failed.
I have read the link you passed and I guess rthe solution is there...but I have no ideas as how to even start (beginer). If you agree the solution is there somewhere, could you provide a step to step guideline for me?
Thanks
Robert
<<1) ASP is running in 32bits....defined in App Pools of IIS >>

  OK, so then you need to be using the ODBCad32.exe in the \sysWOW64 folder.

<<2) To create I used \sysWOW64. It works well when opening tables on Access user interface>>

   That's good and as long as ASP is running in 32 bit mode, then that should be fine.

<<3) I am the administrator to the server, but when I try accessing SYSTEM DSN on 32bits administrator, a msg appears saying I have non Admistraive privileges to create or modify System DSN. How do I get around this. What should I ask network Help Desk to workaround this?>>

  When you go to run it, make sure you right click and then select "run as administrator".


<<4) Microsoft JET Dqatabase Engine error 80004005>>

 Work through the DSN setup first and make sure that's good there.  If still an error, then most often it's that the account that ASP is connecting under does not have security for the directory where the DB resides.  Make sure it has modify permissions.

Jim.
3) Tried so and still same msg...

4) Exactly where is this defined? right clicking folder in explorer and defining permissions or within WEB SITES in IIS? And which users should be granted? IUSR and who else? Anyone else because of this odbc issue?
Sorry for the delay in getting back to this.

Take a run through the following, which should get you on the right track:

http://www.iis.net/learn/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/using-classic-asp-with-microsoft-access-databases-on-iis

 Originally I thought you were just having a problem with the DSN, but it looks like you have some type of a permissions problem.

 Let me know if that helps or not.  If not, I will find someone that knows more about classic ASP then I do.

Jim.
Jim, Thanks a lot...
What actually solved the problem was:

a) Creating a System DNS and not a User one

b) Renaming 32bits ODBC Driver and changing registry values to point to it.

Thanks,
Robert