Hi David,

Thanks for your tip.
I have conducted the test as per your suggestion and from the results of the 
test, it does not appear to be a firewall problem.

a)  4Dv15.5 (32-bit) - server app launched directly - database server appears 
on Available tab on Client (works OK)
b)  4Dv15.5 (32-bit) - server app run as Windows service - database server 
appears on Available tab on Client (works OK)
c)  4Dv15.5 (64-bit) - server app launched directly - database server appears 
on Available tab on Client (works OK)

d)  4Dv15.5 (64-bit) - server app run as Windows service - Available tab on 
Client is empty  (does NOT work)

For the failed service (d), when I highlight the service it shows that the 
service is running.
Further examination of the service properties shows that the service is NOT 
running or has stopped.  
I have to click the Start button again and even then, the available tab on the 
client is still blank, connection fails.

In the event that I have to give up on the 64-bit version of 4Dv15.5 server, 
what else will I lose by deploying the 32-bit version?

Regards,
Ronnie
Tarawerkz

> On 12 Sep 2018, at 10:35 PM, David Samson <[email protected]> wrote:
> 
> Hello Ronnie,
> 
> Sorry to come in on this one late but I have been away. We had a similar 
> problem and it turned out to be the Windows firewall settings. Each program 
> needs explicit firewall rules to allow it to publish.
> 
> One quick way to verify this is to run 4D client on the server. If that 
> connects OK then it is just being blocked on the network.
> 
> HTH
> David
> Manchester 
> UK
> 
> 
> 
> Message: 1
> Date: Mon, 10 Sep 2018 12:21:23 +0800
> From: Ronnie Teo <[email protected] <mailto:[email protected]>>
> To: Jim Hays <[email protected] <mailto:[email protected]>>
> Cc: 4D iNug Technical <[email protected] <mailto:[email protected]>>
> Subject: Re: 4Dv15 applications as a Service in Windows Server 2012
> Message-ID: <[email protected] 
> <mailto:[email protected]>>
> Content-Type: text/plain;       charset=gb2312
> 
> Hi Jim & Paul,
> 
> This is my finding after testing over the weekend with Windows Server 2012 
> and 4Dv15.5.
> 
> Running a v15 app with 4Dv15.5 (64bit) as a Windows service does NOT work.
> Running the same app with 4Dv15.5 (32bit) as a Windows DOES work.
> 
> In the latter scenario, the database name appears in the Available tab on the 
> client software and we are able to log in and use the app as per normal.
> 
> I do not understand why it does not work with the 64-bit version.
> But my next question would be, what do we give up by not using the 64-bit 
> version of 4Dv15.5?
> 
> Regards,
> Ronnie  
> 
> -- 
> D Samson

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to