[C#, WEB, ODBC] iSeries Access ODBC Address Resolution Issue

[seligerasmus]

Greetings,

I'm having a bit of trouble with a small web service I've been writing, specifically with the connectivity aspect of the service.

My scenario is as follows :

I'm using the IBM iSeries Access ODBC driver to connect to an iSeries (i5/OS, V5R4) midrange box. I've used this driver and a similar DSN in the past with no problems.

When an attempt to open a connection is made, an exception is thrown with the following message -

ERROR [08S01] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=11001 - CWBCO1004 - Remote address could not be resolved

This error message struck me as particularly odd, given that I'm using the same host name in other connection strings and DSNs without any hitches. I've verified I can reach the AS/400 in question, and that the AS/400 allows remote ODBC connections for the user name I'm supplying. I've also tried using the IP address of the system in question, with no results.

Additionally, I've verified that my hosts file contains an entry for the AS/400 in question (although I've never needed one in the past.)

Any help or insight would be greatly appreciated,

SeligErasmus

[Plater]

Well, is it possible that your connection string has a typo in it or something?
Or does not follow a new format for it?
I am unfamiliar with your database type but it seems like there is something fishy somewhere

[seligerasmus]

Hmm, I'm thinking that's probably not the case, because I'm using the exact same connection string in a different application with no issues. The only thing that's changed is the hostname supplied.

[Plater]

The only thing that's changed is the hostname supplied.

That would fall under the "different" connection string.

You could try and take an application that correctly connects, and replace with the string from this new application that isn't working.

That should hopefully give you some kind of better idea of whats going on (cut out the varriables until the problem is found approach)

[seligerasmus]

That would fall under the "different" connection string.

You could try and take an application that correctly connects, and replace with the string from this new application that isn't working.

That should hopefully give you some kind of better idea of whats going on (cut out the varriables until the problem is found approach)

Right.

To clarify - I've copied the connection string from the application that works correctly and changed the hostname. Since the two servers are identical (one is for testing, the other for production), I've only changed the hostname.

When I supply the problematic connection string to the working application, it connects fine and executes accordingly. Since I'm testing both applications locally, it's puzzling to me that one application can connect and the other cannot -- especially since I'm using the same initialization code in both applications.

[Plater]

Is there any run-as permissions set for the working program that isn't there yet for this new program?
That *IS* very strange that one works and the other doesn't

[seligerasmus]

If anyone is interested, the issue ended up being a corrupt profile. My sys admin cleared my Windows profile and reinstalled the iSeries Client Access Library for Windows and everything worked fine.