The version conflict that it talks about is after you have migrated to a new
server. Seeings as though you don't say you have migrated, and it has 'just
started' it more likely seems as though it could be something else.

If a reboot doesn't help, remove the IMS and install it again. Obviously
this is going to cause some downtime. But it does sound as though something
has got itself confused somewhere.

Regards

Mr Louis Joyce
Computer Support Analyst
Network Administrator
BT Ignite eSolutions




-----Original Message-----
From: Allan Johnson [mailto:[EMAIL PROTECTED]]
Sent: 11 December 2001 22:36
To: Exchange Discussions
Subject: extension smtp cannot be loaded


Hoping someone has run into this before.

I am receiving "extension smtp cannot be loaded" when trying to open the IMC
on my Ex 5.5 SP4 / NT 4 SP6a.  I have the option of abort/ignore/retry, if I
ignore the IMC opens.  This has just recently (past week) started, I
originally saw it running admin from my W2K pro workstation.  It also
happens logged onto the server.

Q196924 and Q250907 both refer to a version conflict of IMCADMIN.DLL but
when I follow the instructions and look at the version number in raw mode it
matches the version of the file.

Any ideas?  I am planning a reboot during off hours but I hate that answer.
The only other thing I can think of right now would be to re-apply SP4 but
that is not a willy-nilly answer for a production server.

Any help is appreciated.

Allan Johnson

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to