After moving users to a new exchange (2003) server they recieve sync errors when launching Outlook

[spyordie007]

After moving a number of users on to a new 2003 Exchange server (from
Exchange 2000) they recieve a sync error in Outlook every time it is launched
if they are using offline mode.

Error example:
--------------------------------------------
10:24:19 Synchronizer Version 11.0.6352
10:24:19 Synchronizing Mailbox 'Name, User'
10:24:19 Synchronizing server changes in folder 'Inbox'
10:24:19 Downloading from server 'mail.server'
10:24:19 1 item(s) added to offline folder
10:24:19 Error synchronizing folder
10:24:19 [80040119-501-0-5C0]
10:24:19 The client operation failed.
10:24:19 Microsoft Exchange Server Information Store
10:24:19 For more information on this failure, click the URL below:
10:24:19
http://www.microsoft.com/suppo...err=80040119-501-0-5c0
10:24:19 Done
--------------------------------------------

I've ensured Outlook is set for unicode mode for these clients as well as
disbling/recreating the .ost but the issue persists. I've seen others with
this problem before and they were typically able to resolve it by recreating
the .ost and ensuring Outlook was in unicode mode so I'm kind of at a loss
for what step to take next.

Anyone have any suggestions for resolving this issue or where to look as a
next step?

Thanks in advance,

-Erik

 

[spyordie007]

bump

 

[spyordie007]

bump

 

[GTiBri]

I probably don't have a fix for you, but I had a very similar issue with our new Exchange 2k3. I just recreated the users profile. Have you tried that?

 

[spyordie007]

You mean their windows profile? I wouldnt exactly call that a reasonable fix (I've got about 300 users on this server). I'll see if I cant try it with an account to see if it makes a differance.

thanks for the reply

-Erik

 

[GTiBri]

No, I mean the profile for Outlook. Of course the whole windows profile would include the outlook profile.

The reason I delete the Outlook profile and deleted is that I changed the server but when the sync windows popped up, it still had the old server name on it. so I just deleted the Outlook profile and created a new one. All fixed.

Sorry it took me a bit to answer. The holidays were busy here.

 

[spyordie007]

Than I'm not sure I understand what you mean by their Outlook profile. Do you mean deleting the Outlook registry key for the user (and allowing it to recreate)? Do you mean the Outlook directory in their Application Data? A user's settings for Outlook are stored in a couple of differant places in their Windows profile so I'm not sure what you mean by "recreate their profile."

Thanks for the responses.

And no problem about the holidays

 

[GTiBri]

Well, when you go into the settings for Outlook (at least the way we have it set up) you usually have an option to show profiles. At that point you can delete the profile and create a new on.

When you change settings in Outlook, how do you usually do it? From the tools menu in outlook or from the control panel->mail options?

If you use the tools menu way, you won't see an option to show profiles.

 

[mikecel79]

Which AV program are you running on your Exchange Server and your clients? I had problems synchronizing offline folders and it turned out to be the AV program was causing the sync to timeout.

 

[Skunk]

I just went through this with users on one of our exchange servers. It turned out to be the offline address book that was causing all the trouble. I had to open exchange system manager, delete the offline address book and recreate it. The next time a send and receive is run it should download the newly created OAB.

 

[spyordie007]

GTiBri-

Okay I get what you were going after. Thanks for the suggestion, I'll take a look.

Which AV program are you running on your Exchange Server and your clients? I had problems synchronizing offline folders and it turned out to be the AV program was causing the sync to timeout.

Mcafee Virus Scan versions 7 & 8 on the clients. The server is running Groupshield 6. I suppose I could try temporarily disabling groupshield and the AV on a client machine to see if the symptoms persist. Thanks for the suggestion.

I just went through this with users on one of our exchange servers. It turned out to be the offline address book that was causing all the trouble. I had to open exchange system manager, delete the offline address book and recreate it. The next time a send and receive is run it should download the newly created OAB.

Also a good idea, and perhaps the easiest to test (no client configuration).

Thanks for all the suggestions,

-Erik

 

[jaykleg]

So this is all on the same domain, and it was upgraded from 2000 AD to 2003 AD? There were no problems running the "prep" tools? (My questions have more to do with curiosity than thinking that I might be useful.)

 

[spyordie007]

All the users that are experiencing the problem are on the same server and are members of the same domain.

The domain is running in 2000 Native mode and the exchange organization is running in mixed mode.

AFAIK if forestprep or domainprep were to fail the installer for exchange wouldnt have worked. But to answer the question no there werent any problems, both went as they should have.

 

[loup garou]

Are you running in cached exchange mode (ol2k3)?

 

[spyordie007]

Sorry if it wasnt clear before, yes the users who recieve the sync error are in exchange cached mode.

 

[mikecel79]

Any luck with this so far? When someone suggested the OAB I thought about that too. Had a similiar problem with Exchange 5.5 one time and recreating the OAB fixed it.

 

[spyordie007]

Thanks for all the suggestions.

The good news is I've been able to stop the synch errors from occuring by recreating the outlook profile (as was suggested by GTiBri).

The bad news is that rebuilding the OAB and disabling groupshield did not stop the errors for all the other accounts.

At this point the only real *fix* I have is to go around and manually recreate the outlook profile for the roughly 300 users on this server (blowing away their views and settings in the process). Obviously a PITA solution, but at least I know that something works.

Thanks for all the help guys,

-Erik