Warning: I am not a regular Dotnet head, so maybe totally off center ;-)

First thought: Interop often used to describe Dotnet#COM interaction, perhaps only the COM wrapping of those dll's is gone ?
Second thought: Dotnet loading from other locations (less danger on a server as less is installed/tested, but still a possibility

afterthought: check loaded dlls with Process Monitor from Systernal or try dependency walking

HTH

thomas

P.S. # was .LT. .GT. in Fortran notation before triggering the HTML check. I thought you had written you had fixed this ?

>I removed the following two files from the Web site Bin directory:
>
>Interop.ADODB.dll
>Interop.CDO.dll
>
>...so I can run the Web site application pool in 64 bits.
>
>I would have assumed that a specific page on the Web site would no longer work as it has lines like this:
>
>

>        Dim loStream As ADODB.Stream = New ADODB.Stream
>
>        loStream.Mode = ADODB.ConnectModeEnum.adModeReadWrite
>        loStream.Type = ADODB.StreamTypeEnum.adTypeText
>        loStream.Open()
>
>        loStream.LoadFromFile(cFile)
>
>        oMessage.DataSource.OpenObject(loStream, "_Stream")
>
>        ' From
>        If Not RetrieveHeader(oMessage.From) Then
>            Return False
>        End If
>
>        cFrom = oMessage.From
>        cFromAddress = cAddress
>        cFromName = cName
>

>
>So, if the two 32 bit library files required for ADODB related commands to work are no longer in the Bin directory, how can this work? I did stop and start the Web site a few times.