Re: Windows Service / Registry security
- From: "Skywing [MVP]" <skywing_NO_SPAM_@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 18 Aug 2006 18:36:32 -0400
14001 is a Side-by-Side (SxS) error. I would imagine that you are linking
to the DLL version of the C runtimes and did not install the appropriate C
runtime DLLs through SxS on the target computer.
--
Ken Johnson (Skywing)
Windows SDK MVP
"Mystagogue" <Mystagogue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F4EE623B-4F96-4F04-9CF4-8212E4C63647@xxxxxxxxxxxxxxxx
I've taken over legacy code (no documentation of course), where I need to
"drop in" debug builds of executables / DLLs on top of an existing
installation of the legacy app (installed on XP SP1).
One of the executables (built with VS2003) is registered as a service in
the
"services" MMC. When I stop the service, and replace it with a debug
version
of the same exe (built with VS2005), and then restart the service, I get
this
message:
Could not start the <MyApp> service on Local Computer
Error 14001: This application has failed to stat because the application
configuration is incorrect. Reinstalling the application may fix this
problem.
I'm wondering if this is because my debug exe does not have an internal
checksum or ID that correctly matches a registry entry I found in
"HKEY_LOCAL_MACHINE -> System -> CurrentControlSet -> Services ->
<MyApp> ->
Security". It contains:
Security REG_BINARY 01 00 14 80 90 00 00 00 ... <etc, etc>
In short, I'm making a guess that this app has some security built in
(perhaps leveraging win32 offerings) that tries to match the exe signature
against that registry entry (and unfortunately my debug build doesn't
"pass").
So I'm writing this in hopes that someone can confirm / deny that the
above
registry entry is "telltale" of the signature matching I'm suggesting. If
not, is it "telltale" of any particular windows / win32 idiom?
It may be that the above registry entry is entirely peculiar to the legacy
app. But if it is, unfortunately I have yet to find its origin in the
legacy
code.
.
- Prev by Date: Re: Role of the code segment register during "far" CALLs
- Next by Date: Re: Role of the code segment register during "far" CALLs
- Previous by thread: Role of the code segment register during "far" CALLs
- Next by thread: about drive remap
- Index(es):
Relevant Pages
|
