"Outlook is trying to retrieve data..." Server doesnt exist!

[crackinchris]

Hi,
We have an new exchange 5.5 box - box called LD1NTS025.
We recently had an exchange box that died which was called LD1NTS002. We moved all our clients from this old box and onto the new one.

One of our Outlook 2003 Pro users (on new server) tries to send an external email. On doing this, a message appears saying "Outlook is trying to retrieve data from LD1NTS002.." - However LD1NTS002 is switched off, dead!

I have tried removing the MS Exchange account from client PC, re-adding, uninstalling office, checking to see if there are any COM-Addins (which there arn't). I'm running out of ideas and the user is getting frustrated. This problem doesn't happen with any other Outlook 2003 users using the new LD1NTS025 exchange box.

Any Ideas?

Chris

 

[zbnet]

Have you tried deleteing and recreating his MAPI profile?

 

[dennisbbb]

On the client machine, remove the Outlook profile, then do a registry search for all instances of LD1NTS002. Once you found, change the name to new name.

Or delete them. Reboot machine. Then add user to Exchange again.

 

[crackinchris]

Hi again,

Dennisbbb, tried your way, no luck.

zbnet, I'm not sure what a MAPI profile is?

Still having no luck, The error appears after approx 30 secs after clicking Send on the email message - this error only appears on sending to an external email address.

Screen dump of error:

http://chriswh.websiteallies.com/exchangeerror.jpg

 

[zbnet]

The MAPI profile is what dennisbbb is calling the Outlook profile, accessible via the Mail icon in Control Panel.

Have you had public folders configured? Were there PFs on the old server? Have you altered the Public Folder server setting in the properties of your Private Information store on the new server? This is important to stop the clients try and access the contents of the PF hierarchy on the old server. Even after you change this setting, certain cliets can still have problems in trying to access the old server, because MAPI profiles cache this info. That's why I told you to delete and recreate the MAPI profile, this will force the client to read the PF folder again from its logon server, and all will be well again. dennisbbb was trying to get you to do the same thing which his instructions to scan the registry and alter the name, but deleteing and recreating the profile is easier. But change the PF server setting on your new server's Private Information store first.

 

[dennisbbb]

Simply can't believe Outlook can be that stubborn and want to find it's way home to the old server.

A brute approach is simple do a cleansweep of the registry after Outlook is uninstalled. There is no way the reinstallation will know what the old server's name was.

BTW, the screenshot is not of Outlook 2K3. More like Outlook 2K?

 

[Zelandakh]

unhide files and delete outlook.nk2 and see if the problem goes away. It is in c\docs and settings\<user>\local settings somewhere.

 

[crackinchris]

Tried all of the above with no luck.

In our company we hav about 10-12 exchange boxes around the country replicating every 5mins. I'm thinking that the headers/indexing in the old Priv.edb has some pointers to our old server and its conflicting somewhere.

I'm hoping that after a short while (days) that with replication, all email servers will sort themself out and get rid of this error; Unless someone else has any ideas?

Cheers