Re: Problems with Outlook after Moving Mailboxes



Wow, THANK you so much for posting. I barely caught this in time. I found
this error on my test move mail box (Exchange 2003 sp2). It's ok to move
mailboxes from storage group to storage group on the same server, but the
leap to another exchange 2003 sp2 server spawned the exact same errors for
us.

We use the Symantec AV for Exchange as well.

I was about to migrate the first large group. Whew! You saved my week
William!

T H A N K Y O U ! ! !

"william r. riley" wrote:

Try stopping the antivirus service and then restarting the Microsoft
Exchange Routing service first and the Microsoft Exchange Information Store
service second to see if that helps. The other option is to disable the
antivirus service from starting and rebooting the system.

After we tested the issue and determined that it was tied to the antivirus
software, Symantec AntiVirus for Microsoft Exchange, we disabled the service
and rebooted with no errors. After uninstalling the software and
reinstalling it, the problem did not returns and everything has been working
for about 5 days. The only difference that we noted in the two
installations was that when we initially installed it we pushed the install
from an existing server and when reinstalling it we did so from CD.

Hope this helps.

"Cain Aaron" <CainAaron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2AE90B07-E2C7-411F-A23E-6171D431987D@xxxxxxxxxxxxxxxx
The customer is running virus protection on the affected Exchange server;
however after stopping the virus software the problem still persist. So I'm
completely stumped here.


"Cain Aaron" wrote:

I'm also having this problem and there is no virus software or add-ins
installed on the affected system. I can open the mailbox just fine from
my
system. Outlook opens if I disable the Use Cached Exchange Mode, but if
I
try to click on any folder outlook crashes on the affected system. This
is
after migrating from Exchange 5.5.

Any help would be greatly appreciated



"william r. riley" wrote:

It appears that the problem seems to be tied to our antivirus software
on
this particular server. After stopping the service and restarting it
the
issues seem to be resolved. From here we will be monitoring the issue
and
see what happens after rebooting the server later this week. Thanks
for the
information and help.

"Yizhar Hurwitz" <no@xxxxxxxxxxx> wrote in message
news:Oo2EIAYQGHA.3192@xxxxxxxxxxxxxxxxxxxxxxx
HI.

Have you checked public folder replication?

Are you sure that you did try to create a fresh new mail profile
(no need to modify or delete the original yet, just create an
ADDITIONAL
one),
and see if you still have the problem?

Please also list the 3rd party related software on the workstations
(such
as anti virus or Outlook add-ons).

Try also using:
Start - Run
outlook /safe

Yizhar Hurwitz
http://yizhar.mvps.org


william r. riley wrote:
We haev tried recreating the profile and have had no luck. On the
test
system that we used, if we rolled them back from Office 2003 to
Office XP
the problems went away. If we move the mailboxes back to the old
server,
some of them will then work, but not all.

What do you mean by cleaning the profile?


"Mark Arnold [MVP]" <mark@xxxxxxxx> wrote in message
news:5d9p02lbmv2v2vfblqn5dkus819qitdo1r@xxxxxxxxxx
On Mon, 6 Mar 2006 14:22:27 -0600, "william r. riley"
<ckwagler@xxxxxxxxxxx> wrote:

We are receiving an error message from certain users when they
access
their
mailboxes through Outlook 2003 after moving their mailboxes from
one
Exchange 2003 SP2 server to another Exchange 2003 SP2 server.
outlook
2003
has all of the latest updates and patches applied. The Event
Viewer
message
is that of Event ID: 1000 and is

"Faulting application outlook.exe, version 11.0.8000.0, stamp
43599e06,
faulting module ntdll.dll, version 5.1.2600.2180, stamp 411096b4,
debug? 0,
fault address 0x0000eddc."

If we try to access the same mailbox through OWA or Office XP we
do not
have
any issues.

If we move affected mailboxes back to the original server, so far
we
have
not had the problem continue on the test group. Is this the only
solution
or will we run into issues having to do this as well?

Thank you.

Sounds like a pure client side thing. I'd be tempted to either
recreate the profile or clean the existing one. It doesn't look
like
an Exchange issue to me.






.



Relevant Pages

  • RE: Single Server Upgrade Exchange Question
    ... The Exchange Migration Wizard can migrate all user mailboxes. ... server and then import them to the destination server. ... Single Server Upgrade Exchange Question ...
    (microsoft.public.windows.server.sbs)
  • Re: no mailboxs in private foulder
    ... limited experince with exchange. ... Ping the exchange server ... Right click the mailbox store, is the first option "mount store" or is it ... Where are you seeing "Mailboxes and stuff"? ...
    (microsoft.public.exchange.admin)
  • Re: ADC Tool Step 3 - Resource Mailbox Wizard
    ... The resource mailboxes are still going to be replicated ... > will still exist on Exchange 5.5 server, ... I think of the AD as Exchange 2K3's ...
    (microsoft.public.exchange2000.setup.installation)
  • Re: ADC Tool Step 3 - Resource Mailbox Wizard
    ... The resource mailboxes are still going to be replicated ... > will still exist on Exchange 5.5 server, ... I think of the AD as Exchange 2K3's ...
    (microsoft.public.exchange.setup)
  • RE: is there a windows or exchange equivalent of fetchmail?
    ... SBC email account and put it on a local exchange mailbox. ... In SBS Server, we can use the POP3 Connector to ... retrieve incoming email from ISP POP3 mailboxes. ...
    (microsoft.public.windows.server.sbs)