🚀 go-pugleaf

Hi again,

OK,
I made changes as suggested:
* start socket INactive, switched on in ServiceStart
* useEvent log for output

For user names (ServiceStartName and Password in service properties),
I have tried 3 options:
quentin.jones, password
.\quentin.jones, password
quentin.jones@romteck.com, password


I also looked under the LOGIN tab for the service, and enabled Login as Service for both
quentin.jones and
quentin.jones@romteck.com
(and asked our support people to set Login as Service for that user on the MMC.)
I know you said it wasn't needed, but I thought I try it - it didn't help.
Note: When I entered quentin.jones, it changed to .\quentin.jones, so that's why I tried that option.


So,
here is the current situation -

For BOTH local user .\quentin.jones and domain user quentin.jones@romteck.com I get the following result :

Step A - Build and install the service (command line "datesvcserver /install")
The service installs without error, and appears in the SCM.

Step B - START the service.
This produces two events immediately:
1. Application event "Socket activated" - as expected
2. ERROR event " Windows socket error: The requested name is valid and was found in the database, but it does not have 
the correct associated data being resolved for (11004), on API 'ASync Lookup'. "

Will post new code below.

What on earth is this ASync Lookup error caused by?

(Note that it only shows in Event Viewer now, not as a Windows error popup.)


Quentin