Kbase P165313: PROWIN32 fails to start with Microsoft Visual C++ Runtime Library error when executed from Shared Ne
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/3/2010 |
|
Status: Unverified
SYMPTOM(s):
PROWIN32 fails to start with Microsoft Visual C++ Runtime Library error when executed from Shared Network Installation
Microsoft Visual C++ Runtime Library
Program: Z:\OpenEdge\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 article C Run-Time Error R6034 suggests that the error can be related to the .manifest file
Custom prowin32.exe.manifest file is used:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<description>Windows Forms Common Control manifest</description>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
</assembly>
FACT(s) (Environment):
No errors occur during netsetup installation
Full installation of OpenEdge located on a mapped drive.
Users have full permissions to access the mapped drive
No problems seen when starting PROWIN32.EXE directly on the server where the full installation is located
No problems seen when starting PROWIN32.EXE from 10.1B netsetup
Removing and reinstalling Microsoft Visual C++ 2005 SP1 Redistributable Package (vcredist_x86.exe) on the client does not make a difference
A version of prowin32.exe.manifest has been included in the product since OpenEdge 10.1A was released
OpenEdge 10.1C
OpenEdge 10.2x
Windows
CHANGE:
Upgraded to OpenEdge 10.2B
CAUSE:
In OpenEdge 10.1C the format of the prowin32.exe.manifest file changed, adding an entry for Microsoft.VC80.CRT. This change rendered the custom prowin32.exe.manifest file incompatible/unsuitable for use with OpenEdge 10.1C and later; the custom format can only be used with versions 10.0B, 10.1A and 10.1B.
FIX:
Option #1
Use the version of the prowin32.exe.manifest file shipped with OpenEdge 10.1C and later
Option #2
Modify the content of the custom prowin32.exe.manifest file as follows:
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
<dependency>
<dependentAssembly>
<assemblyIdentity type='Win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*' />
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type='win32' name='Microsoft.VC80.CRT' version='8.0.50608.0' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' />
</dependentAssembly>
</dependency>
</assembly>