Incorrect side-by-side configuration?

[Rachel Weinstein Petterson]

Hi,

I'm trying to install (aka copy over and run) a debug version of Chromium on a test machine, but when I go to run it, I get the following error:

This 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.

Googling this suggested that I didn't have the correct Visual C++ Runtime DLLs installed, but I've tried installing various versions (2005, 2008, 2010) and that has not helped.

I am on Windows 7 Enterprise 64-bit, but building for 32 bit in Visual Studio. The machine in question is running Window 7 Ultimate N 32-bit. Testing my copy on other machines seems to work which implies that there is something wrong with the setup of the test machine such that I can't run my debug build.

Anyone know how to get my debug version running on this test machine?

Thanks,

Rachel

[Ricardo Vargas]

See the common issues section of  http://www.chromium.org/developers/how-tos/component-build 

tldr: copy the crt from the redist/debug_noredist vc folder to the target folder on the target machine.

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Rachel Weinstein Petterson]

Thank you, Ricardo!

- Rachel

[Alex Pakhunov]

Hi,

You can also do what the error message suggests you to do - use sxstrace.exe to get the exact version of the runtime library you are missing. From an elevated command promt:

1. sxstrace.exe Trace -logfile:sxstrace.etl
2. Launch Chromium
3. Stop the trace. sxstrace.exe will promt you to hit Enter at step #1 to stop it I believe.
4. sxstrace.exe Parse -logfile:sxstrace.etl -outfile:sxstrace.txt

sxstrace.txt will shown the log of SxS events including errors. Once you get the full assembly name from the log it will be easier to google for exact version of the runtime you need. They all available at download.microsoft.com but it is not possible to search by version number so Google to the rescue. :-)

Alex.

On Tue, May 22, 2012 at 4:46 PM, Rachel Weinstein Petterson <r...@chromium.org> wrote:

--

[Rachel Weinstein Petterson]

Hi, Alex,

I did use sxstrace to figure that out, but unfortunately the CRT files are what I need to run a debug version and those aren't available for download AFAICT. Ricardo's method solves that issue.

- Rachel

[Gabriel Charette]

On Tue, May 22, 2012 at 8:07 PM, Ricardo Vargas <rva...@chromium.org> wrote:

See the common issues section of  http://www.chromium.org/developers/how-tos/component-build 

tldr: copy the crt from the redist/debug_noredist vc folder to the target folder on the target machine.

tldr: You need to copy chrome.exe, chrome.exe.manifest, and *.dll from the build output.

As of http://codereview.chromium.org/10399041/ : you also need to copy chrome.exe.manifest from your build output.

As of http://codereview.chromium.org/10387140/ : The CRT DLLs are copied to the build output (mainly to make installing a component build on another machine work, but if you copy *.dll along with chrome.exe they should be picked up).

Cheers,

Gab

[Ricardo Vargas]

On Thu, May 24, 2012 at 8:12 AM, Gabriel Charette <g...@chromium.org> wrote:

On Tue, May 22, 2012 at 8:07 PM, Ricardo Vargas <rva...@chromium.org> wrote:

See the common issues section of  http://www.chromium.org/developers/how-tos/component-build 

tldr: copy the crt from the redist/debug_noredist vc folder to the target folder on the target machine.

tldr: You need to copy chrome.exe, chrome.exe.manifest, and *.dll from the build output.

the common workflow (copy stuff to a single folder on the target machine) does not require copying chrome.exe.manifest, right?

[Gabriel Charette]

On Thu, May 24, 2012 at 3:33 PM, Ricardo Vargas <rva...@chromium.org> wrote:

On Thu, May 24, 2012 at 8:12 AM, Gabriel Charette <g...@chromium.org> wrote:

On Tue, May 22, 2012 at 8:07 PM, Ricardo Vargas <rva...@chromium.org> wrote:

See the common issues section of  http://www.chromium.org/developers/how-tos/component-build 

tldr: copy the crt from the redist/debug_noredist vc folder to the target folder on the target machine.

tldr: You need to copy chrome.exe, chrome.exe.manifest, and *.dll from the build output.

the common workflow (copy stuff to a single folder on the target machine) does not require copying chrome.exe.manifest, right?

Now yes, chrome.exe.manifest used to be embedded in chrome.exe, but now (for the component build only) it is layed beside chrome.exe instead so that we can do necessary manipulations to it before putting it in the installer's archive.

This means that your chrome.exe now does NOT have a manifest in it (which could potentially lead to very subtle issues, so I highly recommend copying it over to your target machine as well).

Cheers,

Gab