1. I go to any of my weblogs
2. I start a new entry
3. I enter the info into the fields
4. I hit "save"
5. It looks like it's rebuilding the new entry, but then I get an Internal Server Error

The weird thing, though, is that despite the error the entry appears
both on the site and in the database.

So when I try to delete the entry, this is what happens...

1. I view all entries and check the one I want to delete
2. I hit "delete" button
3. I get a message up top that says it's been deleted from the database,
but I have to rebuild in order to remove it from the site, so I hit
"Rebuild My Site"
4. I select "Rebuild All Files" and hit "Rebuild"
5. It looks like it's rebuilding, but then I get the same Internal
Server Error

The entry is not deleted from the site unless I select "Rebuild Indexes
Only" and in that case everything works fine.

Setup details: MT 3.2, freshly upgraded from 2.?. Using Berkeley DB.

Please help! I've seen a lot of comments about 500 errors but nothing this detailed. I'm not sure where to begin.

Thanks
Groutscott

Are you on a Windows, Unix or Mac server? Have you always gotten these random errors?

500 errors can be caused by a lot of things (unfortunately). This Knowledge Base article will give you a place to start your research.

It's running on a Unix server. These problems never existed until I did the upgrade. I followed the upgrade instructions VERY carefully. What I thought was odd was that the instructions told me to overwrite the preexisting site. Why not delete the old one first? Now it's a mix. I wonder if I were to delete all the files, and do a fresh install rather than an upgrade, might that change things? Is it possible to do that and retain my old data? If so, then what should I NOT delete? (Other than the db files)

Another thing that seemed odd was that all of the db files from the previous install were located in the root directory for the blog. Is this where they should be?

Make sure you back up mt-config.cgi and your database files. It's not usually suggested to have your Berkeley files in your web root. A lot of people put them in cgi-bin.

Also, once you get upgraded, if you have the option, I would recommend upgrading to MySQL. It's a more stable solution than Berkeley.
http://www.sixapart.com/movabletype/kb/dat...ase_conver.html

Right. I'm doing this upgrade for a client; the db file were in the root when I was handed the project.



I'd be willing to do this, and will look into it, but I'm not convinced that it would address the existing problem. Any suggestions on how can I hunt down this internal server error? When I performed the upgrade, a quick once-over had me thinking that everything was working fine.

Just a thought.
When I upgraded my own installation I started to get 500 errors.
We boosted the memory limit on the webserver, problem solved.
One possible solution worth checking into,

I wish I had that option, but it's not on my server, and besides it doesn't answer the question of why it's not working ... I was hoping someone would point me in the right direction to fix or even diagnose this; it's frustrating because I was very careful to follow the instructions exactly. Now it's taking me far more time than I had ever intended or charged for, and I'm thinking that I should maybe steer clear of mt in the future and recommend Wordpress to my clients instead.

Any real suggestions on how to diagnose this problem?

Whoever has access to the server's error logs needs to take a look at them, preferably right after generating the 500 error. It may tell what the problem is, if set up properly.

If it's a memory issue, the only way to fix it that I know of will be to have the host raise the allowed memory cap.