We have a vendor developed, customized application that, among other things, builds an aspx web page using a link that looks like this:
The part in the curly braces is an identifier used to retrieve a database record, so there is a database lookup involved.
Here's the problem:
When the URL is accessed the first time, the page opens just fine. If the browser is closed and re-opened and the URL (or a similar URL calling a different database record)is accessed a second time, the is an aspx error page that indicates a failure at datasource.open.
Occasionally, we successfully open the page on the 2nd attempt but usually we have to restart IIS before successfully opening the aspx page again. More often, the second attempt results in a long delay and an error page that indicates a "Server Application Error".
Having eliminated network timeout issues, the vendor now wants me to re-install MDAC_TYP.exe and the Oracle ODBC drivers in a different order from the first install. The vendor claims that a similar setup, as described, works perfectly in their lab but their setup is not an exact duplicate of ours. This project is in pre-production and has not yet had a successful end-to-end test.
1. Is it safe to install the same Oracle ODBC drivers and the same MDAC on top of the existing ones?
2. Does anyone have any suggestions on possible causes for this datasource.open error? Could connection pooling be involved?
The system is as follows(in order of installation):
- Windows 2000 Server SP2
- IIS installed (Web services only)
- .NET Framework Redistributable installed (runtime components)
- .NET Framework Service Pack 2
- MDAC_TYP installed (not sure which version but will find out if necessary)
- Oracle ODBC installed (the app makes calls to an Oracle DB on another server)
- The clients used to access the URL have .NET Runtime components installed.
I am a system admin, not a developer so I'm not intimately familiar with .NET. If more info is needed, I will be happy to provide it.