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

Resolved Deploying .Net components to IIS

  1. Issue
0
Votes
Undo
  1. Georgios Papageorgiou
    Georgios Papageorgiou
  2. PowerBuilder
  3. Friday, 4 August 2017 09:13 AM UTC

Hi PowerSphere.

In old days ( pre Appeon PowerBuilder 2017) it was possible to use the runtime packager to make a .Net runtime package to install on the IIS.

This option in not available anymore. (I guess) 

Is there another solution other than to manually copy the Sybase.PowerBuilder.*.dll to the IIS 's  \assembly\GAC_[MSIL|32|64] 

And can I find some kind of documentation on this ?

Regards

Georgios

  1. IIS
Powerbuilder and Realm mobile database
Error al ejecutar web Service en power builder 201...
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Saturday, 5 August 2017 02:27 AM UTC
  2. PowerBuilder
  3. # 1
Hi Georgios; I'm using the PB 2017 "Packager" utility to install the run-time on to IIS machines successfully. The key is the regular DLL's are in the machines system path & the .Net DLL's get registered in the GAC. To which, the "Packager" produced MSI should do for you. The next key part is that you setup the appropriate Application Pools for your PB web services, enable 32bit execution in the target IIS machine and assign the proper execution rights as well to the application pools. Regards ... Chris
Comment
Marian Klco
  1. Marian Klco
  2. Wednesday, 20 September 2017 14:37 PM UTC
Hi Chris, 



PB 2017 Runtime Packager utility do not have option to generate .PB NET runtime package. All steps you described are valid for PB 12.6 but not for PB 2017. There is actually no other way how to deploy .NET web service target to IIS than manually copy all PB 32 bit runtime dlls and copy all PB .NET dlls to GAC. Evn 32 runtime package generated by PB 2017 Runtime Packager do not include all required files for .NET web service target. Problem is that there is no documentation which files are needed for supported .NET targets, this mean all dlls has to be copied to deployment machine. I believe Runtime Packager should be able generate runtime package for all supported targets (as did on PB 12.6), not just for 32/64 bit windows executable. 



Regards,



 Marian.

  1. Helpful
Phil Chapman
  1. Phil Chapman
  2. Wednesday, 20 December 2017 09:03 AM UTC
We have recently begun migrating our 12.5 application to 2017 which we consume Powerbuilder web services. After installing the PB 2017 via the runtime packager on our application server, we also are left without the .Net components being installed in the GAC and get the following error on the server when the web service is called:



Could not load file or assembly 'Sybase.PowerBuilder.Core, Version=17.0.0.0, Culture=neutral, PublicKeyToken=98a699138181d746' or one of its dependencies. The system cannot find the file specified. (C:\inetpub\wwwroot\wsreport\web.config line 386)



Is there a separate installer for the .Net assemblies we can use or do we have to register these manually?



Thanks



 

  1. Helpful
Dong Le
  1. Dong Le
  2. Thursday, 20 September 2018 08:01 AM UTC
Hi Phil,

Did you solve that problem. I deployed the .new assembly, but seems the datawindow could not be called success from IIS
  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.