I am attempting to Archive data from a outlook 2007 after a user reached his quota on the exchange server. The problem I am running into is there is one folder that conitues to duplicate itself in the mailbox as it is archived. and then archives, but does not remove that data from the folder, duplciates again and archives again. The 1GB mailbox has now created a 10GB PST. its a never ending loop and its not lowering the server data at all. HELP...

You state you are attempting this 'after' the user reaches his quota. Are you trying to set a rule to fire off to start the Archiving process? Perhaps this method is simple copying the data each time the user reaches his limit. Best to start from scratch. Remove all archiving and rules, and start again. If some folders are working as desired, you their settings as a guide. Good Luck. Jeremy

Who knows why it was happening. And who knows what the end user was doing. I ended up reinstalling office, manually creating a PST and manually moving the files over. Took forever, but it got the job done. Thanks for your reply.

Has the issue been solved by reinstalling office and recreating the PST file? You said that you did it because user reached limitation, so, its the archive option in File menu you used, not follow the AutoArchive setting, right? You can base on the following steps to isolate the cause: 1. Create affected users mail profile on a testing PC, try to reproduce the symptom [put a test message in that duplicate folder then try to archive], if the issue persisted, we can consider that issue is related to mailbox on the server somehow. So you can try to move the mailbox to another store and move it back, its an easy way to scan the mailbox for any corruptions. If issue not appears in testing PC, go on step 2 2. Go the affected PC, start Outlook in Safe Mode <Start->Run->Outlook /safe>, and try to reproduce the issue Notes: in this way, outlook will disable the most influence from 3rd-party Add-ins 3. I assumed that youd already tried to remove all the old OST files and recreate users profile, right? 4. If the issue reproduced, go to users application log, see if you can find any related information, warning or error about this archive action, cross-match with the log in fine users log, see if you can find any differences, or you can post in here

Hi, MSHelpNeeded, did the suggestions help? How's the issue now?