To solve the issue and to insure that this object isn't related to any Authentication Scheme anymore, you need to check the object validity through XPSExplorer:
- Open XPSExplorer tool from a command line on your Policy Server.
- In the "Main menu", type the option number for SAMLv2IdP (could be number 144) and hit enter
- Type S and hit enter to show the current objects of this type. You should see the one named as shown in the error (i.e. "myobject")
- Type the corresponding number for the object (located at the beginning of the entry), and hit enter.
- On the header displayed, you will see a "Parent" field, and should reference the Authentication Scheme where this configuration was generated.
- If you type L and hit enter, it should show you that Authentication Scheme object.
- Check also the values for SPID and KEY_IdPID, and check if those are still existing and/or valid as follows.
- Return to the Main Menu (by typing Q and hitting enter until you reach there) and check SPBase objects to find the SPID referenced:
- Type the value for SPbase* and hit enter
- Type S and hit enter. You should find a partnership matching the SPID you have found before.
- Repeat the same steps for IdPbase* menu, for the KEY_IdPID value.
If any of those IDs are not matching anymore any object, or the authentication scheme is empty or not existing anymore, you may want to delete this SAML Config object as it could be an old configuration which has not been removed properly.