• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue [PPPM-7412] Cannot backup domain - No objects dumped because of errors

DylanJ

New Pleskian
I've set up a new Windows 2012 VPS. It came pre-installed with Plesk 11.5 so I ran the upgrade wizard for Onyx 17.5.3 and all looked ok. However, the backup functionality for websites does not work. I keep receiving the following errors:

Error: server "server"
No objects dumped because of errors
Warning: server "server"
Cannot backup domain 'domain.com' '[Method not found: 'System.String psadumpagent.CommonEnv.GetTempDirName()'.]'

How can I resolve this? I have tried to repair Plesk using the repair utility Plesk Repair Utility but this doesn't appear to work.
 
Yes, it is known bug PPPM-7412 which will be fixed in one of Plesk updates.
I would suggest you contact Plesk Support Team, they will apply temp custom fix for your server if it is critical for you.
 
According to the changelog PPPM-7412 has been fixed but the problem persists for me on the latest version so this must be a different issue.
 
According to the changelog PPPM-7412 has been fixed but the problem persists for me on the latest version so this must be a different issue.
In this case I can only recommend creating a request to support team to do the in-depth investigation to find the reason and to fix it. Please create a ticket to support at Plesk Help Center
 
Back
Top