I am in the processing of upgrading our internal work websites from
ASP to ASP.net. Due to resource and time constraints, I am doing the
poor man's upgrade, so, for example, I am still using COM connections in
the ASP.net pages.
My current environment uses .Net Framework 1.1. The new environment uses .Net Framework 2.0.
All of my pages have been upgraded from ASP to ASP.net, except for
one. That page tries to connect to a DB2 database and call a stored
procedure to update rows in the DB2 database.
I made a barebones test .aspx page that simply tries to establish a
connection to the DB2 database. In our current production environment
(.Net 1.1), it runs fine. In the new .Net 2.0 environment, it gets a
catastrophic failure error.
I did not set up the new 2.0 environment, but those who did, say that DB2 is set up for my DB2 database.
Any ideas on why the new environment would get a catastrophic failure
error, while the old one does not? I did try making a test page that uses an
OleDBConnection, but that fails as well in the new and works in the
Could it be that the IBM DB2 Data Provider needs to be updated for .Net 2.0?
Here is the test page.
<% @Page Language="vb" runat="server" aspcompat="true" debug="true" %>
View Complete Post