As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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 :
quote:
private OdbcConnection edaConn = new OdbcConnection("dsn=EDAPNHUB;uid=xxxxxxxx;pwd=xxxxxxxx;");
which from an ASP.NET page works in 5.2, but not in 7.6, the error message being :
quote:
ERROR [08001] [IBI][EDA]Unable to connect to database server (Eda error -7: EDA INIT EDANET ERROR) 'EDACONNECT' (25.6)
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 ?