John, I agree with Jim: separate the creation of the file from moving the file to the network. A lot has changed in the last 20 years or so with the way network access is managed and old code like this that looks at a network address as equivalent to a local disk are problematic. We ran into this on another project where the 4D app is doing a lot of file manipulation on a networked drive.
Better yet - re-write the file generation to run on the server. In my experience when a report like that takes so long to run it's due to moving lots of data back and forth. Move the code that actually creates the file to a method that can execute on the server. On Wed, Apr 15, 2020 at 10:10 AM John J Foster via 4D_Tech < [email protected]> wrote: > Hey All, > > When it rains it pours… > > 4D v17.2 64bit Windows > Windows 10 Pro > > We have some reports that are run in a batch overnight. Have to because > they take that long to run all of them. Anyway, since we’ve upgraded from > Windows 7 to Windows 10 there have been I’m guessing timeouts on some of > these larger reports. > > The report is running along and then we get the error: "executing the > method “EXP_CumulativeClaims” at the lilne number 63. The .txt document > cannot be written. File not found.” > > This is line #63: > SEND PACKET($fileRef;$packet) > > It varies when it quits. It’s usually saved to a network drive and IT says > nothing is happening to disrupt the connection. And there are other reports > where this happens as well. > > The text file report size - when it works - is large: > > Reserve file: 831,801kb > Claims file: 26,959kb > > So these reports were created way back in 2004. The number of records has > grown dramatically over the years. Reserves is up beyond 2.3 million > records. > > Is it possible that this is a client-server timeout issue? If so, how to > fix? > > Clients IT claims the network drive is always available. Is there a way to > “know” for sure and test each time? > > Is there a way to capture debug info which might reveal the cause? Would > logging using 4D’s component help? > > Would it be helpful and speedier to redesign the reports so they are not > sending out each row but maybe save each row to a text variable, say 100 or > 1000 rows and then send packet? > > We are open to all ideas. > > Appreciate, > John… > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** -- Kirk Brooks San Francisco, CA ====================== ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
