• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 964
  • Last Modified:

dllregisterserver entrypoint was not found

I have made a dll's which runs perfectly under windows95 however under windows nt I got the message dll not found.

Tried regsvr32 dllname.dll with as result the following message :

Dllregisterserver entry point was not found. DllRegisterServer may not be exported, or a corrupt version of dllname.dll may be in memory

I am not understanding this why because of the fact that the dll is not an OLE server neither of these things the only wicked thing is that it works under windows95.

Help me out dudes.

regards,

Cono
0
Ronald Buster
Asked:
Ronald Buster
  • 4
  • 3
  • 2
  • +1
1 Solution
 
MadshiCommented:
Hi Cono,

I can't explain why it works with win95 and NOT with NT. Perhaps you should just try to add this to your dll (if you don't have done this already):

uses comServ;

exports DllGetClassObject, DllCanUnloadNow, DllRegisterServer, DllUnregisterServer;

Regards, Madshi.
0
 
MadshiCommented:
I think you need D3 or D4 to compile it...
0
 
philipleighsCommented:
If it is not a ole server, then there is no point calling regsvr32. All it does is load the dll, locate and find that function, call it, then close the library.

Cono, I know you're not a bozo so forgive me if I offend you with such obvious comments like these:
Is the dll in \system or \system32?
Is it on the path?
Try putting it in the exe dir.

Also, when you declare the function in your exe, type external 'dllname.dll' at the end, not just external 'dllname';
I was bitten by this once, but it was a D1 program on NT.

Cheers,
Phil.

0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
rwilson032697Commented:
I think Madshi has it...

Raymond.
0
 
rwilson032697Commented:
Umm.. On reflection I think the answer is none of the above.

Do you declare youre functions like this (in an interface unit)?:

procedure MyFunc; external 'MyDLL';

if so change them so they look like this:

procedure MyFunc; external 'MyDLL.DLL';

NT is touchy about missing extensions on DLL filenames...

Let me know how you go.

Cheers,

Raymond.
0
 
philipleighsCommented:
Raymond, Dude!

Read my comment!

Cheers,
Phil.

0
 
rwilson032697Commented:
Botherations! My brain has turned to mush - I'm outta here!

Raymond.
0
 
Ronald BusterAuthor Commented:
He Madshi,

Answer the question and you receive the points. Fair is fair ok.

regards,

Cono
0
 
MadshiCommented:
So I guess, my comment helped you?
If not: please reject my answer...   :-)

Thank you, Madshi.
0
 
Ronald BusterAuthor Commented:
Madshi,

Yes your comment solved my problem

However it is kind of strange that the same dll works on windows 95 but not on windows NT without registering the dll with regsvr32. Don't you agree with me

Anyhow thanks,

regards,

Cono
0
 
MadshiCommented:
Yes I do. But I'm used to this kind of problems...   :-(
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now