• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • DataWindow Server PBDWM150.DLL or required DLLs (atl71.dll, msvcp71.dll or msvcr71.dll) not found

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved DataWindow Server PBDWM150.DLL or required DLLs (atl71.dll, msvcp71.dll or msvcr71.dll) not found

  1. How-to
0
Votes
Undo
  1. Ying Chin
    Ying Chin
  2. PowerBuilder
  3. Thursday, 27 May 2021 15:34 PM UTC

I am trying to migrate a web service application, running on IIS, from PB 11.5 to PB 2019 R3. When I tried to run the web service, I got the

DataWindow Server PBDWM150.DLL or required DLLs (atl71.dll, msvcp71.dll or msvcr71.dll)  not found

I understand that I need a .NET runtime, but the runtime created by PB 2019 R3 did not include PBDWM150.DLL. 
There are blogs to get the .NET runtime before PB 2019 R3 but I cannot find the instruction to get the
.NET runtime for PB 2019 R3 Packager.

How do I get the required .NET runtime? 

Thank you.

 

  1. Web Service
How to pass data to a separate EXE
Connect to TFS server as my Source control when it...
Responses (2)
Albert John
Albert John Accepted Answer Pending Moderation
  1. Thursday, 27 May 2021 15:44 PM UTC
  2. PowerBuilder
  3. # 1

Bro all you need is

Visual C++ Redistributable Packages

I believe you need 2003 version which is 7.1.

in addtion you can copy the dll files from shared folder within the PB IDE folder as well

hope this helps

Comment
Ying Chin
  1. Ying Chin
  2. Thursday, 27 May 2021 15:52 PM UTC
I had the atl71.dll, msvcp71.dll and msvcr71.dll installed. However, I could not find the PBDWM150.DLL.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 May 2021 16:51 PM UTC
  2. PowerBuilder
  3. # 2

Hi Ying;

  The "PBDWM150" DLL would be from PB version 15.0. Since Sybase never released that version, you have had to grabbed that off of a PB15 "beta" release. Sybase released v15 as 12.6 and thus all runtime DLL numbering would have been reset to PBXXX125. Thus any DLL with a 150 is invalid.

   For the PB Packager, you need to perform the following ...

1) Copy the PBPACK.ini that I attached to this post to your PB PAcjager utility's folder

2) Restart the PB Packager and you should now see a .NET deployment option.

3) Create the PB .NET MSI and then run this MSI on the IIS server machine.

4) Deploy your PB Web Service from the WS "project"

5) Select the RMB on the WS project ans then select "RUN" to test the WS.

HTH

Regards ... Chris

Attachments (1)
PBPack.zip
Comment
Load more comments
Ying Chin
  1. Ying Chin
  2. Friday, 4 June 2021 20:19 PM UTC
I found that I have subscription to PB 2017 and the .NET web service is not obsolete.



I still having many issues when running IIS web service from PB 2019 which marks .NET web service as obsolete.



Do you think that migrating from PB 11.5 to PB 2017 will work?

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 4 June 2021 20:49 PM UTC
PB2017 R3 is the LTS (Long Term Support) version of PB2017 Rx and is to be supported until 2023.07.31 at minimum from what we see here ...

http://www.appeon.com/update
  1. Helpful
Ying Chin
  1. Ying Chin
  2. Friday, 4 June 2021 23:03 PM UTC
Hi Chris,



We use the web service to generate pdf letters from datawindows. the same datawindows are used in our client/service application. Have to search for a solution in 2 years.



Thank you for the info on PB2017 support.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.