1. iliyan iliev
  2. PowerBuilder
  3. Wednesday, 2 February 2022 14:19 PM UTC

when i call ws give faultstring 

System.Web.Services.Protocols.SoapException: Could not load file or assembly 'Sybase.PowerBuilder.Interop.dll' or one of its dependencies. The specified module could not be found. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Sybase.PowerBuilder.Interop.dll' or one of its dependencies. The specified module could not be found.

this is happen on my dev pc ! I have installed PB 2019 r3 & PB 2021 v1506.

This happen when call WS who deploy with pb 2021.

Sybase.PowerBuilder.Interop.dll in GAC and App Poll allow 32bit processing.

iliyan iliev Accepted Answer Pending Moderation
  1. Tuesday, 8 February 2022 13:17 PM UTC
  2. PowerBuilder
  3. # 1

Thanks for everyone to help me :)

Problem is wrong or missing register of pb.net runtime package !

After create package with packager  and install everything works :) PB 2019 R3 and PB 2021 :) 

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 8 February 2022 13:36 PM UTC
Yes, the PB Packager's .Net MSI registers the DLLs as well during the PB.net runtime installation process.
  1. Helpful
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 7 February 2022 12:30 PM UTC
  2. PowerBuilder
  3. # 2

Hi Iliyan,

it worked for me from PB 2021.

To be honest however, I had to manually convert to Application the WS webroot ("webservice" in my attached example). Right-click on it and IIS will give you the option. Also, it is imperative that application pool is PBDotNet4AppPool as configured by PB (and also check that this Pool has 32bit mode enabled). Last, deploy as privileged user.

Best,

.m

 

Comment
  1. iliyan iliev
  2. Monday, 7 February 2022 13:57 PM UTC
for me he doesn't works :(

error still has it:(
  1. Helpful
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 7 February 2022 11:29 AM UTC
  2. PowerBuilder
  3. # 3


Hi Iliyan,

I guess you use datastores in your WS, so it is most likely Sybase.PowerBuilder.DataWindow.Interop.dll that is missing, which is one of the dependencies of  Sybase.PowerBuilder.Interop.dll.

Considering that SOAP WS is a deprecated feature that has indeed deployment hurdles, can't you just run the installation of PB 2021 on the server machine? This will certainly fix all PATH and GAC pre-requirements.

Best,

.m

Comment
  1. iliyan iliev
  2. Monday, 7 February 2022 11:31 AM UTC
This is happen on my dev pc ! PB 2021 actually installed !
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 2 February 2022 20:56 PM UTC
  2. PowerBuilder
  3. # 4

Hi iliyan ;

    Did you create a PB .NET runtime MSI installation for the IIS server machine? Then after the MSI is installed, add the PB runtime folder of the MSI installation to your O/S's System Path so that IIS can resolve these DLLs?

Regards ... Chris

Comment
  1. iliyan iliev
  2. Monday, 7 February 2022 14:00 PM UTC
How to make visible Powerbuilder .NET Components in RT Packager ?! I can't find pb share folder to add pbpack.ini !
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 7 February 2022 15:57 PM UTC
Hi iliyan ... Using Notepad, create a PBPACK.ini file as follows:



[Packager]

DotNetComponents=1



Copy this file to the PB Packager App utility's runtime folder. Then the next time you restart the utility, the 3rd (.NET MSI) option should appear.

HTH
  1. Helpful 1
  1. iliyan iliev
  2. Tuesday, 8 February 2022 09:05 AM UTC
Thanks :) In 2019/2021 pbpack.ini is in IDE folder and only need to DotNetComponents=1 :)
  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.