Running dhRPCService on Win7 64

[Phil McFarlane]

The computer (Win2000) that I have been running as
my server currently has issues. I have therefore
started using a Win7 64 computer as a server.
dhRPCService ran as expected under Win2000 and
automatically started when the server was
restarted. This however appears not to be the case
under Win7 64.

When dhRPCService is started under Win7 64 it runs
fine however the service does not show in the list
of services and needs to be started manually if
windows is restarted. A look using Sysinternals
Process Explorer shows that it is being run as a
job and is a child process of Explorer.exe.

My question is: Is there a way to to run
dhRPCService as a service under win7 64.

[Schmidt]

Post by Phil McFarlane
The computer (Win2000) that I have been running as
my server currently has issues. I have therefore
started using a Win7 64 computer as a server.
dhRPCService ran as expected under Win2000 and
automatically started when the server was
restarted. This however appears not to be the case
under Win7 64.
When dhRPCService is started under Win7 64 it runs
fine however the service does not show in the list
of services and needs to be started manually if
windows is restarted. A look using Sysinternals
Process Explorer shows that it is being run as a
job and is a child process of Explorer.exe.
My question is: Is there a way to to run
dhRPCService as a service under win7 64.

Whew, seems I have to install a Win7-64Bit-system here
the next weeks, to play around with all that on my own.

Cannot give any hints for that so far - other than to
"use the dhRPC-Service-App on known 32Bit OSes". ;-)
BTW, this does not need to be a full-blown Server-OS.
A "normal XP-Pro" does just fine, even for more than
10 concurrent connections (this XP-limit is there only for
the "wellknown MS-Networkservices").

Maybe one thing you could try (if the whole thing is not
that much 64Bit-related, but potentially a "UAC-thing")...
The registering of the ServiceApp (as a System-Service)
is done from the Controller-Application dynamically.
And as with all "registering-stuff", which is not run "elevated",
there might be problems with the UAC.

Maybe it helps, if you create a link to the *Controller-App*
first (on your Desktop). Then right-click on that "Link-Icon"
and switch to the setting: "Run as Administrator" there.
Then Double-Click the Controller-Link-Icon, answer the
"do you really want to run this stuff as Admin"-question
with yes - and then try to click the "Run as Service"
checkbox after that (which under the hood tries to attempt to
register the ServiceApp.exe under the hood, and from
the now elevated Controller-App this might succeed).

HTH

Olaf

[Phil McFarlane]

Post by Schmidt

Post by Phil McFarlane
The computer (Win2000) that I have been running as
my server currently has issues. I have therefore
started using a Win7 64 computer as a server.
dhRPCService ran as expected under Win2000 and
automatically started when the server was
restarted. This however appears not to be the case
under Win7 64.
When dhRPCService is started under Win7 64 it runs
fine however the service does not show in the list
of services and needs to be started manually if
windows is restarted. A look using Sysinternals
Process Explorer shows that it is being run as a
job and is a child process of Explorer.exe.
My question is: Is there a way to to run
dhRPCService as a service under win7 64.

Whew, seems I have to install a Win7-64Bit-system here
the next weeks, to play around with all that on my own.
Cannot give any hints for that so far - other than to
"use the dhRPC-Service-App on known 32Bit OSes". ;-)
BTW, this does not need to be a full-blown Server-OS.
A "normal XP-Pro" does just fine, even for more than
10 concurrent connections (this XP-limit is there only for
the "wellknown MS-Networkservices").
Maybe one thing you could try (if the whole thing is not
that much 64Bit-related, but potentially a "UAC-thing")...
The registering of the ServiceApp (as a System-Service)
is done from the Controller-Application dynamically.
And as with all "registering-stuff", which is not run "elevated",
there might be problems with the UAC.
Maybe it helps, if you create a link to the *Controller-App*
first (on your Desktop). Then right-click on that "Link-Icon"
and switch to the setting: "Run as Administrator" there.
Then Double-Click the Controller-Link-Icon, answer the
"do you really want to run this stuff as Admin"-question
with yes - and then try to click the "Run as Service"
checkbox after that (which under the hood tries to attempt to
register the ServiceApp.exe under the hood, and from
the now elevated Controller-App this might succeed).
HTH
Olaf

After some further investigation I now have
everything working.

First step was to install the service using the
controller application. This does install OK and
sets the start-up type to automatic and the log on
as local system account. However the service does
not start when the system is restarted.

Changing the log on to a user account with
suitable credentials allowed the service to start
automatically at system restart.

The problem was of course a UAC thing. All changes
were made using 'Run as administrator'

Phil

[Ralph]

Phil McFarlane wrote:
<snipped>

Post by Phil McFarlane
Changing the log on to a user account with
suitable credentials allowed the service to start
automatically at system restart.

Thanks for reporting back.

That actually helped me with some other service issues. Amazing how one can
over-look the obvious. <g>

-ralph

[Schmidt]

Post by Phil McFarlane
First step was to install the service using the
controller application. This does install OK and
sets the start-up type to automatic and the log on
as local system account.
However the service does
not start when the system is restarted.
Changing the log on to a user account with
suitable credentials allowed the service to start
automatically at system restart.

Thanks for reporting back - and good to know,
that the whole thing (SQLiteDB-engine + RPCServer
+ regfree instantiations per DirectCOM.dll) work
also on a "shiny new 64Bit-OS"... ;-)
Also with regards to general "embedding/upstarting of
32Bit-service-Apps".

Seems I can delay my "Win7-test-install" somewhat further...
<g>


Olaf