Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved The assembly 'nameAssembly.dll' doesn't exist

  1. Issue
0
Votes
Undo
  1. Menna Pablo Javier
    Menna Pablo Javier
  2. PowerBuilder
  3. Tuesday, 10 May 2022 12:05 PM UTC

In PB2021, with client-server system mode, this error occurs. It happens at runtime from source code, when you pull up a dll generated by a proxy.

"The assembly 'nameAssembly.dll' doesn't exist"

From connection_ws.createinstance(), where connection_ws is an object of type SoapConnection.

We generate the proxy with the "Web Service Proxy Wizard" tool.

It should be noted that once the application is compiled, this error does not occur and it connects correctly.

This was working fine in PB2017. We migrated to 2021 and it started to happen. Can you think of something that needs to be configured or programmed?

Regards

Attachments (1)
error_assembly.png error_assembly.png
REST API calling
Column Does not exist
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 10 May 2022 20:55 PM UTC
  2. PowerBuilder
  3. # 1

Hi Menna;

  Did you replace the old "pbwsclient170.pbd" file in your App's PBL list with the PB2021 new version (pbwsclient.pbd)?

Regards ... Chris

Comment
Menna Pablo Javier
  1. Menna Pablo Javier
  2. Wednesday, 11 May 2022 12:02 PM UTC


Hi;

Moving the assembly to the "C:\Program Files (x86)\Appeon\PowerBuilder 21.0" folder does not cause the error.

Thank you very much!



Regards
  1. Helpful
There are no comments made yet.
Menna Pablo Javier
Menna Pablo Javier Accepted Answer Pending Moderation
  1. Tuesday, 10 May 2022 14:17 PM UTC
  2. PowerBuilder
  3. # 2

Thank you Chris.
The .dll file is located in the same folder where the sources are.

What project are you referring to? The project where the proxy is configured? I attach an image of how the options are configured there

Regards

Attachments (1)
config_proxy.png config_proxy.png
Comment
Load more comments
Menna Pablo Javier
  1. Menna Pablo Javier
  2. Tuesday, 10 May 2022 17:55 PM UTC
The same happens, when saving the project it assigns the path automatically.

Any other idea? The funny thing is that in PB2017 it works. Could it be a permissions issue?
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 10 May 2022 18:41 PM UTC
Then that should work then when run from both the IDE and from the App's EXE (it will look for that DLL in the same folder as the deployed App's EXE).

Are on the latest PB2021 (build 1509)?
  1. Helpful
Menna Pablo Javier
  1. Menna Pablo Javier
  2. Tuesday, 10 May 2022 20:22 PM UTC
I was in 1506 and then migrated to 1509. Nothing changed.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 10 May 2022 12:49 PM UTC
  2. PowerBuilder
  3. # 3

Hi Menna;

  This might be a "pathing" issue. Check how your assembly is being accessed from its project specifications.

Regards... Chris 

Comment
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.