Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

OpenEdge GUI client fails to start with Microsoft Visual C++ Runtime Library error R6034


PROWIN32 fails to start with Microsoft Visual C++ Runtime Library error R6034

PROWIN32 fails to start with Microsoft Visual C++ Runtime Library error R6034


Microsoft Visual C++ Runtime Library
Program: %DLC%\bin\prowin32.exe
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.

Microsoft Visual C++ Runtime Library
Program: %DLC%\bin\prowc.exe
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.

FACT(s) (Environment):

No errors occur during installation
Full installation of OpenEdge located on a local drive.
Users have full permissions to access the drive
Removing and reinstalling Microsoft Visual C++ 2005 SP1 Redistributable Package (vcredist_x86.exe) on the client does not make a difference
OpenEdge 10.x
Windows
OpenEdge Category: Installation

CAUSE:

The manisfest file that should be used by the client executable cannot be found. The manifest file controls which .DLL versions the executable is supposed to use. The manifest file is located in %DLC%\bin\<executable name>.manifest (where %DLC% is your OpenEdge installation folder).

FIX:

Ensure that the manifest file for PROWIN32.EXE or PROWC.exe is available and add the file to the Working Directory specified when installing on the client.

If this still fails, please trying specifying the location of the manifest file in the PATH environment variable of the client machine.


FIX:

References to Written Documentation:

Progress Solutions:
P165313, "PROWIN32 fails to start with Microsoft Visual C++ Runtime Library error when executed from Shared Network Installation"