Ordinal not found error

numberone · 13th April 2001, 19:54

I have compiled an installation that uses the DLLRegisterServer function, and it works fine with Windows 2000 SP1 machines (Mfc42.dll 6.0.8665.0), but when a client runs it on an NT 4.0 SP4 machine (Mfc42.dll 4.2.xxxx) they receive the following error when the install program tries to register a DLL:

Olemainthreadwndname:
Ordinal 6663 could not be located in the DLL Mfc42.dll

Is this because the Mfc42.dll is too old on the client's machine? I did not think this installer had a reference to the MFC, but mabye I'm wrong. Can anybody help? Thanks.

rsegal · 3rd June 2003, 21:38

Saw this was posted two years ago. I've actually run into now. Is it from out of date MFC42 DLL?

numberone · 4th June 2003, 05:23

If I remember correctly, the problem was an out of date Mfc42.dll. I was able to rename the old version, then copy the newer version from a Win2k box, then reboot the NT4 machine, and then it worked (I think). That was a while ago so I can't remember exactly how I resolved the issue.

Joost Verburg · 4th June 2003, 11:47

Are you using the RegDLL command?

rsegal · 4th June 2003, 14:03

No I don't use RegDLL anywhere in my script. At least not to my knowledge. Could be it's hidden away in a macro or something but I doubt it.

Joost Verburg · 4th June 2003, 14:25

So which command are you using to call DLLRegisterServer?

rsegal · 4th June 2003, 17:36

Correction, I used to call RegDLL to register a DLL but I no longer use that. I now only have a call to UnRegDLL to get rid of the DLL I was formerly registering. Could that cause the problem?

kichik · 4th June 2003, 19:42

When installing an MFC application you should make sure the computer you're installing to has the right MFC version. IIRC Microsoft provide pre-built installers for MFC, so you can get one from MSDN and install it if the MFC dll version doesn't match your plug-in expectations.

rsegal · 4th June 2003, 20:32

Ok thanks Kichik, I'll do that.

4th June 2003, 11:47	#4
Joost Verburg NSIS MUI Dev Join Date: Nov 2001 Posts: 3,717	Are you using the RegDLL command? Last edited by Joost Verburg; 4th June 2003 at 14:25.

4th June 2003, 19:42	#8
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,337	When installing an MFC application you should make sure the computer you're installing to has the right MFC version. IIRC Microsoft provide pre-built installers for MFC, so you can get one from MSDN and install it if the MFC dll version doesn't match your plug-in expectations. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

13th April 2001, 19:54	#1
numberone Junior Member Join Date: Jan 2001 Posts: 12	I have compiled an installation that uses the DLLRegisterServer function, and it works fine with Windows 2000 SP1 machines (Mfc42.dll 6.0.8665.0), but when a client runs it on an NT 4.0 SP4 machine (Mfc42.dll 4.2.xxxx) they receive the following error when the install program tries to register a DLL: Olemainthreadwndname: Ordinal 6663 could not be located in the DLL Mfc42.dll Is this because the Mfc42.dll is too old on the client's machine? I did not think this installer had a reference to the MFC, but mabye I'm wrong. Can anybody help? Thanks.

3rd June 2003, 21:38	#2
rsegal Senior Member Join Date: Feb 2003 Location: Toronto, Canada Posts: 227	Saw this was posted two years ago. I've actually run into now. Is it from out of date MFC42 DLL?

4th June 2003, 05:23	#3
numberone Junior Member Join Date: Jan 2001 Posts: 12	If I remember correctly, the problem was an out of date Mfc42.dll. I was able to rename the old version, then copy the newer version from a Win2k box, then reboot the NT4 machine, and then it worked (I think). That was a while ago so I can't remember exactly how I resolved the issue.

4th June 2003, 14:03	#5
rsegal Senior Member Join Date: Feb 2003 Location: Toronto, Canada Posts: 227	No I don't use RegDLL anywhere in my script. At least not to my knowledge. Could be it's hidden away in a macro or something but I doubt it.

4th June 2003, 14:25	#6
Joost Verburg NSIS MUI Dev Join Date: Nov 2001 Posts: 3,717	So which command are you using to call DLLRegisterServer?

4th June 2003, 17:36	#7
rsegal Senior Member Join Date: Feb 2003 Location: Toronto, Canada Posts: 227	Correction, I used to call RegDLL to register a DLL but I no longer use that. I now only have a call to UnRegDLL to get rid of the DLL I was formerly registering. Could that cause the problem?

4th June 2003, 20:32	#9
rsegal Senior Member Join Date: Feb 2003 Location: Toronto, Canada Posts: 227	Ok thanks Kichik, I'll do that.