We have 4D Server v17 HF3 set up as a service on Windows Server 2016. I checked the service properties -- the "Log on as:" is set to "Local System account" and "Allow Service to interact with desktop" is checked.
I also have FireDaemon installed to make it easy to bounce into the "session 0" user interface if I need to view the 4D Server user interface. > On Feb 27, 2019, at 9:43 AM, Tom Benedict via 4D_Tech <[email protected]> > wrote: > > Hi Pat, > > I don’t have any experience with running 4D as a Service, but I see that > there is a Tech Tip from about 10 years ago which mentions having to “Run as > Administrator” > > https://kb.4d.com/assetid=75056 > > HTH, > > Tom Benedict > >> On Feb 27, 2019, at 02:40, Pat Bensky via 4D_Tech <[email protected]> >> wrote: >> >> I'm having a bit of trouble trying to set up our 4D app to run as a service >> on a Windows server. >> >> The server version is Windows Server 2016 Standard. >> If I run the app "As Administrator" it starts up OK and we can connect to >> it. >> >> If I don't start it as Administrator, I get a message that the database (or >> one of its segments) is locked. >> If I try to set it up to run as a service, it doesn't work - in the >> Services window, it says it's running, but in the Task Manager it says >> Stopped. I'm guessing this is because when it tries to start the service, >> it can't because of the locked data file problem. ********************************************************************** 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] **********************************************************************
