Hello -
We are running 1.5 Alpha on a 2019 box as a service on a domain joined system to be used as a central location for the HTTP interface to run queries from URL links and such.
However, when we log off the box completely we can no longer reach the web service. This feels like it's acting more like a program and less like a service. Ideally we want this web service to run regardless of any user login status.
Any thoughts?
Thank you!
Everything as a Service (Windows Server 2019) closing on logoff
Re: Everything as a Service (Windows Server 2019) closing on logoff
I guess you should run the ETP/FTP server option
Re: Everything as a Service (Windows Server 2019) closing on logoff
That doesn't quite work as we are looking to utilize Everything to perform dynamic search queries and then pull up the matching content.
For example, if someone barcode scans a serial number, search in a particular folder for a matching PDF and pull that up in a browser. i.e. "click" the link in a browser to load the PDF that way. FTP would download the file at best, which is not what we're looking for.
For example, if someone barcode scans a serial number, search in a particular folder for a matching PDF and pull that up in a browser. i.e. "click" the link in a browser to load the PDF that way. FTP would download the file at best, which is not what we're looking for.
Re: Everything as a Service (Windows Server 2019) closing on logoff
ETP is Everything's extension to the FTP protocol/server. Using an ETP Server should work for your organization too (at least: based on the requirements you specified) as you can open files too.
However ...
That would still give you the same issue: logging off == exiting Everything.
To fix that, here are the instructions to run an ETP Server as a service
They are similar for the HTTP Server.
However ...
That would still give you the same issue: logging off == exiting Everything.
To fix that, here are the instructions to run an ETP Server as a service
They are similar for the HTTP Server.
Re: Everything as a Service (Windows Server 2019) closing on logoff
Thanks for the response! Sorry if my requirements were not well defined enough - I'll try to explain better.
With the ETP server, my understanding is we would need to install this client on every endpoint, and then connect those endpoints to the ETP server? That is not an ideal solution if it can be avoided.
Ideally it would be a barcode that software would do a web lookup against a dynamic url such as this: http://productionfileserver/?search=pdf+SN82812
Then, it would simply just load the document with some custom HTML to open unique search results. (You helped me with this years back, lovely fix.)
So that's the goal. If it helps further, it's from a manufacturing assemblers station. They pick up a work order, scan the order, then it will do some logic to find the matching work instruction, and then pull it up via Everything. I had this working at a prior company with a less secure method of having a server that -never- logged out, so I didn't fully realize the issue until now as I try to repeat it at another organization. It allowed them to scan a document and have the matching instructions up instantly. Any other method had delays and failure points behind it I wasn't a fan of.
Now ultimately if it's not doable I can figure something similar out, but it is quite a security risk. Additionally, anytime the server is patched, it would require some manual effort to get the items back in place - which is what I had to do at the prior.
Hopefully that makes sense!
With the ETP server, my understanding is we would need to install this client on every endpoint, and then connect those endpoints to the ETP server? That is not an ideal solution if it can be avoided.
Ideally it would be a barcode that software would do a web lookup against a dynamic url such as this: http://productionfileserver/?search=pdf+SN82812
Then, it would simply just load the document with some custom HTML to open unique search results. (You helped me with this years back, lovely fix.)
So that's the goal. If it helps further, it's from a manufacturing assemblers station. They pick up a work order, scan the order, then it will do some logic to find the matching work instruction, and then pull it up via Everything. I had this working at a prior company with a less secure method of having a server that -never- logged out, so I didn't fully realize the issue until now as I try to repeat it at another organization. It allowed them to scan a document and have the matching instructions up instantly. Any other method had delays and failure points behind it I wasn't a fan of.
Now ultimately if it's not doable I can figure something similar out, but it is quite a security risk. Additionally, anytime the server is patched, it would require some manual effort to get the items back in place - which is what I had to do at the prior.
Hopefully that makes sense!
Re: Everything as a Service (Windows Server 2019) closing on logoff
Yes, that made sense 
Thank you for explaining.
In that case, using a HTTP Server would indeed be better.
In the link I posted you can find instructions to run your Everything HTTP Server as a service.
My personal suggestion would be to start this service delayed, to avoid "reboot-rushhour"
(Startup Type = Automatc (Delayed startup) in services.msc)
Thank you for explaining.In that case, using a HTTP Server would indeed be better.
In the link I posted you can find instructions to run your Everything HTTP Server as a service.
My personal suggestion would be to start this service delayed, to avoid "reboot-rushhour"
(Startup Type = Automatc (Delayed startup) in services.msc)
Re: Everything as a Service (Windows Server 2019) closing on logoff
I see installing as a service for ETP, but not for HTTP.
I tried the ETP method, but it gave the following error:
Unable to create the Everything Service: 1072
Some googling said that it may not be possible to install it as a service when HTTP is enabled?
I tried the ETP method, but it gave the following error:
Unable to create the Everything Service: 1072
Some googling said that it may not be possible to install it as a service when HTTP is enabled?
Re: Everything as a Service (Windows Server 2019) closing on logoff
Tried a few other things, still not getting the ultimate best result. Any thoughts? Otherwise I may just have a dedicated computer that is on 24/7 handle it.
Re: Everything as a Service (Windows Server 2019) closing on logoff
It is still on my agenda to test and describe this, but that has to wait until tomorrow due to lack of time.
Re: Everything as a Service (Windows Server 2019) closing on logoff
Please see Everything Client Service Help
Running Everything as a client service will allow you to run an Everything HTTP Server without having to be logged in.
Error 1072: ERROR_SERVICE_MARKED_FOR_DELETE
The Everything client service is pending deletion.
Please try restarting your PC.
The old client service will be removed on the next boot.
Please try reinstalling the client service.
Running Everything as a client service will allow you to run an Everything HTTP Server without having to be logged in.
Error 1072: ERROR_SERVICE_MARKED_FOR_DELETE
The Everything client service is pending deletion.
Please try restarting your PC.
The old client service will be removed on the next boot.
Please try reinstalling the client service.