1. ENRICO MENEGOTTO
  2. PowerBuilder
  3. Thursday, 20 May 2021 16:55 PM UTC

Hi all,

From a long time I have a webservice that always worked fine.

After I've installed the last PB 19.2.0.2703, if I create and install the msi file, when I call the webservice it return me SOAP SERVICE ERROR. I've found that the error is about "Sybase.PowerBuilder.Interop.dll"; it seems that the system can't find this module or it's dependencies. 

Obviously before to run the webservice I've installed also the "Powerbuilder .NET Component" using the packager utility.

Can anyone help me?

ENRICO MENEGOTTO Accepted Answer Pending Moderation
  1. Tuesday, 21 September 2021 07:37 AM UTC
  2. PowerBuilder
  3. # 1

Hi All,

I know that .NET WS is not yet supported.

But I'have still the problem and I can't now migrate the system to C#.

The problem is that after I installed R3 2703, when I call the webservice, it returns "SOAP Service Error"

The path of the Powerbuilder .NET Component is corretcly setted.

Any suggestion?

Comment
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 24 May 2021 13:58 PM UTC
  2. PowerBuilder
  3. # 2

Hi Enrico,

hope the upload works.

Best,

.m

Attachments (1)
Comment
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 24 May 2021 12:42 PM UTC
  2. PowerBuilder
  3. # 3

Hi Enrico,

I already reported this error to Appeon in January, bug number is #5979, it is fixed.

Unfortunately the bug report is private, I attach PDF export for your review.

Best,

.m

 

Attachments (1)
Comment
  1. ENRICO MENEGOTTO
  2. Monday, 24 May 2021 15:15 PM UTC
Hi Marco,

I made what you suggested, but it didn't works.

My error message is as follows and so I think the problem is related to the DLL Sybase.PowerBuilder.Interop.dll'



Error log taken from JAVA calls

16:31:21.986 ERROR - IpertechSoapServiceImpl (45) - Errore SOAP

org.springframework.ws.soap.client.SoapFaultClientException: Non è stato possibile caricare il file o l'assembly 'Sybase.PowerBuilder.Interop.dll' o una delle relative dipendenze. Impossibile trovare il modulo specificato. ---> Non è stato possibile caricare il file o l'assembly 'Sybase.PowerBuilder.Interop.dll' o una delle relative dipendenze. Impossibile trovare il modulo specificato.

at org.springframework.ws.soap.client.core.SoapFaultMessageResolver.resolveFault(SoapFaultMessageResolver.java:38) ~[spring-ws-core-2.4.6.RELEASE.

  1. Helpful
  1. Marco Meoni
  2. Monday, 24 May 2021 15:43 PM UTC
Hi Enrico,

Sybase.PowerBuilder.Interop.dll is another DLL, the remaining dependencies cannot be found in your env.

Your SOAP WS deployed under C:\inetpub\wwwroot\<yourWSpath>\bin\yourWS.dll needs the entire SOAP WS runtime, whose DLLs must be registered and available in the proper PATH.

The PB MSI should do that, but on my side I was already in panic-mode and installed the entire PB distro on the production server, while on my test env was enough to replace Sybase.PowerBuilder.DataWindow.Interop.dll (not Sybase.PowerBuilder.Interop.dll)

Best,

.m
  1. Helpful
  1. ENRICO MENEGOTTO
  2. Tuesday, 25 May 2021 07:41 AM UTC
Hi Marco,

I know that Sybase.PowerBuilder.Interop.dll is another DLL. It is the DLL I mentioned from the start of issue.

I'm using WS from a lot of years and I installed everything as always.

I can't understand why this DLL is not working properly. I tried also to use the previous runtime version 2670; before was working, but after installation of 2703 it also not works.

All tests were done on my development PC, so all DLL are in path.

Any Ideas or suggestions?
  1. Helpful
There are no comments made yet.
ENRICO MENEGOTTO Accepted Answer Pending Moderation
  1. Friday, 21 May 2021 07:25 AM UTC
  2. PowerBuilder
  3. # 4

Thank you Chris,

a valid way may be to return to the previous version and wait for resolution.

Comment
  1. Chris Pollach @Appeon
  2. Friday, 21 May 2021 14:36 PM UTC
Hi Enrico ... that would be very messy as the R3 installation has really messed around with the R2 installation in order to support the new "detached runtime" feature. You would basically have to Uninstall R3 completely and then reinstall R2. Then the other problem would be restoring the R2 version of your PB App's source code.

Regards ... Chris
  1. Helpful
  1. ENRICO MENEGOTTO
  2. Friday, 21 May 2021 14:53 PM UTC
I think this time APPEON has really created a lot of trouble.

When others install the R3 version then there will be a riot!

Regards Henry! :)
  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 20 May 2021 17:24 PM UTC
  2. PowerBuilder
  3. # 5

Hi Enrico;

  FYI: I am getting the same error on my new R3 installation this week. This worked OK in R2 so I think that we are looking at a new issue introduced in the R3 release. Please open a support ticket for this problem. When I see the ticket, I'll add my $0.02 to it before getting Engineering to look at it.

Many thanks in advance!

Regards ... Chris

Comment
  1. ENRICO MENEGOTTO
  2. Monday, 24 May 2021 10:06 AM UTC
Hi Chris,

it seems a little odd that to fix a feature that used to work well, you have to pay.

However, now we will buy the ticket.
  1. Helpful
  1. Kevin Ridley
  2. Tuesday, 21 September 2021 13:10 PM UTC
Why do you have to "buy" a ticket? You can open a ticket without a charge using the Standard Support Portal:

https://www.appeon.com/standardsupport/search



Click New Bug.



HTH,

Kevin
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.