Hi<BR><BR>We have built an asp application for intranet, which is working well on IIS4 (asp 2.0). Right now, we are trying to port it to windows 2000 (IIS5 and ASP 3.0) and are facing a lot of problems with session variables when they are set to hold recordsets.<BR><BR>In our scripts we are using session variables to hold recordset (ADOR.Recordset) objects. The problem is, if a session variable already pointing to a recordset is now set to point to a new recordset an exception is thrown.<BR><BR>See the code<BR><BR>dim rst1<BR>dim rst2<BR><BR>set rst1 = Server.CreateObject("ADOR.Recordset")<BR>&#039rst1 is then filled with some rows<BR><BR>set rst2 = Server.CreateObject("ADOR.Recordset")<BR>&#039rst2 is then filled with some rows<BR><BR>set Session("ssn_rst") = rst1<BR>&#039this statement works fine<BR><BR>set Session("ssn_rst") = rst2<BR>&#039at this statement an exception is raised.<BR><BR>There were no problem on IIS4 and ASP2.0<BR><BR><BR><BR>Awaiting help<BR>Regards<BR>Mohan<BR><BR><BR>