During migration from legacy Exchange 5.5 to Exchange 2003 SP3 evyrything worked fine until public folder migration. I am getting the following message when trying to open Public folders on the organizational level in the exchange systems manager (V2003). "An existing connection was forcibly closed by the remote host" Facility: win32 ID No: c0072746 Exchange System Manager From users point of view everything works fine. Any ideas? What is the safest for decomissionig Exchange 5.5 in this situation ?
Hi, This might help: http://groups.google.dk/group/microsoft.public.exchange.admin/browse_thread/thread/5cfa726245e0b08b/d25e88350746181f?lnk=st&q=c0072746&rnum=3&hl=da#d25e88350746181f I would wait with the decommisioning till this issue is resolved. Leif "Sergey Kharitonov" <Sergey Kharitonov@discussions.microsoft.com> wrote in message news:58472B8A-0D68-45BB-88A4-64C2B4F4DF1A@microsoft.com... > During migration from legacy Exchange 5.5 to Exchange 2003 SP3 > evyrything worked fine until public folder migration. > I am getting the following message when trying to open Public folders > on the organizational level in the exchange systems manager (V2003). > > "An existing connection was forcibly closed by the remote > host" > > Facility: win32 > ID No: c0072746 > Exchange System Manager > > From users point of view everything works fine. > Any ideas? > What is the safest for decomissionig Exchange 5.5 in this situation ? >
I've read the mentioned link during the Google search, it's not my case :-(( "Sergey Kharitonov" wrote: > During migration from legacy Exchange 5.5 to Exchange 2003 SP3 > evyrything worked fine until public folder migration. > I am getting the following message when trying to open Public folders > on the organizational level in the exchange systems manager (V2003). > > "An existing connection was forcibly closed by the remote > host" > > Facility: win32 > ID No: c0072746 > Exchange System Manager > > From users point of view everything works fine. > Any ideas? > What is the safest for decomissionig Exchange 5.5 in this situation ? >
