Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  Internet  |  Email  |  Entourage Email Archive X  |  Will no longer function-Applescript error

Entourage Email Archive X

Entourage Email Archive X

Archive emails within Microsoft Entourage.

Version:  4.2.0

   [ Views: 380 ]

Will no longer function-Applescript error

Feedback Type:  Troubleshooting Report

Contributed by: n9vjg Wednesday, July 16 2008 @ 07:47 AM PDT

Product Platform: MacOSX

Used Product For: Less than a month

I sent some emails to support asking for help. No response yet, but maybe I'm rushing it. I'm falling behind on work because I got involved with this thing. They definitely need support forums!

It seemed to work great. But then I processed almost 30,000 messages and EEAX didn't like moving all of them to the trash. So I've been making backups of my database before running EEAX to restore things. I set a filter to process a year's worth instead and that seemed to work.

But then I started over again because I wanted to try the FM database. I processed about 20,000 messages and worked great. But then again, I can't move them to the trash because it crashes with another Finder error (which I cannot find right now). I left all messages where the were in the database.

So then I wanted to have the Folder Archive as well. So I ran it and got the the "Finder got an error: AppleEvent timed out. (-1712)" error. Sometimes it freezes the Finder too. Now it will not run for Text, Tab-Text nor Archive Folders. I have even set it to search only one folder of 20 messages. Same error. Basically, it's dead.

Can anyone offer some advise? Should I reinstall?   
System Info:Mac Pro Quad 10.5.4 4GB RAM

1 of 1 users found this helpful.

Rate this Troubleshooting Report

Was this Troubleshooting Report helpful? Yes | No

Comments

1 comments |

Will no longer function-Applescript error-SOLVED - n9vjg

A person from Softhing responded. We went back and forth to make sure I was doing everything right. I was asked if my destination folder was in my "Microsoft User Data" folder. Yes it was. I changed the destination to another location away from that folder and it works.

Reply to This

Thursday, July 17 2008 @ 07:52 AM PDT