On Nov 17, 2016, at 1:51 PM, Cheryl Michels wrote: > This seems simple so I must be missing something very basic. We have a > merged/built server application. Customer wants to run it as a Service and > backup the data to a drive other than the one that it is currently installed > on. The backups are not getting written. There is no error. They simply > don't write. If the backup is configured to write to the same drive that > Server is on, then the backup writes without error.
Keep in mind that when running as a “Service” on Windows the environment is completely different than running 4D Server from a user’s account. Drives and shares may or may not be mounted based on the settings for the user account that is used for the service. Also access to printers can be different. I would do some testing by creating a Stored Procedure that you can run and have it check the path to the backup drive using “Test path name”. If it is available, have the stored procedure create a text file at the backup location and see if that works. Could be that when you are running as a service the user account that is in effect does not have the backup drive mounted or the permissions don’t allow it. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ******************************************** ********************************************************************** 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] **********************************************************************
