I recently upgraded the iWay client software on my PC from version 5.2 to version 7.6 in order to bring it in line with the version on our web server. The reason for this upgrade was that an ASP.NET page written to access data on our Data Warehouse managed to connect OK when run in localhost using iWay Client 5.2, but failed to do so when copied to the web server. I had hoped that an upgrade would allow me to replicate and hopefully resolve the server-side connection issue, but this turned out to be a vain hope.
I use the following DSN in both versions :
which from an ASP.NET page works in 5.2, but not in 7.6, the error message being :
The same connection string when used in a .NET application run from my PC does work, which seems to imply that the DSN, username and password are valid - but not from a locally run ASP.NET page.
Does anyone have any clever ideas as to why a connection can be established in 7.6 from an application but not from a web page ?
Problem solved - a change of the connection string to read :
appears to have done the trick.
I must admit that I have no clear idea why this worked, though.
|Powered by Social Strata|