Connection pooling issue, urgent

Question

Hi,
Our asp.net web application use sAP .net connector to make RFC call to sap CRM system. recently, I am trying to utilizing connection pooling, but assigning connection obtained from pool to proxy class , I did exactly the online help docs says, but, i got some very disappointment result, it cause iis worker process memory write proctection error. and very time, I reboot my machine, the problem does not go away, my O.S tells me that "Data Execution proctection" warning comes up and afterwords, iis worker process and etc, I am not sure what I did wrong, any body experience similar problem,
after I uninstall .net connection, and I reboot my machine
, this error went away. Please help.
following is my configuration settings:
<SAP>
       <Connector>
             <ConnectionPool              
               MaxOpenConnections="20"  
                             MaxCapacity="20"
                       MaxIdleTime="10"
                       CleanupInterval="10" />                   
                      <Destinations Default="cd1">
                          <Entry
                            DestinationName="cd1"
                            AppServerHost="ASHOST=sapcrd01.bentley.com"
                            SystemNumber="00"
                            Username="ASPRFC"
                            Password="bentley"
                            Client="100"/>                        
                       </Destinations>
          </Connector>
     </SAP>
following line of code is from myproxy constructor
     this.oCommonProxy.Connection=SAP.Connector.Connection.GetConnectionFromPool(GetConnectStringForUser(this.sRfcUser,this.sRfcPass));
public void CloseConnection()
                                   SAP.Connector.Connection.ReturnConnection(this.oCommonProxy.Connection);
Message was edited by: Yuwen Li
Message was edited by: Yuwen Li

Answer 1

Hm, sounds strange. Can you try to attach a debugger with both, managed and unmanged mode, turn on "first chance exception handling" for all exception types and check the call stack when the exception happens?