After upgrade from 10.2B to 11.5.1: VC++ Error R6034 calling external dll - Forum - OpenEdge Deployment - Progress Community

After upgrade from 10.2B to 11.5.1: VC++ Error R6034 calling external dll

 Forum

After upgrade from 10.2B to 11.5.1: VC++ Error R6034 calling external dll

This question has suggested answer(s)

After an update from 10.2B(32bit) to 11.5.1 (32bit) we hit this error from the VC++ Runtime Library when we call an procedure in an existing dll.

R6034
An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support tem for more information.

procmon shows that syswow64\msvcr80.dll is called

Any suggestions? The used dll remained the same.

All Replies
  • Was it just Progress version that changed or did you change windows version too?
     
    James Palmer | Application Developer
    Tel: 01253 785103 | Fax: 01253 785001 | Web: www.inenco.com | Twitter : @inenco

    footer
     
    From: Stefan Marquardt [mailto:bounce-Marquardt@community.progress.com]
    Sent: 11 June 2015 15:39
    To: TU.OE.Deployment@community.progress.com
    Subject: [Technical Users - OE Deployment] After upgrade from 10.2B to 11.5.1: VC++ Error R6034 calling external dll
     
    Thread created by Stefan Marquardt

    After an update from 10.2B(32bit) to 11.5.1 (32bit) we hit this error from the VC++ Runtime Library when we call an procedure in an existing dll.

    R6034
    An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support tem for more information.

    procmon shows that syswow64\msvcr80.dll is called

    Any suggestions? The used dll remained the same.

    Stop receiving emails on this subject.

    Flag this post as spam/abuse.




    This email has been scanned for email related threats and delivered safely by Mimecast.
    For more information please visit http://www.mimecast.com
  • Sounds like your manifest file is missing.

    knowledgebase.progress.com/.../000029416

    Make sure you have the manifest files in the proper location and/or the PATH is set properly.

  • Same server, only 10.2b removed, 11.5.1 installed, db conversion, compile and copy the external dll to .\bin directory again.

    The prowin32.exe.manifest is in the .\bin dir too - that's the fresh 11.5.1 installation.

  • Hmmmm,,, just throwing some ideas out at this point.

    Do the mainfest files look ok in both directories?

    Maybe try copying them to your working directory?

  • It seems to be an error in the used external dll because OE 11.5.1 now uses another VC++ dll.