Closed simiii closed 3 years ago
As you say, it is most likely an issue with missing VC++ redistribution library. Also, make sure you only deploy 'Xbim.Geometry.Engine64.DLL' OR 'Xbim.Geometry.Engine32.DLL'. IIS is trying to load everything in the folder and if you are running 32bit process, loading 64bit dll will fail.
Hi Simon,
It's always slightly tricky to track down these issues on servers under IIS etc. it could be one of several issues: https://github.com/xBimTeam/XbimGeometry/issues/312#issuecomment-778184952
I'd recommend hooking up logging to a file or other log source, which may help diagnose if it's a path/permission issues, or a VC dependency issue.
See https://github.com/xBimTeam/XbimGeometry/issues/195#issuecomment-514151888 for how to do that
Thank you guys for your help. I will try to implement the logging functionality.
I switched to Azure. No problems there. Can be closed.
We searched all issues regarding the topic 'Could not load file or assembly 'Xbim.Geometry.Engine64.DLL' or one of its dependencies. But we couldn't find a solution to our problem.
I am having setup a .NET 4.7.2 project in Visual Studio which works just fine on our development machines. We want to host the application on AWS elastic beanstalk. If we deploy our app to AWS Beanstalk (IIS 10.0 running on 64bit Windows Server 2019/2.6.3) the following error occurs:
Assemblies and versions affected:
The following software is installed on the AWS Elasticbeanstalk ec2-Instance:
The following DLLs are copied into the bin folder on the ec2-windows-instance (which looks quite good in our opinion as there is the Xbim.Geometry.Engine64.DLL
packages.json
logging form AWS elastic beanstalk
We would like to deploy the application to AWS elastic beanstalk and would be very happy if you could have a quick look into this issue. Perhaps you see the error at once, like an incompatible redistribution library or missing DLLs or one of its dependencies.
We were able to deploy a .NET 4.7.1 App to AWS Elasticbeanstalk. So it might be a configuration problem, that comes into play with .NET 4.7.2.