Run error Entry point not found

Post your questions and problem reports here

Moderator: kfury77

Forum rules
Please try to follow these guidelines. This will help to receive faster and more accurate response.
  • Check the Support section of the corresponding product first. Chances are you will find your answer there;
  • Do not create new topics for already reported problems. Add your comments to the existing topics instead;
  • Create separate topic for each problem request. Do NOT post a number of non-related problem reports in a single topic;
  • Give your topic a meaningful title. Titles such as "A question," "Bug report" and "Help!" provide others no clue what your message is about;
  • Include the version number of the software you are using;
  • This is not an official customer support helpdesk. If you need a prompt and official response, please contact our support team directly instead. It may take a while until you receive a reply in the forum;
Post Reply
martin86
Posts: 61
Joined: Mon Mar 12, 2012 12:58 pm

Run error Entry point not found

Post by martin86 »

Version: WeBuilder11

Hi, thank you for HTML5 support in WeBuilder 11, but I have an error whenever I load WeBuilder (Win XP). This is on a fresh install.

webuild.exe - Entry point not found
The procedure entry point ConvertToGlobalHandle could not be located in the dynamic link library KERNEL32.dll

Any ideas?
Life is too serious to be taken seriously Image
User avatar
Aivars
Blumentals Software Developer
Posts: 2462
Joined: Thu Aug 22, 2002 1:40 pm
Location: Latvia

Re: Run error Entry point not found

Post by Aivars »

Why are you copying this post word by word??? http://forums.blumentals.net/viewtopic. ... dle#p17712
Blumentals Software Programmer
User avatar
Aivars
Blumentals Software Developer
Posts: 2462
Joined: Thu Aug 22, 2002 1:40 pm
Location: Latvia

Re: Run error Entry point not found

Post by Aivars »

Anyway, if you really have the problem, know that it's a problem with the system and not WeBuilder. You can try this suggestion found online somewhere:

"If you see the message ... it comes from Svrapi.dll.
In Windows 7 64 you can find it under windows\SysWOW64. Simply rename it, or delete it and problem solved. "
Blumentals Software Programmer
Post Reply