为什么CreateProcess的失败在Windows Server 2003 64位？ [英] Why is CreateProcess failing in Windows Server 2003 64-bit?

问题描述

我们有一个32位应用程序，在其过程中启动其他32位应用程序。该应用程序工作正常，在其他64位平台，但在Windows Server 2003 64位，我们得到一个错误尝试启动应用程序：

We have a 32-bit application that launches other 32-bit applications during its process. The application is working fine on other 64-bit platforms but on Windows Server 2003 64-bit, we get an error trying to launch the apps:

error 193 (not a valid 32 bit application)

我们可以手动启动该系统上的这些应用程序没有任何问题。

We can manually launch these applications on that system without any problem.

我认为我们已经找到了这篇文章的问题，但我们的客户已经有了这个补丁在他的系统和故障仍出现。

I thought we had found the problem with this article, but our customer already has this patch on his system and the error is still occurring.

如果任何人都遇到类似的东西，或者如果任何人有关于如何解决这个任何想法，这将是极大的AP preciated！

If anyone else has encountered something similar or if anyone has any idea on how to resolve this, it would be greatly appreciated!

谢谢！ 弗朗索瓦的Côté

Thanks! François Côté

推荐答案

您可能想要做的使用依赖学步车使用自动打开并配置文件的子进程选项，运行时配置文件。这会给你一个更好的主意走多远它越来越并依赖它解决在运行时。

You might want to do a runtime profile using dependency walker using the "automatically open and profile child processes" option. This will give you a better idea how far along it's getting and which dependencies it is resolving at runtime.

这篇关于为什么CreateProcess的失败在Windows Server 2003 64位？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！