Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 8 of 8 total |
Problems with running server as a service |
Tue, Dec 20 2016 12:58 PM | Permanent Link |
Michael Saunders | I have hit a problem running my app remotely with edbsrvr running as a service for a specific database There is no problem when running edbsrvr from the desktop or as a service with other databases but when this particular database is used I get an error (see attachment) Stopping and restarting the service does not make any difference nor does replacing it with a backup database using explorer I would have thought replacing the complete database including rhe EDBDatabase files would have fixed it and this concerns me
Many thanks Attachments: error.JPG |
Tue, Dec 20 2016 3:09 PM | Permanent Link |
Terry Swiers | Hi Michael,
Is the E: drive a mapped network drive? If it is, you will need to change the account that the EDB server is running under. By default, it will run under the local system user which doesn't have access to anything that isn't directly connected to the system. Changing the EDB service to log on and run under an account that has access to the network drive should resolve the issue. |
Tue, Dec 20 2016 4:39 PM | Permanent Link |
Michael Saunders | Interestingly this issue occured after I had set the path as a mapped drive on the host (which did not work as I presume the service has no knowlege of mapped drives) and then and then set it back agaiin to a genuine drive letter.
I accept I have screwed this up somehow but cannot understand why a PC reboot as well as a database folder replacement using windows explorer (which includes all the EDBDatabase files) does not correct this issue Any ideas Mike |
Tue, Dec 20 2016 7:46 PM | Permanent Link |
Raul Team Elevate | On 12/20/2016 4:39 PM, Michael Saunders wrote:
> Interestingly this issue occured after I had set the path as a mapped drive on the host (which did not work as I presume the service has no knowlege of mapped drives) and then and then set it back agaiin to a genuine drive letter. Service runs under special local system service account (unless you change it). By default i believe it does not even have network access and even if it did it would not see user mapped drives (since mapped drives are specific to logged in user)/ > I accept I have screwed this up somehow but cannot understand why a PC reboot as well as a database folder replacement using windows explorer (which includes all the EDBDatabase files) does not correct this issue What exactly did you replace ? EDB is catalogue based so you'd need to restore the catalogue as it stores the paths if you moved databased from local drive to network or such. However the path to the catalogue in stored in the edbsrvr.ini file (under common data folder) so you either need to restore it as well or at least start the server and reconfigure it to update the config folder path Raul |
Wed, Dec 21 2016 7:06 AM | Permanent Link |
Michael Saunders | Raul wrote:
What exactly did you replace ? Firstly I have removed all mapped drives from my PC and do not reference them anywhere Plus I keep all my databases in separate folders each of which which includes the 3 EDBDatabase files ~(EDBCAT, EDBCATOLD and EDBLCK) I am trying to resolve this using EDBManager with 2 sessions A local Session plus a Remote session The particular database I am having an issue with opens fine using the local session as well as with the remote session provided I am running it the server with user interaction However when I restart the server as as service I get the error previously described What I do not understand is that if I replace the problem database folder contents with a backed up copy using Windows Explorer the error still persists Surprising as the backed up database opens without issue in the Remote session even with the service running as a service EDB is catalogue based so you'd need to restore the catalogue as it stores the paths if you moved databased from local drive to network or such. However the path to the catalogue in stored in the edbsrvr.ini file (under common data folder) so you either need to restore it as well or at least start the server and reconfigure it to update the config folder path The only path here is to the Config File location I have checked this and it is pointing to the correct place Thanks for your help Mike |
Wed, Dec 21 2016 8:33 AM | Permanent Link |
Raul Team Elevate | On 12/21/2016 7:06 AM, Michael Saunders wrote:
> Firstly I have removed all mapped drives from my PC and do not reference them anywhere Plus I keep all my databases in separate folders each of which which includes the 3 EDBDatabase files ~(EDBCAT, EDBCATOLD and EDBLCK) > > I am trying to resolve this using EDBManager with 2 sessions A local Session plus a Remote session The particular database I am having an issue with opens fine using the local session as well as with the remote session provided I am running it the server with user interaction However when I restart the server as as service I get the error previously described The OS error listed in the original post indicates possible file permissions issue. > What I do not understand is that if I replace the problem database folder contents with a backed up copy using Windows Explorer the error still persists Surprising as the backed up database opens without issue in the Remote session even with the service running as a service I would start checking folder permissions first and file permissions after. EDB Manager and EDBSrvr running interactively use your logged in user account credentials. Service uses whatever account service is configured with (by default local system or local service) so my guess here is permissions issue Raul |
Wed, Dec 21 2016 9:48 AM | Permanent Link |
Michael Saunders | Raul wrote:
I would start checking folder permissions first and file permissions after. Thanks Raul you are absolutely correct This folders permissions were only set for the logged in User The SYSTEM User which I assume was needed for the service to worlk properly was completly missing How that had occured I have no idea but after restoring it it all works OK Thanks again Mike |
Wed, Dec 21 2016 10:13 AM | Permanent Link |
Michael Saunders | Thinking about this maybe by providing a networked file path to the database folder (which I can see now is to be avoided if I run the server a a service) means that the SYSTEM User is removed or not included when setting up the paths initally using EDBManager
Mike |
This web page was last updated on Sunday, May 5, 2024 at 10:18 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |