John, I finally had a chance to look at this -- still no success. Each time
I tried, I started with a new database. In the prefs, I set it t Entourage
for the program and for outgoing mail and made no other changes; in the
setup, I set it to archive stuff older than 300 days and changed it to
Normal mode (rather than Test mode) and made no other changes.

Here's what I found:
The librarian did not load by itself. I never once saw FileMaker change to
eMA database. I went into Scriptmaker and ticked on Launch and then ran it
as a script on its own; it then launched and for the first time I noticed
that in the Progress box on the setup page it said "ready"! However, it
still didn't work...

I found no "unknowns" in either script.
The Temp Text 1 field said 0.
I upgraded Entourage, and I tried it in safe mode.
I didn't repair permissions, although I did do it a few weeks ago. But
frankly, I don't think it's going to solve the problem...!



> On Jan 5, 2005, at 5:25 pm, Madeline (mad9303) wrote:
>> I gave up trying to get eMA to work again, until a few days ago. I
>> installed the beta version of eMA, and then started with a fresh
>> FileMaker database, but still cannot get the folder lists to update.
>> I set the prefs for Entourage (v10.1.4), and when I click on "Update
>> Lists" in SetUp, I get a quick beep -- presumably because the
>> Librarian hasn't launched. So then I click on "Archive" and it asks
>> to be taken to the Librarian, which then launches, whereupon I get
>> the following error message;
>>
>> 0S 10.3.7, Entourage, Filemaker, eMA 0403 , db version 0402.
>>
>> Error -2700. StartScript: Archive: ArchiveFolder: getting list of
>> messages in : GetFolderInfo: TextToFolderPath(): FolderPathStr: ' ')
>> is empty; please update folder list.
>>
>> I press okay, and now, assuming that the Librarian is running, I try
>> to click on the "UPdate Lists" again, but I still get the same
>> response of a quick error beep.
>
>
> I downloaded yesterday fresh copies of eMA 4.02 and 4.03b1 to check out
> myself, and checked out each one of the 2 databases in each. In all
> four cases, using the Update Lists button worked perfectly for me.
> That¹s with OS 10.3.7 and Entourage X 10.1.6.
>
> That is why I am at a loss as to why it does not work correctly for
> you, and I cannot repeat it in order to debug it. I will list a few
> things you can to consider and/or try, but the simple truth now is that
> I don¹t know why you are having this problem.
>
> TO ALL: Does anyone else currently have this problem?
> Or had it but fixed it? Anyone using other than Entourage?
> If this is due to something I did, I would like to fix it in
> the coming update. If not, but you know the cause,
> that fix should be added to the docs.
>
> 1) If the "Update Lists" button does not work for you, and it has not
> listed Entourage¹s folders, then pressing the "Archive" button will
> surely not work, for you have not been able to check the folders you
> want archived. That¹s why the error message said that the folder name
> ³...is empty; please update folder list.² But it at least showed that
> eMA Script Librarian was running in that case.
>
> 2) When eMA Script Librarian is launched, within a few seconds of
> pressing either button, it comes to the front (if only for a few
> seconds), so you should see its name appear in the menu bar, just to
> the right of the Apple menu (where it said ³FileMaker Pro² before you
> pressed the button). Do not assume that, because Librarian ran for the
> ³Archive² button, it is runs for ³Update Lists² Look for the name
> change in the menu bar.
>
> Since you heard a beep, that means that it is not getting to the step
> that launches Librarian. The script is set to beep
>
> Did you see a dialog after pressing the button, asking ³Are you sure
> you want to update the folders for Entourage?² If not, or there is a
> beep, there is something wrong happening for the scripts called.
>
> Also, since you got a beep, which is in the script for when it doesn¹t
> detect your pressing the ³OK² button, I presume that the dialog was not
> working right for you.
>
> Here are two things you can do if you want to try to pin it down:
>
> To check why there was a beep, pressing the Update Lists button and
> then go to the ³List Useful Fields² layout, scroll down one page, and
> look for the value, if any, in the field ³Temp text 1². This is set
> right after the error beep if FMP found an error, and may include an
> FMP error number. If it does have a number there, let me know.
>
> You could also check two scripts (³Update Lists² & ³Ask confirm²) for a
> missing parameter. If you have not done this before, don¹t worry: for
> this, you won¹t have to understand FMP scripts at all. I will explain
> the steps to get to the script, and what to look for. Go to the
> ³Scripts² menu and select the first item, ³ScriptMaker....² This takes
> you to the list of scripts that I wrote for eMA. The script named
> ³Update Lists² is near the top of the list, and ³Ask Confirm² is about
> 2/3 the way down. For each one in turn, select its name and click the
> Edit button. That will take you to the listing of the script: just scan
> the lines, looking for the word "<unknown>". If you don¹t find that,
> just press Cancel to leave. But if you do find ³Unknown² let me know
> where.
>
> 5) Do a Finder search on ³eMA Script Librarian² on all disks. There
> should only be one; if more than one, make sure the others are deleted
> and the trash emptied.
>
> 6) Have you tried to launch and check out eMA after restarting your Mac
> in "Safe Mode" (with the shift key down during startup? This is
> supposed to prevent startup items and some non-Apple system extensions
> from launching? It¹s a way to make sure that no such items that you
> have cause a problem. For example, I have found that the ³APE²
> Application Enhancer thing that is needed for several popular ³haxies²
> was causing at least one other standard application to crash. There are
> others that have caused other people problems. I suggest that you also
> perform a "Repair Permissions" with Disk Utility on your disk, if you
> haven't lately; I find it useful to do it often, at least once per
> month.
>
> 2) As you noted before, Michele Capurso seemed to have the same
> problem, using an Italian system with Entourage, but I received no
> response to my last suggestions. Are you by any chance also using a
> non-US system or time zone?
>
> 3) I notice that two of your recent messages were sent using Entourage
> 10.0.0 and 10.1.4. You might want to update these to 10.1.6, just in
> case some bugs needed fixing with the latest Mac OSs. That¹s a general
> suggestion; I doubt it is the cause of your problems with eMA.
> --
> Cheers,
> John
>
>
>
> --
> IMPORTANT: give your versions of eMA, FMP, Mac OS & your Email App.
> Latest eMA versions: <http://homepage.mac.com/ThinkAgain/Mac>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>