cancel
Showing results for 
Search instead for 
Did you mean: 

We have Migrated the powerbuilder from 2008 to 2012 server

Former Member
0 Kudos

We have Migrated the Powerbuilder from 2008 to 2012 server.

There is one executable file which is not executing in 2012 server but it is executing on 2008 server.

Below are the error which i am getting.

It is showing that "The Program can't start because MSVCP71.dll is missing from your computer. Try reinstalling the program to fix this problem.

This dll is already being installed.

Error we get is :

Event 1000, Application Error


Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Sure, i will look at it and update the status.

Thanks!

former_member202249
Active Participant
0 Kudos

Aruna,

As Chris asked above, please let us know what version and build of PB you are using.

FYI, only PB 12.6 is fully supported on Windows Server 2012.

Pat

Former Member
0 Kudos

We are not understanding what is going wrong. Only one file is failing to execute after migration rest all are working in 2012 server

This is what we did:

I am assigned to the case that you submitted below. It seems that the ld_mileageinsert.exe application is failing and not CWA. Have you tried to run it outside of CWA?

Problem Details: Job fails on 2012 server but runs successfully on 2008 server. Our DBAs are not sure why.

I'm just looking into some insight here

Event log

Faulting application name: ld_mileageinsert.exe, version: 1.0.0.1, time stamp: 0x4cdaaed3

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00050600

Faulting process id: 0x8d4

Faulting application start time: 0x01d3d24720f6ce85

Faulting application path: C:\PB\FRT_MI~1\LDMILE~2\ld_mileageinsert.exe

Faulting module path: unknown

Report Id: 5ef46a5d-3e3a-11e8-810d-0050569321ec

Faulting package full name:

Faulting package-relative application ID:

cpollach
Explorer
0 Kudos

Hi Aruna;

What version & build of the PB IDE are you using?

Regards ... Chris

former_member202249
Active Participant
0 Kudos

Hi Aruna,

Are you sure that you have the 32-bit version of the dll and that it is on the path?

You can use Process Monitor to see where your exe is looking for the dll.

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

Pat