1. Phil Chapman
  2. PowerBuilder
  3. Wednesday, 20 December 2017

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

Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

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
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. Phil Chapman
  2. Thursday, 21 December 2017
Hi Phil;



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



Regards ... Chris

  1. Chris Pollach
  2. Thursday, 21 December 2017
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. Georgios Papageorgiou
  2. Monday, 5 February 2018
There are no comments made yet.
  1. Wednesday, 20 December 2017
  2. PowerBuilder
  3. # 1
Moshe Tangi Accepted Answer Pending Moderation
0
Votes
Undo

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.
  1. Sunday, 21 January 2018
  2. PowerBuilder
  3. # 2
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.