Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Couldn't Find Main Entry Point (48::72) after trying to use third party library.

Community Beginner ,
May 24, 2021 May 24, 2021

Hello! 

 

Currently trying to build my first plugin. Right now I've been working on it within the Queuebert example plugin in the latest SDK. (March 2021). I haven't changed anything outside of Queuebert.cpp.

 

My plugin gathers info like composition names and lengths and I wanted to upload this to a database so I planned on using the Mongocxx drivers for MongoDB. 

 

I added the two include statements at the top of my file. 

#include "QueueBert.h"
#include <mongocxx/client.hpp>
#include <mongocxx/instance.hpp> 

I also added in one line within the plugin itself. 

 

if (command == S_queuebert_cmd) {

		mongocxx::instance inst{};

After adding this one line above, I now get the Couldn't Find Main Entry Point (48::72) for my plugin. 

 

I'm not expecting anyone to be familiar with MongoDB, but I'm unsure why this would cause this error in the first place. The plugin builds successfully and this code shouldn't get called until I click on the Menu item, so I don't see why code in this part of the program should produce this error anyways. 

 

If anyone has a possible solution, insight, or advice, please let me know! 

TOPICS
Error or problem , SDK
1.4K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 24, 2021 May 24, 2021

the library you added probably relied on some external dll being preset in the same folder as .aex file.

use "dependency walker" to see.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
May 25, 2021 May 25, 2021

Hi Shachar, 

 

Thank you for you advice. I used Dependency Walker and did see that the mongocxx DLL was missing! 

 

I grabbed that from elsewhere in my computer and put it next to the aex file and rebuilt it. Using dependency walker again, I saw that the mongocxx one could be found but now there were many more that needed to be found.

 

Am I missing something here? There are a lot of them that need to be used, but I searched for a couple of them on my PC and they all showed up, so I know I have them. Shouldn't my plugin just automatically link to those already on my PC? If not, is there anyway to automatically move them all into that folder? 

 

Thanks so much! 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 25, 2021 May 25, 2021

some dlls will show up as missing on dependency walker, even though they will be found on runtime. as long as you plug-in loads and runs it's all fine...

is it running now that you put mongocxx  next to it?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
May 25, 2021 May 25, 2021

Unfortunately it still won't run. Is there a way to find out which specific DLLs I would need to move over?

 

I also noticed that when the error pops-up, the output in Visual Studio stops on this line until I click "ok" on the popup. 

 

Exception thrown at 0x00007FFD5B804B89 in AfterFX.exe: Microsoft C++ exception: vcfoundation::base::VCIllegalArgument at memory location 0x0000000000BFC120.

 

Does this provide any insight? 

 

Thank you so much! 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 25, 2022 Jun 25, 2022
LATEST

You wrote: "After adding this line above, I now get the message Could not find the main entry point (48::72) for my plugin."

Try in this case, if you have Windows 10, replace the driver file "OpenCL.dll " in the catalog:

C:\Windows\System32

The problem of Adobe After Effects CC 2015-2022 errors like "Couldn't find main entry point for Pro X-Element.aex ( 48 :: 72 )" is solved this way. Checked only on Windows 10.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines