I will like to get some help in knowing where i am going wrong in the deloyment of my asp.net website. I am able to view the data on my production machine but when I send the data to the web server I get the following error . The database is an access database
with a link Manager to a DNS i Series Access ODBC Driver
ODBC--connection to 'PFW Test' failed.
Description:
An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.OleDb.OleDbException: ODBC--connection to 'PFW Test' failed. Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I am new to all this and I know the two enviroments are different . The deployment is running on a 2003 and the production is 2008 . Can you help me let me know what you need to know . I know for sure that i had to convert the database to 2000 on the
deloypment enviorment .
If you are experiencing : "The 'Microsoft.Jet.Oldedb.4.0' provider is not registered on the local machine." kind of error due your 64 bit machine, HERE IS THE
SOLUTION ... !
please convert your Target Framework from "Any CPU" to "x86" in project properties and make sure the same by right clicking solution and going to "Configuration Manager"
OR
Installing 2007 / 2010 Office System Driver: Data Connectivity Components (2007 /
2010 )
With the 2nd alternative you may want to change the Provider argument of the ConnectionString property to “Microsoft.ACE.OLEDB.12.0”
natalieo
0 Points
3 Posts
ODBC--connection to''failed.
Nov 26, 2012 05:05 PM|LINK
I will like to get some help in knowing where i am going wrong in the deloyment of my asp.net website. I am able to view the data on my production machine but when I send the data to the web server I get the following error . The database is an access database with a link Manager to a DNS i Series Access ODBC Driver
ODBC--connection to 'PFW Test' failed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.OleDb.OleDbException: ODBC--connection to 'PFW Test' failed.
Source Error:
Stack Trace:
aarsh
Participant
1543 Points
427 Posts
Re: ODBC--connection to''failed.
Nov 26, 2012 09:07 PM|LINK
Can you please rpovide info for deployment environment and the production environment for
A) same hardware architecture (32-64 bit)
B) version of the MsOffice installed ( is 32 bit office intaleld on 64 bit amchine ?)
If that is not the case, please stare at your connection srting
otherwise, fi you are using Ms Access as your database, try :
natalieo
0 Points
3 Posts
Re: ODBC--connection to''failed.
Nov 26, 2012 10:38 PM|LINK
Hi aarsh ,
I am new to all this and I know the two enviroments are different . The deployment is running on a 2003 and the production is 2008 . Can you help me let me know what you need to know . I know for sure that i had to convert the database to 2000 on the deloypment enviorment .
aarsh
Participant
1543 Points
427 Posts
Re: ODBC--connection to''failed.
Nov 27, 2012 12:50 AM|LINK
What is the architecture of the dev machine and server ? ( 64 bit architecture or 32bit architecture ? )
Decker Dong ...
All-Star
118619 Points
18779 Posts
Re: ODBC--connection to''failed.
Nov 27, 2012 04:53 AM|LINK
If you are using Access2003 or below, you can try to use this connection (Make sure that you must have the Access Engine):
http://www.connectionstrings.com/access
But if you are using Access2003+ (Access2007/2010……), please try these connection strings:
http://www.connectionstrings.com/access-2007
aarsh
Participant
1543 Points
427 Posts
Re: ODBC--connection to''failed.
Nov 27, 2012 03:48 PM|LINK
If you are experiencing : "The 'Microsoft.Jet.Oldedb.4.0' provider is not registered on the local machine." kind of error due your 64 bit machine, HERE IS THE SOLUTION ... !
With the 2nd alternative you may want to change the Provider argument of the ConnectionString property to “Microsoft.ACE.OLEDB.12.0”