How can I retire a Smartconnect instance on version 20 .18
We only use SC on two database servers, prod and test, yet we are locked out. It must have been counting DNS alias changes over the years as instances. I found registered instances were “sql”, “sql\db”, and “sqldb”, and sql3 (test/dev). Three of these are the same instance using different names to point to the database.
The screens in the documentation, running eOne.SmartConnect.Config to retire an instance, do not look like our screens. We’re on version 188.8.131.52 of SmartConnect.
If you would like to submit an answer or comment, please sign in to the eOne portal.