Rule error in Outlook

[Flinty]

Hi all,

We have an 1100 user Exchange 2000 environment and 1 user out of the whole bunch started receiving an error message regarding rules today. The error happens at Outlook startup. Here's the error:

Rules in Error
Rule: Server-Requested Client Action
Error: MoveCopy, Unable to create dest msg.

All of the users rules have been subsequently removed but the error still occurs and this happens regardless of login location. I found one article at MS regarding Exchange 5.5 and upgrading to SP3 (which doesn't really apply to us) and somebody else suggested to reboot the PO. That is not too much of a problem but I'd like to avoid if possible. Thanks for any suggestions.

 

[chrisedwards6]

Recently having the same problem with this error message within an Exchange 2000 environment. Wondering if you found a solution.

 

[jongaze]

I'm in the same boat as you guys. This has happened since I applied Office XP SP3 to the Win2K Terminal Server. Was wandering if either of you had done the same?

The help in Outlook mentions creating rules in one version of Outlook and then running up a different version of Outlook causing this problem - am trying to work out if a service pack change might cause this prob.

Cheers!

 

[RedRaistlin]

I had a user with exactly the same problem.

I finally fixed it, but the fix could be one of two/three things:-

1. The rules that the user had (before I deleted them all) were pointing to a folder which had been recovered 'FolderName (Recovered)'

I removed the '(Recovered)' from the folder name.

2. The other thing I did was to move all the emails that were in this folder to a new folder I had called 'Test'

Uppon restarting Outlook, the progress bar appeared saying that it was processing rules on newly received emails (this had previously been running behind the error window) and when I restarted Outlook again everything was fine

3. The only other thing I noticed was that there was extensive use of Automatic Formatting (Colour coding emails) on the folder in question.

Good Luck guys/gals and be sure to post back if you can narrow down the exact fix.