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
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.
I am glad that you finally wrestled this issue to the ground and now have it all working!
Regards ... Chris
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