Hi Team,
While deploying application over Web (PowerServer Configuration toolkit), I selected all necessary DLLs in Deploy .Net/ DLL components section. When I run application in Browser getting 20021 - Loading DLL failed.
We have below versions
PB - Appeon PB 2017 R2 (Trial) Build 1756.
PS - Appeon PowerServer 2017 Build 1689.00 32-bit Edition
Windows: Windows 10
IE - IE11.
I tried with running IE as Admin & also tried on Edge. But getting same error.
Please let us know solution or any pointers to way forward.
Thanks & Regards,
Devang Modi.
The DLL that we are calling is 3rd party DLL.
Application starts up successfully but when application tries to call any function of the DLL then it displays the error message.
In general, when we are moving to Powerbuilder web, what is the recommendation about DLLs deployment.?
PB application that we are using is referring to lot of windows DLLs and also to 3rd party DLLs. Now its possible that these windows DLLs or 3rd party DLLs also has some dependencies on other DLLs, so is application supposed to download all those DLLs as part of web deployment?
When we run the PB native application in windows, all the required DLLs path is configured in system PATH variable from where it picks up dependent DLLs as well. In case of web, for e.g. if we are using one of the windows system DLL which may have dependency on 10 other windows DLLs, then are we supposed to deploy all those DLLs on client machine?
Thanks,
Devang
If you are just calling MS-Windows DLL's - then there is nothing to deploy. In fact, you should never do that as those MS-DLL's may not match the O/S version that the end user is actually using.
For 3rd party DLL's, they can be deployed from PowerServer automatically when the App launches. You can even request that those DLL's be registered as well in the GAC if required based on the Application Profile in PowerToolkit . The key to remember though is if your app is running in a 32bit browser - your probably OK. However, if the Web app is launched as a 64bit app - then you'll need the 3rd party DLL's in 64bit compliance.
Windows DLLs are working fine.
These are 3rd party DLLs. I tried running 32 IE but still getting same error.
Thanks & Regards,
Devang.