Mark

This article points to the IBM docs about "breaking changes" in the V6R1 provider, and the IBM docs show a possible work-around (point the .config file to the correct version of the provider that you want):

http://systeminetwork.com/article/whats-new-ibm-v6r1-net-provider

Craig Pelkie



----- Original Message ----- From: "Mark Walter" <mwalter@xxxxxxxxxxxxxxx>
To: "Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
Sent: Thursday, September 17, 2009 10:32 AM
Subject: Re: [WEB400] idb2Connection Connection String error.


Right.

Here's what I'm doing to try to debug this thing.

First I create the connection string just using the DataSource parameter, and it works. No exception. However, when I add UserID, it throws the exception putting showing UserID in the MessageDetail argument of the exception class. So, I put Password in front of UserID in the connection string, and it throws the exception again showing Password as the MessageDetail argument of the exception class.

Ok, so I put UserID first in the connection string, and it throws the exception, showing UserID as the MessageDetail argument of the exception class.

I'm catching the iDB2InvalidConnectionStringException explicitly.

This is getting very irritating.



Mark Walter
Business to Business Data Integration Specialist
Certified IBM System i Specialist
Paragon Consulting Services, Inc
mwalter@xxxxxxxxxxxxxxx
717-764-7909 ext. 126


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Thursday, September 17, 2009 12:59 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] idb2Connection Connection String error.

I seem to remember an issue on the DefaultCollection with V6R1 not
working, however it sounds like you're having the reverse issue since
the problem is with V5R4.

Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

------------------------------

message: 2
date: Thu, 17 Sep 2009 08:33:37 -0400
from: Mark Walter <mwalter@xxxxxxxxxxxxxxx>
subject: [WEB400] idb2Connection Connection String error.

I have an application that uses the ibm.data.db2.iseries library. When I
install the application on a computer running iSeries Access Version
6.1, which is iseries.dll version 12.0.0.0, it works fine, but when I
try to run on a computer running iSeries Access Version 5.4, which is
iSeries.dll version 10.0.0.0, I get an invalid connection string error.
The same connection string is utilized. This is the Connection String:
DataSource=myserver.paragon-csi.com;User
Id=userid;Password=pwd;DefaultCollection=MPFCUST;

Any insight would be appreciated.

Thanks,

Mark

Mark Walter
Business to Business Data Integration Specialist Certified IBM System i
Specialist Paragon Consulting Services, Inc mwalter@xxxxxxxxxxxxxxx
717-764-7909 ext. 126

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.