Re(2): Database Rebuild FAILED
This leads me to believe that perhaps the root of this could be a single bad email. I agree strongly with this assumption. The only time I've ever had a problem with PM was when I had 1 bad HTML message and I could no longer index and PM would constantly crash and I was not able to rebuild cleanly etc. To solve the problem I archived my PM database folder for folder until I had gotten rid of that specific message and ever since PM does again great. ---marlyse
Re: Database Rebuild FAILED
Amnon Yaish said: I told you I checked the fonts and found them sound. PowerMail uses the default system fonts for chinese, and I checked the same fonts are also used by other programs. This is no proof they are sound. How are you checking it? What do you know about font corruption? A more reasonable approach would be to replace the fonts from original media and see if the problems go away. PM 5.2.2 Swedish | OS X 10.3.9 | Powerbook G4/400Mhz | 1GB RAM | 30GB HD
Re: Database Rebuild FAILED
On Jan 23, 2006, at 5:02 PM, Andy Fragen wrote: Agreed. But my experience differs. I've never had an unfixable db error with PM and I've been using it since v3 Andy, I also have had PM since v.3 and until Sunday had not encountered a problem that PM could not recover. An interesting side note, and one that really disturbs me, is that just prior to the PM failing to compress with DB errors my account on my OS X server mail server became corrupt and had to be recovered by doing a rebuild on the server. Since I use PM in pop mode for this account, the server only has messages on it for a very short period of time (the build up between checks and logins). This leads me to believe that perhaps the root of this could be a single bad email. As to PowerMail Salvage, I purchased it--given how long it took to run through just 1% of the DB, I didn't want to have run the tool twice since you have to quit to enter the purchase key, and then start the salvage all over again. PMS has been running on my system for over 24 hours, and so far it it reports that his recovered 219,798 messages in 825 folders. The progress bar shows about 10% left to go. Of course until I actually am able to finish the salvage and export the recovered emails, I won't be sure this has worked, but things are looking good. A suggestion to anyone in my shoes. Buy the license key for PMS before running the salvage all the way through once on a large DB. You will just have to start it from scratch again once you get the license key. Second, do the salvage on desktop system and not on a laptop. I have had to drive to and from work with the powerbook open on the passenger seat to keep the salvage running. I would guess that the beefier the machine, the better. Thanks for the feedback from everyone. Robert
Re: Database Rebuild FAILED
Mikael Byström wrote: What's your excuse for not having backed up your DB? And may I ask what's your excuse for being so agressive? I *did* backup my DB. I did not say PM was expensive. However it is a paying client in a world of many good free ones, so I think I'm entitled at least to reliability, not to say proper tech support. I used PM for years without problems and gladly paid upgrades among other reasons to support diversity on my platform of choice. It also used to be quite good software. However I think something has stopped evolving, and it has become unstable and unreliable. I can assure you I tried everything, including the options you suggested. My system is thoroughly checked and presents no problem. I also know precisely what - in my case at least - hangs PM : it cannot properly deal with certain chinese Unicode ranges, and the fallback mechanism for unfound characters seems badly implemented. I have definitely tested this, and also checked that other software (including browsers or mail clients like Thunderbird) do not react in the same manner. I'm also very dissatisfied with CTM's support in this case: At first they pretended that they could find nothing in the crash log I sent them, however when I pointed to the problem and insisted, they suddenly could see in it that it was related to some font problem, and quite easily suggested that I have some corrupt fonts. And when I took the time to explain and prove my point, they just disappeared from the radar screen - mute, nothing, not even the acknowledgment of having received the message, which could be automatic. The result: however much I tried, CTM has made me look into other mail clients, since the PM crashes definitely corrupt the DB making it totally unreliable, and therefore unusable. I certainly hope Robert Snyder has a backup and wish him good luck in his ordeal. Amnon. Mikael Byström wrote: At least you can try PowerMail Salvage and see if it finds your messages before you have to pay. If you think it's expensive, then you don't value your messages. What's your excuse for not having backed up your DB? PowerMail is not expensive, so you can't reasonably demand it should be included in the package we are paying for. Of course that would be nice, but I wouldn't expect it at the price level of PM. It's possible there are some problems with 10.4.x and PM 5.2.2, but I seriously doubt DB errors under Panther is a common experience. Have you also deleted the PowerMail pref files and the index? Have you verified your system regarding file system errors and permission settings? PM 5.2.2 Swedish | OS X 10.3.9 | Powerbook G4/400Mhz | 1GB RAM | 30GB HD
Re: Database Rebuild FAILED
Amnon Yaish said: The situation described by Robert (and which I experimented all too often) should'nt ever happen, and if it happens, the tool to *try* and retrieve some of the messages in the corrupt database should be included in the package we are paying for, not paid (rather expensive) to a third party developer. Especially since the problem is evidently with PowerMail. At least you can try PowerMail Salvage and see if it finds your messages before you have to pay. If you think it's expensive, then you don't value your messages. What's your excuse for not having backed up your DB? PowerMail is not expensive, so you can't reasonably demand it should be included in the package we are paying for. Of course that would be nice, but I wouldn't expect it at the price level of PM. It's possible there are some problems with 10.4.x and PM 5.2.2, but I seriously doubt DB errors under Panther is a common experience. Have you also deleted the PowerMail pref files and the index? Have you verified your system regarding file system errors and permission settings? PM 5.2.2 Swedish | OS X 10.3.9 | Powerbook G4/400Mhz | 1GB RAM | 30GB HD
Re: Database Rebuild FAILED
Agreed. But my experience differs. I've never had an unfixable db error with PM and I've been using it since v3 -- Andy Fragen On Mon, Jan 23, 2006, Amnon Yaish said: The situation described by Robert (and which I experimented all too often) should'nt ever happen, and if it happens, the tool to *try* and retrieve some of the messages in the corrupt database should be included in the package we are paying for, not paid (rather expensive) to a third party developer. Especially since the problem is evidently with PowerMail. Amnon. Jean-Michel Therond wrote: Le 23 janv. 06 à 19:41, Robert Snyder a écrit : Hi, My database was nearing 2GB, so I tried to compress it, but that tailed with a database error. So I tried to perform a low level database rebuild, but that failed. HELP. This has all of my important data in it--licenses, serial numbers, job histories, etc. Is there any way to extract data from the database? How can I get PowerMail to launch again--it keeps failing with a database error when I try to launch it. As the low level rebuild doen't do the job, you may consider trying a third party software such as PowerMail Salvage. http://www.zygoat.ca/products/pmsalvage/ HTH, Jean-Michel
Re: Database Rebuild FAILED
Le 23 janv. 06 à 19:41, Robert Snyder a écrit : Hi, My database was nearing 2GB, so I tried to compress it, but that tailed with a database error. So I tried to perform a low level database rebuild, but that failed. HELP. This has all of my important data in it--licenses, serial numbers, job histories, etc. Is there any way to extract data from the database? How can I get PowerMail to launch again--it keeps failing with a database error when I try to launch it. As the low level rebuild doen't do the job, you may consider trying a third party software such as PowerMail Salvage. http://www.zygoat.ca/products/pmsalvage/ HTH, Jean-Michel
Database Rebuild FAILED
Hi, My database was nearing 2GB, so I tried to compress it, but that tailed with a database error. So I tried to perform a low level database rebuild, but that failed. HELP. This has all of my important data in it--licenses, serial numbers, job histories, etc. Is there any way to extract data from the database? How can I get PowerMail to launch again--it keeps failing with a database error when I try to launch it. Robert Snyder
