Spam Filter ISP Support - Exception occurred during RECEIVEMESSAGE: Access violation at address

Print Page | Close Window

Exception occurred during RECEIVEMESSAGE: Access violation at address

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=152
Printed Date: 27 December 2024 at 4:30am

Topic: Exception occurred during RECEIVEMESSAGE: Access violation at address

Posted By: Guests
Subject: Exception occurred during RECEIVEMESSAGE: Access violation at address
Date Posted: 03 April 2003 at 12:00am

hi Roberto,

we are running the latest version off the web and just waiting for a cheque to clear before we are properly registered for the software.

however, even running the latest version on w2k with lots of memory, we are getting problems every 2-3 days when the service starts to drop or refuse messages with "Exception occurred during RECEIVEMESSAGE: Access violation at address 00429A8D in module 'SpamFilterSvc.exe'. Read of address 66727467"

I thought something similar to this was fixed in version 1.1.0.73, and we are now running 1.1.0.80.

is this fixed in the current registered version?

thanks

Replies:

Posted By: LogSat
Date Posted: 03 April 2003 at 12:00am

We've had a couple os similar reports and are trying to isolate the problem. Currently the registered and evaluation versions are exactly the same, so a bug in one will also be present in the other.

Roberto F. LogSat Software

Posted By: Guests
Date Posted: 03 April 2003 at 12:00am

thanks roberto, is there anything I can do to help? (think you've been talking to my colleague Nigel to get us licensed).

a logfile, more details or similar perhaps.

I'd guess we've had this happen wed, sunday and today at about 1pm gmt, so the cycle appears to be 3 days approx.

the box isn't doing huge amounts of mail, between 30-50,000 per day, has 1gb of memory so not short of resources.

we haven't put it in yet, but we were going to stick in a nightly restart just for safety to get around this problem for the time being.

any thoughts?

Posted By: LogSat
Date Posted: 03 April 2003 at 12:00am

Yes, traffic is fairly low, the max we've seen SpamFilter handle is in the range of 1 million per day. So far the reports of this problem have been when SpamFilter runs in service mode. We did make a rather drastic change in the way the service is implemented with this last build in order to make the input fields editable (they were read-only before).

Is there any chance you can run SpamFilter in the standalone application mode for a few days to see if the issue is isolated to the service mode?

Even though we haven't yet pinpointed the cause, we're making a few changes that *may* help solving it. Are you willing/interested in to test one of our internal build within the next few days?

Roberto

Posted By: Guests
Date Posted: 04 April 2003 at 6:34am

okay, we are currently running in application mode and not as a service as suggested.