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

Resolved Issue with using a homegrown C# dll with the appeon dot net component

  1. How-to
0
Votes
Undo
  1. Mark Lundell
    Mark Lundell
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 31 July 2020 20:37 PM UTC

I have a very small c# dll which is working on my localhost, a test server, and 1 of our 2 production servers.  It is failing on our second production server.  It is unable to load the dll or one of its components.  The dll has been loaded into inetpub\wwwroot\appeon\AEM\components on all 3 servers.  The testing application has been deployed via the same configuration to all 3 servers.  

I also have another c# dll, used by another app, which is working correctly on all servers.  Both dlls are created with MS Visual Studio 2017.  Both dlls are created with or for the 4.51 version of dotNet.  Both are created for any cpu type.

Neither dll has been registered.

The error message has been attached.

I need ideas for what is different, or how to find it.

Thanks

 

Attachments (1)
ComponentIssue.pdf
  1. .NET Assembly
PowerServer Oracle decimal separator
How to get Power Server host server name
Responses (2)
Mark Lundell
Mark Lundell Accepted Answer Pending Moderation
  1. Monday, 3 August 2020 14:21 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

All versions of Powerserver are 2019 Build 1988.00 64 bit.  I'll work with Dependency Walker to see if I can find something.

Thanks
Comment
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Monday, 3 August 2020 02:47 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Mark,

Did you install 32-bit or 64-bit PowerSever on the test server, and it is the 32-bit or 64-bit PowerSever installed on the production server that can’t load the DLL?
Please go to AEM > Server > License Management > Licensing to check the product version and see if they are the same.

From the error message “Could not load file or assembly '*.dll' or one of its dependencies”, this might be caused due to some missing dependency files.
Please use Dependency Walker to check and see if there is any DLL's dependency file missing.
https://www.dependencywalker.com/

Or please refer to the article below for more details.
https://stackoverflow.com/questions/7378959/how-to-check-for-dll-dependency

Regards,
Zhaokai

Comment
Mark Lundell
  1. Mark Lundell
  2. Thursday, 6 August 2020 21:13 PM UTC
Turns out that I initially set up the dll to be registered, and deployed it to "failing" server. I changed the name of the dll and deployed it as a DotNet assembly. The problem went away.
  1. Helpful
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Friday, 7 August 2020 00:08 AM UTC
Glad to hear that.
  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.
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.