MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

RE: Provider Strings for AS400 data on Windows Server 2008R2 64Bit



fixed

Are you sure you have the OLE DB drivers installed and registered? They are different than the ODBC drivers and you are specifying an OLE DB provider in your connection string.

coy

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Monday, October 22, 2012 11:52
To: Midrange Systems Technical Discussion
Subject: RE: Provider Strings for AS400 data on Windows Server 2008R2 64Bit

Sorry, Cory....I misunderstood.

Yes, I did go into the application pool and set the "Enable 32 bit applications" to TRUE. I stopped and started the server, but the message persists.

Thanks!

/b;

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Coy Krill
Sent: Monday, October 22, 2012 2:31 PM
To: Midrange Systems Technical Discussion
Subject: RE: Provider Strings for AS400 data on Windows Server 2008R2 64Bit

Is your website/app now 64 bit as well? Try setting enable 32bit applications in website connection pool, it's under the general secion.

coy

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Monday, October 22, 2012 11:23
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: Provider Strings for AS400 data on Windows Server 2008R2 64Bit

Hi All,

We're in the process of migrating our web pages from Windows Server 2003 32bit to Windows Server 2008r2 64bit. I've installed the 64bit ODBC drivers, IIS and all relative code for the website.

However, when I try to connect to the AS400 I am getting this error:

==========================

ADODB.Connection error '800a0e7a'

Provider cannot be found. It may not be properly installed.
==========================

I rechecked and ensured the driver was installed. I have these two drivers in the ODBC manager on the 2008r2 64bit server:

Name: Client Access ODBC Driver (32-bit)
Version: 12.64.00.00
Company: IBM Corporation
File: CWBODBC.DLL
Date: 11/12/2007

Name: iSeries Access ODBC Driver
Version: 12.64.00.00
Company: IBM Corporation
File: CWBODBC.DLL
Date: 11/12/2007


The connection string I am trying to use is this:
adoCon.Open "Provider=IBMDA400.DataSource.1;Persist Security Info=False;User ID=<user>;Password=<password>;Data Source=<AS400 IP Address>"

When I use the identical connect string on the old webserver I do not get any nasty errors. When I try on the new webserver, I get the one above.

Any ideas where I might be going wrong?? I've tried changing the connection strings, trying new drivers, etc., etc., but I end up with the same result (or some variant that is still not letting me connect).

Thankee-sai!

/b;

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Manager - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-5029
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com<http://www.simcoeparts.com/>

Please consider the environment. Don't print this e-mail unless you really need to.

The information contained in this communication is confidential and intended only for the use of those to whom it is addressed. If you have received this communication in error, please notify me by telephone (collect if necessary) and delete or destroy any copies of it. Thank you!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


************************************************************************
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or taking any action based on it, is strictly prohibited.
***********************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


************************************************************************
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or taking any action based on it, is strictly prohibited.
***********************************************************************





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact