• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Fatal error: Cannot redeclare class pleskexception

E

erolmercan

Guest
Fatal error: Cannot redeclare class pleskexception in C:\..\Plesk\admin\plib\PleskException.php on line 76

Sometimes, our panel stops with this error. There is no solution I've found. Everybody says PrivateTemp folder but why I am doing that instructions and restarting my plesk panel? If there is a bug where is the patch?

We are using the latest version and all the plesk 8.2 pathces installed on our Windows 2003 Std. Server. We have a 300-domain license with an additional language support.

We changed the Plesk web server from apache to IIS 1 or 2 months ago. There wasn't any error but I think this fatal error is being originated from IIS. If it is not, what is the problem?

Thanks.
 
SWsoft developers are working on that issue already. The fix should be included in the further release.
 
As far as i remember this happens when someone upgrade his Plesk from old version 7.5 to a new one 8.x. Old Plesk has only Apache engine, newest Plesk had Apache and IIS. So those problems comes from there.
 
I meant "when will it be fixed".

I'm running a clean install of plesk 8.2 on a clean install of Win Server 2003 R2. The server has only been live about a month. The fix recommended in this post has had no effect.
 
Try the 8.3 and 8.3.0.1 updates. I have not experienced the error again since I isntalled those, BUT it may not be a direct result of those changes (I've made several other changes, too).
 
Hi Sergius

could you address this if its going really to be solved if 8.3 updates are planend also i can see already so many other issues with 8.3 updates in forums.

Try the 8.3 and 8.3.0.1 updates. I have not experienced the error again since I isntalled those, BUT it may not be a direct result of those changes (I've made several other changes, too).
 
Hi Sergius

could you address this if its going really to be solved if 8.3 updates are planend also i can see already so many other issues with 8.3 updates in forums.

Hello funky123,

We are not going to release more updates for 8.3 - 8.3.0.1 fixes most of critical issues.
 
Back
Top