G
Guest
Can anyone help?
We have a site written in ASP.NET that uses verisigns payflow pro object.
About once a week (its been getting more frequent) the page that uses the
object starts timing out and the code returns the "Object reference not set
to an instance of an object" message. The line it errors out on is
immediately below the line that instantiates it (its not a session timeout
issue).
The code appears to freeze when trying to get a reference to the COM object,
then eventually times out returning a null reference. When in this state, the
site will still occasionally process a request now and again, but ~90% of
them will time-out like this.
Recently we noticed a similar situation appear on another app with the
CDO.Message object.
We already tried turning off Worker Process Recycling.
When this starts to happen, only restarting the IIS services clears it up.
Its a Windows 2003 box btw.
Any ideas?
We have a site written in ASP.NET that uses verisigns payflow pro object.
About once a week (its been getting more frequent) the page that uses the
object starts timing out and the code returns the "Object reference not set
to an instance of an object" message. The line it errors out on is
immediately below the line that instantiates it (its not a session timeout
issue).
The code appears to freeze when trying to get a reference to the COM object,
then eventually times out returning a null reference. When in this state, the
site will still occasionally process a request now and again, but ~90% of
them will time-out like this.
Recently we noticed a similar situation appear on another app with the
CDO.Message object.
We already tried turning off Worker Process Recycling.
When this starts to happen, only restarting the IIS services clears it up.
Its a Windows 2003 box btw.
Any ideas?