cancel
Showing results for 
Search instead for 
Did you mean: 

Procedure entry point could not be located in DLL

SOLVED
Occasional Contributor

Procedure entry point could not be located in DLL

I am testing a desktop application.

If I run the application natively outside of TestComplete, it works fine. However, if I run it from TestComplete, it gives me an error message "The procedure entry point [lots of text] could not be located in the dynamic link library [etc.]"

 

I tried running sfc /scannow, and that did fix some errors, but not this particular one.

I really can't ask IT to reinstall the application, because it works just fine if I open it from its shortcut, so I couldn't show any reason to do so.

--
You might not like AI, but it doesn't care about you.
1 ACCEPTED SOLUTION

Accepted Solutions
Occasional Contributor

Re: Procedure entry point could not be located in DLL

I was right-clicking and selecting "Run" from the Tested Apps tab.

 

I figured it out, I set the compatibility to Windows 8 in the shortcut, and now everything is working fine.

--
You might not like AI, but it doesn't care about you.

View solution in original post

2 REPLIES 2
Community Hero

Re: Procedure entry point could not be located in DLL

How are you running it from TestComplete?

Occasional Contributor

Re: Procedure entry point could not be located in DLL

I was right-clicking and selecting "Run" from the Tested Apps tab.

 

I figured it out, I set the compatibility to Windows 8 in the shortcut, and now everything is working fine.

--
You might not like AI, but it doesn't care about you.

View solution in original post

New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors