Just to update on this. We still don't have a resolution, but we know that what is happening is that under undefined circumstances the output from PRINT statements in PHANTOM processes is being written over the top of hashed files and distributed file stubs, corrupting them. It is as though jBASE is losing track at a very low level of which file handle it should write to. Unfortunately it's very hard to reproduce this in isolation for jBASE to work on. John Fenlon is working very hard with us to try and make this problem recur on a test bed, but so far no luck. We just keep sending copies of corrupted files whenever this happens and I'm sure they're getting almost as fed up as we are.
Someone at jBASE did suggest we replace all our PRINT statements in our codeset but we are giving them the benefit of the doubt and assuming they lost track of the date and thought it was April 1! Will update you all again once it is properly resolved. Meanwhile, if anyone comes across anything similar, please let us know. Regards, Ken On Tuesday, 2 June 2015 18:46:17 UTC+10, Ken Wallis wrote: > Hi, I'm just wondering how many people actually have production sites > running jBASE on Windows Server 2012? > > We (Paperless Warehousing) have 2 production sites with Server 2012 and > apart from the horrible mess Microsoft have made of the interface to this > server OS, everything seems fine except these sites experience at least 10 > times the frequency of data corruption that we get at any other Windows > site and that's without them doing random reboots or anything like that. > > We have had completely static and never updated files like jBASE's > internal jbcmessages get corrupted, but most frequently it is an index on > one of our busiest files that goes south - often somewhere in the early > hours of the morning. > > Of these 2 sites, one is running 5.2.26 and the other 4.1.6.16. The 5.2 > server seems to have more trouble than the 4.1 site does, but both > experience far more issues than our Server 2003 or Server 2008 sites do. > We have been down the path of making sure the boxes aren't being rebooted, > verifying that the AV tools on the boxes have exceptions for the database > disks and checking that they aren't using the new ReFS filesystem, but > still we keep getting files that look like they've had random blocks > stomped onto them. For example we've had distributed file stubs which > should be less than 1K suddenly become much larger and stop working - the > first few bytes seem right, but the part file information is all wrong and > the file is a few MB. > > I'm wondering if anyone has spent enough time with this OS to identify a > service that Microsoft might have added that thinks it is helping us but is > actually stuffing us up. > > Short of that, I'd just be interested to hear if there are hundreds of > sites out there running on Server 2012 without any issues - at least I'd > know it was only us going mad! > > Thanks, > > Ken Wallis, Paperless Warehousing > Sydney, Australia > -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
