1. Devang Modi
  2. PowerBuilder
  3. Wednesday, 18 April 2018 11:01 AM UTC

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.

Who is viewing this page
mike S Accepted Answer Pending Moderation
  1. Thursday, 21 April 2022 16:03 PM UTC
  2. PowerBuilder
  3. # 1

was this ever resolved? 

I'm was getting the same problem.

i had added cgi/fastcgi to the webserver (common for things like php).

 

This auto added a dll handler for isapi, which f'd up the downloads.

You can either remove it for powerserver applications one at a time, or remove it entirely from website and add it back for each fastcgi application as needed.


this is the webconfig to remove it for specific powerserver application:



<configuration>

<system.webServer>

<handlers>

<remove name="ISAPI-dll" />

</handlers>

</system.webServer>

</configuration>

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 26 April 2018 14:20 PM UTC
  2. PowerBuilder
  3. # 2

The other issue could be that your DLL's are 32 bit based and your Web app under IE is running in 64 bit mode.

You can check the URL when your app is running and if it contains the "x64_application.htm" designation for 64 bit mode.

 

Comment
  1. Devang Modi
  2. Sunday, 29 April 2018 05:40 AM UTC
Hi Chris,



Yes, When we launch application then its opening x64_application.htm. We tried with launching application using x32_application.htm then its not opening. 

 



The Appeon Xcelerator plug-in cannot be loaded.





Try this if the current browser is Internet Explorer:





Step 1: Add the URL of this Appeon Web application to the Trusted sites zone in Internet Explorer.

Step 2: Make sure the Enable Protected Mode option on the Security tab in Internet Explorer is not selected.

Step 3: Check the URL of this Appeon Web application (http://Hostname:Port/appname/index.html).





Click here for detailed instructions on the above steps.



If the Appeon Xcelerator plug-in still cannot be loaded with the above steps, you may try to download Appeon Xcelerator package, unzip the package, close any opened Web browser, and then right click the Update.exe file in the package and select Run as administrator to install the plug-in.







May be problem with installation ? 



What could be problem ? 



 



 

  1. Helpful
  1. Devang Modi
  2. Sunday, 29 April 2018 05:42 AM UTC
Hi Chris,



When I launch application using x_32application.htm - I am getting below error : 

 



The Appeon Xcelerator plug-in cannot be loaded.





Try this if the current browser is Internet Explorer:





Step 1: Add the URL of this Appeon Web application to the Trusted sites zone in Internet Explorer.

Step 2: Make sure the Enable Protected Mode option on the Security tab in Internet Explorer is not selected.

Step 3: Check the URL of this Appeon Web application (http://Hostname:Port/appname/index.html).





Click here for detailed instructions on the above steps.



If the Appeon Xcelerator plug-in still cannot be loaded with the above steps, you may try to download Appeon Xcelerator package, unzip the package, close any opened Web browser, and then right click the Update.exe file in the package and select Run as administrator to install the plug-in.



 



This is due to wrong installation ? 



 



Thanks & Regards,



Devang Modi.

  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 18 April 2018 23:34 PM UTC
  2. PowerBuilder
  3. # 3

Hi Devang,

This is what the Error 20021 refers to:

Error Message

Failed to load DLL file. For more help, please consult the Appeon user document.

Possible Cause

1) The DLL files were not deployed when the application was deployed.

2) The DLL file was not downloaded to the correct location.

Solution

1) Check that the DLL files are configured for deployment before deploying the application.

2) Manually copy the file to the correct location.

 

Please try the solution and let us know if this helped.

 

Regards,

Comment
  1. Govinda Lopez @Appeon
  2. Wednesday, 18 April 2018 23:34 PM UTC
By the way, try adding the .dll extension type to your MIME Types in IIS.

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 18 April 2018 13:37 PM UTC
  2. PowerBuilder
  3. # 4

Hi Devang;

  • Can you explain what DLL's you are referring to that you need to deploy?
  • Does the application start-up at all?

Regards ... Chris

 

Comment
  1. Devang Modi
  2. Thursday, 19 April 2018 13:22 PM UTC
Hi Chris,



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

  1. Helpful
  1. Chris Pollach @Appeon
  2. Thursday, 19 April 2018 15:41 PM UTC
 



    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.

  1. Helpful
  1. Devang Modi
  2. Wednesday, 25 April 2018 06:27 AM UTC
Hi Chris,



Windows DLLs are working fine. 



These are 3rd party DLLs. I tried running 32 IE but still getting same error. 



 



Thanks & Regards,

Devang.

  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.