Hi Mohan;

   The issue is most likely caused because you did not deploy the PB.Net run-time via the PB Packager.

   In PB2017/2019, the PB Packager does not display this option any longer. Here is what you need to do in order to restore this deployment option ...

1) Create a PBPACK.ini file.

2) Add the following section & value to the INI file, as follows:

[Packager]
DotNetComponents=1

3) Copy the PBPACK.ini to the PB's "Shared" foilder

3) Restart the PB Packager and then choose the "PB .Net Components" option to create the PB.Net MSI

4) Run the new MSI on the IIS Server machine where the deployed WS resides.

HTH

Regards ... Chris

My assumption is that somewhere in your PBL files you imported a .PBX file (containing web-service extensions). Alternatively you include a PBxxx120.PBD file containing web-service or XML processing.

• Does any file in your library list have name like PBxxx120.PBD ?
• Did you update the Sybase-PowerBuilder assemblies to the v. 17 files?
  You find them in folder = "...\shared\PowerBuilder"

You will need to upgrade every PB version 12 component to current PB 17.

HTH /Michael