Create process failed code 14001??

[Simon]

Hi,

I am developing on windows Vista for XP & Vista machines.
I use VS2008, but I am linking statically, so I assume that I don't need any
redistributable.

But when the users try to launch the app they get an error, "Create process
failed code 14001"

Any idea what the problem could be and how it could be fixed.

Many thanks

Simon

[Joseph M. Newcomer]

Did you first try one of the two blindingly-obvious approaches to this error?

First blindingly-obvious approach: run Error Lookup and type the number in

Second blindingly-obvious approach: search for the error number in winerror.h:

//
// MessageId: ERROR_SXS_CANT_GEN_ACTCTX
//
// MessageText:
//
// The application has failed to start because its side-by-side configuration is
incorrect. Please see the application event log for more detail.
//
#define ERROR_SXS_CANT_GEN_ACTCTX 14001L

Then, did you, as the message suggests, check the event log to see what was wrong? What
did it say?

Note that SxS configurations cover a LOT of DLLs that are not, and cannot be, statically
linked. It is a myth that copy==install except in some rare special cases.

You have said nothing about the conditions under which this occurs; does it happen after
you've moved the program to a different machine? Did you presume that copy==install?

I've no idea what the problem is, but you have to ask the question with enough information
that the people who might know the answer can actually answer it. Even if I knew what the
answer was, I'm more likely to know a bunch of different causes and you have not said
specifically what the actual scenario is under which this occurs.
joe

Joseph M. Newcomer [MVP]
email: newc...@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm

[Simon]

>
> First blindingly-obvious approach: run Error Lookup and type the number in
>
> Second blindingly-obvious approach: search for the error number in
> winerror.h:
>

Well, The error was not so blindlingly obvious at first.

> Then, did you, as the message suggests, check the event log to see what
> was wrong? What
> did it say?

Unfortunalty the application in question is with a user so I cannot check
their logs.
I will install a virtual windows XP machine on my machine and try and
reproduce the error.

>
> Note that SxS configurations cover a LOT of DLLs that are not, and cannot
> be, statically
> linked. It is a myth that copy==install except in some rare special
> cases.
>

As you said, I did not say much in my OP.
But I did not say anything about copy.

The problem was happening at the final steps of the Install app.
The launching of the newly installed software itself.

But I will now test it on a virtual machine and see if I can get the
error(s) and fix it via install.

Regards,

Simon

[Joseph M. Newcomer]

All error codes have the same blindingly-obvious solution. This is just part of what you
need to know to do the most elementary analysis of an error. I continue to be appalled at
the inability of people to do the simplest analysis of an error code, such as actually
looking it up to see what it means. It took me longer to write the response than to
discover what the error code meant (about 30 seconds to launch Error Lookup and type in
14001).

You have to state the nature of the problem. For example, what did you do to deploy it?
Since you know it is a SxS problem, the nature of your distribution is critical. Probably
someone who understands manifests will want to see the manifest file contents.

You can't just say "it doesn't work", and even if you isolate it to the true meaning of
14001, you will then have to provide enough information to someone who understands SxS
installs so they can diagnose it.
joe