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

Resolved Web Service Proxy issue

  1. Issue
0
Votes
Undo
  1. Sally D
    Sally D
  2. PowerBuilder
  3. Wednesday, 3 July 2019 03:29 AM UTC

Hi all,

When i change a server to deploy, once all the webserivce, it shows the error  'The definition of the method signature in Web Service proxy is wrong', is there any error on the sever?

 

Thanks a lot.

Sally

Cursor is not open
Need to SAVE 40 Datawindow reports into Word Docum...
Responses (3)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 3 July 2019 04:32 AM UTC
  2. PowerBuilder
  3. # 1

So you mean you have it working fine on one server but when you deploy to a different server you have the problem you mentioned?

Comment
Sally D
  1. Sally D
  2. Wednesday, 3 July 2019 05:52 AM UTC
Yes, this issue sever worked before, but occurr this issue without any changes. The proxy is used within the assmebly
  1. Helpful
There are no comments made yet.
Mark Lee @Appeon
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 3 July 2019 09:01 AM UTC
  2. PowerBuilder
  3. # 2

Hi Sally,

 

Due to that I don’t have your case and haven’t encountered such issue before, I suggest you do the following methods:

  1. Please make sure your current server machine meets the system requirements of PB 2017 & PB 2019. You can refer to below link for more details:

           https://www.appeon.com/support/documents/appeon_online_help/pb2019/release_bulletin_for_pb/ch01.html

  1. Try to full build your application code and see if it works.
  2. Delete the existing WebServer proxy objects and then deploy again and see if it works.
  3. In the current server machine, install PB .NET MSI package and then restart the machine and see if it works.

          You can refer to the following to generate the PB .NET package:

          a) In the directory where pbpack170.exe is stored (the default directory is C:\Program Files (x86)\Appeon\Shared\PowerBuilder), add the pbpack.ini with below contents (as attached):

          [Packager]

          DotNetComponents=1     

          b) Launch the Runtime Packager of PB 2017 and the previous PowerBuilder .NET components will be showing up.·        

          c) Create the PBNETER170 MSI package and install it on your machine.

  1. If the issue still persists after the above methods, it is recommended that you report this bug via our support ticketing system with a reproducible case.

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

 

Regards,

Mark Lee

Attachments (1)
pbpack.zip
Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 3 July 2019 16:02 PM UTC
  2. PowerBuilder
  3. # 3

Hi Sally;

  I have received this type of error before. For me, it was normally that the Web Service my App(s) were dealing with had changed their definition. So all I had to do then we re-run the PB "Project" that rebuilt all the WS "proxy" objects based on the current WS's definition.

  Hopefully, that is all you might need to do as well.

HTH

Regards ... Chris

 

Comment
Sally D
  1. Sally D
  2. Thursday, 4 July 2019 11:31 AM UTC
Hi Chris,



Thanks, but not work for me. My situation is that the project is ok on the other severs, but with issues only on one sever. So should not be code issue, it may caused by IIS server, but could not find out it. Do you have some idea of the iis config?



Thanks
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 5 July 2019 14:44 PM UTC
Hi Sally;

If its only the one IIS server that is giving you the issue on this W.S., then I wonder if it might be worthwhile trying to reinstall the web service on that IIS instance since it runs OK on other IIS instances (correct)?

Regards ... Chris
  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.