It looks like the Adaxes service that was deleted was the schema master role owner of the AD LDS instance that your Adaxes services use as backend. Since it was not uninstalled properly, the role has not been transferred to another Adaxes service.
To remedy the issue, you need to transfer the schema master role manually. For information on how to do this, see the following article by Microsot: http://technet.microsoft.com/en-us/libr ... 10%29.aspx.
Important Notice: since only Adaxes default service administrator can manage the settings of the AD LDS instance used as Adaxes backend, you need to launch the MMC console with credentials of Adaxes default service administrator (the user that you specified when installing Adaxes).
On the 1st step of the article, you'll need to connect to the AD LDS instance used by Adaxes. For information no how to connect, see the following article: http://technet.microsoft.com/en-us/libr ... 10%29.aspx. On Step 10, you need to supply the name and the port of the AD LDS instance used by Adaxes. To find out the name and the port:
- Launch Adaxes Administration Console.
- In the Console Tree, right-click one of your existing Adaxes services and click Properties.
- The DNS name of your Adaxes service and the port used by Adaxes backend will be displayed on the General tab. You need to supply them when connecting to the backend with the Active Directory Schema snap-in.