Re(3): I NEED HELP ASAP!
selecto only one folder and export that. folder by folder. then you will see which folder contains the corrupt message(s) and can narrow it further down. ---marlyse former message(s) quotes: - On trying to export, I get the assistant. I follow the prompts, screen # 3 gets me save, and when I try, I get a dialog box saying A Powermail engine error occurred. So I can't export anything. Now what?
Re(3): I NEED HELP ASAP! - PS
BUT, I did make an exported Mail file, before attempting the upgrade. What can I do with that? thanks On trying to export, I get the assistant. I follow the prompts, screen # 3 gets me save, and when I try, I get a dialog box saying A Powermail engine error occurred. So I can't export anything. Now what? Thanks Rick, When I attempted an upgrade from 4.2 to 5.0, all hell broke loose! Upon starting up, the sort index function started, got to the end, and then the app quit (5.0). Can you send me a crash log? Crash logs are stored in your Library/Logs/ CrashReporter folder. (With Mac OS X older than 10.3, you first have to enable crash reporting in the preferences of the Console application). BUT, any attempt at using the sorting function takes me through the process , sorting 15,000 messages, and then at the very end I get the above problem again. Do you mean the search function? If so, the crash occurs when reindexing your database. If you can't fix the problem with the low level rebuild (and if disk utilities do not help), you can disable indexing from the preferences, then export your database to the PowerMail Exchange format. Note that, as somethings seems badly corrupted in your DB, the export will probably crash as well, so the best is to select all your folders, and export the selected mail folder; if a crash occurs, the corrupted message is located in the last exported mailbox. You can then export this folder in several steps, by selecting groups of messages and exporting the selected messages. Once you have successfully exported all the non corrupted messages, quit PM, remove the corrupted Message Database file from your PowerMail user folder, relaunch PM, reactivate the indexing, and import the exported data. You will have to verify all your filters after that, because it will break the move to folder ones. Best regards Jérôme - PowerMail Engineering - The powerful tools and superior usefulness of PowerMail certainly make it a better choice for me and my business than Entourage or Eudora. Jaede Miloslavich, PowerMail user Download a demo version from www.ctmdev.com -
Re(2): I NEED HELP ASAP!
On trying to export, I get the assistant. I follow the prompts, screen # 3 gets me save, and when I try, I get a dialog box saying A Powermail engine error occurred. So I can't export anything. Now what? Thanks Rick, When I attempted an upgrade from 4.2 to 5.0, all hell broke loose! Upon starting up, the sort index function started, got to the end, and then the app quit (5.0). Can you send me a crash log? Crash logs are stored in your Library/Logs/ CrashReporter folder. (With Mac OS X older than 10.3, you first have to enable crash reporting in the preferences of the Console application). BUT, any attempt at using the sorting function takes me through the process , sorting 15,000 messages, and then at the very end I get the above problem again. Do you mean the search function? If so, the crash occurs when reindexing your database. If you can't fix the problem with the low level rebuild (and if disk utilities do not help), you can disable indexing from the preferences, then export your database to the PowerMail Exchange format. Note that, as somethings seems badly corrupted in your DB, the export will probably crash as well, so the best is to select all your folders, and export the selected mail folder; if a crash occurs, the corrupted message is located in the last exported mailbox. You can then export this folder in several steps, by selecting groups of messages and exporting the selected messages. Once you have successfully exported all the non corrupted messages, quit PM, remove the corrupted Message Database file from your PowerMail user folder, relaunch PM, reactivate the indexing, and import the exported data. You will have to verify all your filters after that, because it will break the move to folder ones. Best regards Jérôme - PowerMail Engineering - The powerful tools and superior usefulness of PowerMail certainly make it a better choice for me and my business than Entourage or Eudora. Jaede Miloslavich, PowerMail user Download a demo version from www.ctmdev.com -
Re: I NEED HELP ASAP!
I was probably the first one to encounter this problem. This was clearly caused by new indexing engine introduced with PM5. I hope CTMDev is taking a hard look at this. In my case, PMSalvage ($50!) did not help, but just wasting my two days to find it couldn't transfer most of my mails in Japanese. You might not have this problem if no multi-byte message in your dB. I ended up with exporting from PM5, importing to PM4, rebuild database then reimport back to PM5. Since then, PM5 has been working just fine. The entire process took me 10 days. I do not believe my PM4 database was somewhat less than kosher. My strong believe was that PM5 background indexing in some point made a few old messages corrupted. -- - Hiro [PROTECTED] [PROTECTED] [PROTECTED]
Re(2): I NEED HELP ASAP!
Since you saved your old files and you were able to go back to 4.2, first try starting up powermail 4.2 with both the apple and alt keys down - then click all the boxes to rebuild the database files, and disable all indexing. That might be enough to repair any damage and let you upgrade. I tried that. It didn't help. in my wife's case, this still did not let us upgrade - apparently there were still corrupt messages in her database file still that screwed up PM5 - and when building the sort index, it choked on these messages. Apparently that's the case with me. You have to find them and get rid of them, which can only be done by tedious trial and error. There are 15,000 messages in the Database! It's impossible. Are you telling me that the Message Database File is corrupted in some way and can't be fixed otherwise? If so, by paying$$ and upgrading, I've lost all sorting functions for all existing messages? Holy ^%$*!!! And if so, how do I ever get PM 5.0 to even open?? Rick
I NEED HELP ASAP!
Hi When I attempted an upgrade from 4.2 to 5.0, all hell broke loose! Upon starting up, the sort index function started, got to the end, and then the app quit (5.0). I went back and tried to open with 4.2, and the same thing happens, except I get a dialog box that says Power Mail Engine error occured There are two buttons. the More Info yields another dialog box that says Class = MAS, what= 1, when=100. Clicking the OK button DOES NOT clear the dialog box. Meanwhile, I can see my browser window open, but can't access it since I can't past the endless loop of the non-working dialog box. It iwas necessary to Force Quit. I was able to work around the problem by bypassing the sorting function. I did that by first trashing the Message database index file within the PowerMail Files Folder,then opening 4.2 , and then selecting the PowerMail Files Folder ( which still had the Message databse file but not the Message database index file). BUT, any attempt at using the sorting function takes me through the process , sorting 15,000 messages, and then at the very end I get the above problem again. What's wrong and what can I do? Thanks Rick Thanks Rick PS: I'm on digest mode. Please e-mail me direct
I NEED HELP ASAP!
Hi When I attempted an upgrade from 4.2 to 5.0, all hell broke loose! Upon starting up, the sort index function started, got to the end, and then the app quit (5.0). I went back and tried to open with 4.2, and the same thing happens, except I get a dialog box that says Power Mail Engine error occured There are two buttons. the More Info yields another dialog box that says Class = MAS, what= 1, when=100. Clicking the OK button DOES NOT clear the dialog box. Meanwhile, I can see my browser window open, but can't access it since I can't past the endless loop of the non-working dialog box. It iwas necessary to Force Quit. I was able to work around the problem by bypassing the sorting function. I did that by first trashing the Message database index file within the PowerMail Files Folder,then opening 4.2 , and then selecting the PowerMail Files Folder ( which still had the Message databse file but not the Message database index file). BUT, any attempt at using the sorting function takes me through the process , sorting 15,000 messages, and then at the very end I get the above problem again. What's wrong and what can I do? Thanks Rick Thanks Rick PS: I'm on digest mode. Please e-mail me direct
I NEED HELP ASAP!
Hi When I attempted an upgrade from 4.2 to 5.0, all hell broke loose! Upon starting up, the sort index function started, got to the end, and then the app quit (5.0). I went back and tried to open with 4.2, and the same thing happens, except I get a dialog box that says Power Mail Engine error occured There are two buttons. the More Info yields another dialog box that says Class = MAS, what= 1, when=100. Clicking the OK button DOES NOT clear the dialog box. Meanwhile, I can see my browser window open, but can't access it since I can't past the endless loop of the non-working dialog box. It iwas necessary to Force Quit. I was able to work around the problem by bypassing the sorting function. I did that by first trashing the Message database index file within the PowerMail Files Folder,then opening 4.2 , and then selecting the PowerMail Files Folder ( which still had the Message databse file but not the Message database index file). BUT, any attempt at using the sorting function takes me through the process , sorting 15,000 messages, and then at the very end I get the above problem again. What's wrong and what can I do? Thanks Rick Thanks Rick PS: I'm on digest mode. Please e-mail me direct
Re: spamsieve scripts
On 8/27/04, PowerMail discussions wrote: 5) In the Script Editor, change SpamSieve to iCal and compile the script. (note: you will get a compile error, that's OK) 6) Change iCal back to SpamSieve, compile it again, and save. I had not read any of this before running into the problem, but I just added a blank space at the end of the script file and recompiled, and it worked. Bob * Bob Parks [EMAIL PROTECTED] [EMAIL PROTECTED] www.kidsource.com I hate documentation, it gives you a false sense of having done some useful work! - Anon. 2003 *
