Our local web server that acts as the transaction conduit between BBNC and RE has had intermittent freezing problems and I can't figure out what the problem is. It generally happens overnight, when there may be only a few online donations coming in. We are on a sadly slow DSL connection because it turned out that our brand new building is too far from the telephone box, and we can't use wireless because the building cannot pick up that signal. We are now looking at satellite. However, there is nothing much competing for either of the 2 DSL lines (load balanced)overnight. The freezing never happens during business hours.

Any ideas?

What happens during the freezing process - are there any errors, or website goes down, or is it merely the link between the two?

Is it possible that it's when your backups, or other database processes, are running?

The system totally freezes, including keyboard and mouse. I do not run backups on this server because its only purpose is as a transaction connector between BBNC donations pages and RE. There are no other applications run from this server. There is no error message on the screen. We do have a slow DSL connection, but I would expect the freezes to happen during business hours, rather than overnight.

It might still have to do with backups, depending on what's happening.

But let me just get a clear understanding of this machine.

So, this is a workstation, rather than a server, that has RE and the BBNC plugin, which is used exclusively (or, at least the plugin is exclusive to this machine) for the purpose of bringing transactions into The Raiser's Edge.

Assuming that's the case:
-Do you always leave the plugin running, or do you log out of the machine (or even just RE/BBNC Plugin)
-Do you have any other machines that you could put the plugin on and see if it happens there as well?

K

This is a server. It is our RE services web server. We are "split-hosted" with RE being local and BBNC hosted by BB. Any transactions that come in via BBNC must go through this server.

Ah... I should have clued in. My apologies... that makes far more sense than my convoluted view...

I'm not aware of any memory leak with the service, but I might recommend running the resource monitor over the period of a day and see if memory, or network traffic, starts becoming a major concern over the day. Potentially, if you reset in the morning, it takes 20 hours to completely deplete itself of resources and then locks... which would be why it happens at night.