Skip to Content
avatar image
Former Member

My application keeps crashing on Windows Server 2012 R2.

Powerbuilder 10.5

Since migrating to a Windows Server 2012 R2 Terminal Server my application keeps crashing. On the old Windows Server 2003 TS it worked fine.


From the event log


Windows cannot access the file for one of the following reasons:

there is a problem with the network connection, the disk that the file is stored on, or the storage

drivers installed on this computer; or the disk is missing.

Windows closed the program <program> because of this error.

Program: <program>

File: The file name is blank so I don't know which file is is!

Etc.

Followed by:


Faulting module name: MSVCR71.dll, version: 7.10.3052.4, time stamp: 0x3e561eac

Exception code: 0xc000041d

Fault offset: 0x0002094a

Faulting module path: <path>MSVCR71.dll

Etc.


The faulting module paths can also be:


C:\Windows\SYSTEM32\ntdll.dll

<path>PBSHR105.dll

<path>pbdwe105.dll

<path>PBVM105.dll

<path>pbdwe105.dll

C:\Windows\SYSTEM32\MSVCR100.dll


I have installed a trial version or PB12.6 (build 3506) on a VM under Windows 7 (the gui won't run on my W10 box, but that is another story), compiled the application and installed this in a separate directory. This doesn't help either.


This is giving me an ulcer. Can anyone please point me in the right direction.

I am desperate so any ideas are welcome.


Thanks.

Gerry.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Apr 14, 2016 at 04:01 PM

    Hi Gerry;

    Not surprising when using the old EOL PB 10.x version. Version 10.x was around long before W2012 and never tested / supported on that platform by Sybase or SAP. 😉

    Regards .. Chris

    Add comment
    10|10000 characters needed characters exceeded