Howdy fabios_ss!
Microsoft Knowledge Base Article - 183414 describes your problem
pretty much spot on, but under somewhat different circumstances.
Regardless, all of the articles point to a missing/damaged/corrupt
Mfc42.dll file being on your NT box.
http://support.microsoft.com/default.aspx?scid=kb;en-us;183414
"The information in this article applies to: Microsoft Exchange
Server 5.5
...
SYMPTOMS
... the following error message may be displayed:
The extension [smtp] could not be loaded. The error 87 occurred while
formatting Windows NT error 182. Microsoft Windows NT ID
No 0xc00200b6.
CAUSE
This problem can occur when the Mfc42.dll file in the Winnt\System32
folder is missing or damaged.
WORKAROUND
To work around this problem, follow these steps:
Rename the Mfc42.dll file in the Winnt\System32 folder, if it exists.
[ You might want to rename it to something such as Mfc42.dll.old ]
Copy the Mfc42.dll file from the Server\Setup\I386 or Server\Setup\Alpha
folder on the Exchange Server 5.5 CD-ROM to the Winnt\System32 folder on
your hard disk. To do so, type the following command at a command prompt,
and then press ENTER:
copy <drive>:\server\setup\<platform>\mfc42.dll c:\winnt\system32
where <drive> is letter of your CD-ROM drive and <platform> is the
appropriate folder on the CD-ROM (I386 or Alpha).
Quit and restart the ... program.
If this does not resolve the problem, another successful workaround
has been to remove and reinstall the Exchange Administrator using the
Exchange Setup program."
There are additional things to check and additional workarounds at
the Microsoft Knowledge Base Article - 186787
http://support.microsoft.com/default.aspx?scid=kb;en-us;186787
You might also check the third party application directory, etc. for
an updated version of the Mfc42.dll file if none of the above work.
Search Strategy:
Used the Microsoft Knowledge Base search facility located at:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
with the keywords:
error 87 182 formatting nt 0xc00200b6
Using (the option): All of the words entered
If you need any clarification, feel free to ask.
Looking Forward, denco-ga |
Request for Answer Clarification by
fabios_ss-ga
on
18 May 2003 19:56 PDT
Looks like a tough one.
This is what I did.
1) Copied over the mfc42.dll from the exchange CD(919K) into the
system32 dir (backed up old)
No Luck
2) Checked the add in and other folders to see if permissions were ok
(also reset applied them)
No Luck
3) Copied in the mfc42.dll from the third party application (972K)
into the system32 foler
No Luck
4) Reinstalled exchange ontop
No Luck
4) Reapplied SP4
Still no Luck
I noticed the the mfc42.dll file is still the one from the third party
app (972K) so im thinking that it never got updated in the re
install??
I going to request some support from the third party.
If you have some more ideas I would love to hear from you
Note: I do not get this error using the exchange administrator on a
2000 box.
My question would this error be affecting the use of this connector? I
am having other issues with the support but im trying to rule out
whether this error is associated to them.
Fabian
|
Clarification of Answer by
denco-ga
on
18 May 2003 21:00 PDT
Howdy fabios_ss!
Sorry that the first run through did not work.
Make sure to check the "MORE INFORMATION" section at the bottom
of the Microsoft Knowledge Base Article - 186787 web page.
http://support.microsoft.com/default.aspx?scid=kb;en-us;186787
"If you are running Exchange Server on a Windows NT 4.0 system, and
if the HKLM\System\CurrentControlSet\Control\LSA\restrictanonymous
registry key exists, make sure it is set to 0."
You can do the above, by clicking on Start, then Run and in the box
next to Open, type in regedit and click on the OK button.
You should probably go to File and do an Export of the Registry
before doing the rest of the following.
A tree style window will open, and you will want to click on the
plus sign next to Hkey_Local_Machine, then the plus sign next to
System, then the plus sign next to CurrentControlSet, then the
plus sign next to Control and then on the folder (not the plus
sign) next to Lsa. In the right tree window, you might see an
entry marked restrictanonymous there. There might be an entry
marked restrictanonymoussam as well, so be careful to get the
correct register entry.
Double click the restrictanonymous entry on the right side and
make sure the entry under Vale Data is a 0 (zero).
A Google cached version of a Macarlo, Inc. web page describes
a problem with "RUNNING TWO DIFFERENT VERSIONS OF EXCHANGE".
http://216.239.39.100/search?q=cache:www.macarlo.net/msbackoffice1509.htm+error+%27182%27+%2787%27+%22service+pack%22
"An Exchange Server Update reader describes how he has
two Exchange Server systems joined to the same site in
two different locations. One is running Exchange Server
5.5 and the other is running Exchange Server 5.0. The
servers are joined by one Internet Mail Connector on
the Exchange Server 5.0 system. He received an error
message on the Exchange Server 5.0 after he installed
the Exchange Server 5.5 saying: There was an error
connecting to the SMTP extension While formatting Nt
error 87 error 182 was noted Nt id : 0xc00200b6
The problem occurred because two different versions of
Exchange Server are functioning together. The solution
is to copy the mfc42.dll file from the Exchange Server
5.5 CD-ROM to the winnt\system32 directory of the
Exchange Server 5.0 system."
Yes, I agree that the Mfc42.dll file did not replaced
in your latest reinstall of Exchange. Are there any
tests suggested by the third party in order to see if
the connector is working correctly? I don't like that
the error message specifically stating the connector
could no be loaded, and would be wary that it indeed
was working.
I will continue looking for anything else I can find,
and good luck with the third party.
Looking Forward, denco-ga
|
Request for Answer Clarification by
fabios_ss-ga
on
25 May 2003 01:15 PDT
Definetly a tough one.
No matter what DLL I use either the third party or the one from the
exchange CD is still gives me grief.
I also check that setting in the registry and there is no such key
there.
"restrictanonymous" should I create this key? is it a key or a value?
I have also setup another NT box and been able to replicate the
problem with the same connector.
The only thing I can think of now is this registry key...whether it
should be created or not?
I think I will go off to the third party to get them to figure this
one out.
If you have any more ideas let me know.
Cheers,
Fabian
|
Clarification of Answer by
denco-ga
on
25 May 2003 17:18 PDT
Howdy fabios_ss!
As the Microsoft Knowledge Base Article says:
"If you are running Exchange Server on a Windows NT 4.0 system, and
if the HKLM\System\CurrentControlSet\Control\LSA\restrictanonymous
registry key exists, make sure it is set to 0."
I would say you do not need this key at all. It is just in situations
where you do have this registry key, you need to make sure it is set to
0 (zero) which is the same thing as turning it off. Since your system
does not appear to have this key, it is the same as it being off, so
that (unhappily) is not going to be a factor in solving the problem.
I agree with you that the problem is in the third party software, and
it would appear to be a conflict between it and the mfc42.dll file.
I will check even further, but unfortunately I have not come across
anything new so far.
Looking Forward, denco-ga
|
