Hi John and Jeffrey,

The version of 4Dv15 Server implemented is indeed the 32-bit version.

The client has a hardware vendor who set up the whole network, so I’m not 
actually privy to the network settings.

How can we tell if the new network layer is turned on/off?

By this, are you referring to the System Integrity Protection  (SIP) in El 
Capitan?

Regards,
Ronnie


> From: John DeSoi <[email protected]>
> To: 4D iNug Technical <[email protected]>
> Subject: Re: 4Dv15 and El Capitan
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=utf-8
> 
> Are you using the new network layer and the 64 bit version of 4D server? It 
> might be worth trying to turn off the new network layer or even just run the 
> 32 bit version for now. Those features are very new. 15.2 32 bit has been 
> very stable.
> 
> John DeSoi, Ph.D.
> 
>> On Sep 9, 2016, at 3:12 AM, Ronnie Teo <[email protected]> wrote:
>> 
>> This is one of the user diagnostic report entitled "4D 
>> Server_2016-09-06-100602_4D-SERVER.crash”
> 
> 
> From: Jeffrey Kain <[email protected]>
> To: 4D iNug Technical <[email protected]>
> Subject: Re: 4Dv15 and El Capitan
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
> 
> We couldn't even run the new network layer for 15 minutes in 15.2. All kinds 
> of weird errors, crashing, application-layer bugs. Others seem to be able to 
> run it somehow.
> 
>> On Sep 9, 2016, at 4:06 PM, John DeSoi <[email protected]> wrote:
>> 
>> Are you using the new network layer and the 64 bit version of 4D server? It 
>> might be worth trying to turn off the new network layer or even just run the 
>> 32 bit version for now. Those features are very new. 15.2 32 bit has been 
>> very stable.

**********************************************************************
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]
**********************************************************************

Reply via email to