'Outlook Trying to Retrieve data...' from WRONG server!

J

JayDee

I've just completed migrating from exchange 5.5 to exchange 2003

My clients are all Outlook XP sp2 on win2k sp4

Users are all looking at their migrated mailboxes on a new server.

I have a few users complaining that they get the 'outlook is trying to
retrieve data from server...' dialog box, and outlook freezes
I checked it out and found they were right.

Outlook is trying to find the old exchange 5.5 server, which is now offline.
Suubsequently outlook appears to hang until it times out this request

the fact that it doesn't find the old exhange server doesnt appear to cause
any errors, but it makes outlook pretty frustrating to use for these people.
sorry - did I say frustrating... i mean unuseable!

I thought that the problem would go away if I created new MAPI profiles for
the affected users, but sadly, it doesn't

I've seen a few things dotted around the web of others having a similar
problem, but there arent really any solutions or even suggestions.
One guy mooted that Outlook 2000 thru Outlook 2003 are pretty buggy in this
respect and dont update their MAPI object references properly
But I really would have expected a new MAPI profile, new OST file and a full
sync to sort it out if this were the case

I'm at my wits end,

Anyone got any ideas?

regards

J
 
J

JayDee

Thanks for the prompt reply Neo.

This doesnt really apply in my situation as the two servers were never in
the same Exchange organisation.
We chose the more difficult 'Inter-Org' migration method, becuase we wanted
to start all over again.

The two servers have never shared configuration info. The new Server and the
Old server are not aware of each other in any way.
We used EXSSRV to replicate public folder content, ADC to mail enable the AD
user accounts, and MAILMIG.EXE to migrate the mailboxes.

anything else you can think of?

regards
J
 
N

neo [mvp outlook]

I've never done this type of migration. Have you tried posting this
question in one of the microsoft.public.exchange.* groups? (right now I'm
thinking that the ADC is the wild card since you didn't mention if it was
ADC from Exchange 2003 or Windows 2003.)
 
J

JayDee

Yeah, I have.
There's an identical thread running in 'microsoft.public.exchange.misc'- but
I really dont think that its a server / migration issue or hangover, because
70% of my clients are working fine. - myself included.

pehaps it would help if I explained how ADC was used in context - just to
rule it out.
ADC is was simply used to 'mail-enable' my pre-existing AD user objects in
my windows 2003 domain by copying the exchange attributes from the
corresponding Ex5.5 Directory Object into the user object on the AD side.
Another connection agreement existed to copy the attributes from the user
account in AD, into the user object in the exchange 5.5 DS.
Using ADC in this way, configured with 2 separatate one-way, inter
organisational.connection agreements., is how we maintained full
bi-directional syncronicity between the old Exchange 55 users in the
exchange DS, and the corresponding users in the AD.

It also created 'custom recipients' in ex 5.5 as placeholders, for migrated
and deleted the 5.5 mailboxes. This was necessary to maintain interop
between exchange orgs, so users on each server could exchange mail during
the migration - which was phased.
They exchanged email by way of an SMTP connector configured for our address
space.

It all worked beautifully, once we'd figured it out.

but really I think this is a client / outlook problem rather than an
exchange / migration / server one.
Something on the client is haunted by the old exchange server.

I know this, because I've used logged on to another workstation as one of
the affected users, created an outlook profile, and tested it AOK - no
problem..

It definitely must be outlook client / MAPI related.



J
 
J

JayDee

Hmmmm..

that'll be a 'no' then, I guess.

lets see if the window-lickers at PSS can help.

But my spidey-sense tells me I know what they'll say
"reinstall the affected clients"
Click to expand...

ho hum. :(
 
Top