Posted by Tom Fulton on April 17, 2014 at 08:17:56: Uploaded files: 1
An end-user account is heavily using XAP. Their website pushes sales and sample orders through XAP and we've deployed a number of mobile apps using iPod plus barcode scanning case. The scanning app is used in a warehouse to inventory memo samples. My XAP program is called and it creates a work file in TMP called 'MEMO'+partition$+'.XML' The program gets the POSTed data, does its file updates and returns XML letting the user know what update took place. They have started getting an Error 29 in my XAP program, see attachment. This is a big problem because the XAP program does not terminate normally, leaving my work file open in the Comet File Server. Exceptions are coded on the erase & create expecting that these files are never in use. When the "locked" file is encountered again, XML piles on top of the old data and bad return data is sent. I have worked around this by building a sequence # into the file name. The end-user reboots all every Sunday so this vm always has a fresh TMP every Monday morning. Nevertheless, I would like to investigate the source of this Error 29 and do something to eliminate it. Thanks in advance.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.