• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 838
  • Last Modified:

Application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

Hi there;

I got an C++ application that I compilen in 32-bit Windows XP and works without an issue but;

When it comes to Windows 7-64 bit, it fails to operate and gives the following error:

Application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

How to fix?

I want it to run in Windows 7-64 bit too. I am using VS2010

Kind regards.
0
jazzIIIlove
Asked:
jazzIIIlove
  • 11
  • 4
  • 2
  • +1
5 Solutions
 
ZoppoCommented:
Hi jazzIIIlove,

I think you'll have to install the VS 2010 redistributables on the target machine. You can download it here for Windows 7 64 bit: http://www.microsoft.com/download/en/details.aspx?id=14632

Hope that helps,

ZOPPO
0
 
jazzIIIloveAuthor Commented:
hmm, wait wait.

I misinformed you, I did the implementation in Windows XP 32-bit but in VS 2008
where as the target machine is Windows 7 64-bit (which has VS 2010 which is irrelevant).

Yep, long day...you know...

Kind regards.

0
 
jazzIIIloveAuthor Commented:
Here you go, in my 7-64 bit, c++ redists.

Kind regards. redist
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jkrCommented:
Have you tried the Dependency Walker (www.dependencywalker.com) to see which file(s) is/are missing?
0
 
jazzIIIloveAuthor Commented:
When I check for the event viewer, there is a source named as SideBySide and the output in the event viewer is as follows:

Activation context generation failed for "C:\My.EXE". Dependent Assembly Microsoft.VC90.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e5b",type="win32",version="9.0.21022.8" could not be found.

But I installed as above and still the same problem.

Kind regards.
0
 
jazzIIIloveAuthor Commented:
Very nice tool. Definitely, an architecture problem.

The output is as follows from dependency walker is as follows:

Error: The Side-by-Side configuration information for "c:\Mycollection\Myfor\My.EXE" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
Error: The Side-by-Side configuration information for "c:\Mycollection\Myfor\MyUITP.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
Error: The Side-by-Side configuration information for "c:\Mycollection\Myfor\My32P.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
Error: The Side-by-Side configuration information for "c:\Mycollection\Myfor\MyP.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
Error: At least one required implicit or forwarded dependency was not found.
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

Kind regards.
0
 
jazzIIIloveAuthor Commented:
And the program is working correctly after i build it in VS 2008 in Windows XP-32 bit but fails in windows 7 even in compatibility mode...

Kind regards.
0
 
evilrixSenior Software Engineer (Avast)Commented:
The couple of times I've had this it was because I had the wrong version of the Debug CRT installed. More specifically, I had a different version of release and debug CRT (caused by a Microsoft Update). Make sure your release and debug CRT match and both are the latest version for your compiler (ie, install any service pack that is outstanding).
0
 
jazzIIIloveAuthor Commented:
Ok, what is CRT and how can i find out the appropriate one for Windows 7? Which package?

Regards.
0
 
jazzIIIloveAuthor Commented:
Hi there;

I haven't checked but 2008 redistributable SP1 x86 and x64 are not installed in my Windows 7 64 bit.

I will inform you on monday.

Regards.
0
 
evilrixSenior Software Engineer (Avast)Commented:
>> what is CRT

Sorry, CRT = C Runtime... basically the framework that provides all the libraries and stuff for running C/C++ applications.
0
 
ZoppoCommented:
>> Dependent Assembly Microsoft.VC90.DebugCRT
Is it a DEBUG build? If so IMO installing the redistributable won't fix the problem since it doesn't contain DEBUG version of CRT. You'll have to install VS 2008 on the target machine to get the DEBUG versions installed. For a RELEASE build installing the appropriate reditributable should solve the problem ...

ZOPPO
0
 
jazzIIIloveAuthor Commented:
>>Is it a DEBUG build? If so IMO installing the redistributable won't fix the problem since it doesn't contain >>DEBUG version of CRT.

You are right, nothing changed.

>>You'll have to install VS 2008 on the target machine to get the DEBUG versions installed.
Oh, dear...But why?...

>>For a RELEASE build installing the appropriate reditributable should solve the problem ...
Ok, I did but the release folder is empty, why?

Regards.
0
 
ZoppoCommented:
>> >>You'll have to install VS 2008 on the target machine to get the DEBUG versions installed.
>> Oh, dear...But why?...

Because the DEBUG versions of many needed DLLs are shipped with VisualStudio only, they aren't part of the redistirbutables since usually no one needs them except those who write applications with VisualStudio. Usually only RELEASE builds are intended to run on machines where no VS is installed.

>> >>For a RELEASE build installing the appropriate reditributable should solve the problem ...
>> Ok, I did but the release folder is empty, why?
Hard to say - did the build succeed? I guess it's a matter of different project settings in RELEASE configuration. Check project settings and compare all path-related settings (especially within linker settings) with those form the DEBUG configuration ...

0
 
jazzIIIloveAuthor Commented:
>>Hard to say - did the build succeed? I
Yep.

>> guess it's a matter of different project settings in RELEASE configuration. Check project settings and compare all path-related settings (especially within linker settings) with those form the DEBUG configuration ...

You mean configuration manager of the solution or propery of the project(s)

Configuration of the solution is Release/Win32

Configuration of one project (there are several but the setting is same for all) as in the shot.

But the executable and dlls are not there.

What should I do?

Kind regards.
project.png
0
 
jazzIIIloveAuthor Commented:
Ok, solved, I simply search for the executable name in the solution, and find out there is another release folder created and yes, copy paste from the release works.

Regards.
0
 
jazzIIIloveAuthor Commented:
But why the hell that release folder is created in the 2 upper folder?

Where to set this?

Regards.
0
 
ZoppoCommented:
Usually the binaries are put into the folders '<solution_path>\Release' or '<solution_path>\DEBUG' - this is defined in each project's linker settings 'OutputFile' which is '$(OutDir)$(TargetName)$(TargetExt)' per default. The '$(OutDir)' is set in 'Configuration Properties->General' as 'Output Directory', the default here is '$(SolutionDir)$(ConfigurationName)'. So, i.e. for an EXE built from a project 'MyProject' the resulting binary is '<solution_path>\Release\MyProject.exe' for RELEASE build and '<solution_path>\DEBUG\MyProject.exe' for DEBUG builds. Compare these settings between DEBUG and RELEASE cofnigurations ...
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 11
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now