I'm running MT v. 2.62.

As of a couple weeks ago, users have been complaining that they cannot login. I've tried the resetauth.cgi script, but it can't find any of the users I know are entered in the system.

It says:


Is there a file that could've been improperly CHMODDED or become corrupt that can be fixed without having to wipe and re-load MT. We have alot of entrys in the system as well as well-done and amazing-looking templates?

Thanks for your help!
-Matt

You can see if MT Medic can find any authors, but it sounds like your database may have suffered some corruption, or perhaps your host upgraded Perl on your server? Are you using Berkeley?

Thanks girlie, I'll try MT Medic.

As far as perl being upgraged our host has recently upgraded from 5.6.1 to 5.8.3; nobody on their support forum has posted anything about problems with MT.

Oh, and we are using Berkley DB.

If they upgraded the version of DB_File (Berkeley) along with it, that could definitely account for the problem you're facing.

I was unable to do anything with MT Medic. I'll check with them and see if they did upgrade DB_File. If that's the case, is there anything I can do?

Unfortunately, database corruption with Berkeley DB is very difficult if not impossible to recover from

Do you have any exports of your entries? If you do, you can re-install MT and import the entries and that will save most of your site. If not and you're still unable to login to do an export, there's a script that attempts to extract the entry information from your HTML pages and repopulate the database with that but otherwise you would have to recreate the posts manually

This is a bit different from database corruption, since it's more likely to be about having a new version of Berkeley installed now on your server.

Although you may still be looking at a fresh start, you should first see if the last section of the Troubleshooting Manual on I changed hosts and now I can't login to Movable Type is an option for you. Changing servers is the equivalent of changing hosts in this case, and if you can upgrade the files as noted in that section, it will save you the grief of starting over.

My bad. I misread what the problem was. I guess I'm too used to Berkeley DB problems being corruption.