After copying a production database to an acceptance database, depending on the script used after restoring the database, it is possible to overwrite the Scheduling Service settings with wrong keys / settings.
What is a failsafe way to correct your Scheduling Service if this happens?
Right now, my Scheduling Service is disconnected (according to the application, not sure whether this is the case on the server) and every attempt at reconnecting to the Scheduling Service gives me the message “Error while registering to the scheduling service: You are not authorized”. What can I do to fix this?
There is a way to force re-pairing.
Simply remove the false information (all 3 certificates). Then click on the Generate key pairs button again to create new private and public keys for yourself (or enter the ones you have backed up). Click the “Get certificate from scheduling service” button to get the correct certificate. Then hit save and re-pair your application.
I have tried this already, without success. I am able to get a new certificate, but after saving the Pair button still gives me the “Unauthorized” message.
I’m running to a similar problem. This conversation starts with a lot of prior knowledge on how and where to generate the keys. Is there any step by step documentation available to get to point of the buttons mentioned in this thread?
