Facebook
TwitterI just migrated a web application to a new web host and the new host threw the error. Is there anything that I can do from the PLESK Control Panel or code that I can add to the web.config file that will tell the local machine where to look for the OLEDB driver. Or does the physical hardware need to be updated with the OLEDB capability? Your help is greatly appreciated.
-
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.
Resolved Microsoft Access OLEDB "The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine"
- Thread starter Ross1492
- Start date
