- VINOD NAIR
- PowerBuilder
- Monday, 6 January 2025 08:11 PM UTC
We have a ASP.NET application running on IIS. This utilized a PowerBuilder 11.5 .PBD file. This was working fine until we came across a bug. In order to fix the bug we had to migrate this PBD to PB 2019 R2. We build the PBD and deployed it on the server and when we run the application it fails to find the following files Sybase.PowerBuilder.Common.dll, Sybase.PowerBuilder.Core.dll etc. We do have 32 Bit enabled in the application pool.
These files are in the windows system path (d:\windows\system32\appeon\shared\powerbuilder) and the path variable shows it (have rebooted the machine after setting the path) and still the application doesn't find them. If I move the files to the ASP.NET applications BIN folder it finds them but the issue is it is not just these handful files. The PowerBuilder PBD also requires other files so I created the PB Packager PBCLTRT190.msi using PB 2019 R2 packager utility and installed the files in the same d:\windows\system32\appeon\shared\powerbuilder folder.
Any idea why the application doesn't find the files even though the System path is set to that folder? what else can we do to fix this issue? Even if I copy the entire folder content into the application BIN folder the application doesn't find the PBD file to reference and fails.
Also, when we deploy the application on local IIS where we built the application or on the laptop where we have PB 2019 R2 installed then the ASP.NET application is able to reference the PBD and have no issues. So, we definitely feel that the reason it is not running on a server is because it is not able to access dependency files and we can't figure out what those dependency files are.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.