I've installed BOINC at my company on about 30 boxes, connecting to WCG so that I can easily manage projects and we can help out humanity when our machines are unused. Everything went flawlessly until late last week, when people started complaining of a window entitled "Visual C++ 7 Runtime Error" popping up randomly. The error window cannot be clicked on and must be closed via end task. On every machine that has the VC++ problem, similar errors are present in the BOINC message log. Here is an example (I snipped out stuff specific to this machine):

4/13/2009 7:39:43 AM||Starting BOINC client version 6.4.5 for
windows_intelx86
4/13/2009 7:39:43 AM||log flags: task, file_xfer, sched_ops
4/13/2009 7:39:43 AM||Libraries: libcurl/7.19.0 OpenSSL/0.9.8i zlib/1.2.3
4/13/2009 7:39:44 AM||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 2200+
[x86 Family 6 Model 8 Stepping 1]
4/13/2009 7:39:44 AM||Processor features: fpu tsc sse 3dnow mmx
4/13/2009 7:39:44 AM||OS: Microsoft Windows 2000: Professional x86 Editon,
Service Pack 4, (05.00.2195.00)
4/13/2009 7:39:44 AM||Memory: 255.48 MB physical, 1.23 GB virtual
4/13/2009 7:39:44 AM||Disk: 61.50 GB total, 56.40 GB free
4/13/2009 7:39:44 AM||Local time is UTC -4 hours
4/13/2009 7:39:44 AM||Not using a proxy
4/13/2009 7:39:44 AM||No CUDA devices found
4/13/2009 7:39:44 AM||No coprocessors
4/13/2009 7:39:44 AM||General prefs: from World Community Grid (last
modified 18-Mar-2009 16:47:49)
4/13/2009 7:39:44 AM||Computer location: work
4/13/2009 7:39:44 AM||General prefs: using separate prefs for work
4/13/2009 7:39:44 AM||Preferences limit memory usage when active to 38.32MB
4/13/2009 7:39:44 AM||Preferences limit memory usage when idle to 191.61MB
4/13/2009 7:39:44 AM||Preferences limit disk usage to 1.00GB
4/13/2009 7:39:44 AM||Suspending computation - user is active
4/13/2009 7:39:44 AM||Suspending network activity - user is active
4/13/2009 7:50:46 AM|World Community Grid|Restarting task
X0000057631409200509161409_1 using hcc1 version 606
4/13/2009 7:55:18 AM||Suspending computation - user is active
4/13/2009 7:58:58 AM|World Community Grid|Task
X0000057631409200509161409_1 exited with zero status but no 'finished'
file
4/13/2009 7:58:58 AM|World Community Grid|If this happens repeatedly you
may need to reset the project.
4/13/2009 9:21:02 AM||Resuming computation
4/13/2009 9:33:28 AM||Suspending computation - user is active
4/13/2009 10:08:42 AM||Resuming computation
4/13/2009 10:11:25 AM||Suspending computation - user is active
4/13/2009 11:37:23 AM|World Community Grid|Task
X0000057631409200509161409_1 exited with zero status but no 'finished'
file
4/13/2009 11:37:23 AM|World Community Grid|If this happens repeatedly you
may need to reset the project.
4/13/2009 12:05:35 PM||Resuming computation
4/13/2009 1:10:47 PM||Suspending computation - user is active
4/13/2009 1:19:35 PM|World Community Grid|Task
X0000057631409200509161409_1 exited with zero status but no 'finished'
file
4/13/2009 1:19:35 PM|World Community Grid|If this happens repeatedly you
may need to reset the project.

I've tried resetting the project on more than one machine - sometimes it seems to fix the problem and sometimes it doesn't. The anti-virus and anti-spyware programs are the same since well before I installed BOINC; though the definitions have been updated, there have been no alerts that anything has been found. It's happening on machines that have everything from a dual-core AMD box to Intel to an Athlon 1800, running XP or 2000, and the systems range from having 256 meg of ram to 2 gig. I installed BOINC from a flash drive, so I know that the same version of BOINC is on all machines and I configured it the same on each. Google brings up many hits related to these problems, but none seem to have a solution. I have the network preferences to only communicate at night, but since the errors pop up randomly throughout the day, I don't believe that is the source of the trouble as many google hits seem to insinuate.

I really enjoy the feeling of actually helping accomplish something big that comes from having BOINC installed and running, but management is going to put the kabosh on it if employees are presented with errors constantly. :(

Anybody have a solution or any ideas?