We recently cloned over the instance that I am trying to setup this environment record on. This is the controller instance, and I am attempting to setup the environment record for this instance. When I attempt to validate the record, I get a "Controller is not valid" error. This only started happening after the clone.
Just wondering if anyone else has experience this type of behavior after a clone and if there are any known solutions.
I ended up just deleting the controller environment record and re-creating it. That solved the issue. This is not the first time I've encountered this though so might need some input from ServiceNow themselves.
I have verified the password and everything is correct. I am getting the error when validating the environment record. I get it on all environments in the pipeline, even on the controller itself, oddly enough.
I ran into the same issue and found out that we need to first validate the environment without making it controller. Once successfully validated, we can mark it as controller and validate it again.
