🚀 go-pugleaf

"Quentin David Jones" <quentin.jones@romteck.com.spamprotect> wrote in
message news:4578ed46@newsgroups.borland.com...

> 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

If the user account is local to the machine that the service is installed
on, then use the second format above, as per the documentation.

> Step B - START the service.
> This produces two events immediately:
> 1. Application event "Socket activated" - as expected

Then the service is starting properly, and the socket is opened.

> 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'. "
>
> What on earth is this ASync Lookup error caused by?

The only way for that to occur is if you have the TServerSocket's Service
property set to a non-empty string.  When you do that, TServerSocket
dynamically queries the port number that is associated with the specified
Service provider.  Obviously, you are setting the Service to an invalid
value.  You should get rid of the Service property value altogether and just
set the Port property directly instead.

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

As it should be.  Uncaught exceptions that occur in the context of
TService's thread will be passed to the NT Event Log.


Gambit