Thanks, Ted. And I apologize for the initial vague description. This is a Windows 2012 R2 VM in our own corporate "cloud". There is also another VM running SQL 2014 which it connects to via ODBC. No VFP installation, per se. It's just my EXE and the appropriate DLLs/FLLs. VFP9 SP2. All proper versions of DLLs to match. Using REPORTENGINE 90. Using XFRX previewer instead of the native previewer. Not using a ton of report listeners in general but of course, the XFRX previewer does. I have a back door built into my EXE. It's not as slick as VFOXRUN but it gets the job done. Yes, the TMPFILES/sharing stuff is definitely a bit on the tricky side. Our app config is typically set to a local folder on the C drive but when run via RDP we redirect to a unique location for each user logged in. Having said that, you've given me an idea to try out. I also just added the R attribute to the 3 report*.app files. Since the majority of the crashes seem to revolve around reporting, maybe that will be the magic bullet. I also just cleaned out any saved printer environments.
-- rk -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Ted Roche Sent: Tuesday, April 11, 2017 8:13 AM To: [email protected] Subject: Re: VFP EXE and RDS random crashes On Tue, Apr 11, 2017 at 7:30 AM, Richard Kaye <[email protected]> wrote: > Throwing this out to the collective wisdom. > > I've recently rolled out a hosted environment for my application. So I'm in > the cloud... It's hard to see clearly with your head in the clouds... Which cloud? I'm guessing multiple WIndows X VMs hosted on... something. Azure? Amazon? Hosted server? What brand/version of all? > I've been observing random hard application errors, particularly around > running reports. Of course, it's not consistent. Which VFP? Reports using VFP9 or VFP8 compatibility? New Report listeners or old "classic" FRXs? How was VFP installed? Are all the runtimes the same version? Are they patched up to Sedna + service packs? Install vFoxRun if you haven't already. This is a *GREAT* tool for debugging (Thanks, Ed!) Then you can test things like VERSION(), and REPORT FORM right from the commandline, in your runtime environment. One owner of our vertical-niche app runs virtualized, using RDP and TS to run multiple workstations on a hosted WInServer2008. There are lots of kinks with TMPFILES and sharing... > A user will be able to run a report with no errors just fine one time and > then other times the same report will just result in an application crash. > What I'm seeing in the Windows application log when this happens are mainly > C6 errors. The Google gave me some recommendations about setting the EXE and > the runtime DLLs read-only but I'm hoping that out there in Profox land this > might ring some bells. *ding* -- Ted Roche & Associates, LLC http://www.tedroche.com [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/bn4pr10mb09134354f4b0cb46c1bdce7cd2...@bn4pr10mb0913.namprd10.prod.outlook.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
