• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Microsoft JET Database Engine Unrecognized database format psa.mdb

J

jacko@

Guest
When going to the Plesk login page the following error shows:

ERROR: PleskMainDBException
<b>Source:</b> Microsoft JET Database Engine<br/><b>Description:</b> Unrecognized database format 'C:\Program Files\SWsoft\Plesk\admin\db\psa.mdb'.

0: plib\common_func.php3:666
reconnect()
1: plib\common_func.php3:614
db_connect()
2: auto_prepend\auth.php3:80

Anyone seen this before?

Thanks,
jacko
 
Did you perform any actions on Plesk database before such error occurred?
Probably Database got corrupted. Try to run Plesk reconfigurator > Repair installation;
you can also try to change Plesk database provider from Jet to MySQL:
http://kb.odin.com/en/5532
 
Did you perform any actions on Plesk database before such error occurred?
Probably Database got corrupted. Try to run Plesk reconfigurator > Repair installation;
you can also try to change Plesk database provider from Jet to MySQL:
http://kb.odin.com/en/5532

Thanks for your reply. No manual changes were made to the plesk mdb file.

In the end we were able to fix this by downloading it and loading it in ms access and fixing the tables and re-uploading it. Plesk then started fine again.

Your suggestion sounds good though, will try that next time.

Thanks,
jacko
 
Back
Top