• 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.

PMM Conflict Error. Can't figure out what this is

WesleyG

New Pleskian
Hi everybody! First off, thanks in advance for helping however you can. I received this conflict which is causing Plesk Restore to error out when trying to run. The error is:

<conflict id="0" guid="b72a34858def2872ec2824475b3ca867">
<type>
<timing>
<reason-description plesk-owner-guid="" backup-owner-guid="">
<plesk-object-identifier>
<type>admin</type>
<database-id>1</database-id>
<guid>D990FA3D-9998-4AC4-854B-1EAF8B4EE00F</guid>
</plesk-object-identifier>
</reason-description>
<resolve-options>
<option name="do-not-restore"/>
<option name="proceed-with-current"/>
<option name="overwrite"/>
</resolve-options>
</timing>
</type>
<conflicting-objects>
<node name="admin">
<attributes>
<attribute name="guid" value="D990FA3D-9998-4AC4-854B-1EAF8B4EE00F"/>
</attributes>
</node>
</conflicting-objects>
<overview>
<object>
<message>backup__restore__conflict_object_name</message>
<name/>
<type>backup__restore__object_plesk_admin</type>
<reasons>
<reason>
<message>backup__restore__conflict_timing_reason_noname_object_already_exists</message>
<param name="type" value="backup__restore__object_plesk_admin"/>
</reason>
</reasons>
</object>
</overview>
</conflict>

Any ideas?

Thanks,
Wes
 
conflicts_description.

We figured it out though. The client bought the hosting company from somebody else and when hen did, the previous owner created a new admin account and deleted the original one from the psa database.

When restoring the backup, the admin account that existed was not the original, so Plesk so it as trying to create a new one named admin and came to a hault.

I wouldn't call this a bug as much as I would call it a weird scenario.
 
Back
Top