First, specifying the -lf parameter without an argument causes a problem because the parser assumes that the next argument is a file name. I thought that it was also used as a boolean parameter (-lf for file logging, -lc for console logging, -ls for stdout). Turns out that -lf is the default, and that you only need to use it if you want to change the name of the file.
In reading further stuff in the EMSRV docs, it talks about making sure that the EMSRV account that you use has the authority to "Log on as a service". That got me past the WINSOCK issue.
On Friday, December 15, 2017 at 4:49:04 PM UTC-6, Steven LaFavor wrote:
The company here is migrating servers from 2008 to 2012, and we are trying to move the smalltalk repositories from one machine to another.
In trying to install the EMSRV process on the new machine (I'm using the one that was distributed with 8.6.3), I am using the following line:
I wanted to ask a question for Windows installations of EMSRV.
As companies are wont to do, there are "security cleanups" of older userid accounts, as well as reorganization/restructuring of assets, etc....So an account that was being used to execute the EMSRV process was being removed.
I removed the existing EMSRV service thru SC DELETE.
I then installed a new EMSRV service/process without using the -u and -p parameters, thinking that I would be able to use the "Run under a specific account" on the services' properties page. But that does not seem to work. The service starts and immediately stops.
Adding the -u and -p parameters with the account information works, of course
Is there a reason why the EMSRV code does not use the Log On As... settings in the Services dialog? Or am I missing something here?