Excel 32bit - Entry Point Not Found

Question

Getting this error when opening a certain file that has some macros that run on open.

If i close the force close the application and reopen after the save, it opens fine.
any ideas?

Answer 1

Hi @Guy, 

Thank you for posting your question in the Microsoft Q&A forum. 

I understand that you’re encountering the "Entry Point Not Found" error when trying to open an Excel file. To better understand the situation and provide more targeted guidance, could you please help clarify a few details? 

• Does this issue occur with other files as well, or only with a specific file or macro? 
• Have you tried opening the same file on a different device? If so, does the issue still occur? 

In the meantime, please try the following step: 

Open Command Prompt with administrator privileges: 

• On Windows 10/11: Right-click the Start menu and select Windows Terminal (Admin) 
• In the elevated command window, type the command below and press Enter:  sfc /scannow  

Thank you again for your time and patience. This initial step may not resolve the issue immediately, but the information you provide will help me investigate further and offer a more precise solution. I appreciate your cooperation and look forward to your reply. 

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".      

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread  

Answer 2

The dll that is failing is v8jsi.dll

what does that one do?

Answer 3

The error message about an entry point when opening a macro-enabled workbook typically indicates a problem with a DLL or type library that the VBA project is calling.

Based on the documented behavior, the most likely cause is that a referenced DLL entry point is invalid or no longer matches what Excel/VBA expects. This can happen if:

• A type library used by the VBA project incorrectly describes the DLL entry point (misspelled procedure name or wrong ordinal), or
• The DLL or component the macro calls has changed or is missing on this machine.

When Excel is forced closed and reopened, the problematic call may not be hit in the same way (for example, if the macro doesn’t fully re-run), so the file appears to open fine.

To troubleshoot:

1. Open the workbook with macros disabled (e.g., hold Shift while opening, or disable macros in Trust Center) so the auto-run macro does not execute.
2. In the VBA editor, review any Declare statements or references that call into external DLLs.
3. Verify that each DLL exists on the system and that the procedure names/ordinals match the actual DLL exports. If a type library is involved, it may need to be corrected or updated by the vendor.
4. If the project was created in another host application (for example, a different Office app), ensure it is opened in the same host where it was created.

If the error text specifically says it cannot find a DLL entry point, the underlying guidance is that the type library or declaration is wrong and must be corrected; otherwise the error will continue whenever the macro runs.

---

References:

• Can't find DLL entry point in specified DLL
• This VBA project was created while running VBA in a different application. You may only open it from inside the same application in which it was created.