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

Resolved IIS web service runtime

  1. Issue
0
Votes
Undo
  1. Phil Chapman
    Phil Chapman
  2. PowerBuilder
  3. Wednesday, 20 December 2017 13:30 PM 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 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. IIS
  2. Service
OCX Issue with PB2017
RTE controls and colors
Responses (2)
Moshe Tangi
Moshe Tangi Accepted Answer Pending Moderation
  1. Sunday, 21 January 2018 06:06 AM UTC
  2. PowerBuilder
  3. # 1

hi ,

i had the same problem . somewhere the pc confuse and "prefer" the old dll of pb12.5 over 2017 version.

if you uninstalled 12.5 and reinstalled 2017 it will be fixed or copy all needed 2017 dlls to the pbl's directory.( pbwsclient170.dll , Sybase.Powerbuilder.Webservice.dll  and so on )

and maybe to unregister from GAG the old one's ( 12.5 )

good luck

 

 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 20 December 2017 14:30 PM UTC
  2. PowerBuilder
  3. # 2

Hi Phil;

      The description of your problem is confusing as you would not need to register your PB Web Service objects in the GAC when deploying them to IIS or to be able to access them as Web Services. It sounds like you are having issues with .NET Assemblies in relation to how you are trying to use them - however, that is not clear.

Regards ... Chris

Comment
Load more comments
Phil Chapman
  1. Phil Chapman
  2. Thursday, 21 December 2017 08:57 AM UTC
This got rid of my original error, but then got the following error in the event log:



Exception information:



Exception type: HttpException



Exception message: Could not load type 'PBWebApp.Global'.



at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()



at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()



at System.Web.Compilation.BuildManager.CallAppInitializeMethod()



at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)



 



I then looked at the deploylog.txt for my web service and noticed that it failed to copy files from "C:\Program Files (x86)\Appeon\PowerBuilder 17.0\DotNET\webroot" which did not exist on my local computer nor did it exist on our other developers computers!



I then copied this directory from our old 12.5 installation and re-published the app to IIS and it worked!



Hope this helps anyone else with the same issue.



 

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 21 December 2017 14:33 PM UTC
Hi Phil;



   I am glad that you finally wrestled this issue to the ground and now have it all working!



Regards ... Chris

  1. Helpful
Georgios Papageorgiou
  1. Georgios Papageorgiou
  2. Monday, 5 February 2018 11:51 AM UTC
Hi,



The folder ( "pbruntime.msi" file located in the "C:\Program Files (x86)\Appeon\PowerBuilder 17.0\DotNET\pbiu\BootStrapper\Packages\1-PBRuntime")  seems pretty empty in the 2017R2 release. (at least no msi packages)



Regards



Georgios

  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.