McGillivray, Don [IT]
Donald.A.McGillivray at sprint.com
Fri Jun 20 16:54:47 CDT 2008
Thanks to all who have responded so far. It's starting to look as if this problem is not Access/VBA related at all. A little background for those who may be interested, or in case it sparks some further helpful ideas . . . I manage a couple of apps that run in a terminal server environment, using Windows remote desktop services on a Win 2003 server. The one that I'm having trouble with runs basically 24 x 7 in a disconnected session, gathering data from text files on three different servers. Its processing is mostly about cataloguing and tracking those text files through their life cycles, then removing them from the servers, extracting summarized data from them, and archiving them for future reference. The extracted data is then made available to users for browsing and reporting thru another app that is served up in user sessions on the same server - one session per user. Both front ends are attached to the same back end data - one pushing data in, the other reading it only. This arrangement has been working well for several years, but recently we were forced by our network gestapo to migrate to a new server which is set up as a VM slice on a larger server. So, now we're one of many VM slices on some server in a farm somewhere in the wilds of Missouri, and (as I understand it) that VM slice is serving up the individual terminal sessions to my app and my users. Despite a few stutter steps at the beginning, even this arrangement has been working OK, though the new server (promised to be more reliable than our dedicated one) has had more unexpected outages in its first 3 months than we had in the last 4 years on the old one. But I digress . . . . I closed all my users' sessions and restarted the main app in a new session. To my surprise, the errors stopped. So, it looks as if the problem may be related to something in the configuration of the server where this all runs. Perhaps a lack of resources, or maybe a memory leak somewhere in one of the apps, or maybe the server needs to be re-booted. Maybe somebody out there has experience running Access apps in a similar configuration, and can share some stories and/or expertise. Or maybe comebody can validate or repudiate my sense of what's going on . . . I any case, it looks like I have a procedure that will get me back in business - however temporarily - if this happens again . . . Don -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of McGillivray, Don [IT] Sent: Friday, June 20, 2008 11:28 AM To: Access Developers discussion and problem solving Subject: [AccessD] Error 3001 - invalid argument - What the . . . . ? Out of the blue, I'm getting the above error (minus the "What the . . .?") in a proc that has been running rock solid forever. It's in a block of code where I'm using DAO to write a record to a table: .AddNew !field1 = SomeValue1 !field2 = SomeValue2 .Update Code is puking on the .Update line. I suspect some sort of corruption, but all my usual remedies (decompile/recompile, compact/repair) don't seem to be having any effect. This is probably my weakest area of understanding with Access, etc., so I'm not even sure I'm using those approaches correctly. Hoping somebody might be able to suggest a more reeliable way to the problem . . . . Don McGillivray -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com