A514Style
asked on
Exchange 2003 MSExchangeMTA / Event ID: 9220 Warning
We have a windows 2003 server with exchange 2003 loaded on it, i have been getting the below warning
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Operating System
Event ID: 9220
Date: 12/27/2004
Time: 10:55:14 AM
User: N/A
Computer: FIMCMAIL
Description:
A sockets error 10047 on an open() call was detected. The MTA will attempt to recover the sockets connection. Control block index: 20. [BASE IL X25 DRIVER 11 261] (12)
For more information, click http://www.microsoft.com/contentredirect.asp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
can some help me
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Operating System
Event ID: 9220
Date: 12/27/2004
Time: 10:55:14 AM
User: N/A
Computer: FIMCMAIL
Description:
A sockets error 10047 on an open() call was detected. The MTA will attempt to recover the sockets connection. Control block index: 20. [BASE IL X25 DRIVER 11 261] (12)
For more information, click http://www.microsoft.com/contentredirect.asp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
can some help me
athelu
Did you migrate from an exchange 5.5 environment?
ASKER
Yes we had a Exchange 5.5 and upgreaded to a Exchange 2000 and then built a new exchange 2003 server and did a move mailbox and moved all user to that...
For some reason the server is still attempting to contact the 5.5 server : )
here is an article that describes how to remove the last traces of exchange 5.5 from AD
http://support.microsoft.com/kb/q284148/
here is an article that describes how to remove the last traces of exchange 5.5 from AD
http://support.microsoft.com/kb/q284148/
ASKER
I have tryed all of this and everthing is setup allready do u have any other comments?
is the Microsoft Exchange Event service running on your server? if so, stop it and set it to manual run. This service is for monitoring Exchange 5.5 connectsion/operations.
ASKER
No it was not running, its allread set to Manual..
ASKER
Ok i have called MS and worked out the problem, in are System manager under the conectors folder there was a conector that we had to delete, also on the default SMTP Virtual Server we set the IP address to (All Unassigned), also the Microsoft Exchange MTA Stacks Service was started we have stoped that..
Good to here!
The connector would have been an obvious one to look for. Don't we always forget to check the obvious : )
I sometimes have to import data from Exchange 5.5, so forgot about the x.400/mta stacks service. That might not be necessary to disable, but if you have elevated your operation mode to native mode, then this definitley will not be necessary. Thanks for the update. Nice to have the fix for the database at least.
The connector would have been an obvious one to look for. Don't we always forget to check the obvious : )
I sometimes have to import data from Exchange 5.5, so forgot about the x.400/mta stacks service. That might not be necessary to disable, but if you have elevated your operation mode to native mode, then this definitley will not be necessary. Thanks for the update. Nice to have the fix for the database at least.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.