It is the 4D 32 bit client that is crashing. So you are running the job from a 4D Client on a Windows Server 2012 R2 operating system?
Try running the web process on the 4D 64 bit Server instead of the 4D 32 bit client. As 32 bit applications are not fully supported on Windows Server 2012 R2. Alternatively try running from a supported 4D 32 bitclient version of windows I am running it now on the 64 bit client. Been up for half an hour and no crashes. Hopefully that has sorted it. Thanks Neil for all your help. On Thu, 26 Jan 2017 at 14:06 dov uhrmasher <[email protected]> wrote: > > Faulting application path: C:\Program Files (x86)\4D\4D v16.0\4D\4D.exe > > Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll > > Looks like you are running the 32Bit version of 4D. The 32Bit version of > 4D and 4D Server isn’t certified for your operating system, try running the > 64 bit version of 4D Server. > > I am running the 64 bit Server, but 32 bit client. > > > On Thu, 26 Jan 2017 at 13:54 dov uhrmasher <[email protected]> wrote: > > > The only thing I can ascertain is that the crash will happen > > just after a http post. > > > Does anyone have any ideas as to why this might be happening? > > 1 - Are you running Windows Server 2012 or Windows Server 2012 R2? > Windows Server R2 > 2 - Are you running for a 4D Server or a 4D Client > I tried both, but same problem. > 3 - Are you using a worker process or a normal process > Normal > 4 - Are there any plugins involved > No > 5 - Are you parsing XML or using Object or Text or what? > As part of that download I am using just text. There is a second api call > that does using objects. > 6 - What do the crash logs have in them for the system and application > > Faulting application name: 4D.exe, version: 16.0.0.0, time stamp: > 0x585d2c4c > Faulting module name: ntdll.dll, version: 6.3.9600.18233, time stamp: > 0x56bb4e1d > Exception code: 0xc0000374 > Fault offset: 0x000e6054 > Faulting process id: 0x60f8 > Faulting application start time: 0x01d27769d6db89f2 > Faulting application path: C:\Program Files (x86)\4D\4D v16.0\4D\4D.exe > Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll > Report Id: 1e2c7255-e361-11e6-80f1-44a842093a83 > Faulting package full name: > Faulting package-relative application ID: > > On Thu, 26 Jan 2017 at 13:21 dov uhrmasher <[email protected]> wrote: > > Hi > > I have a routine that runs constantly in the background. It sends http > posts to an api, gets information back and then processes it. > > Through each run, the http post will get called around 100 times. Then the > process is delayed for 10 minutes and then starts again. > > The api can accept a request every second. so I put in a delay in between > each call of 1.25 seconds. > > The process runs fine and will complete running once, but on most > occasions 4D will crash during the second run. No actual error is > generated, just 4D will crash. > > At first I was using pointers to pass arrays from one method to another > and thought that might be causing the issue. But I stripped them out and it > still crashes. The only thing I can ascertain is that the crash will happen > just after a http post. > > Running v16 on Windows Server 2012. > > Does anyone have any ideas as to why this might be happening? > > TIA > > Dov > > -- > > ------ > Dov Uhrmasher > +972 542 88 3612 > > -- > > ------ > Dov Uhrmasher > +972 542 88 3612 > > -- > > ------ > Dov Uhrmasher > +972 542 88 3612 > -- ------ Dov Uhrmasher +972 542 88 3612 ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
