Re: startup progress on server

c.f. ACI0096115 (fixed in v17), ACI0094811 (fixed in v17, 16.3.HF5), ACI0097654 (fixed in 16R6) I recall the workaround prior to the fix was to duplicate the numeric menu reference ( i.e. $menu:=Create menu(1) ) instead of using design mode directly ( SET MENU BAR(1) ) but I may be wrong.

RE: startup progress on server

> So what’s the recommendation on giving startup progress so they know that the > server hasn’t frozen at some point during the startup method? To the best of my knowledge, we do not recommend any sort of UI on the server. So, it is hard to make a recommendation for something we don’t recommend.

Re: startup progress on server

> On Aug 6, 2018, at 12:39 PM, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com > > wrote: > > Regarding the menu bars on server - > >> Calling SET MENU BAR during On Server Startup >> - this crash will occur in a test database with only this line of code in

RE: startup progress on server

Regarding the menu bars on server - > Calling SET MENU BAR during On Server Startup > - this crash will occur in a test database with only this line of code in the > On Server Startup method This *was* a known issue, it was filed as ACI0097391. It should be fixed in the latest v16 and v17

Re: startup progress on server

SET MENU BAR has never actually done anything to change the menu bar on the server, so I think it’s just been ignored all these years. It’s never been a problem until v16R6 Server. Of course, this is the first time we’ve had 64bit on Mac, so it may be related to that. Either way, starting a

Re: startup progress on server

There could be, sure. John DeSoi makes a good point that it could b the 64bit version as opposed to 32bit. As I mentioned, the startup method was working fine up through v15.4 HF3, which was the last version before jumping to v16R6, but we went right to the 64bit version of that so I’ll have

Re: startup progress on server

We call QUIT 4D directly with no timer. Our On Exit and On Server Shutdown methods already do checks to be sure the processes we started are dead. I’m hoping for sure this is all that is needed. I didn’t think to test if this was only an issue related to 64bit version of server on Mac. I’ll

Re: startup progress on server

Randy, I'll be interested to hear if this permanently fixes the problem. I'm still having random crash on quit errors on 4D Server (16.3HF4, 64-bit). Never a problem in version 15, 32-bit. I have never connected crashing to a status interface, but in my case it has always run in a separate

Re: startup progress on server

Ok. So moving our STARTUP method into a stored procedure using $procID:=New Process(“STARTUP”;512000;”On Server Startup) takes care of BOTH problems. So it looks like the Application Server process on 4D Server v16R6 and higher is more sensitive to interface related commands like

RE: startup progress on server

Randy There might be something else in the mix, all of my databases do a set menu bar during startup and open a window for progress. I'm not having the same crash you are. However I haven't tested with 4D v16r6. Neil Privacy Disclaimer: This message contains confidential information and

startup progress on server

I’ve spent the morning trying to track down why our database started crashing when we quit 4D Server v16R6 on Mac OS…I haven’t tested yet to see if it affects the Windows version as well. I have tracked down 2 contributors to the crash. 1) Calling SET MENU BAR during On Server Startup