• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

After applying ASP.NET Setting - removing providername on ConnectionString.

A

Andrei C

Regular Pleskian
Dear Support,

Why on ASP.NET Setting, I don't see providername for my ConnectionString?
After applying new ASP.NET Setting, Plesk Panel removing providername on ConnectionString (web.config) -> there are errors like "Unable to find the requested .Net Framework Data Provider" occurred on sites.
Could you fix this?
 
You must log in or register to reply here.

Similar threads

K
Resolved Send detailed error to client-side for 500 errors with ASP.NET
Replies
1
Views
12K
kelmore5
K
K
Question Error applying firewall configuration despite of changing almost nothing
Replies
2
Views
2K
Kaspar
K
Z
Issue Firewall stopped working after update to Plesk Obsidian v18.0.77 on Debian 11.11
Replies
12
Views
6K
Kaspar
K
T
Forwarded to devs FTPS remote backups fail after upgrade to Plesk 18.0.80 due to TLS session not being resumed on the FTP data connection (pmm-ras regression)
Replies
6
Views
2K
Hangover2
Hangover2
F
Issue Plesk Backup Suddenly Fails on SSHFS: pmm-ras Returns EPERM After Years of Working
Replies
6
Views
2K
FloLa
F
Back
Top