• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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